Single point of failure

Is it a database? → Is it a component? → Is it an API…?

👉 No… it’s a software developer…

👉 A single point of failure can be a disaster for your software system, but when that single point of failure is a developer, it could be a disaster for your whole team and potentially your business...

It might look a bit like this:

Only [Chris] knows how that feature/system works... The rest of the team doesn't understand it and are scared they'll break it if they change it...

[Chris] wants to share his knowledge, but he's just so busy all the time...

The team and business dread [Chris] taking time off - or even worse, handing in his notice.

👉 They don't realise the impact on [Chris].
👉 [Chris] is a "top developer":
→ He stays late,
→ Tackles hard tasks
→ and helps non-tech areas of the team too.

👉 [Chris] doesn't take much time off:
→ He feels pressure,
→ Stress
→ and responsibility for the team - although this might not show.

👉 When [Chris] takes time off, it's short, and he worries things will go wrong at work.
👉 [Chris] doesn't relax:
→ He checks his emails
→ and is distracted by his phone in case work calls.

👉 [Chris] can't go on like this forever... He's not:
→ Recovering
→ De-stressing
→ Relaxing
→ Recharging...

Having a software developer as a single point of failure is a massive business risk, but more importantly, it's disastrous for the wellbeing and performance of your software developer.

👉 How can we help [Chris]?

👉 How can [Chris] help himself?