Practical founder guide
Turn your founder result into a seven-day experiment
A reflection result becomes useful when it changes a specific, observable action.
A founder quiz result becomes useful when it changes a decision you can observe. Use your result to examine one working habit, then try a small adjustment in a real task. A label cannot tell you which business to start or whether an idea will work.
This guide provides an editorial worksheet created for FounderType. The seven-day schedule is a convenient timebox, not a promise that a business can be validated in a week. The example below is hypothetical.
Start with a behavior you can observe
Choose one description in your result that feels relevant. Rewrite it without the type label. For example, change “I am an idea person” into “When I get a new idea, I open another project before finishing the current test.” The second sentence describes something you can notice and change.
Then record a counterexample: a recent time you behaved differently. This prevents the result from becoming an excuse to avoid work outside your preferred style. Your circumstances, the wording of a question, and your interpretation of your own behavior can all affect a self-reflection result.
Worksheet: from description to behavior
| Reflection | Your notes |
|---|---|
| A description in my result that resonates | ____________________ |
| A recent situation where I showed this behavior | ____________________ |
| A situation where I behaved differently | ____________________ |
| The consequence for a customer, collaborator, or unfinished task | ____________________ |
| One adjustment I can try | ____________________ |
Choose an adjustment that addresses a blind spot
Pick a row that describes your current behavior. You do not need to match every row or belong to a particular type. These are reflection options, not rules about personalities.
| If you tend to… | Try this | Record |
|---|---|---|
| Generate alternatives but postpone deciding | Choose one customer problem; defer new ideas until a scheduled review | A completed test and written decision |
| Build before checking the problem | Ask an intended user to demonstrate the current task | The steps and friction points |
| Promote an offer before defining delivery | Write the smallest outcome you can reliably deliver | The promise compared with delivery |
| Plan extensively before showing anything | Show an intended user a rough but usable example | What they can complete without explanation |
Write the experiment before starting
Copy and complete this sentence:
When [specific situation] occurs, I will [observable action] instead of [default action]. I will record [evidence] and review it on [date].
“Become more customer-focused” is difficult to review. “Before adding another feature, ask an intended user to show the most recent task it would help with” is observable. Choose something appropriate for your available time and responsibilities.
Decide what would count as a useful result before seeing the outcome. You are evaluating the adjustment, not proving that a quiz label is correct. Strategyzer’s Test Card similarly separates an assumption, a test, a measure, and an advance criterion. The worksheet here is a separate exercise, not a reproduction of that tool.
A seven-day plan
| When | Action | Output |
|---|---|---|
| Day 1 | Choose one behavior and one relevant situation | Your experiment sentence |
| Day 2 | Prepare the smallest task or conversation needed | A question list, sample, or brief |
| Days 3–4 | Try the adjustment and write down what happened | Observations close to the event |
| Day 5 | Look for evidence against your first interpretation | A counterexample or alternative explanation |
| Day 6 | Repeat if useful without changing the question | Another observation or a reason not to repeat |
| Day 7 | Review and choose the next action | Keep, adapt, or stop, with a reason |
If the relevant situation does not occur, record that. An unrun experiment is not a failed business idea, and missing observations are not positive evidence.
Worked example: a hypothetical first-time founder
Alex wants to build a reminder tool for freelance designers and notices a habit of adding features without speaking to potential users. Alex pauses new feature work and asks designers to describe how they handled a recent overdue payment.
Alex records the steps, existing tools, and consequences the interviewees can describe. Compliments about the app go in a separate column from examples of late invoices. At the review, Alex decides what deserves another test. This scenario is illustrative: it is not a report of interviews or proof that designers want this product.
Use the customer interview worksheet to organize such a conversation. Once you have a specific uncertainty to investigate, continue with the MVP scope worksheet.
Review your behavior and the business separately
- Working habit: Did you carry out the adjustment? Did it help you complete a task or notice something you had overlooked?
- Business evidence: What did you learn about an intended user’s actual problem, behavior, or response to an offer?
You may improve a habit while discovering that the idea needs to change. Write both conclusions separately. YC’s essential startup advice emphasizes learning from users and revising what you deliver. A self-reflection result can help you choose an action; external evidence should still be able to change that choice.
Do not use this quiz as a hiring filter, a diagnosis, or a prediction of entrepreneurial success. Save your observations and review notes: they are a better basis for the next decision than repeatedly taking a quiz to obtain a preferred label.