Your first 90 days as a technology leader

The first 90 days in a technology leadership role set the tone for everything after. The pressure to show momentum is real, and the temptation is to announce a grand plan in the first week. Resist it. The plan you would write on day five is based on the org chart, the previous leader's slides and your last job. None of those is the system you now own.

Days 1–30: listen and map

Meet engineers, product, finance, operations and, wherever possible, customers. Ask each group the same few questions: what slows you down, what are you proud of, what would you change first? Then map the real systems — the ones that wake people up at night, the ones only one person understands, the ones everyone works around.

Write down what surprises you. Surprises are where the official story and the real one diverge, and that gap is usually where your first priorities live.

Days 31–60: remove friction visibly

Pick two or three wins that remove friction teams feel every week: a flaky pipeline, an unowned service, an on-call rotation nobody understands, an approval that takes days for no reason. These are rarely strategic on their own, but fixing them proves that raising a problem with you leads to change. That proof is worth more than any slide.

Days 61–90: publish an honest strategy

Now write the strategy — short, specific and measurable. Describe the current state truthfully, name a small number of bets, and say clearly what you will not do. Share it widely and invite challenge before you finalize it.

• Name owners for each priority, not committees.
• Choose a handful of signals you will report on every month.
• Schedule the first quarterly review before you publish.

Clarity builds more trust than ambition. A leader who says "here is what we will do, here is what we won't, and here is how you will know if it is working" gives people something to commit to — and something to hold you to.