Your work lives in people's heads. There is no shared picture of how the core things actually get done, so you cannot train a new person quickly, you cannot spot where the work breaks, and you cannot improve a process you cannot even see.
This work makes the invisible visible: you list the core work your organization does over and over, map how each piece actually happens, and find the points where it breaks, so you have something real to standardize and improve. It is the work of seeing your operation clearly, not fixing it yet, and it is not a bureaucratic mapping exercise that produces diagrams no one reads; the goal is a plain, usable picture of how the work really flows, warts and all. Use this if your core work is undocumented and lives in heads. You do not need it if your processes are already mapped and your real trouble is that they are not followed, or not improving, or the tools are wrong; in that case go to the guide your diagnostic named.
You cannot map everything, and you should not try. Name the handful of processes that matter most, the ones that deliver your mission and keep the organization running: how a person is taken in and served, how a gift is received and thanked, how a program is delivered, how you pay and get paid, how you bring on a new person. Focus on the repeating, mission-critical ones, then mark which are most broken and most important, so you map those first.
Open the Core Process Inventory →A process you cannot see is a process you cannot fix. Sit with the person who actually does each process and write down every step as it really happens, including the workarounds and the parts that only they know. Do not write the ideal version; write the real one. For each, note who is involved, what tools and information it needs, and where it hands off to someone else.
Open the Process Map →Now that you can see the work, you can see where it fails. On each map, mark the trouble spots: where it stalls or waits, where it depends on one person, where it produces inconsistent results, where information gets lost, where a tool fights the work. Then sort what you found into the kinds of trouble the next guides address: needs standardizing, depends on one person, needs a better tool, needs cleaner data, keeps recurring.
Open the Breakpoint Finder →If mapping your work makes plain that the whole operation runs through one person, most likely you, that is a real risk with its own weight, and while this work will help you build the systems to spread the load, protecting yourself from burnout in the meantime is its own priority and worth a trusted person's help. This work maps the work; it cannot carry it for you.
You have a plain map of each core process that a new person could actually read. You know exactly where each one breaks. And you could hand the map to someone and have them understand how the work flows without you narrating it.
Most leaders move from here to Make Your Core Work Repeatable, to turn the maps into reliable practice, unless the sorted breakpoints point first to key-person risk, the improvement habit, technology, or data. If mapping reveals the real problem is one specific program's design, that routes to program design and delivery.