Lessons learned from building a product team
When we started building Pilot I had close to zero experience running a product team. We’ve built a lot of products for our customers, but our strengths were in managing the design and engineering part of the process. We had a lot to learn.
Matt Drozdzynski
PEO vs EOR: What are the Differences and Which is Right for You?
Read Story →A Guide to the Best Remote Work Tools for HR Teams
Read Story →How to Manage a Remote Team: 6 Ideas for Better Remote Work
Read Story →We started with a process closely modelled after [Intercom’s](https://blog.intercom.io/how-we-build-software/). They had a team six times as large, but what they wrote about rang true. So we adopted it as is.Five months later we had to scrap everything and start from scratch. Our product was nowhere near done. The team was consistently underperforming. Everyone was frustrated.So what went wrong? For one, getting from nothing to a minimum viable product takes different skills and processes than developing an existing product. And two, until you understand the jobs to be done in your team, it’s unlikely that any process will work.If you’re struggling with the same problem, here’s what worked for us.