Today, I had a conversation with another product manager about the experience of being the first PM. While I wasn't the inaugural PM at efood (that was Jason), I did get involved with the product at an early stage. At Instacar, I was the first hands-on PM consultant.
Every popular app or online service we use today, regardless of its size, started with a small team of engineers and a first PM. Many companies have CEOs who built the initial product from scratch, as was the case with efood. Nevertheless, the first PM was always close to this stage.
Moving from zero to one is one of the most challenging stages in product development. The development uncertainty, the volume and complexity of decisions, and the absence of structure can make this journey quite a roller-coaster ride.
In an environment where there is no established rulebook, the first PM must operate without the advantage of set documentation and procedures. Their approach is more practical and agile, always ready to adapt and pivot as required.
The first PMs of successful products are invaluable sources of insights, wisdom, and lessons.
Their experiences, including both failures and successes, form a solid foundation of knowledge that can guide future PMs and other professionals in the field.
Therefore, it is beneficial to seek them out, engage with them, and ask them questions. You might gain insights that could help your product become the next big thing.
It's all about managing the chaos, thriving in uncertainty, and having the foresight to build from nothing to something.
Relevant posts:
![[Guide] PM Growth assessment example](/_next/image?url=https%3A%2F%2Fassets.super.so%2F99cb30f3-9f77-4c1d-ac55-11edd83a4bb1%2Fimages%2F3b5fe93c-649c-4717-8ea6-54ce3e4e6ea0.jpg&w=3840&q=80)