Home About Experience Projects Case studies Resources Articles Briefs Playbook Tools FAQ How we start Security Get in touch

Case study 07

The first month operations reset

Confidential engagement, described by its shape. Every image and file on this page is rebuilt with invented data.

All case studies · 07 of 15

Case study 07

The first month operations reset

WhereA small professional-services team running a few dozen client accounts; details changed
RoleRemote operations and project management, acting as chief of staff across a wide time-zone gap
ScaleUnder 10 people; a few dozen client accounts, most of them active at once
StackTask boards, a shared file store, spreadsheets, scheduled scripts, email

In one month, a team with no written procedures got 15 to 25 of them, one status standard on every board, a meeting pipeline that no longer drops calls in silence, an automated hours ledger, and a weekly client health page that leadership reads instead of builds.

When I arrived, recurring work lived in people's heads and in screen recordings. Status meant different things on different boards, and only about one in four tasks owned by leadership carried any status at all. An automation that turned meetings into tasks was missing most calls without raising an error. Recordings had stopped reaching the file store, and nobody owned that. Client hours were reconciled by hand from monthly exports, and recurring client reports from people who had moved on had no owner.

I built it in seven layers.

Visibility. A weekly team digest, a reminder engine, a daily task health report, and a short end of day note.

Standards. One status field, a comment line and a critical flag added to every board in a single day, a template board for new work, an automatic status sweep, and written task rules.

Pipelines. A daily end of shift audit of every recording (filed, indexed, turned into a task), an audit tracker, and rule fixes written up for whoever owned the automation.

Money and time. An automated client hours ledger, run beside the manual method until the two agreed, with each client's hours task updated weekly.

Client Hours Ledger, OVERVIEW tab

ClientPurchasedUsedBalance
Alder12047.5072.50
Basalt8019.7560.25
Cedarline (flat fee)6017.7542.25
Dolomite10047.0053.00
Fernworth4016.2523.75
Total, all 8 clients615223.50391.50
Used =SUMIF(DETAIL!$B$2:$B$121,A6,DETAIL!$E$2:$E$121)  Balance =C6-D6  Check =SUMPRODUCT(C6:C13-D6:D13-E6:E13) must read 0

Task Health Dashboard, PERFORMANCE tab

OwnerOpenOverdueClosedOn time
Sarah Tellwick1671687.5%
David Rooker1341675.0%
Megan Fairhall1131675.0%
Chris Dunmore2061788.2%
Rachel Ostley2881593.3%
James Welford1751080.0%
Total (5 open have no owner)110339083.3%
Overdue =COUNTIFS(RAW!$D$2:$D$201,"Sarah Tellwick",RAW!$H$2:$H$201,"",RAW!$G$2:$G$201,"<"&DASHBOARD!$B$5,RAW!$G$2:$G$201,"<>")

Knowledge. An SOP library on one approved template, a department taxonomy and an ID scheme, filled from walkthroughs as duties were handed over.

Reporting. An automated weekly one-page client health rating for leadership, with every reference linked.

Weekly Client Health demo page: one line per client with a red, amber or green rating, the driver, the next step, the owner and the partner ask
Weekly client health: one line per client
Task Health Dashboard DASHBOARD tab: 200 tasks, 110 open, 33 overdue, 83.3% closed on time, with counts by status and overdue by person
Task health: counts recalculate from the raw export
Pipeline Audit Tracker Summary tab: 40 meetings audited, a 25% gap rate, and gap rate by type with a trust verdict and a draft rule
Meeting pipeline audit: gap rate by type

Click any image to see it full size. Every file here is rebuilt with invented data.

Client work taken over. Weekly and monthly client analytics, a month-end close, and a competitive price study.

The results, in bands. Status fields went onto every active board within one day, up from about a quarter of leadership tasks. A gap of about three in four client calls was found and covered the same day while the automation was fixed, and a few dozen missed tasks were backfilled. The weekly client health page became a scheduled send, and my part shrank to review. Monthly reshaping of hours became an automated weekly pull. The price study grew from a handful of seed rows to 100 to 150 checked rows across 30 to 40 competitors. Several inherited reports went out on schedule after handover, each with its own SOP.

What went wrong

Plenty, and each slip sits with the system it belongs to: the transcript filing in case study 08, the re-check rounds and the image slip in 09, the flipping test switch and the inbox clutter in 11.