customer-hypothesis

To define a customer profile for early adopters, you replace vague demographic segments with a concrete, situation-based portrait. This approach captures the user's specific context, daily environment, and emotional drivers to identify ideal early adopter candidates.

Situation-based user research is a method that documents a user's context, pain, motivation, and current workarounds. You need it for problem validation when your target customer description is too vague and you must build for a real early adopter rather than a broad market.

You create a customer-profile.md by answering six targeted questions about your early adopter's situation. This generates a document detailing the user's context, pain points, core motivations, and existing workarounds to guide product development.

Yes, this approach is specifically designed for instances where your startup persona feels too broad. It sharpens your target audience by focusing on concrete situational contexts and practical workarounds, ensuring you build for an early adopter with an actual pain point.

The best way to document early adopter workarounds and motivations is to capture the user's situational context and emotional drivers. This translates abstract user research into a practical profile that outlines exactly how and why they currently solve their problems.

A vague customer description limits early traction because it targets a broad demographic rather than addressing a specific user's situational pain. Replacing it with a concrete portrait of an early adopter ensures your product directly solves a real, documented problem.