Experience evidence refreshed Aug 11 · 14:00 UTC
Engineering effectiveness intelligence
Improve the system.
Engineers move faster.
Connect friction, flow, toil, delivery reliability, platform enablement, and learning health into one executive operating cadence.
Experience indexStrained
61/100
Executive posture
Reduce friction before delivery pressure becomes attrition.
2 interventions · 3 burnout signals · 4 decisions
01 / Team experience portfolio
Engineering health without vanity metrics.
The index joins delivery evidence with human-system signals. Select a team to inspect active rules, top drivers, and the recommended leadership action.
TeamStageTierIndexBlocks
How the Engineering Experience Index is calculated +
Flow efficiency
How much engineering time reaches value-producing work instead of waiting, rework, or coordination drag.
Delivery reliability
Predictability of commitments, release quality, dependency clarity, and delivery confidence.
Developer experience
Tooling friction, local setup, build speed, documentation, cognitive load, and autonomy.
Platform enablement
Reusable paved roads, self-service capabilities, golden paths, and internal platform maturity.
Operational load
Interrupts, support burden, incident fatigue, after-hours load, and unplanned work pressure.
Learning health
Onboarding, knowledge flow, technical coaching, psychological safety, and continuous improvement.
Hard rules: missing transformation owner caps at 54 · critical team with high incident load caps at 47 · burnout signal caps at 59 · five or more blocked dependencies caps at 62 · build loop over 30 minutes caps at 58 · stale evidence gets a 7-point penalty.
02 / Experience system
DevEx improves when leaders manage the system.
Each stage turns vague complaints into evidence, ownership, intervention, and a measurable closure path.
1 team
Discover
Developer research, friction inventory, service ownership, and outcome hypothesis
2 teams
Build
Golden-path adoption, dependency clarity, backlog quality, and platform self-service
1 team
Review
Quality signals, team load, dependency risk, and readiness for scale
1 team
Release
Release confidence, change failure signals, runbook quality, and support readiness
3 teams
Operate
Toil, incidents, support burden, resilience practices, and learning loops
Operating principleMeasure friction. Fund leverage. Protect learning.
The goal is not to inspect engineers. It is to improve the system around them.
03 / Friction & exceptions
Make accepted friction visible.
When teams absorb toil, slow builds, unclear ownership, and dependency wait states, the operating model should show the cost.
Flow efficiency61%
Targeted improvement required
Delivery reliability62%
Targeted improvement required
Developer experience61%
Targeted improvement required
Platform enablement66%
Targeted improvement required
Operational load56%
Material friction gap
Learning health64%
Targeted improvement required
04 / Experience trend
Flow improved, but toil is returning.
Platform adoption improved feedback loops, but incident pressure rose again in the latest week. That makes the next leadership decision a capacity decision.
Jul 06
Jul 13
Jul 20
Jul 27
Aug 03
Aug 10
05 / Executive experience brief
Turn DevEx evidence into leadership action.
The local brief converts the visible synthetic evidence into a concise operating narrative. No model call or API key is required.
DEC-601 · Today
Reset capacity for Settlement reliability
Critical team has high incident load, no owner, and very low experience score
DEC-607 · 48 hours
Fund toil reduction for Security engineering services
Operational load is suppressing flow and delivery reliability
DEC-614 · This week
Unblock API modernization dependencies
Six blocked dependencies are delaying shared integration outcomes
DEC-621 · This week
Expand developer portal golden paths
Highest experience score shows reusable pattern ready to scale