MR People Team — Workflow Analysis
This directory summarizes the diagnostic and design work CMPRSSN did on the MR People team before your embed. These docs answer: how does the team actually work, what's broken, what should be automated, and what's the end-state vision.
Documents
| Doc | What it covers | Read when |
|---|---|---|
| workflow-mapping-question-bank.md | The discovery instrument: every question to ask, every workflow to map, organized by operator | You're sitting in a workflow and need to understand why it works the way it does |
| gap-analysis.md | The diagnosis: four-pillar scoring of the People team, prioritized gaps, optimization potential ($250K/yr midpoint) | You need the strategic context for why certain automations were prioritized |
| automate-vs-backfill.md | The staffing analysis of both open People reqs, including your role | You want to understand why the embed exists instead of a traditional hire |
| ai-native-blueprint.md | The end-state vision: domain pods with agent fleets, no processing tier, the People brain, Compression's hand-off plan | You want to see where all of this is heading |
The arc
These documents tell one story in four parts:
- Question bank — here's how to map the workflows (the research instrument)
- Gap analysis — here's what we found (Class 0.5 maturity, $250K optimization potential, August API deadline)
- Automate vs backfill — here's why we're embedding engineers instead of hiring administrators (automate the processing, backfill genuine judgment with part-time/contract)
- AI-native blueprint — here's the destination (domain owners + agent fleets, no human processing tier)
Your job is to execute steps 2-4: sit in the workflows, automate the processing core, and help the team own what gets built.
Source files
The full original documents live in brunz-cmprssn/core/clients/madison-reed/work/. These summaries are written for you; the originals are written for the CMPRSSN consulting team and include internal-only framing, pricing analysis, and cone-of-trust material that shouldn't be shared with the client.