The hardest roles to onboard into are the ones the founder created. There is no prior documentation because the founder never needed any. There is no second person who knows the work because the founder has always been the second person. The paradox: the most important knowledge in the business is the least likely to be written down.

A founder-created role carries years of accumulated decisions, workarounds, client-specific knowledge, and implicit standards. None of it is explicit. All of it is required to do the job well. The person leaving takes it all with them unless a specific extraction process captures it before they go.

This is the most challenging onboarding context a small business faces. It is also entirely solvable if the extraction happens before the departure rather than after. The Knowledge Transfer System from The Knowledge Transfer System That Gets New Hires Up to Speed Without Consuming the Team applies here, with one addition: the knowledge doesn’t just need to be transferred. It needs to be reconstructed first.

The Solo-Role Capture Process gives you the structure for doing that reconstruction before urgency makes it impossible.

Why Solo Roles Lose Their Knowledge on Every Transition

The obvious problem: the person leaving was so embedded in the role that the knowledge was invisible. They didn’t document it because to them it felt like common sense.

The less visible cost is what happens when a successor starts without that context. They can learn the tasks. Tasks are observable. What they cannot learn from observation alone is why things work the way they do, or which clients need particular handling.

The deepest problem is that the person leaving is the only one who knows the difference between doing the tasks and doing the role well. Capturing that distinction before they leave is not just documentation. It is the difference between a new hire who eventually becomes competent and one who becomes excellent.

Without the capture, every transition restarts the institutional knowledge of the role from zero.

The Solo-Role Capture Process

The process has four steps. Each step can be done in a single session if time is limited. All four, done well, produce a knowledge base that a new hire can onboard from rather than reconstruct on their own.

Step 1 inventories the role’s implicit knowledge

The first step is an interview with the person holding the role, structured around categories of implicit knowledge rather than tasks.

What does this person know that isn’t written down anywhere? What decisions do they make that no one else could make without consulting them? Which client relationships do they manage in ways that would surprise someone who only saw the job description? What have they learned that they wish they’d known in their first year?

The inventory is not a detailed document. It is a map of what needs to be captured. Most solo-role holders are surprised by how much they know that isn’t written anywhere.

Step 2 captures the client and relationship context

For most founder-created roles, the hardest knowledge to transfer is the relationship context. Each significant client has a history, a preferred communication style, and things that have gone wrong in the past that the new hire shouldn’t repeat.

A short record for each significant relationship captures what makes them different and what a new hire should know before their first interaction. Two to four sentences per relationship is sufficient.

The relationships that have the most context are usually the relationships the role-holder has managed the longest. Start with those.

Step 3 documents the decision framework

Every role involves judgment calls. The previous holder developed judgment over time through trial, error, and accumulated feedback. Step 3 captures the decision framework: the rules of thumb, the non-obvious principles, and the specific situations that require particular handling.

This is the hardest step and the most valuable. “We always price this kind of project flat because clients can’t budget for hourly” is one sentence. It represents years of learning and client conversations. It cannot be reconstructed from the task list.

Step 4 builds the what-not-to-do list

Every role also has a body of knowledge about what doesn’t work. Approaches that looked right and failed. Promises that shouldn’t be made. Clients or situations that require extra care and why.

This knowledge never gets documented. The person holding it is the only one who knows it. A successor will have to learn it again from experience.

A short what-not-to-do record saves a new hire months. It doesn’t need to be comprehensive. It needs to capture the three to five most important things a person in this role should never do or try.

How the Living Library Assembles Your Solo-Role Knowledge

When a key person is preparing to leave a role they built, the capture process described above generates a significant body of knowledge. Without a system to hold it, that knowledge lives in unorganized notes a new hire will struggle to navigate.

The Living Library is the part of the Kiluma platform that holds and organizes what your business has documented. The Conductor, Kiluma’s context-aware AI, reads from the Solo-Role Knowledge Collection to help the new hire find what they need without reconstructing the capture alone.

When a question comes up in the first quarter, the new hire queries the Conductor. It reads the relationship context records, the decision framework, and the what-not-to-do list assembled in the Living Library and returns what the capture showed. The role’s accumulated knowledge, previously held in one person’s head, is now accessible to whoever holds the seat.

Start the Capture Now, Before a Departure Is Imminent

The best time to run the Solo-Role Capture Process is when there is no urgency. When the person is not leaving, is not planning to leave, and is still fully in the role. The knowledge is most complete and most available in that window.

Schedule the four steps as a one-day exercise, or spread them across four thirty-minute sessions in the next two weeks. The output is a knowledge base that protects the role against every future transition, not just the next one.

Do not wait until someone announces they’re leaving. At that point, the capture has a deadline and the person’s attention is divided.

The One Problem, Five Approaches

Every article in this chapter addressed the same underlying challenge: in a small business, the knowledge needed to do the job well lives in people, not in systems. The five approaches:

The same knowledge runs through all five: what this business knows about how to do the work. The onboarding system is what moves that knowledge out of people’s heads and into a place the next person can find. Try Kiluma free for 14 days at kiluma.ai.