WHERE WORK WAITS / PRIVATE DIAGNOSTIC
How much of your company still lives inside the founder?
Twelve questions. Four operating dimensions. One honest view of where decisions, context and customer work still wait for you.
Run the scorecard ↘About 3 minutes / no signup
01 / THE OPERATING READ
Answer for the last 30 days.
Use what actually happened, not what the process document says should happen. Your answers stay on this device.
00/ 100
OPERATING READ / COMPLETE
Your result
Decision concentration
0
Context concentration
0
Customer continuity
0
Operating visibility
0
This score is a diagnostic heuristic, not a prediction or industry percentile. Use it to choose what to observe next.
02 / METHODOLOGY
Transparent enough to disagree with.
The scorecard is designed as an operating conversation, not a scientific diagnosis. Version 1 makes every question, weight and limitation visible.
Equal weights, visible math.
Each answer is scored from 0 to 3. The total is divided by the maximum possible score and converted to 0 to 100. Each dimension uses the same calculation across its three questions.
Provisional bands.
0 to 24 indicates low concentration, 25 to 49 emerging concentration, 50 to 74 high concentration, and 75 to 100 critical concentration. These bands guide action. They are not validated risk thresholds.
No response collection.
Version 1 calculates locally. Individual answers are not sent to Evan or stored. Standard site analytics may record a page view or generic form interaction. Scorecard-specific analytics adds only start or completion, the broad result band and the highest dimension.
Perception is not workflow evidence.
A founder's answer can differ from the team's experience. Compare responses, then observe one real workflow before changing roles, tools or headcount.
FUTURE RESEARCH STANDARD
When this becomes a benchmark.
- Freeze the instrument.Question wording, weights and bands must be versioned before collection begins.
- Collect explicit consent.No email or company name is required for the research dataset. Context fields remain optional and separated.
- Use a publication floor.At least 100 complete, screened responses across multiple company-size bands, with no subgroup reported below 30 responses.
- Describe the sample.Publish recruitment method, exclusions, sample composition, missing data and limitations. Do not claim representativeness without evidence.
The response floor is an operational publishing rule, not proof that the sample represents every startup. Until those conditions are met, this remains a scorecard, not the Founder Dependency Benchmark.
03 / QUESTIONS
Before you trust the number.
Is this a validated industry benchmark?+
No. Version 1 is an operating heuristic built to help a team locate concentration risk. The score bands are provisional and do not predict company performance. Industry comparisons will not be published until a frozen questionnaire has an adequate, described sample.
Do my answers leave the browser?+
No. This version calculates the score in your browser and does not submit or store individual answers. Standard site analytics may record a page view or generic form interaction. Scorecard-specific analytics records start or completion, plus the result band and primary dimension.
Who should complete the scorecard?+
A founder can complete it alone, but the most useful review compares the founder's answers with one operator or functional lead. A large disagreement is itself an operating signal.
Does a high score mean the founder is performing badly?+
No. Founder concentration is normal in an early company. The score highlights where concentration has started to create waits, inconsistent customer experiences or invisible work.
What should I do after receiving the result?+
Start with the highest-scoring dimension. Observe the relevant workflow for one week, record waits and rescues, then change one ownership rule or handoff before adding headcount or software.
Follow the wait.
Then redesign the system.
If the score exposed a stubborn concentration point, bring the workflow, the evidence and the exception nobody knows how to own.
Bring Evan the operating gap ↗