The first layer of the work is the first layer of the learning.
Junior engineers learned by writing the first version, breaking something, and finding out why. Reviews, incidents and small collisions with real systems built the instinct that later made them senior.
AI writes much of that first version now. Output has not slowed, but the experience that turns output into judgment has thinned.
AI helps individuals. The business effect is lagging.
McKinsey's August 2026 State of AI report found that 80% of respondents say AI has improved their individual productivity, while 37% attribute at least some EBIT impact to AI, about the same as a year earlier.
The distance is people: asking the right thing, checking what comes back, and owning the call. In engineering, those are specification, verification and conviction.
Systems thinking, dissent and the habit of checking.
A senior engineer sees how a change moves through the system, says so when the plan is wrong, and does not accept a confident answer without checking it. None of that appears in a ticket count.
These are behaviors. They build through repetition with feedback and fade without it.
Decisions with incomplete information and real tradeoffs.
In RCM ThinkLabs, engineers work through an immersive narrative where characters have their own interests and information is incomplete. There is no script to repeat, so people use the skill.
Each session takes up to fifteen minutes and ends with private feedback. Engineering leaders see through RCM Advisor where systems thinking is strengthening and where it has levelled off, and mentor from there.
What changed for participants.
Wingbrace is an advanced engineering team. Production data over 39 days, measured against each person's own opening baseline, showed more questions that asked why and 84% of regular participants improving on a full read.
Questions about the engineering pipeline
How do you develop senior engineers when AI writes the junior work?
Rebuild the repetitions on purpose. Engineers need frequent decisions with tradeoffs, incomplete information and feedback, which used to come from first-draft work. RCM ThinkLabs supplies them in short recurring sessions and measures systems thinking, dissent and decision quality over time.
What skills separate a senior engineer from a junior one?
Systems judgment: seeing how a change moves through the whole system, weighing tradeoffs, dissenting when a plan is wrong, and verifying answers before accepting them. These are behaviors, so they can be practiced and measured, unlike tenure or ticket volume.
Can you measure engineering judgment?
Yes, from behavior. RCM ThinkLabs scores the decisions people make across sessions against each person's own baseline, and shows leaders where capability is strengthening or levelling off. It measures what people did, not what they said they would do.
Does this replace mentorship and code review?
No. Mentors and reviewers transfer context that no tool holds. RCM ThinkLabs tells them where to look: which engineers are strengthening on which behaviors, so mentoring time goes where it changes the most.
Do the results come from engineering teams?
Yes. Wingbrace is an advanced engineering team. Over 39 days, measured against each person's opening baseline, 84% of regular participants improved on a full read. Results elsewhere will depend on participation and reinforcement.
Sources. McKinsey, The State of AI in 2026: On the Road to ROI, August 2026, 1,719 respondents in 97 countries. Wingbrace figures are RCM ThinkLabs production data from an advanced engineering team, Days 1 to 12 against Days 28 to 39, measured against each person's own opening baseline. If anything here is out of date, tell us and we will correct it.
Rebuild the path to senior. On purpose.
Comparing options? See how RCM ThinkLabs compares with Workera, BetterUp and other alternatives.