Module 6 — Metrics That Matter · Lesson 6.4
Operating Metrics
Capture latency, negation reuse, AI Employee contribution, customer outcomes
~12 min
What you'll learn
- Read capture latency and use it to choose the next integration
- Track AI Employee contribution as a percentage of team capacity
- Tie throughput metrics to customer-outcome metrics so the team is not optimizing in a vacuum
- Run a quarterly operating-metric review that closes the loop on the full course
Input metrics tell you about discipline. Throughput metrics tell you about flow. Operating metrics tell you about whether the whole system is producing what it exists to produce. This lesson is the last layer — the metrics that, taken together, are the closest thing the team has to a single question of 'is this working.'
Capture latency — the conversation-to-task loop
Capture latency is the median time between an in-conversation commitment and the task appearing on the board. It is the metric that tells you whether the capture pipeline is functioning end-to-end.
A healthy workspace runs at under 10 minutes for chat-originated commitments (the agent's scan cadence) and near-zero for commitments made directly to the AI agent. Email-originated commitments are slower (the integration sync cadence applies), usually under an hour. Anything substantially slower is a sign the agent's scan is not running, an integration is broken, or member ACLs are blocking the agent from seeing the surface.
The action when capture latency climbs: check the agent's scan logs and the integration health on /settings. The most common cause is an integration whose OAuth token has expired silently. The metric catches it before the team notices the missed commitments.
Negation reuse rate — operating discipline
Module 5.4 introduced negation hits. The operating-layer view of the same metric is rate-of-reuse — how often per week, on average, do the workspace's Negations get cited?
A workspace running a healthy operating cadence will produce dozens of negation reuses per quarter. The number itself is not the goal; the trend is. Falling reuse means either the team is hitting fewer boundary-adjacent situations (possible but rare) or the discipline of citing has degraded (more common).
The action when reuse falls without an obvious cause: surface it in the quarterly retrospective. The team has probably started accepting work that the Negation was supposed to deflect, and the slippage is invisible because the dismissals stopped happening.
AI Employee contribution — what fraction of capacity comes from personas
As personas become first-class assignees, the question 'how much of the team's capacity is coming from AI Employees vs. humans' becomes a real operating metric.
The metric: total estimated hours of completed work assigned to AI Employees divided by total estimated hours across all assignees, per sprint.
The healthy trajectory for a team using personas well is rising over time, plateauing somewhere between 20% and 50% depending on the team's work mix. Higher fractions mean the team has successfully scoped personas to take real load; lower fractions, while not unhealthy, mean the personas you've stood up are not yet absorbing the work they were intended to.
This is also the metric that justifies the cost. Persona usage shows up in usage-events with token + active-CPU breakdowns. The operating question is: are the hours absorbed worth the inference cost? At a workspace level, AI Employees are earning their keep when their absorbed-hours-per-dollar is comparable to human capacity at the same skill level.
Time-to-first-real-task per member
An underappreciated operating metric: how long does it take, from invite, for a new member to ship their first real task in the workspace?
A healthy onboarding is under one week. Slower onboarding means the workspace's KVN is opaque enough that the new member spends days figuring out what 'good' looks like, or the assignment system isn't routing appropriate work to them (no declared skills yet, no learned history). Both are fixable.
The metric is also a useful customer-acquisition signal for the workspace itself. If you bring a new client team into a multi-tenant workspace, their time-to-first-task is a leading indicator of whether they'll engage long-term. Below a week and they tend to renew; above two weeks and the relationship is at risk.
Project Vision hit rate — outcomes finally
All of the above is internal. The single most important outcome metric is the project Vision hit rate: across recently closed projects, what fraction shipped what their charter V said they would ship?
Kavanah's close-out flow includes a confirmation against the V (Module 5.2). A close-out memo notes which parts of the V were met, which were partially met, and which were dropped. The aggregate of this across closed projects is the hit rate.
A healthy hit rate is above 70%, with the misses concentrated in clear categories (scope cut by stakeholder, requirement learned mid-project, technical infeasibility discovered). A hit rate below 50% across many projects means project V's are being written aspirationally — the team isn't honestly stating what they intend to ship.
The action when hit rate drops: tighten V-writing at kickoff. The agent's KVN generator can be set to bias V's toward what historical projects of similar shape actually shipped, not what the leadership wished for.
Customer-outcome ties — the link to revenue
The last metric is the link between work metrics and customer metrics. Whatever your team's customer-side outcome is — retention, ARR per seat, NPS, support resolution time — tie it to the projects that were meant to move it.
Kavanah's portfolio surfaces a per-project tag for customer outcome. When a project closes, the team records (or the agent infers) which customer-outcome metrics it was intended to move and the observed delta on those metrics in the following quarter. Over many projects, this produces the team's project-to-outcome conversion rate: of projects you committed to as outcome-moving, what fraction actually moved the outcome.
This is the meta-metric. It is slower than every other metric in the dashboard (outcomes lag); it is the most subject to confounds (other things move outcomes); and it is the only metric whose answer ultimately decides whether the team's work was worth doing.
Build the operating dashboard
- 1
Confirm capture latency, negation reuse, AI Employee contribution, and project V hit rate are surfaced.
- 2
Tag each active project with a customer outcome
Use /portfolio per-project metadata. The tag is what enables the project-to-outcome metric.
- 3
Schedule a quarterly operating-metric review
60-minute slot. Leadership + project leads. Read all six metrics; produce concrete action items.
- 4
Close the course by writing your team's three north-star metrics
From the lists in this module, pick three. One people, one work, one operating. Those become your standing scoreboard.
Operating metrics
- Capture latency (median)
- Time from in-conversation commitment to task on board.
- Healthy signal: Under 10 minutes for chat; under 1 hour for email.
- Negation reuse rate
- Negation citations per week, workspace-wide.
- Healthy signal: Stable or rising. Falling without obvious cause is a red flag.
- AI Employee contribution
- Fraction of estimated-hours completed by AI Employees over total estimated-hours completed.
- Healthy signal: Rising over time; plateau between 20–50% depending on work mix.
- Time-to-first-real-task
- Median days between member invite and their first shipped task.
- Healthy signal: Under 7 days.
- Project V hit rate
- Fraction of closed projects whose stated V was substantially met.
- Healthy signal: Above 70%.
- Project-to-outcome conversion
- Fraction of projects tagged with a customer-outcome target that moved the outcome in the following quarter.
- Healthy signal: Variable; the trend matters more than the level. Rising over years is a sign the team is learning to commit to projects that matter.
Key takeaways
- ·Capture latency is the health check for the conversation-to-task loop.
- ·Negation reuse rate is the health check for boundary discipline.
- ·AI Employee contribution justifies (or fails to justify) persona investment.
- ·Project V hit rate is the most honest outcome metric the team can produce internally.
- ·Project-to-outcome conversion is the link to revenue — slow, confounded, and the only one that finally matters.
This is the dashboard. People, work, operating — three to six metrics per layer, each with a concrete action attached. Run them, watch them, revisit them quarterly. The course is done; the practice is yours. Open /workspace-kvn and start with the charter, and the rest of the system will earn its place on the team.