A sample built on fictional content. Whitlow Ferris Partners is not a real firm and this reflects no real engagement.
An engagement closes. Watch its lessons reach the playbook.
Whitlow Ferris Partners is a fictional management consulting firm working for private-equity portfolio companies. It runs on Microsoft 365, BigTime, HubSpot, and QuickBooks Online, and its method and positions (the playbook, the scoping rules, the case examples, and what each sponsor prefers) have been organized and approved, each with an owner. When an engagement closes, the debrief line reads the debrief notes and the final readout, matches each lesson to the entry it bears on, and proposes the change to that owner with the source attached. Nothing changes until the owner decides. Each step below is the screen a real person would be looking at.
What it is worth
The value in this workflow is how many lessons from a closed engagement reach the playbook, the scoping rules, and the case examples, and how long that takes. The pattern it bears on: a debrief ends at a slide, and the lessons reach a Lessons channel and rarely the playbook. We would measure both on your own last several debriefs. The diagnosis measured proposal development and not this workflow, so we do not put a number on it.
TeamsSearch─ ▢ ✕
ActivityChatTeamsCalendar
Teams
WFWhitlow Ferris Partners
General
Proposals
Lessons
ENG-2611 Beltline
ENG-2634 Tolland
# ENG-2611 Beltline
PostsFiles+
Tuesday, September 22
JH
Jen Halvorsen11:52 AM
Debrief notes from this morning’s call are attached. Sorry these are a month late; the sprint started the Monday after the readout and this was the first slot we all had. The final readout is already in the Engagements folder.
DOCXENG-2611 debrief notes.docx Word · 1 page · shared in ENG-2611 Beltline
Call held Tuesday, September 22, 2026, 11:00 to 11:30. On the call: Jen Halvorsen, Greg Hollis, David Nwosu, Marcus Delgado.
Inventory count cadence. Our week-one data request assumed a monthly count. Beltline does a full physical count quarterly (last one June 30) and cycle-counts the A items, so the module 4 inventory analysis ran off the June count plus receipts and shipments by SKU. Rebuilding it cost us two days in week two. Module 4 should ask the cadence before the data request goes out.
Data readiness. SC-4 caught the fourteen-business-day close and the readiness week was the right call. What we didn’t see coming: the ERP extract is run by an outside IT contractor and took another week after the close. The readiness week covered the close but not the extract.
Outcome. Four weeks into the sprint the working-capital release is tracking at the low end of the readout range, about 9 days of inventory against the 9 to 14 in the readout. The safety-stock reduction on the C items is done; the supplier-terms piece hasn’t started.
Sponsor. Dan told Marcus after the week-three check-in that he wants the sprint steering deck to carry a risk page third, right after the KPIs. His words: the deal team reads the value bridge, the KPIs, and the risks in that order, then everything else.
Nothing changed yet each proposal waits for its owner, with the source passage attached.
Start a post in ENG-2611 Beltline
12:31The diagnostic phase of ENG-2611 closed in August, and the implementation sprint started the next Monday, so the debrief call waited a month. Jen posts the notes to the engagement channel; the final readout has been in the Engagements library since August. The debrief line watches both from inside WFP’s Microsoft 365 tenant: it read the notes and the readout, matched four lessons to the entries they bear on, and posted the card thirty-nine minutes after the notes.
The proposed changes · current text and proposed text
PB-100 v4 · module 4 · the week-one data requestfrom DB-2611, item 1Queued to Priya Raman
Current
Request the monthly inventory count file for the trailing twelve months, receipts and shipments by SKU, and the AP and AR aging at each month end.
Proposed
Ask first how often the company counts inventory. Request the count files at that cadence for the trailing twelve months, receipts and shipments by SKU to bridge between counts, and the AP and AR aging at each month end.
Owner of PB-100: Priya Raman. The engagement, the notes, and the passage stay attached to the entry if she accepts.
PB-100 v4 · module 4 · the data-readiness weekfrom DB-2611, item 2Queued to Priya Raman
Current
Where SC-4 adds a data-readiness week, use it to close the prior month with the controller and reconcile the extracts to the trial balance.
Proposed
Where SC-4 adds a data-readiness week, use it to close the prior month with the controller and reconcile the extracts to the trial balance. Ask in the first week how long the ERP extract takes after the close and who runs it; an extract run by an outside contractor can add a week after the close.
SC-4 itself is not proposed for change. Its trigger fired on the fourteen-day close and was right; the note is to the playbook module that uses the week.
CASE-2611 · the outcome linefrom the readout, slide 4, and DB-2611, item 3Queued to Priya Raman
Current
Identified a working-capital release of 9 to 14 days of inventory at a $62M specialty fastener manufacturer, with the low end reachable from safety stock on the C items alone.
Proposed
Delivered a working-capital release of about 9 days of inventory, the low end of the 9 to 14 identified, at a $62M specialty fastener manufacturer, measured four weeks into the implementation sprint.
The source is a sprint reading at week four, and the proposal says so. Whether that is the outcome is Priya’s call.
SP-2 · Larkspur Ridge Capitalfrom DB-2611, item 4Queued to Marcus Delgado
Current
Larkspur Ridge readouts open on the value bridge and carry the deal team’s three KPIs on page two; Redfield has no recorded preference yet.
Proposed
Larkspur Ridge readouts open on the value bridge and carry the deal team’s three KPIs on page two. On implementation sprints, the steering-committee deck carries a risk page third, after the KPIs (Dan Kowalczyk, September 2026). Redfield has no recorded preference yet.
Owner of SP-2: Marcus Delgado, so this one is queued to him and not to Priya.
Checks · plain code, run when the proposals were drafted
✓ PassedEvery source passage was found where it is cited: DB-2611 items 1 to 4 in the notes, and slide 4 of the final readout in the Engagements library. Not a model’s recollection.
✓ PassedEvery entry matched is the approved version: PB-100 v4 module 4, SC-4, CASE-2611, SP-2. No superseded copy was read.
✓ PassedEach proposal is queued to the owner recorded on the entry: Priya Raman for PB-100 and CASE-2611, Marcus Delgado for SP-2.
⚑ To ownersNothing has changed. Four proposals wait for a decision, each with its current text, its proposed text, and its source. The playbook reads today as it did this morning until Priya and Marcus decide.
12:31This is the page the Teams button opens, on WFP’s own SharePoint. Each lesson sits beside the entry it bears on, the passage it came from, and the owner it is queued to, and the current text and the proposed text are both on the page, so the owner reads both before deciding. Click any source to read the passage.
DecidedPriya Raman · Wednesday, September 23 · 9:12
ACCEPTED, WITH AN EDITModule 4, the week-one data request. Priya took the cadence change and edited the first sentence: “Ask first how often the company counts inventory, and the date of the last full count.” The rest stands as proposed. Written to PB-100 v4 with ENG-2611 and the passage from the notes attached.
ACCEPTEDModule 4, the data-readiness week. The note on ERP extract lead time goes in as proposed. SC-4 stays as written.
SENT BACKCASE-2611. Priya’s reason, kept on the proposal: “The week-four reading is not the outcome. CASE-2611 holds the identified range until the sprint measures at week eight, the week of October 12. Bring it back then with the measured number.”
FORWARDED · ACCEPTEDSP-2 is Marcus Delgado’s entry, so the line queued it to him. He accepted the addition as written at 10:05, and the Larkspur Ridge account summary (ACC-LARK) now points at the changed entry.
PB-100 · changelog · latest entries
Date
Where
Change
Source
Reviewed and approved by
Sep 23, 2026
Module 4 · the week-one data request
Asks the inventory count cadence, and the date of the last full count, before the request goes out
ENG-2611 · DB-2611 item 1
Priya Raman
Sep 23, 2026
Module 4 · the data-readiness week
Note on ERP extract lead time added
ENG-2611 · DB-2611 item 2
Priya Raman
SP-2 · changelog · latest entry
Date
Where
Change
Source
Reviewed and approved by
Sep 23, 2026
Larkspur Ridge Capital
Risk page third in sprint steering decks, after the KPIs
ENG-2611 · DB-2611 item 4
Marcus Delgado
The proposal drafter and the playbook desk read module 4 from the same memory, so the next diagnostic proposal carries the cadence question in its week-one data request, and the next consultant who asks about week one gets the changed module.
✓ Recorded. Two changes written to PB-100 v4 with their changelog entries and the passages they rest on. CASE-2611 held to the week-eight measurement, with the reason on it. SP-2 changed by Marcus Delgado. Every proposal and every decision is logged.
A proposal that is sent back stays on this page with the reason and the date. The line raises CASE-2611 again when the week-eight measurement lands in the Engagements library.
9:12Priya’s Wednesday morning on this: two changes accepted, one of them with a wording edit, one sent back with a date on it, and one forwarded to the entry’s owner. The software read, matched, and proposed, and the owners decided; the playbook changed only where they said so.
Under the hood· what ran, and where everything lives · drawn by Ermetis, not an app─ ▢ ✕
What runs it
The debrief line is software configured in WFP’s own Microsoft 365 tenant.It reads the engagement channel, the Engagements library, and the approved entries under the permissions WFP already set. Nothing about this workflow leaves their environment.
The model reads and matches; code checks.A language model reads the notes and the readout and matches each lesson to the entry it bears on. That every cited passage exists where it is cited, that every entry is the approved version, and that every proposal goes to the owner recorded on the entry all run as plain code.
The honest mechanism
Nothing in the memory changes without the owner’s decision.The line proposes; Priya and Marcus accept, edit, or send back. A proposal that is sent back keeps its reason and its date, and the line brings it back when what it was waiting on arrives.
What gets recorded
Every proposal, decision, and change is logged,with who decided, when, and the passage it rests on. The proposal drafter and the playbook desk read from the same memory the next morning.
This is the whole machine. The notes and the readout land where they always did, one piece of software inside the tenant reads and matches them, the checks are code, the proposals queue to their owners, and the memory changes only when an owner decides.
What this took, in this fictional world
One debrief call and one final readout produced four proposals on Tuesday afternoon. Priya spent part of Wednesday morning on three of them, and Marcus took the fourth. Two changes reached the playbook the day after the debrief, with the engagement and the passage they came from attached. Before this, the same lessons went into the Lessons channel and a slide, and the playbook changed when Priya found the time for it.
The same workflow, elsewhere
At a law firm, this is the matter debrief reaching the precedent bank and the engagement letter template. At an accounting firm, it is the post-busy-season review reaching the engagement checklist and the scoping assumptions. At a marketing agency, it is the campaign post-mortem reaching the brief template and the client preferences file. The pattern is the same: read, matched against what the business has already approved, proposed to the owner, and decided by a person.