Define the problem

Strong businesses start with a problem that is painful, frequent, and already costing someone money or time. Write the problem from the customer's point of view, in their words, without mentioning your solution. "Owners of small clinics spend six hours a week rebuilding the schedule after cancellations" is a problem. "They need my scheduling app" is a sales pitch wearing a costume. If the problem statement contains your product, rewrite it. A common mistake when defining a problem is writing it in your own industry language instead of the customer's plain words. A dentist might write "patients have poor treatment plan adherence," when the customer would actually say "I forget what the dentist told me to do once I leave the office." The second version is usable because it points directly at a fix; the first version hides the real obstacle behind professional vocabulary. You can tell a strong problem statement from a weak one by checking whether it survives without your solution attached. Read the sentence and delete any mention of your product or service; if the sentence still makes sense and still sounds painful, it is a real problem statement. If deleting your solution makes the sentence collapse into nothing, you were describing your pitch, not their problem. When a problem statement turns out to be wrong after you talk to real customers, do not simply tweak the wording. Go back to the actual conversation and find the sentence the customer used that surprised you, since that sentence usually points to the real problem hiding underneath your original guess. Founders who keep editing their own assumptions instead of replacing them with customer language tend to stay stuck on the wrong problem far longer than necessary. A software developer believed small retail shops needed better point-of-sale software because checkout was slow. After watching several shops in person, he learned the actual daily pain was not checkout speed but the ten minutes each night spent manually counting cash against the register tape to catch mistakes. He rewrote his problem statement around nightly reconciliation instead of checkout speed, which completely changed what he built next.

Key takeaways

• Write the problem from the customer's point of view, in their words, without mentioning your solution.
• If the problem statement contains your product, rewrite it.
• It names who, what it costs, and how often — with no solution attached.

Sign in to complete activities, save progress, and use the AI Coach.