What it is

Frontline staff log every point where the system made their job harder, for two weeks — dated, specific, first-person entries with the workaround they used. The internal counterpart to a client journey map.

What it tells you and what it cannot

Tells you	Cannot tell you
Systemic operational failures, from the people who hit them daily	The client's experience directly — it is the staff side of the glass
Workarounds staff use to keep services moving despite system limitations	Frequency across all staff, unless participation is structured
Which processes staff have already quietly re-engineered	Anything, if the culture punishes honesty

How it runs

Who does the work	Participants	Elapsed time	Cost
Staff self-log during real work; a facilitator synthesizes	A handful of frontline staff per site, spread across roles	~2.5 weeks (2-week window + synthesis)	$ — near zero

Strengths, watch-outs and quality signals

Equity & consent

Low client-privacy burden (entries are staff-facing; keep client details generic), but real staff protection needs: anonymize, let leadership model an entry first, and keep the focus on the system rather than individual workers. Explain how the findings will be used and follow up visibly.

When to choose it

Scenario: How this can help examine HR1 impacts

Two weeks of HR1-tagged logs can reveal why staff cannot consistently carry a client from notice to accepted proof or from benefit loss to service received. Include benefits, Customer Relations, behavioral health, CPS, and workforce or referral staff. Log unclear affected-status flags, inaccessible notices, duplicated evidence requests, exception-documentation ownership, system mismatches, deadline tracking, and referrals without confirmation.

Measure entries and staff time by theme and process stage, but pair each proposed fix with an owner and metric: affected-status fields completed; duplicate requests per case; proof items with confirmed acceptance; deadlines with an accountable role; and alternatives advancing through offered, contacted, enrolled, and received. Keep entries generic and system-focused.

Blind spot: logs show the staff side of the glass. They undercount normalized friction, reflect volunteer and workload bias, and cannot establish what a client understood or received. Pair them with client-controlled evidence and case review. See the HR1 listening plan and HR1 Impact Report.

Framing printed on every log template: this critiques the system, not the worker.

Setup

Six frontline staff across two sites logged every point where the system made their job harder during two working weeks, July 20–31, 2026. The template was deliberately light: date · task · what made the job harder · severity (blocker / slowed / minor) · workaround. To support candid reporting, entries named systems rather than colleagues, and supervisors saw only aggregate results. The method has real grounding: frontline observation studies found about 8.4 work-system failures per 8-hour shift (real background: Tucker & Spear 2006), costing roughly 42 minutes per shift (real background: Tucker 2004). The six logs produced 87 entries; featured below is one intake worker's complete 14-entry log, lightly edited for anonymity.

Raw log excerpt

First-person entries reproduced as written. The recurring thread "Client J." — a DV-entry case open in multiple programs — is anonymized to what any such case would share. Sections from "Ranked friction themes" onward are analyst synthesis.

Date	Task	What made the job harder	Severity	Workaround
Mon 7/20	New intake — Client J. (DV entry, multi-program)	One household record typed into the intake system, benefits portal, and referral tracker before noon. I expected the entry to carry over; none did.	Slowed	Scratch doc open all day to copy-paste from
Mon 7/20	Warm handoff to housing intake	No cross-program directory exists. I expected a transfer list; got the public main line, twice, to voicemail.	Slowed	Direct line from the sticky note on my monitor
Tue 7/21	BH referral for Client J.	The referral goes by fax. I expected a confirmation; got a transmission report that proves nothing about receipt.	Blocker	Calendar note to call and ask if it arrived
Tue 7/21	Eligibility interview, walk-in	The portal logs me out after 15 idle minutes; an interview runs longer. I expected a draft save; got a blank form.	Slowed	Paper notes first, re-key after the client leaves
Wed 7/22	Reschedule Client J.'s recertification	Her BH slot and our recert landed 40 minutes apart across town. I can see our calendar, not theirs. Three calls of phone tag to move one appointment.	Slowed	Phone tag; told her to keep proof of the change
Wed 7/22	Print verification checklist	The shared-drive checklist is three versions old; the current one lives in an email attachment.	Minor	My own printed stack, updated by hand
Thu 7/23	Housing status check for Client J.	No visibility into the housing queue. She asked where she stands; I expected a status screen; the phone line I reached cannot see the queue either. Nothing to tell her.	Blocker	Emailed a housing contact; flagged urgent, like every case
Fri 7/24	Intake, returning client	Her 2024 file is archived and unlocking it needs a supervisor override, so I ran the full history script again. Is there a reason she has to repeat this here? I could not tell her, or myself.	Slowed	Wrote see-prior-file in the notes
Fri 7/24	Benefits data correction	The portal bounced the case because intake says Ave and the portal wants Avenue. I expected validation to fix it; it just rejected the record.	Minor	Retyped the address
Mon 7/27	Case review — Client J.	A missed appointment at another program surfaced in our record as a no-show flag, no context. She has kept every appointment with us. How many misses like this start as two programs booking the same morning?	Blocker	Free-text note that the flag is not ours
Mon 7/27	Referral follow-ups	Two of last week's faxed referrals had no confirmations. I called; one was never received.	Blocker	Re-fax plus a standing Thursday call-back reminder
Tue 7/28	Morning-slot booking	The client can only do mornings; the scheduler releases mornings in an overnight batch. I expected to book while she was on the phone; instead, call back tomorrow.	Slowed	Post-it to call her when slots drop
Wed 7/29	Monthly numbers for supervisor	I combined exports from three systems in a spreadsheet I maintain manually.	Minor	The template I made myself last year
Thu 7/30	Document intake, walk-in	Scanner down; the copier defaults to the wrong tray. Fifteen minutes of a client's bus-fare morning re-copying papers we already hold somewhere.	Slowed	Photographed them with the desk tablet

Two entries described a shared contact tracker built by a colleague as helpful.

Ranked friction themes

All 87 entries across six loggers, ranked by theme count:

Re-keying is the workday's background hum — one intake, three systems. Status visibility is what staff cannot answer when a client asks where things stand. Unconfirmed referrals fail silently; scheduling runs on phone tag; timeouts eat finished work; the rest are papercuts, paid in minutes.

Workarounds as warning signs

Waste map by process stage

All 87 entries, grouped by process stage:

• Intake — 26 entries. Re-keying and repeated histories; prior records locked or siloed.
• Eligibility — 17 entries. Timeouts, validation mismatches, re-collected documents.
• Referral — 25 entries. Unconfirmed faxes, no queue visibility, routing by personal contact.
• Scheduling — 19 entries. Cross-program collisions, phone tag, overnight slot release.

Friction concentrates at the seams between programs — referral plus scheduling are 44 of 87 entries — the same seams clients cross with the least help.

Findings & recommendations

Candidate fixes by severity removed versus effort to implement (analyst judgment):

Limitations & quality self-check

• Under-logging of normalized friction. About 1.4 entries per logger-day, far below the ~8.4 failures per shift observed in comparable frontline work (real background: Tucker & Spear 2006); the log is a floor, not a census — friction staff no longer notice goes unlogged.
• Participation skew. Six volunteers, two sites; the most burdened staff may have logged least; severity is self-rated.
• Staff-side view only. This log mirrors the client's experience but cannot see it; pair with client-side methods (journey mapping, exit intercepts) before acting alone.
• Unknowns preserved, unresolved. The log wonders at three questions; this synthesis leaves them open: "Which retellings are legally required and which are habit"; "What information can travel with consent today"; "Which missed appointments could be prevented by sequencing". Answering them requires a records-and-consent review, not more logging.

Setup

Fifteen volunteer staff kept a two-week HR1-tagged friction log from January 18–31, 2027. The group included benefits eligibility, Customer Relations, behavioral health, CPS, and Workforce Development or referral staff. They logged a moment only when the system made the work harder: expected action, what happened, workaround, minutes, process stage, and whether a client outcome was still unknown.

Staff used non-identifying case keys and never copied notices, diagnoses, immigration documents, case numbers, or client narratives into the log. Supervisors could see patterns but not individual logger identity. The readout evaluates systems and ownership, not worker performance.

For every alternative pathway, the shared outcome ladder was offered → contacted → enrolled → service received. A log entry could mark only the rung staff could actually confirm.

Janice's case thread uses the same dates as the mobile diary, journey map, and QSR. It begins in the log when her submitted SNAP proof shows “received” January 18 and continues through her January 28 Medicaid renewal submission. Later restoration and service outcomes were appended to the readout from the shared continuity record, not counted as friction entries.

Raw log excerpt

Date / role	Expected	What happened	Workaround	Minutes
Jan 18 · Benefits	Confirm whether J-P03 proof matched	Local note said submitted; state view said received; neither showed match or acceptance	Worker opened both views and queued a callback	22
Jan 19 · Customer Relations	Explain one next step	SNAP and Medicaid notices used different household and exemption language; neither said her SNAP status is what excludes her from the Medicaid rule	Handwritten two-column explanation, then policy-lead check	31
Jan 20 · Behavioral health	Route minimum necessary provider evidence	No named role could say which channel would preserve receipt and consent, or whether the required ex-parte check had already been run	Secure message plus telephone confirmation	37
Jan 22 · Benefits	Check unmatched proof before action	Closure queue did not surface the January 18 receipt	Manual escalation after SNAP displayed closed	46
Jan 22 · Referral	Send food option and confirm next step	Directory recorded a phone number but no accepted referral status	Worker called the resource and set a Jan 23 contact	18
Jan 24 · Referral	Confirm service outcome	Referral record had no field beyond “sent”	Free-text note recorded intake and groceries received	12
Jan 27 · CPS	Coordinate benefit and treatment dates	CPS view did not show coverage uncertainty or provider-document deadline	Cross-program call; calendar copied into case note	29
Jan 28 · Benefits	Submit Medicaid renewal packet	Document names differed between provider, local, and state views	Manual rename-and-index checklist	34

The excerpts show competent staff creating shadow infrastructure: two-column explanations, calls to confirm transmissions, manual calendars, and free-text referral outcomes. The failure unit is the workflow, not the person who used the workaround.

Ranked friction themes

All 76 entries, with one entry assigned to its primary theme:

Proof status and affected-status identification account for 32 of 76 entries. That concentration does not mean those failures are most common across DCHS; it means they were most often logged by this volunteer group during this two-week affected-cohort window.

Workarounds as warning signs

Workarounds are evidence of protective staff capacity: people notice a gap and keep the case moving. They are also unsafe infrastructure. A process that succeeds only when a particular worker remembers a direct number, personal spreadsheet, or document-name convention will fail unevenly under higher volume.

Waste map by process stage

Stage 4 had the largest entry count, while Stage 3 consumed the most recorded time. Stage 6 appears smaller partly because staff systems could not see whether a client received outside help; missing outcome visibility suppresses the log itself.

Findings & recommendations

Every proposed response below has an operational owner and a measure. The fixes concern identification, evidence movement, outreach, continuity, and referral completion within DCHS's role.

The first 30-day test should focus on definitions and two low-technology workflows: a maintained HR1 screen and a standard proof-status checklist. If staff cannot use those consistently, a new dashboard will reproduce the ambiguity at greater cost. Pre-closure review and the alternative referral states should be tested alongside them.

Limitations & quality self-check

• Under-logging is expected. Seventy-six entries are a floor. Staff stop noticing routine friction, forget during peak volume, or avoid logging a problem that feels risky.
• Volunteer and role bias. Fifteen staff do not represent every site, shift, function, or contractor. Customer-facing roles may log more visible failures than policy or data teams.
• Staff-side evidence only. A log cannot establish what a client understood, submitted, or received. It needs mobile, interview, journey, and case-review evidence.
• Outcome visibility shapes counts. A referral failure that no system can see may produce no entry. Low counts at Stage 6 are not evidence of a reliable transition.
• Eligibility evidence stays distinct. Treat a worker's uncertainty or workaround as operational evidence; eligibility and exemptions require an authorized determination.
• Unknowns preserved, unresolved. “Whether proof can be matched ex parte before staff ask her to submit it again.” “Which alternative services remain usable after a benefit ends, and whether she actually receives them.” These require system testing and record evidence beyond the log.
• Quality checks. Non-identifying case keys; system-focused language; anonymous readout; every recommendation has an owner and metric; shared Janice dates reconciled; all fabricated counts marked.