Knowledge risk
One person still carries the answer.
Critical decisions, exceptions, relationships, or timing cues are known by heart but cannot yet be taught or checked.
Good fit
The business runs on knowledge no one has written down.
We are most useful when a leadership change exposes operating knowledge that needs to be understood, verified, and transferred—not simply automated away.
Working boundary
The founder remains part of the proof.
We need a real workflow, source records, and time with the people responsible for the work. A detached strategy deck is not the deliverable.
Selected cases
Proof stays close to the claim.
Public work is shown only where it supports a factual claim. It is not presented as an invented succession case study.
Product delivery
Family Recipe Box
A shared recipe library that keeps one family collection readable across phones, with a clear place for source material and instructions.
Product framing · interface design · implementation · public release
Inspect the live productClient delivery
Borussia Minerals
A public mineral showroom that gives specimen photography and collection context room to carry the experience.
Site strategy · visual system · implementation · public release
Inspect the live client siteEngagement
Start where continuity is most at risk.
Begin by making founder-held knowledge visible. Then build the company memory and improve the workflow around it at a pace the business can verify.
01 · Diagnose
Knowledge Transfer Diagnostic
Map the founder-held decisions, exceptions, relationships, and process know-how that make the work run today.
02 · Build
Company Memory Build
Create a secure, maintainable memory from verified interviews, records, and operating documents—owned by your business.
03 · Improve
Workflow Modernization & Care
Modernize the workflows around the memory using the tools you already trust, with human approval where judgment belongs.
Boundary
Founder judgment stays visible
We document and support decisions; we do not replace the person accountable for quality, relationships, or the final call.
Plain answers
The boundary is part of the work.
Plain answers before a family business begins a knowledge-continuity engagement.
What does a knowledge transfer diagnostic produce?
A practical map of the decisions, exceptions, sources, owners, and knowledge risks in one operating area—plus a recommendation to fix now, measure first, or leave it human-led.
Who owns the company memory?
You do. Your business owns its data, credentials, recordings, source documents, and operating documentation. We begin with the tools your team already uses whenever they are fit for the job.
Will this automate the founder out of the process?
No. Founder knowledge is captured and verified with the founder before it is transferred. Human approval remains wherever quality, judgment, or accountability requires it.
What happens after the first workflow?
The first workflow becomes a reusable pattern. You decide whether to improve another area, maintain what exists, or stop with the documentation and recommendation already delivered.
Approach
Observe. Capture. Verify. Transfer. Improve.
Knowledge moves only when the person who holds it can recognize it, correct it, and approve what the next generation receives.
- 01
Observe
Trace one real workflow with the people who carry its quality, exceptions, and timing.
- 02
Capture
Gather the records, conversations, decisions, and source context that explain how the work actually runs.
- 03
Verify
Review the memory with the founder or responsible operator. Correct it before anyone depends on it.
- 04
Transfer
Structure the approved knowledge so the next generation can find it, use it, and keep it current.
- 05
Improve
Modernize one workflow around the verified memory, preserving the human approval that protects quality.
Field notes
The first client result should change the playbook.
We do not claim a succession case study before one exists. The first engagement will produce a verified knowledge-risk baseline, a practical recommendation, and a better version of this method. Personal writing and history stay on Drew's site.
Read Drew's personal workInquiry
Name the thing only one person knows.
Tell us which workflow or decision depends on one person today, and what the next generation needs to understand or do with confidence.
No deck required. One real example is enough.
A useful inquiry answers three questions.
What does only one person know?
Name the workflow, decision, relationship, or exception that is hard to hand over.
What must the next generation know?
Tell us what they need to understand, decide, or do with confidence.
What can we begin with?
Point to the people, records, and existing tools that carry the current context.