Our leadership team frequently debates subjective feelings during Level 10 Meetings about whether projects are on track. How do we convert soft operational sentiment into hard weekly Scorecard measurables?

Question

Tyler Smith · Accepted Answer

When a leadership team runs on feelings, meetings disintegrate into endless debates about whether delivery feels rocky or a department feels slammed. The phrase running on data within EOS means converting soft operational sentiments into objective, binary truths that fit on a Scorecard.

To convert subjective friction into hard weekly numbers, follow these direct substitutions:
- If operations says projects feel off track: Replace the sentiment with percentage of active client milestones delivered on time this week. Set a goal of ninety-five percent.
- If support claims the team is overwhelmed: Replace the sentiment with customer ticket response time in minutes and number of unresolved tickets aging over forty-eight hours.
- If account managers say client sentiment is shaky: Replace the sentiment with client health escalations logged, where any account showing dissatisfaction triggers a measurable incident.
- If engineering claims delivery is slowed by technical debt: Replace the sentiment with weekly percentage of dev capacity allocated to bug resolution versus feature delivery.
- If leaders say employees are disengaged: Replace the sentiment with weekly core value call-outs or employee attendance punctuality rate.

Every emotional complaint in a business originates from an observable friction point. The role of the Integrator is to push past the narrative by asking what specific event happened this week that made you feel that way.

Once you identify the recurring event, quantify it as a weekly number. If the number meets the agreed goal, the team must stop talking about feelings. If it turns red, it gets dropped to the Issues List for IDS without drama.