Context Theory Get your growth audit

Answer

What changes about managing a team that uses AI?

Output stops being evidence of understanding, review capacity becomes the constraint, and the training route quietly closes.

Three things. Output no longer tells you whether someone understood the work. Review capacity rather than production becomes the constraint. And the tasks people learned judgement from are the ones now being delegated.

The first change is the loss of a signal managers relied on without noticing. A well-structured document, a competent analysis or a clean piece of work used to be evidence that the person understood the problem, because producing it required understanding it. That inference no longer holds, and continuing to make it means assessing people on an output that is now cheap. What still distinguishes is the ability to explain the reasoning, defend a choice, and say what was considered and rejected, which is a conversation rather than an artefact.

The second is where the bottleneck sits. When production was the constraint, adding capacity meant adding producers. When production is fast and review is not, adding producers makes the queue longer. Teams that adopt these tools without addressing review find that throughput does not improve as expected and that quality drifts, because the review that used to be sufficient is now spread across more work. The uncomfortable resolution is that the arrival rate has to match the review capacity rather than the production capacity.

The third is the training problem. The tasks traditionally given to less experienced people — first drafts, initial research, the tedious groundwork — are exactly the tasks now most easily delegated, and they were the mechanism by which judgement developed. A team that removes them gains throughput and loses its pipeline, and the consequence arrives years later when the people who would have been reviewing have not built the judgement to do it. This has no cheap solution and it needs to be a deliberate decision rather than a default.

There is a fourth change that is about consistency. When everyone uses different tools, different prompts and different personal settings, the same task performed by two people produces genuinely different work, and the difference is invisible because it lives in configurations nobody can see. Shared standing context and shared templates address this, and the reason to bother is that unexplained inconsistency between people is expensive to manage.

The measurement question changes too. Output volume was a reasonable proxy for effort and is now a proxy for nothing, so any management practice resting on it needs revisiting. What remains meaningful is outcomes, the quality of judgement in hard cases, and whether the work someone produces holds up when examined. Those are harder to measure and were always the things that mattered.

Finally, the practical management task is different from the technology question. What people need is permission to use these tools openly, clarity about what may not go into them, and an expectation that they can explain what they produced. Those three are ordinary management and they resolve most of what appears to be a technology problem.

A good document used to tell you the person understood the problem; it now tells you a good document exists.

Siddharth Sharma, Context Theory

Related questions

How do you assess someone whose output is largely generated?

By the questions they can answer about it. What did you consider and reject, why this approach, what is the weakest part, what would change your mind. Someone who directed the work can answer those and someone who passed it through cannot, and the difference is visible in a few minutes of conversation.

Should everyone be expected to use it?

Expect the outcome rather than the method. Requiring the tool creates resentment and performative compliance; expecting work of a certain quality at a certain pace lets people find their own route. The exception is where a shared standard matters, in which case the standard is the requirement and the tool is how it is met.

METHOD

Every figure below carries its source and the date it was verified. Nothing on this page is asserted.

The numbers on this page.

Datapoints
What Value Specific to
Sub-15-minute compliance — automated routing vs manual only62.5% vs 39.1%Category-wide
Close rate — response under 5 minutes vs over 24 hours32% vs 12%Category-wide

2026 speed-to-lead benchmark · verified

Optifai speed-to-lead benchmark · n=939 companies · Q2 2025–Q1 2026 · verified

What is specific to this page.

Evidence
Kind Claim Check it against
WorkflowA competent artefact previously evidenced understanding because producing it required understanding, and that inference no longer holds, so assessment must move to explaining reasoning, defending choices and naming what was rejected.Asking the producer of a competent document what they considered and rejected, and comparing across producers.
Buying behaviourWhere production is fast and review is not, adding producers lengthens the queue rather than increasing throughput, so the arrival rate must be matched to review capacity rather than to production capacity.Comparing items produced per week against items reviewed at full depth in the same period.
ConstraintThe tasks that developed judgement in less experienced staff are the ones most easily delegated, so removing them trades throughput now for review capability several years later, with no inexpensive substitute.Listing the tasks previously assigned to new staff and checking which are now delegated to tools.
ResponseDifferences in personal tooling, prompts and settings produce genuinely different work from the same task, and the difference is invisible because it resides in configurations that are not shared or inspectable.Comparing the standing instructions and connected sources two team members are using for the same work.

Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.

Start with the measurement.

Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.

Get your growth audit

$497 · delivered in 5 business days · credited against month one