What I'm Actually Doing While I'm Reading Your Clarity Diagnostic Responses.

People tell me things.

They share them in a questionnaire. A form they fill out at 10 pm after the kids are in bed, or during a rare quiet hour between meetings, or in desperate fragments across three days because that's the only way it was getting done.

They answer questions about workflows and processes and "how things work around here."

But here's what I've learned: when you ask the right questions with genuine curiosity, people don't just give you information. They give you the truth.

Even in a form. Especially in a form. There's something about writing it down, without someone watching, that lets people say what they might not say out loud.

And the truth is where the real work begins.

There's a thing that happens when I'm reading through a Clarity Diagnostic questionnaire. On the surface, it looks like I'm reviewing answers. Checking boxes. Tallying responses.

But underneath, my brain is running a completely different process.

I'm mapping.

Every answer is a data point. Not just the words, but the length of the response. The question you skipped. The one where you wrote three paragraphs when a sentence would have done. The place where you added "(I know this is a mess)" or "(we've been meaning to fix this)" or "(don't even get me started)."

I'm reading for what you're not saying as much as what you are.

Let me show you what I mean.

I ask: "Walk me through what happens when a new volunteer signs up."

You write: "They fill out a form on the website, and then... honestly, it depends on who sees it first. Usually Sam handles it, but if he's out, sometimes it sits for a few days. We've been meaning to fix that."

Here's what I just learned:

There's no standardized process. Institutional knowledge lives in Sam's head. When Sam's unavailable, things fall through cracks. You know it's a problem. You've tried to fix it. Something got in the way, probably time, probably competing priorities, probably the reality that fixing it requires capacity you don't have.

One question. Six insights. And I haven't even asked about Sam yet.

This is why I built the Clarity Diagnostic the way I did.

I wanted to create something accessible. A low-friction entry point for EDs who are overwhelmed and underbudgeted and can't commit to a massive consulting engagement. Something you could do on your own time, at your own pace, without adding another call to your already-packed calendar.

But I wasn't willing to sacrifice depth for accessibility.

So the questionnaire isn't a quiz. It's not a scored assessment that spits out a category. It's a series of carefully designed questions that surface the patterns underneath, the ones you might not even see because you're too close to it.

And when I read your answers, I'm not skimming. I'm doing the same deep work I'd do in a conversation. I'm just doing it asynchronously, in a way that respects your time and your budget.

Every organization has a surface story and an underneath story.

The surface story is "we need a better volunteer management system." The underneath story is "we have a single point of failure named Sam and we're terrified of what happens when they go on vacation."

If I only read the surface answers, I'd give you surface recommendations. And they wouldn't change anything.

But I don't read that way. I read the hesitations. The parenthetical asides. The questions where you wrote "N/A" a little too quickly. The ones where you clearly stopped and thought before answering.

That's where the underneath story lives. And that's what I'm looking for.

Let me give you an example. For one client, the presenting problem was donor retention.

They were losing people after the first gift and couldn't figure out why. The surface story was: we need a better stewardship process. But as I read through their answers, something else emerged.

Their stewardship process was actually fine. The thank-you emails were going out. The follow-up sequence existed. But buried in their answer about "biggest challenges" was a single line:

"I never have time for the personal touches anymore."

I asked a follow-up question about how they spent their time. The answer was a flood. Every day was reactive. No protected hours. No boundaries. Every task felt urgent because there was no system for prioritizing.

The donor retention problem was a leadership bandwidth problem wearing a different costume.

I never would have seen it if I'd just tallied their answers. But I wasn't tallying. I was mapping.

Here's the thing about this kind of reading: it works because I trust that you know more than you think you do.

You're living inside your organization every day. You see the problems, even if you can't name them. You feel the friction, even if you've normalized it. When I ask the right questions, you give me the clues. My job is to piece them together into a picture you can finally see clearly.

That's why the questionnaire matters. Not because I'm testing you. Because I'm listening to you, in the only format that scales without losing the depth.

I've seen how the same patterns show up across industries, wearing different disguises. I've learned to hear the exhaustion in a three-paragraph answer and the avoidance in a one-word response.

And I've learned that people are remarkably honest when you give them the right questions and the space to answer without judgment.

You tell me more in that form than you might tell me in a meeting. Because there's no one watching. No performance required. Just you, the questions, and the truth of how things actually work.

But let's be honest. Naming the problem isn't enough.

You already know Sam is the keeper of the workflow. You already feel that pit in your stomach when they mention taking a week off. What you need isn't someone to creatively articulate your stress.

You need to know what to do about it.

So let me give you something concrete.

When I identify a single-point-of-failure situation, there are three paths forward. The right one depends on your budget, your timeline, and your appetite for change. But all three are real options, and knowing they exist is the first step.

Path 1: Document and Distribute (Low cost, low disruption)

Sam's knowledge lives in their head. Your first job is to get it out of their head and into a format anyone can access.

This doesn't mean a 50-page manual no one will read. It means:

A simple checklist for the volunteer intake process, written in Sam's voice, that lives somewhere everyone can find it. This could be a Google Doc, a Notion page, or a Loom video where Sam walks through the process in 5 minutes. Loom is free for videos under 5 minutes, and sometimes watching someone do the thing is more useful than reading about it.

A "What to do if Sam's out" one-pager that covers the top 5 things that can't wait.

A monthly 15-minute "knowledge transfer" where Sam walks one other person through something only they know. Put it on the calendar. Protect it like a donor meeting.

You're not replacing Sam. You're reducing the risk of them being the only one who can do critical tasks.

Timeline: 2-4 weeks. Cost: Just time.

Path 2: Cross-Train a Backup (Medium investment, medium disruption)

Documentation helps, but it doesn't replace competence. If Sam handles volunteer intake and donor acknowledgments and event logistics, you need at least one other person who can do each of those things at a basic level.

This means:

Identifying which of Sam's responsibilities are most time-sensitive or high-stakes. Use a simple matrix: what breaks first if no one does it for 48 hours?

Choosing one person to shadow Sam on each of those tasks. Not all at once. One task per month and document the procedures while it is happening.

Building "backup mode" into your normal operations, not waiting for an emergency. Some organizations use tools like Trainual or SwipeGuide to create interactive training guides that live in one place and can be updated easily. Others keep it simpler with shared drives and recurring calendar invites. You could also do what I did when I was an ED and make micro training videos in Microsoft Clipchamp. You can read more about that in my post: Why I've Never Niched Down (And Why I Finally Did)

This isn't about Sam training their replacement. It's about building redundancy so your organization doesn't hold its breath every time they take PTO.

Timeline: 1-3 months. Cost: Staff time, possibly some overtime during training. Trainual starts around $250/month for small teams if you want a dedicated platform.

Path 3: Redesign the Role (Higher investment, structural change)

Sometimes the problem isn't that Sam has too much knowledge. It's that Sam has too much responsibility.

If one person is the hub for multiple critical functions, that's not a training problem. That's a design problem. The role has grown organically over time, absorbing tasks that should live elsewhere.

This path means:

Mapping everything Sam actually does. This is often a surprising exercise. I've had clients realize their "operations coordinator" was also doing HR, IT support, donor stewardship, and event planning with no title or pay adjustment to reflect it.

Identifying which tasks are truly theirs and which landed on their plate by default.

Redistributing, eliminating, or automating the tasks that don't belong. This is where technology can create real leverage. A CRM like Bloomerang or Little Green Light can automate donor acknowledgment emails that Sam currently sends manually. A scheduling tool like Calendly can eliminate the back-and-forth that eats hours every week. A project management system like Asana or Monday can make task ownership visible so things don't default to "whoever Sam can grab."

Possibly restructuring roles, rethinking job descriptions, or making the case to your board for a new hire.

This is the biggest lift. It's also the one that creates lasting change instead of temporary patches.

Timeline: 3-6 months. Cost: Consulting support, possible staffing changes, and technology investment ranging from free (Asana's free tier) to a few hundred dollars monthly for robust CRM and automation tools.

Which path is right for you?

It depends.

If Sam's been with you for 15 years and retirement isn't on the horizon, Path 1 might be enough for now. If you're already stretched thin on staff, Path 2 might feel impossible without first addressing workload. If Sam's role has become a patchwork of responsibilities that no job description could contain, Path 3 might be the only real solution.

The point isn't that one path is better. The point is that there are paths.

You're not stuck. You're not at the mercy of one person's availability. You have options, and now you can see them.

This is what I do.

Not just name the problem. Map the options. Show you what's possible given where you are and what you have. Give you a framework for thinking about it, even if you never hire me for another minute.

And if you do want to go deeper, if you want someone to help you figure out which path fits your organization and walk beside you through the implementation, that's what the next level of work looks like.

But even if you stop here, you're not walking away empty-handed.

You're walking away with clarity. And clarity is where change begins.

Learn More About The Clarity Diagnostic