EngThrive: Make It Fast and Easy to Do Great Work
This paper introduces EngThrive, a multidimensional measurement and improvement system developed at Microsoft that organizes developer productivity around Speed, Ease, and Quality while prioritizing wellbeing, utilizing a combination of telemetry and surveys to align metrics with genuine outcomes rather than activity.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are the captain of a massive ship. Your goal is to get the ship to its destination as fast as possible. For years, you've been measuring success by counting how many times the crew turned the wheel or how many buckets of water they bailed out. You thought, "More buckets bailed = faster ship."
But then, you notice something strange: The crew is turning the wheel furiously and bailing water like crazy, yet the ship isn't moving any faster. In fact, the crew is exhausted, angry, and ready to jump ship.
This is the problem Microsoft's engineering leaders faced. They realized that counting "activity" (like lines of code or pull requests) was a bad way to measure if their developers were actually doing great work.
This paper introduces EngThrive, a new way to measure productivity that treats software engineering like a living ecosystem, not a factory assembly line. Here is the simple breakdown of how it works.
The Big Mistake: Counting the Wrong Things
The paper explains that for a long time, companies tried to measure productivity with a single number, like "Lines of Code."
- The Trap: If you pay a writer by the word, they will write long, boring sentences just to get paid more. If you pay a developer by the line of code, they will write messy, inefficient code just to hit the number.
- The "Remote Work" Paradox: During the pandemic, Microsoft saw developers submitting 20% more code. By the old math, everyone was a superstar. But when they asked the developers, "How are you feeling?" 78% said they were burned out. The ship was moving fast, but the crew was drowning.
The Solution: The "Speed, Ease, Quality" Triad
Instead of one number, EngThrive uses a three-legged stool. If one leg is short, the stool falls over. You need all three to stand tall.
- Speed (The Race): This isn't just about typing fast. It's about Idea-to-Customer.
- Analogy: It doesn't matter how fast you paint a car if you have to wait three weeks for the paint to arrive or if the manager keeps changing the color. Speed is measuring the total time from having an idea to the customer actually using it.
- Ease (The Smooth Road): This measures friction.
- Analogy: Imagine driving a car. If the brakes stick, the radio is broken, and you have to fill out paperwork at every red light, you aren't driving fast even if the engine is powerful. "Ease" measures how much time developers spend fighting their tools, waiting for meetings, or fixing broken builds, versus actually building new things.
- Quality (The Durability): This measures if the work holds up.
- Analogy: If you build a house in one day (Speed) with no hassle (Ease), but the roof leaks every time it rains, you haven't been productive. You've just created more work for later. Quality measures how often things break and how long it takes to fix them.
The Guardrail: "Thriving"
There is a fourth element called Thriving. This isn't a goal to maximize; it's a safety guardrail.
- Analogy: Think of a car's speedometer. You can floor the gas pedal to go fast, but if the engine starts smoking and the driver is screaming in pain, you have to hit the brakes.
- If a change makes the team faster but makes them miserable (burnout, bad days), the "Thriving" metric sounds the alarm. The paper found that unhappy developers are 25 times more likely to say they are unproductive and twice as likely to quit. You can't have a fast ship if the crew quits.
How They Measure It: The "Mixed Method"
EngThrive doesn't just look at computer logs (telemetry) or just ask people how they feel (surveys). It combines them.
- Telemetry is like a fitness tracker: It tells you what happened (e.g., "You spent 4 hours in meetings").
- Surveys are like asking the person: "How did that feel?" (e.g., "Those meetings were useless and frustrating").
- Together, they tell the whole story: "We spent 4 hours in meetings, and it felt like a waste of time."
Real-World Examples from the Paper
The paper shares three stories of how this worked at Microsoft:
- The "Meeting" Fix: One team realized developers were drowning in meetings. They set a goal to give everyone more "focus time."
- Result: Developers got 2 extra hours of focus time a week. They didn't just work faster; they fixed old, broken code (technical debt) that had been annoying them. The result? Fewer "bad days" and a 13% boost in actual output.
- The "Gaming" Experiment: One team tried to "cheat" a metric called "Time to First Pull Request" (how fast a new hire submits code) by giving them a tiny, easy task on day one.
- Result: Surprisingly, this worked! Even though they "gamed" the metric, the new hires felt more confident, learned the tools faster, and ended up writing more code over the next year. The "game" forced the right behavior.
- The "Health Days" Experiment: During a burnout crisis, a team gave everyone two unplanned days off.
- Result: Code output dropped for two days (bad for "Speed"). But the burnout relief lasted for months, and the team caught up on all the lost work in just two weeks. Without the "Thriving" guardrail, leaders might have canceled the days off because they looked like a "failure" on day one.
What About AI?
The paper argues that AI is just another tool, like a new hammer or a faster car.
- AI might make people write code faster (Activity), but EngThrive asks: Does it actually get products to customers faster (Speed)? Does it make the job less frustrating (Ease)? Does it break things less often (Quality)?
- The framework works for AI just as well as it works for office buildings, vacation policies, or meeting rules.
The Takeaway
You can't measure a human being with a single number. EngThrive is a system that says: "Let's make it fast, easy, and high-quality to do great work, and let's make sure the people doing the work are happy and healthy while they do it."
It moves companies away from "How many lines of code did you write?" to "How much value did we create, and how did it feel to create it?"
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.