A method that only exists as a page is a brochure. A method that only exists as a GitHub repo is a hobby. Keyteller runs this as Discovery: find the door, name the lock, prescribe the first key, including a pause. That is how the studio forges key systems with founders.
The offer is not the tooling
The method is public so the standard is inspectable. Optional tools show how the studio operates the questions. They do not replace the engagement. A founder who can clone a repository has not found the door. Discovery holds the live direction, the evidence, and the decision rights. That is the first unit Keyteller sells.
What Discovery actually does
Situate the decision
Restate the situation in business terms. Separate the stated problem from the door that is actually locked.
- Bring the live direction, not a rebuilt pitch
- Name who owns the decision and who feels the delay
- Keep the three questions in view from the first session
Diagnose the constraint
Inspect evidence, risks, dependencies, and trade-offs. Run what is true and what is better until the door and the existing keys are arguable.
- Use past behavior and current workarounds, not polite interest
- Write the stronger alternatives in the open
- Record any founder override instead of burying it in optimism
Prescribe the next path
Answer what to build first, or recommend a pause. The output is a path with boundaries, not a promise of outcomes.
- One first key, or an explicit stop
- Evidence gaps and decision criteria the team can reuse
- Only then: a program, a scoped project, or no further studio work
Why this is a system, not a workshop
A workshop ends when the sticky notes are photographed. A system remains after the call. Discovery produces artifacts the team can argue with next week: a restated situation, the door, the lock, the first key, and parked keys that are still visible. The master key is that decision system. That is how Discovery stays inside the Keyteller world instead of becoming another offsite.
What you should leave with
Decision artifacts, not a slide aesthetic.
Core idea: If the founder cannot explain the door, the lock, the first key, and what is parked, Discovery did not finish.
- Situation and constraint brief
- Evidence gaps, risks, and decision criteria
- A prescribed next path with clear boundaries
- A written list of work that is not authorized yet
How this connects to co-build
Keyteller co-builds after the questions have an answer. Shared workspace, shared code, and shared decisions only help if what is being forged is the first key. Discovery protects both sides from paying to forge keys for a door nobody found. If the evidence says pause, that is a successful use of the system.