1. Insights
  2. POV

POV3 min read

Seats logged in is not adoption

Track accepted management work, evidence quality and total effort alongside AI usage. A practical point of view on evaluating a recurring workflow.

Conceptual illustration for Seats logged in is not adoption.
Editorial illustration
Article link

Evaluate an AI rollout through management work that people accept and use, while treating logins and tool activity as evidence of access rather than proof of business value.

Define the work before counting usage

A manager needs to know what the team can now do better. Choose a recurring decision or deliverable with a known reviewer: an operating brief, a growth recommendation or a capacity plan.

Record what makes the output acceptable before the pilot. Its evidence must be traceable, uncertainty visible, options comparable and the next commitment subject to approval. Apply the same criteria to each attempt so the team can compare useful work.

Keep the whole effort in the baseline

Preparation time alone is incomplete. Include source checking, review and rework, then record waiting separately. A faster draft can create more work for the person accountable for the result.

Compare equivalent tasks under the same acceptance criteria. Record errors, rejected outputs and corrections as well as useful ones. Changes in task difficulty, reviewer or input quality can explain an apparent improvement.

Follow the decision through the five steps

In the Upskill Decision Loop, Signal establishes the baseline; Structure identifies where effort and judgment enter the work. Options compares approaches, Pilot bounds the commitment, and Measure decides what the observed evidence supports.

An accepted answer is one checkpoint. Whether the team kept it, reused it or changed an approved decision is a separate question. Do not turn activity into an outcome simply because it is easy to count.

Make the value claim conditional until measured

The AI workflow measurement guide uses a sample baseline of 90 minutes of preparation plus 40 minutes of review and rework: 130 minutes in total. An AI-assisted attempt takes 45 minutes to prepare and 95 minutes to review and correct: 140 minutes. Faster preparation can still mean more total effort. Use this example to design your own scorecard, then measure accepted work.

If the real pilot reduces total effort while maintaining accepted quality, record that result with its limits. If review grows or the work is rejected, revise or stop. Released time is not automatically cash saved, and a small pilot does not establish a general productivity claim.

Your next Decision Loop

Start with a question worth working through.

Adapt this starter to your own context. Copy or download it, then paste it into a conversation in the App.

Explore the related example
Download starter

Start free in the App