The Broken Arm Breakthrough: A Case Study in Delegation

In the autumn of 2023, the software engineering team at Apex Retail in Bristol faced a silent productivity crisis. Sarah, the engineering manager, had always wanted to lead by example. However, her method of leadership involved reviewing every single line of code. She did not let her engineers merge any pull requests without her final sign-off.

This intense approach began to make the developers lose their motivation. Highly skilled engineers like James and Olivia felt that they lacked the autonomy to deploy even the simplest features. Sarah thought this level of extreme control would help her oversee the project's quality, but it only served to spread her too thin.

James recalls that during their weekly one-on-one sessions, the main agenda item was always the massive pending queue of pull requests. "We spent hours discussing minor talking points," James says. "Sarah wanted to set the bar incredibly high, but she was looking over our shoulder constantly. It felt like she didn't entrust us with anything."

As a result, the team's deployment speed dropped by forty percent. Olivia tried to persuade Sarah to adopt a more hands-off approach, but Sarah believed her active daily involvement was necessary to maintain the correct technical direction. She simply could not bring herself to step aside and let the team run with their own ideas.

Then, a dramatic shift occurred. While cycling through the scenic Clifton Downs in Bristol, Sarah fell and severely broke her right arm. With her arm in a heavy plaster cast, she literally could not type for six weeks. This unexpected physical limitation forced her to change her management style completely overnight.

Suddenly, Sarah could not physically review every single line of code. She had to allow James and Olivia to make their own technical choices on the fly. She had no choice but to entrust the codebase to them and expect them to handle the deployment. She had to enable them to act on their own discretion.

To prevent any major errors, Sarah worked with the team to establish clear guardrails. They defined which critical updates required her verbal sign-off and which ones the team could hand off independently. This healthy structure encouraged the developers to focus on outcome over output and take ownership of their engineering decisions.

The results of this accidental experiment were astonishing. Without Sarah checking up on them constantly, James and Olivia found the freedom to move faster. Morale soared, and the backlog of tickets quickly disappeared. The broken arm had forced Sarah to step aside, which ultimately helped the team achieve their true potential.

When the plaster cast finally came off, Sarah realized she did not need to return to her old, stressful ways. She had learned to trust but verify. "It took a broken bone to make me realize how much I was micromanaging my engineers," she admitted. The Bristol team now enjoyed the true autonomy they had deserved all along.

Read again and choose the right answer

Why did Sarah review every line of code initially?

• She wanted to lead by example.
• She did not trust James's skills.
• The company policy forced her to do it.

What was the main agenda item during James's weekly one-on-ones?

• Planning the next sprint goals
• Discussing the pending queue of pull requests
• Reviewing the team's budget issues

What forced Sarah to adopt a hands-off approach?

• A direct command from her director
• A complaint from Olivia and James
• A physical injury that prevented her from typing

What did Sarah do to prevent errors after she stopped reviewing all code?

• She hired external consultants to help.
• She established clear guardrails with the team.
• She made James sign off on every single change.

Sources: photo by Mikhail Nilov on Pexels