A truly product-driven culture involves everyone, not just designers and product managers. At Amo and Zenly, a deep connection between all teams was crucial, with many innovative product ideas originating from unexpected places like the backend engineering team, who were deeply involved in shaping the user experience.

Related Insights

Instead of a traditional product roadmap, give engineers ownership of a broad "problem space." This high-agency model pushes them to get "forward deployed" with customers, uncover real needs, and build solutions directly. This ensures product development is tied to actual pain points and fosters a strong sense of ownership.

Tock rejected traditional focus groups and instead embedded its software engineers directly into restaurants to work shifts as hosts. This forced immersion gave the engineering team firsthand experience with the end-user's pain points, leading to a far more intuitive and effective product than surveys could produce.

The V0 team operates with minimal product management oversight, empowering product-minded engineers (often ex-founders) to make 95% of product decisions directly. This sacrifices potentially "perfect" choices for a dramatic increase in development velocity.

In an AI-driven world, product teams should operate like a busy shipyard: seemingly chaotic but underpinned by high skill and careful communication. This cross-functional pod (PM, Eng, Design, Research, Data, Marketing) collaborates constantly, breaking down traditional processes like standups.

The common product development process is a sequential handoff model. A better approach is a "jazz band" model where cross-functional teams collaborate harmoniously from the start. This fosters creativity and reduces rework by including engineers in early ideation, rather than treating them as a final step.

The best products are built when engineering, product, and design have overlapping responsibilities. This intentional blurring of roles and 'stepping on each other's toes in a good way' fosters holistic product thinking and avoids the fragmented execution common in siloed organizations.

Siphoning off cutting-edge work to a separate 'labs' group demotivates core teams and disconnects innovation from those who own the customer. Instead, foster 'innovating teams' by making innovation the responsibility of the core product teams themselves.

ElevenLabs eliminates the traditional Product Manager role. They hire "product engineers" who own the entire development loop from ideation to shipping and analysis. Growth leads (often ex-PMs) then partner with engineering leads on GTM and acquisition, creating a faster, more accountable structure.

Flexport's internal hackathons are now its primary source for AI-driven innovation. With 90% of projects using LLMs, these events generate real product features and influence the company's roadmap. This demonstrates a powerful bottom-up approach where the most valuable ideas come from engineers closest to the problems.

Elf's CEO hosts product review meetings every two weeks that are open to all employees, regardless of role. He actively monitors the meeting's chat for feedback, believing the best ideas can come from anyone, like an inventory planner with a contrarian view on a new product.

Amo's Best Product Ideas Often Originated From Backend Engineers | RiffOn