Evidence and Methodology

84%of regular participants improved.

+129%largest individual shift on a skill capability.

15,000+decisions scored across 1,088 sessions.

375+reads per person, inside the 39-day window.

Advanced engineering team · each person measured against their own opening baseline

Behavior change, observed

A few minutes a day changed how this team asks.

Over the cycle, their questions got sharper, the raw material of better decisions.

+143%

more of the team’s questions asked why, up from 1 in 17 at the start to 1 in 7 by the final weeks.

+67%

more asked the harder questions that link evidence, test another view, or trace a cause, up from 1 in 5 to 1 in 3.

In the real world

Leaders used it. People noticed.

Wingbrace's chief operating officer used the deep dive reports in mid-term performance reviews. Its program manager reports people doing better in the company's own communication exams, and people getting excited and paying attention.

The exam and engagement observations are Wingbrace's own. RCM ThinkLabs did not measure them.

Calibrated for each client

You get an experience tuned to your team by a Forward Deployed Engineer, not off the shelf.

The proof: a manager privately flagged one dimension for one engineer at Day 0, and the platform, never shown that note, found the same dimension on its own partway through the cycle.

That engineer's signal on the dimension rose 58%.

Manager intuition, independently confirmed, then developed. That is the loop.

Customer story

One engineering team, in eleven minutes.

How an advanced engineering team used RCM ThinkLabs, and what changed for them. The voices are AI-generated, made with Google NotebookLM.

11 min · AI-generated audio · Open on YouTube

How this was measured

Behavior, not self-report.

Every figure above is scored behavior inside real sessions. Capability measurement taken the same way every session, which is what makes a trend line worth reading.

VoluntaryNobody was mandated
LongitudinalTrajectories, not snapshots
SeparateRead without the manager’s notes
BaselinedAgainst each person’s own start

The method, in four steps. A capability model is defined up front with the client and written as observable behaviors. In each micro-session, every choice becomes a signal against that model. Each person’s later behavior is compared with their own opening baseline. The read is produced without access to the manager’s notes.

Capability definitions. The capabilities measured, and how they map to Specification, Verification and Conviction, are set out in the capability model.

How a deployment runs

First the baseline. Then mastery.

IOC Initial Operating Capability

Every skill enters at a measured baseline.

FOC Full Operating Capability

Then it compounds to mastery, skill after skill.

The path between is the deployment. Establish your baseline →

Common questions

Does RCM ThinkLabs actually work? In production with an advanced engineering team, 84% of regular participants improved, at 70% voluntary daily engagement, against a corporate norm of 5 to 25%. The largest individual shift on a single skill capability was +129%. Over the cycle the team's questions measurably sharpened: 143% more asked why, up from 1 in 17 to 1 in 7, and 67% more asked the harder questions that link evidence, test another view or trace a cause, up from 1 in 5 to 1 in 3.

How were these results measured? Every figure is scored behavior inside real sessions, not self-report. Participation was voluntary rather than mandated, the data is longitudinal rather than a snapshot, each person is measured against their own opening baseline, and the read is produced without access to the manager's notes. 15,000+ decisions were scored across 1,088 sessions.

What does the calibration result show? A manager privately flagged one dimension for one engineer at Day 0. The platform, never shown that note, independently identified the same dimension partway through the cycle, and that engineer's signal on the dimension then rose 58%. Manager intuition, independently confirmed, then developed.

What is the difference between Initial Operating Capability and Full Operating Capability? Initial Operating Capability is where a team starts: every skill enters at a measured baseline. Full Operating Capability is what it compounds into, skill after skill, as practice recurs and nothing resets. The deployment is the path between the two, and the compounding is the point.

Keep reading

Ask us anything about the method.

We walk through the data and the definitions on the call.

Request an executive briefing → Assess AI workforce readiness