Evaluating behavioral, managerial, and organizational readiness for AI-driven workflow reinvention — and the one tool the evidence said was worth building.
Across six weeks, BSG ran structured interviews with 11 enterprise workers, 7 managers, and 3 early-career employees — every transcript memoized against a controlled, seven-dimension vocabulary — then scored thirteen hypotheses against that evidence and against Microsoft's own 2026 Work Trend Index.
Microsoft has the usage data, but this engagement adds the layer underneath: why people adopt, hesitate, or disengage, and what the organization can do about it. — Project Overview
No participant's friction was about prompting mechanics. Every barrier was trust, discovery, or governance — and none of it shows up on an adoption dashboard.
Reviews every output. AI drafts, the worker owns all judgment — prompt-and-review.
Delegates a defined task class after testing it, then spot-checks.
Sets the workflow running; audits the exception, not the output.
Twenty-one transcripts, scored against a controlled vocabulary. The heat below reads warm where a dimension diverges by cohort, cool where it holds across all three.
Not an attitude problem — nearly everyone across every cohort is net energized. The bottleneck is structural, and it splits cleanly into four questions.
A probed null is a finding too. Five hold up strongly, three read mixed, two are contradicted outright — and H11 is the one that built Fourier.
Six capabilities, observed in practice across seven manager transcripts. The redesign capabilities — not the encouragement ones — are the ones missing.
Effort and impact are rated per move. Most of the friction here is behavioral — five of seven extend a program that already exists; two are genuine white space.
Programs sold as “reduce anxiety” miss advanced workers, whose worry has moved from competence to standing. Aim the framing at where contribution is recognized.
Extends existingA supervised, recommend-only space to watch AI act before handing over control. Delegation trust is built through reversible testing, not training.
Extends existingCodify “thought partner, not author.” The failure mode workers name is over-delegation, and no current norm names it.
White spaceA catalog of what Copilot can already do, tagged by role. Workers asked for this by name — it moves them up a level faster than more trust content.
Extends existingA structured way for teams to share working AI patterns. Today the best uses spread by accident, one hallway conversation at a time.
Extends existingThe single behavior the Work Trend Index ties to a 17-point adoption lift — and the managers BSG observed don't do it. Currently white space: Microsoft has no interface that makes modeling visible.
White spaceA policy-and-access lane for managers, a time-and-pathway lane for ICs. The binding constraint inverts between them — one playbook can't fit both.
White spaceMost of R1–R7 are norms, manager behaviors, or process changes — software would be the wrong instrument. The evidence pointed to exactly one tool-shaped gap, and it's already built.
Which evidenced gap does it close? Progression is invisible (H11). Every tool measures usage — “Copilot used X times” — but the event that actually matters, a workflow crossing the delegation threshold, goes unrecorded. One manager in the study couldn't even see his own team: “we're too small.”
What actually needs a tool? Almost nothing — which is the point. The single tool-shaped gap is progression visibility: a task→tool finder for individual contributors, and a “did the work actually move up” view for managers.
Fourier is a live Cloudflare app — onboard, add your own tools, and generate a 90-day plan right here.
Open full screen ↗