use case · 04

the knowledge vaultThe way things work lives in Dana's head.

Meet Dana Whitfield, senior operations coordinator at Cascade Dental Group — four locations, three hundred patients a week, and one person who knows how any of it actually works. 'Ask Dana' isn't a saying at Cascade. It's the process.

the story

fictional · illustrative pattern

Dana's week.

Thirty-plus times a day, someone stops by her desk or pings her: how do we file this, who approves that, which code do we use. The answers live in her head because they always have. When she's out, the work stalls — and she knows it.

Run FlowHealth to confirm →
01

Thirty interruptions a day

Every one a question with a known answer. By noon she's done her own job; by five she's done everyone else's.

02

The work stalls when she's out

She took two days off in May. The front desk logged nine 'we'll wait for Dana' items in that window.

03

New hires can't find anything

Week three, a new coordinator asked her how to file an insurance claim — the same question the last new hire asked.

04

She can't take the promotion

The regional role opened twice. Both times, the answer was 'we can't lose Dana from the floor.'

what they'd tried

The honest attempts.

01

An internal wiki

Thirty pages, updated twice, already wrong by the time it was shared.

02

Recorded walkthroughs

Fifteen videos. Outdated within two weeks, because the process changed and nobody re-recorded.

03

Hiring Dana an assistant

The assistant became a second 'ask Dana' queue — just with extra steps.

what they assumed

The quiet beliefs.

01

Writing it down takes longer than doing it

Dana genuinely believed documentation was a tax on her day.

02

I'm the only one who can do it right

Her standards were the process. Handing that over felt like lowering the bar.

03

If I document everything, they won't need me

The quiet fear under all of it — and she wasn't going to say that out loud.

what plainworks did

The process moved out of her head and into the work.

● before
ask Danatwo days out = stallthe wiki nobody updatespromotion on hold
● after
Playbooks written with Dana — not around her
Answers available at every location
An AI assistant trained on the playbooks
New hires self-serve from week one
hrs

22 hours a month

The same questions, answered once, then forever. That's what Dana got back — nearly three full days.

%

Onboarding: 3 weeks → 5 days

New coordinators stopped waiting on Dana and started using the playbooks.

$

~$15,000 a year

The cost of the stall — re-answers, re-training, and the float when she was out.

Dana didn't get replaced by a playbook. She got promoted because of one.

why it mattered

Intrinsic, then direct.

The system didn't subtract Dana from the business. It changed what the business needed her for.

01

Intrinsic value

Dana stopped being the bottleneck and started being the person who built the system. The promotion she'd been told she couldn't take opened up — because the knowledge no longer lived only in her.

02

Direct value

22 hours a month back, new-hire ramp cut from three weeks to five days, and zero 'wait for Dana' stalls across four locations.

how they see it now

Writing it down was never the tax.

The tax was the interruption — hers and everyone else's. Once she saw the playbooks working without her, the fear flipped: she wasn't replaceable, she was scalable.

— Dana, after the promotion

which offering fixes this

This is a _flow problem.

Also common

is this your leak?

Write it down once.

Run the free FlowHealth diagnostic or talk to the consultant. We'll confirm the fix and hand a clear concept to Nathan.