From 0 to product, a decision driven path to success
•
0 likes•27 views
Every day we see dozens of startups skyrocketing or raising incredible amounts of money to make their dreams come true. At the same time, hundreds fail, but that’s not much covered in the news. There are plenty of reasons why ones succeed and others fail, but most of the times, it’s only about the execution. In this presentation, Alvaro Moya, former CTO @ i-surance, will explain how they hired a top team and built an awesome product from scratch in 18 months, explained through the decisions they took. After the session, we will be able to take the right decisions in the right order, improving the execution and the probability to succeed
Recommended
More Related Content
Similar to From 0 to product, a decision driven path to success
Similar to From 0 to product, a decision driven path to success (20)
Recently uploaded
Recently uploaded (20)
From 0 to product, a decision driven path to success
- 1. From 0 to product: a decision-driven path to success Alvaro Moya Tech consultant, CTO
- 2. Starting point 1. B2B2C insurtech running, +3M customers in 12 different countries 2. No internal IT knowledge 3. No IT team 4. No code 5. No documentation 6. Our assets: an *.sql dump
- 3. The challenge Team Product Constraints
- 4. Planning Hiring Getting knowledge Defining architecture MVP Migration Growing the team Product refinement Jan 2018 Dec 2018 Jun 2019
- 5. Hiring
- 6. Agency or not? Agency 1. Deadlines 2. No IT recruiters 3. No brand recognition Always leverage your network!
- 7. Which agency? We worked with Robert Walters 1. Proven track record 2. How they treat the position 3. How they treat candidates
- 8. PHP + reactJS 1. Talent availability 2. Personal knowledge Programming language?
- 9. Junior vs Senior Senior 1. Experience designing and building from scratch 2. Leading teams
- 10. Local 1. Complex project 2. Long-term vision, evolving roles 3. Communication issues Local vs Offshore
- 12. Who to ask? Users Managers Outsurced agency
- 13. What to ask? 1. 3 main tasks you perform 2. 3 biggest pains 3. One wish 4. Content created, and where to find it
- 14. What to ask? 1. 3 main tasks you perform 2. 3 biggest pains 3. One wish 4. Content created, and where to find it
- 15. Tools to collect knowledge X-Mind Draw.io Confluence Office365
- 16. Tools to collect knowledge X-Mind Draw.io Confluence Office365
- 18. What to build? 1. What you need a. Goals now b. Goals in 3 years 2. What you can a. Identify boundaries b. Prioritise
- 19. How to build it? Lean mindset, iterative improvement Focus on top priorities and pains
- 20. How to build it?
- 21. Technical approach? Define product goals: Scalable, maintainable, robust, modular, tech independent AWS ecosystem: ECS, RDS, S3... Microsevices, PHP 7, AMQP, TDD, DDD Don't reinvent the wheel: Auth0, Stripe, Bootstrap, React table, api platform ...
- 22. MVP
- 23. In-house vs Outsource Hybrid 1. In house team put focus on core product 2. Outsourcing: a. Non-core functions b. One-time jobs c. Low value tasks d. Peaks of workload
- 25. Migration
- 26. What to onboard first? Old vs new New content first 1. Don't duplicate efforts 2. Less volume = Less risk BUT we should have migrated after that validation
- 27. How to do the migration? 1. Define stages By partner 2. Define steps First do them manually, then document and automate them 3. Outsource repetitive process Choosing the right partner is key
- 28. Growing the team
- 29. Which roles to hire next? Product Owner (PO) IT Support Quality Assurance (QA) Backend
- 30. How to organize a bigger team? Squads Split by scope PO QA 2 Backend 1 Frontend Team Lead (Backend) 2 Backend 1 Frontend Team Lead (Backend) Features Programs
- 32. Business Intelligence tool Sisense 1. Great integration support and tutorials 2. Easy to prepare and update powerful dashboards 3. Easy to setup roles, permissions and data scope 4. Expensive and resources-intensive
- 33. What to do first? Prioritise! 1. Train the whole company 2. Involve all the relevant stakeholders 3. Set clear communication guidelines 4. Learn to say No
- 34. Conclusions
- 35. Conclusions CTO role is alive Empower your team Focus on value Prioritisation is a global effort Sorry but “It depends”
- 36. Jonathan Blow - preventing collapse of civilizations bit.ly/prevcollapse Thanks to @javisantana
- 38. Q&A Psst! We are hiring the best @ wefoxgroup.com/careers/
- 39. 2 minutes to give back? bit.ly/CTOsurvey2020