Stanford's 77% Rule: Why Most AI Work Is Invisible — And How to Make It Visible

When a founder of a 40-person ops team told me they’d bought Copilot licenses but saw no change in output, I realized the problem wasn’t the tool — it was invisibility.

How do you make invisible AI work visible?

Start by defining what ‘visible’ means in your context. For most knowledge work, visibility comes from artifacts: a generated draft, a cleaned dataset, an automated report. If the AI work doesn’t produce one of these, it’s likely invisible.

Next, create lightweight tracking. Ask champions to log one thing weekly: what they built with AI, what it replaced, and estimated time saved. This isn’t surveillance — it’s creating data where none existed.

Finally, tie visibility to your operating rhythm. Add a ‘AI signals’ line to your weekly plan/fact review: prompts run, automations triggered, hours reclaimed. Over time, this surfaces the 77%.

Manager scan (2-minute digest example)

• Prompts run this week: 142 (up from 89)
• Custom automations built: 3 (0 two weeks ago)
• Estimated time saved: 22 hrs (sales: 8 hrs, support: 7 hrs, ops: 7 hrs)
• Top use case: lead qualification drafts (sales team)
• Gap: marketing team logs 0 AI use despite access

Tool tip (AiAdvisoryBoard.me):

The Plan → Fact → Gap model works because it forces specificity. Instead of asking ‘Are you using AI?’ — which invites vague yes/no answers — you ask: ‘What did you plan to automate this week? What did you actually build? Where’s the gap?’ That contrast reveals whether adoption is real or performative.

Micro-case (what changes after 7–14 days)

A founder of a 35-person professional services firm added a single question to their weekly ops review: ‘What AI artifact did you create?’ Within ten days, champions began sharing prompts and outputs in a shared folder. The founder spotted that while sales used AI for drafting, support had built nothing — revealing a training gap. By week two, support had built their first ticket-triage agent, closing the gap.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

FAQ

How do I know if AI work is truly happening or just performative? Look for artifacts: prompts saved, automations built, outputs shared. If the only evidence is self-reported usage with no trace, it’s likely performative.

Should I require employees to log every AI interaction? No. That creates resistance and inaccuracy. Instead, sample lightly — ask for one weekly example per champion. The goal is signal, not surveillance.

What if my team says tracking AI use feels like micromanagement? Frame it as visibility for improvement, not control. Share the data back: ‘Here’s what we built together.’ When employees see their work reflected, logging becomes contribution, not compliance.

Can I use existing tools like Copilot dashboard for this? Only partially. Native usage logs show license activation, not meaningful work. Supplement them with team-reported artifacts to capture the 77%.

How does this connect to the AI-Champion model? Champions are the source of visibility. Their logs and shared prompts create the observable trace that makes the 77% visible — turning invisible work into measurable progress.

If you want to surface the invisible work your team is already doing with AI — see how the 7-day diagnostic surfaces Plan → Fact → Gap in real time.