Where should AI land first?
Wherever the workflow says, not wherever the demo lands. A 1–2 week assessment that maps the difference.
For CEOs and GMs deciding where AI should land first.
Diagnostic scope fixed before kickoff. Pricing set at the discovery.
Most AI rollouts that fail were misrouted at the start. The team that picked the platform was not the team that did the work. The pilot that launched was not the workflow most worth changing. The Workflow Diagnostic exists to fix the order: map your team's actual work before the platform decision is made.
Licensing AI and using it are not the same thing. In an independent survey of employees with Microsoft 365 Copilot access, just 35.8% actively use it.1 The diagnostic surfaces who is actually using it, which workflows fit them, and which ones need different tools or different change support.
1 Microsoft 365 Copilot workplace conversion rate: the share of employees with workplace access who actively use it. Source: Recon Analytics, AI Choice 2026: Why Licenses Don't Equal Adoption (February 2026), an independent survey of 150,000+ U.S. respondents.
Microsoft Research's own GitHub Copilot RCT (n=200+, randomized) found engineers self-reported time savings that telemetry did not corroborate.6 The diagnostic measures the workflow that ships work, not the vendor's productivity claim.
Two scopes
Founder's Edition
1 week, single function. Built for SMEs and founders who want a clear answer on one workflow.
1 week · single function
Standard
2 weeks, multi-function. Built for organizations evaluating where AI should land across two or more functions.
2 weeks · multi-function
What you get
A workflow map. Each task sorted into three buckets (absorb, assist, avoid) with a change-effort estimate for each.
Frameworks applied
AI risk standards — NIST AI RMF and ISO/IEC 42001 frame the risk read on every task, flagging where regulated data, customer decisions, or compliance-critical processes change the answer.
Workflow analysis methodology — The AI-Workflow-Fit Diagnostic sorts each task into absorb, support, or stay-out, with Lean Six Sigma DMAIC and Value Stream Mapping principles underneath the mapping for ops-heavy workflows.
Cynefin Framework — The sense-making layer beneath the three categories. Clear and Complicated tasks are where AI absorbs, Complex is where it supports, and Chaotic or high-stakes Complex is where it stays out.
Jobs to Be Done — Sharpens the workflow read with one question: what job is the worker actually hiring AI to do? It resists fashion-driven automation and surfaces the jobs people care about but rarely articulate.
6Microsoft Research, GitHub Copilot randomized controlled trial — n=200+ engineers, randomized. Telemetry showed no measurable productivity improvement, despite engineers self-reporting time savings (2024).