Moving from Senior/Lead Engineer into an Engineering Manager and later Enterprise Architect role changed less about what I know and more about what I’m accountable for. A few of the shifts that took longest to internalise:
Your output is the team’s output, not your commits#
The instinct to jump in and fix something yourself doesn’t go away — it just becomes the wrong default. The higher-leverage move is almost always unblocking whoever’s already working on it, or fixing the process that let the blocker happen in the first place.
Architecture decisions are now permission decisions#
Reviewing a design isn’t just “is this technically correct” anymore. It’s “does this fit the team’s actual capacity, does it create a dependency we can’t support in six months, and have we told the people downstream of this decision that it’s happening.” Technical review and organisational review became the same review.
Weekly reporting is a communication tool, not a status update#
Writing a weekly summary for stakeholders used to feel like overhead. It’s actually the cheapest way to catch a misalignment before it becomes a missed milestone — if you can’t summarise the state of a project in five sentences, that’s a signal the project’s scope or ownership is unclear, not a writing problem.
Mentorship is a scheduled commitment, not a byproduct#
As an engineer, mentoring happened opportunistically in code review. As a manager, if it isn’t on the calendar, it doesn’t reliably happen — 1:1s, pairing sessions, and deliberate stretch assignments needed to become recurring, protected time rather than something squeezed into whatever was left over.
None of this makes the engineering background less relevant — if anything, being able to read a design doc or a stack trace quickly is what makes the management judgment calls faster. It just stopped being the job itself.
