essay · 1 min read · originally on LinkedIn

Before you adopt the shiny new thing

#tech leadership#decisions

As a tech lead I get excited about new tools like everyone else. But “it’s cool” has never been a good enough reason to bring something into a codebase other people have to live with.

Before I say yes to a new technology, I ask five questions.

  • Does it solve a real problem for the business, or does it just look good in a demo?
  • What will it cost? Licences, infra, and the maintenance nobody puts in the estimate.
  • Is there a community behind it? If the docs are thin, my team becomes the docs.
  • How much of our existing work has to change to fit it in?
  • Can the team actually learn it in time, or will delivery slow down for months?

When business and developers aren’t in the same room

Most bad tech decisions I’ve seen weren’t bad ideas. They were made by one side without the other.

The business case looks great, but the team can’t adopt it. Money and time go into something that never fits properly. Developers get frustrated because there was no time to learn. A year later you have tech debt instead of the improvement you were promised.

So I try to keep both sides in the conversation from the start. New technology is worth it when it helps the business and the people building with it. If it only helps one of them, I wait.

← back to the log