How We Measure What Works
A practical measurement system begins with clear standards, a small set of meaningful outcomes, and a commitment to distinguish activity from progress.
Organizations can count almost anything. Workshops held, emails sent, meetings booked, and people in a room all describe activity. None of them, by themselves, tells us whether an entrepreneur became more capable or a business became more durable.
Our measurement system starts with that distinction.
Begin with the decision the data should improve
A metric earns its place when it changes a decision. Completion rates can reveal whether a program asks too much at the wrong time. Customer interviews completed can show whether participants are testing assumptions. Cash-flow habits can reveal whether financial instruction is becoming operating behavior.
If a number cannot improve program design, founder support, or resource allocation, it is probably reporting noise.
Separate outputs from outcomes
Outputs describe what the organization delivered: sessions, mentor matches, curriculum hours, or partner events. Outcomes describe what changed for the participant or business.
We plan to track outcomes such as:
- completion of defined business milestones;
- quality and frequency of customer discovery;
- adoption of basic financial and operating practices;
- launches, revenue progress, and responsible hiring where relevant;
- mentor relationship quality and follow-through;
- business continuity over time.
Use a baseline and a follow-up
Change cannot be inferred from an ending snapshot. Participants should describe their starting point before a program begins, record concrete work during it, and complete follow-ups after the immediate energy of a cohort has passed.
That creates a more honest view of what persisted.
Treat stories as evidence with limits
A founder’s story can reveal mechanisms that a spreadsheet misses: why a mentor’s question changed a pricing decision, why a workshop finally made cash flow understandable, or why a customer interview prevented an expensive launch.
Stories are valuable, but they are not a substitute for aggregate results. We use both. Numbers show patterns; careful interviews explain how those patterns may have formed.
Measurement is not a victory lap. It is an operating system for learning.
Publish the useful truth
Credibility requires more than publishing good news. It means explaining the cohort, the timeframe, the method, missing data, and what cannot be concluded.
When real results are available, we will report them with those boundaries. If an element underperforms, the next question is not how to hide it. The question is what to change.
That standard makes measurement practical: evidence improves the next program, and the next program should produce better evidence.