Field Notes on Customers Becoming Teachers

The first version of a product exists to prove one thing: does anybody care enough about this problem to move? Not admire. Not compliment. Move. When we launched Postly, we weren't just putting a tool into the world; we were submitting a hypothesis for grading. The market is a harsh grader, but it is also the only teacher that matters.

The central tension of the early build is that founders often view customer feedback as a list of feature requests to be checked off. In reality, customers are teaching you something much deeper: they are revealing where your assumptions about their life and work have failed. To survive the middle of the journey, you must stop being a defender of your original vision and start being a student of the friction your users encounter.

The Difference Between Movement and Admiration

In the early days, it is easy to be misled by false signals. Friends, peers, and early beta testers might tell you the product is "cool" or "interesting." This is admiration, and it is a trap. Admiration doesn't require a change in behavior. It doesn't require the user to abandon an existing workflow or commit a budget.

Movement is different. Movement happens when a user touches the product and encounters a moment of relief that outweighs the pain of switching. When we built Postly, we entered a crowded category of social media tools. On paper, the world didn't need another scheduler. But by watching how users moved—what they ignored and what they clung to—we realized they weren't looking for more capabilities. They were looking for confidence.

If a customer struggles with a feature, it isn't always a UI bug. It is often a curriculum point. They are teaching you that your mental model of their workflow is incorrect. This realization is essential for navigating the valley between validation and scale, where the initial excitement of launch gives way to the hard work of refinement.

Friction as the Curriculum

Real users touch the product in ways you did not expect. They reveal edge cases, hidden motivations, and emotional triggers that you could never have designed from imagination alone. This friction is not a sign of failure; it is the evidence required to build the "real" product.

When a customer asks for a specific feature, they are using product language to describe an outcome. Your job is to translate that back into the relief they are seeking. For example, a request for "more filters" might actually be a lesson that your search functionality is failing to provide clarity. A request for "faster exports" might be a lesson that your tool is being used as a middle-man for a different process entirely.

The Founder's Syllabus: What Customers Teach

The goal is not to accumulate capabilities. The goal is to reduce uncertainty for the user. The more clearly you see this, the easier it becomes to understand why the first product was never the real one. It was simply the listening device that allowed the teachers to begin their work.

Decision Framework: Listening to the Right Teacher

Not every user is a qualified teacher for your specific journey. One of the hardest parts of the founder breaking before the product is the emotional weight of trying to please everyone. You must distinguish between the "Tourist" and the "Resident."

• The Tourist: They explore the product but have no intention of moving their core workflow. Their feedback is often broad, seeking features that would make the product "perfect" for a use case they don't actually have.
• The Resident: They are trying to live in your product. Their feedback is specific, often frustrated, and centered on the friction that prevents them from completing their daily work.

Listen to the Resident. Their frustration is the highest form of teaching because it shows exactly where the product is failing to provide the relief they are willing to pay for.

Failure Modes in the Student-Founder Relationship

There are three common ways founders fail to learn from their customers:

1. The Visionary's Deafness: This occurs when a founder is so attached to their original idea that they dismiss friction as "user error." They believe the customer needs to be educated, rather than the product needing to be evolved.
2. The Feature Factory: This is the opposite extreme. The founder builds every request without interpreting the underlying need. This leads to a bloated, incoherent product that loses its original purpose.
3. The Survey Trap: Asking customers what they want often results in aspirational answers. Customers are best at describing their current pain, not designing their future solutions. Watch what they do, not just what they say.

Field Notes for the Middle

To turn your customers into effective teachers, you must change your posture. This is a core tenet of The Long Build philosophy. It requires patience and a willingness to be wrong.

• Early versions are not failures because they change. Their job is to teach. If your product looks the same six months after launch, you probably aren't listening.
• Customers rarely describe the product they want in product language. They describe the relief they want in outcome language. Your job is the translation.
• The founder who listens well will outgrow the founder who clings to the original idea. Adaptability is a competitive advantage in a crowded market.

The first product is evidence. Your real product is the interpretation. As you continue your journey, remember that the market is not something to be conquered, but something to be understood. If you are struggling with the slow pace of growth or the complexity of user demands, take a breath. You are simply in a classroom. The lesson is currently in session.

For more reflections on the endurance required for this journey, you can continue with The Long Build and GrowthDiary essays.

Follow via RSS: latest articles · full article archive