Marisol's nineteen-page action-items document was, she now sees, a list. Customer discovery: done. MVP: done. Landing page: done. Each framework a box; each box checked. And nothing worked.
The problem wasn't that she did them. The problem was that she thought they were boxes.
The Reframe
I want to take the weight off you now, because Part Three is going to look, at first glance, like the very thing that's been crushing you: a list of startup frameworks. Customer Discovery, Lean Startup, MVP, Product-Market Fit, the Value Proposition, the Business Model Canvas, Go-To-Market, Traction, Selling, Scaling. The whole syllabus.
But I'm not going to add a single one to your to-do list. I'm going to do the opposite. I'm going to show you what each of these was actually built to do, so you can stop performing them as chores and start using them as what they are. By the end of this part, the goal is for you to feel lighter, not more burdened, because half of what you thought you were failing at, you were simply misunderstanding.
Here's the first thing nobody tells you: these frameworks are not all the same kind of thing. You've been treating them as interchangeable steps in one big sequence, but they belong to completely different categories.
Some are methods — ways of working (Lean Startup). Some are plans — coordinated approaches (Go-To-Market). Some are evidence labels — names for a kind of proof (Product-Market Fit, Traction). Some are activities — things you do (Customer Discovery, Selling). Some are artifacts — things you make (MVP, the Business Model Canvas).
When you hear all of these as items on a single checklist, you flatten that whole structure into "stuff to complete." You build the MVP and check the box. You run discovery and check the box. But an evidence label isn't something you complete; it's a state you either have or don't. An activity isn't a box; it's a thing you do to learn something specific. Treating a method like a deliverable is like treating "the scientific method" as something you finish.
The One Question
So here is the reframe that organizes all of Part Three, and it's a small change in wording that turns out to be enormous.
Stop asking, for each framework, "have I done this?"
Start asking, "what question was this built to answer?"
A framework is not a step you complete. It is a tool for answering a specific question about your business — almost always a question about the outcome, the customer, the roadblock, or the evidence that someone will actually act. When you know the question, the framework becomes useful. When you don't, it becomes a chore you perform to feel diligent, generating activity and no judgment.
I'm framing it as a question, not a "purpose," on purpose. A purpose is a thing the framework has. A question is a thing you ask, and as long as you're asking, you stay in the right posture: a founder trying to find out whether they're wrong, not a founder collecting tools. Founders hoard frameworks the way some people hoard kitchen gadgets. The question keeps you using the knife instead of buying another one.
So as we go through the syllabus in the next three chapters, every framework gets the same treatment. What do founders usually hear it as? And what question was it really built to answer? Keep the beach in mind the whole way through, because nearly every one of these questions is, underneath, a question about the beach.
Marisol re-titles her document. It used to be "Action Items." Now it's "Questions I Haven't Answered Yet." The list barely changes. The way she holds it changes completely.