Thomas Vuchot nous explique l’organisation produit chez Qonto : “Comment passer d’un seul PM à une organisation produit de 4 Product Managers et 3 designers en l’espace de 6 mois ?” Ne manquez plus aucun RDV du Meetup LPCx https://www.meetup.com/fr-FR/laproductconf-x/

1. Scaling your product team in
a fast growing company
LPCx

2. You are probably familiar with this…
The SME banking nightmare

3. What is Qonto?
Easy business banking
Core banking features
to be a real substitute
(e.g. IBAN, cards,
transfers, debit)
Bookkeeping
(e.g. integration with
accounting, receipts
scanner and VAT
extract.)
Financial toolkit
(e.g. analytical codes,
cashflow forecast, team
budgeting)
Customer support
“neo-bankers” answering
to any question within 15
minutes
Faster
100% online / mobile,
signup in 5 minutes
Transparent
Banking fees down by
50%, with clear pricing
Collaborative
Natively designed for
teams
Simpler
Mobile, real-time
notifications
Smoother
UX/UI focused on B2B,
for self-servicex
Easy
banking
for SMEs=
.

4. Product was a cornerstone from Day 1
Timeline
🏁
Qonto, Day 1
APRIL MAY JUNE JUL. AUG. SEPT. OCT. NOV. DEC. JAN. FEB. MAR. APRIL MAY JUNE JUL. AUG. SEPT. OCT. NOV. DEC. JAN. FEB. MAR. APRIL
🕵🕵♂️
First user
tests
🎉
Qonto is live!
👨👩👧👦
5k subscribed
companies
👨👩👧👦👨👩👧
10k subscribed
companies
🙌
Beta
💸
Raised
10.000.000€
👨💻👨💻
1 PM
1 UI/UX
👨👩👧👦👨👩👧
4 PM
3 UI/UX
💸
Raised
1.600.000€
2016 2017 2018
1 founder full time
on product during 1
year

5. 4 key success factors
1. Hire super star talents
2. Build your product based on demand… but most importantly based on
your product vision and the value you provide
3. Make the process right and automate it
4. Measure impact
Or how to build a loved product and scale a product team

6. 1. Building a team
- Invest in multiple channels to attract talents (e.g. Dribbble)
- Prepare your own exercices for on-site case studies
- Meet a lot of potential candidates… even when you are not hiring « now »
- Invest in an efficient Applicant Tracking System to assess candidates
rapidly and fairly
- Make your on-boarding super useful and engaging
- Build a documentation with all your specs from day 1 to spread the
knowledge fast
What worked for us could work for you…

7. 2. How to build the right things
A set of guidelines for making decisions
What we believe in
This is based on our opinion rather than
research, in particular the opinion of our
product leadership team. This includes
trends we see and ideas we have.
Quantitative data
Product metrics gathered in a BI tool +
product success metrics .
Solicited/Unsolicited feedback
Studies by our product team and
conversations between sales team and
customers + Unsolicited feedback from
customers (Zendesk and landing page)
Value (ROI)
Based on how the feature will generate
direct or indirect revenues

8. 2. Gathering insights
The way we build our product vision evolves over time
APRIL MAY JUNE JUL. AUG. SEPT. OCT. NOV. DEC. JAN. FEB. MAR. APRIL MAY JUNE JUL. AUG. SEPT. OCT. NOV. DEC. JAN. FEB. MAR. APRIL
2016 2017 2018
« old-school » interviews with
potential users BUT mostly gut-
feeling
Systematically logging every insight
coming from our users and Qonto
team
Systematically qualifying all
features to match our vision and
define our roadmap

9. Qualify features with many dimensions
Step #1
What theme does it
belong to?
Step #2
Why should we build
this feature?
Step #3
How complex is it to
build?
Step #4
Who is going to use
this feature?
Step #5
Will it generate
revenue?
💳 Banking Adoption 👕 Freelancers Low
📝 Onboarding Retention 👕👕 Small teams Medium
🕵 Accounting Internal efficiency 👕👕👕 Medium teams High
📈 Finance & reporting
Security &
compliance 👕👕👕👕 Large teams No brainer
… Shame 🛎 👕👕👕👕👕 …
…
2. Translate insights into features
…

10. 2. Translate insights into features
Qualify features with many dimensions

11. 3. Make the process right
Define each one’s scope precisely
📚 Research
Understand the problem we try to solve,
JTBD
✍️ Functional specs writing
Describe how we plan to solve the problem as
accurately as possible
🕵🕵 Design brief
Ensure designers have a perfect understanding to
design the best experience
💡 Specs iteration
Until we reach a consistent solution (functional -
design - technical)
🔧 Development follow-up
Answer to remaining questions from tech team and
adjust specs if required
🕵 QA & Release
Test the feature to make sure it meets our
expectations and monitor the release
📢 Communication
Notify customers, write release note, communicate
internally
🔄 Measure and iterate
Make sure the feature is used and continuously
improve it

12. 3. Make the process right
Find the right tools and use them rigorously
🕵 Roadmap and to-dos
Our roadmap is open to everyone internally
📚 Documentation
We document everything to ease onboardings and keep a
clean knowledge base
✍️ Specs
We write very detailed and actionable specs
🕵 Continuous delivery
We merge code several times a day

13. 3. Make the process right
Find the right tools and use them rigorously

14. 3. Make the process right
Stick to your rituals
Formal rituals Informal events
Daily stand-up
With tech team
Specs challenge
Between PMs
Weekly product meeting
With PMs, PDs, founder
QA
On large features
Retros

15. Try Qonto for free during 3 months with this voucher :
THOM3M