The Strategic Value of Ignoring Your Customers

Most product teams treat customer feedback as a mandatory roadmap. Jason Fried and David Heinemeier Hansson argue this is a mistake that traps companies in a cycle of reactive, low-quality development. By treating every request as a requirement, teams trade long-term product integrity for the short-term comfort of doing something. This conversation shows that the value of feedback is not the specific feature requested, but the underlying pain point it reveals. For leaders, the advantage lies in having the courage to ignore the noise, resist the urge to make vague promises, and wait until a solution is ready. Building a durable product requires moving from reactive patching to intentional design, a path that creates a long-term competitive advantage.

The Illusion of Agreement

When teams treat a feature request as a binding contract, they fall into an illusion of agreement. A customer asks for a calendar, and the team builds one. Because the team and the customer do not share the same internal vision, the resulting feature often fails to solve the user's actual problem.

Very often, you are going to get a feature that is in the vicinity of this problem but it does not solve what you are trying to achieve very well or it does not feel right. It does not have the right shape.

-- David Heinemeier Hansson

This creates a downstream effect: the product becomes bloated with features that do not address the root cause, leading to resentment when the delivered solution does not match the customer's expectations. The system forces teams to manage expectations for features that do not exist yet, locking customers into a product based on a promise rather than its current value.

Why Doing Something is a Strategic Failure

Fear often drives product roadmaps. When a new technology like AI emerges, companies feel pressure to do something. This leads to the something bucket: jamming features into a product just to prove the company is relevant.

As Hansson notes, this is rarely effective. It results in cumbersome, poorly integrated features that make the product worse. The conventional wisdom is that being agile means responding to every market signal. However, this logic creates reactive organizations that lose their capacity for original vision. The competitive advantage belongs to those who wait until a solution is solidified. As Hansson puts it, I cannot ship a glimmer.

The 18-Month Payoff: Why Silence is a Moat

The most difficult aspect of this philosophy is the refusal to provide public roadmaps or forward-looking promises. While competitors chase quarterly deadlines and announce features they have not yet built, 37signals maintains optionality.

If you just lay things out before they exist in the product, and you lay out like months worth of work before it exists in the product, you are not leaving yourself open to opportunities that come up.

-- Jason Fried

This requires patience most teams lack. By ignoring the pressure to promise and instead focusing on the current, high-quality state of the product, the company builds a reputation for durability. Over years, this creates a separation from competitors who are constantly over-promising and under-delivering. The pain of not having a roadmap is a filter; it weeds out customers who do not align with the product vision and preserves the team's energy for work that matters.

Key Action Items

• Audit your feedback intake: Stop treating every customer request as a requirement. Move from recording every ticket to listening for patterns that emerge over time. (Immediate)
• Identify the core hurt: When a customer requests a feature, stop asking how do I build this and start asking what is the underlying pain point? Map different requests to the same core problem to find a simpler solution. (Ongoing)
• Kill the long-term roadmap: Shift to a shorter planning horizon, such as 4 to 6 weeks. This preserves optionality and prevents the illusion of agreement that leads to customer disappointment. (Over the next quarter)
• Stop the weasily yes: If a feature is important, build it now. If you are promising it for 6 to 9 months out, you are likely just avoiding the discomfort of saying no. (Immediate)
• Ship solid, not glimmers: Resist the pressure to release half-baked features just to participate in a trend like AI. Wait until the solution is fully formed and adds genuine value. (12 to 18 months)
• Advocate for the silent user: Remember that your most vocal customers represent only the most visible problems. Design for the entire user base, including those who do not write in. (Ongoing)