We scan new podcasts and send you the top 5 insights daily.
While building one-off features for large clients is risky, their requests can be a leading indicator for the market. Lattice CEO Jack Altman notes that like Shopify at Stripe, these clients can push your product in directions that prove valuable for many future customers, making it a strategic bet.
Faced with endless potential use cases, Datycs' CEO reveals their prioritization strategy: they wait for a new feature request, such as for social determinants of health, to mature and be echoed by two or three other customers before investing significant resources in building it.
Nikesh Arora warns that founders often solicit feedback from large enterprise customers too early. These customers ask for "speeds and feeds," not a holistic product, leading founders to build features instead of a complete solution. The best founders first build a product based on their own end-to-end vision.
Don't just collect feedback from all users equally. Identify and listen closely to the few "visionary users" who intuitively grasp what's next. Their detailed feedback can serve as a powerful validation and even a blueprint for your long-term product strategy.
Focusing on individual enterprise client needs creates conflicting workflows that hinder scalability. A successful transition involves moving to a user research-driven approach, using data to justify a standardized product direction that serves the broader market, not just a few powerful clients.
When one customer represents a huge portion of your revenue, your product roadmap is at risk of "slow drift." Your team, eager to please, starts building features the customer "might like," not what they explicitly requested or what your broader market needs, subtly derailing your product strategy.
Product teams often fear showing prototypes because strong customer demand creates pressure. This mindset is flawed. Having customers eager to buy an unbuilt feature is a high-quality signal that validates your roadmap and is the best problem a product manager can have.
Jack Dorsey argues that rigid, pre-planned roadmaps are obsolete. In an AI-driven model, the product roadmap should be generated in real-time based on customer queries and needs, allowing the company to build and compose features on demand.
Avoid the trap of building features for a single customer, which grinds products to a halt. When a high-stakes customer makes a specific request, the goal is to reframe and build it in a way that benefits the entire customer base, turning a one-off demand into a strategic win-win.
Your audience will dictate your product roadmap if you listen. Porterfield's evolution was a direct response to customer feedback. They finished her webinar course and asked what to sell. They finished her product course and asked how to market it. The path to her flagship product was paved with their questions.
Customers often suggest solutions (e.g., "add this feature") based on their limited understanding of what's possible. A founder's job is to look past the specific request and identify the core problem or desired outcome. Building exactly what the customer asks for verbatim is a mistake; solving their underlying goal is the key.