What I’ve Learned Leading Web Operations as a Senior Engineering Manager
Leading web operations is about much more than shipping code. Here’s how I connect people, platforms and priorities to outcomes.
Managing Web Operations has taught me that engineering leadership is about much more than shipping code. On any given week, I’m balancing people, platforms, business priorities, technical debt, security, analytics, content operations and deadlines, often all at the same time and often all in the same meeting.
When I started managing, I thought the job was to be the best technical problem-solver in the room. It took me a while to realize that the role is something different, and in many ways harder.
My job is not to have every answer
One of the biggest lessons I’ve learned is that my job is not to have every answer. My job is to create an environment where the team:
- understands the goal and why it matters,
- knows who owns what,
- can raise risks early without worrying about how it will look,
- and has enough structure to make good decisions without waiting on me.
When those four things are in place, the team moves faster than I ever could on my own. When they’re missing, even a very talented team spends its energy on confusion: duplicated effort, decisions made twice, and surprises discovered late.
The shift for me was learning to measure my contribution by the quality of the team’s decisions, not by the number of decisions I personally made.
Connecting strategy to execution
I spend a significant amount of my time connecting strategy to execution. That sounds abstract, so here is what it looks like in practice.
A business objective, like improving lead quality or modernizing the website platform, doesn’t stay a business objective for long. Eventually it needs to become:
- an architecture decision,
- an epic,
- a sprint,
- a set of tickets,
- an owner for each piece,
- a QA plan,
- and finally a measurable outcome.
Every one of those translations is a place where meaning can get lost. The objective says “improve lead quality,” but by the time it reaches a ticket, it might just say “update form field.” An engineer who only sees the ticket can complete it perfectly and still miss the point.
So a big part of my role is keeping the thread intact. When someone picks up a ticket, I want them to be able to trace it back up the chain: this field change supports this epic, which supports this program, which supports this business goal.
Web Operations is never just one thing
What makes Web Operations interesting, and demanding, is how many disciplines meet in one place. A single website touches marketing, engineering, security, analytics, content, search, forms, integrations and infrastructure. A change that looks small on the surface can ripple across several of those areas.
That means a Web Operations leader has to be comfortable switching contexts constantly. In the morning it might be a conversation about a CMS architecture decision. By lunch it’s a production issue affecting a form. In the afternoon it’s sprint planning, a hiring conversation and a stakeholder asking why their request isn’t in this sprint.
The trick I’ve learned is not to treat those as interruptions to the “real” work. They are the work. The leader’s job is to keep all of those threads moving while protecting the team’s focus as much as possible.
Managing tickets vs. leading an organization
Strong Web Operations leadership happens when all of those pieces connect: the strategy, the architecture, the plan, the people and the measurement.
It’s possible to run a team purely on tickets. Work comes in, gets prioritized, gets done, and goes out. The board moves. Everyone stays busy. But a team run that way rarely gets better over time, because nobody is looking at the system the tickets come from.
Leading an engineering organization means stepping back from the board often enough to ask harder questions:
- Are we working on the right things?
- Are we getting more capable as a team, or just busier?
- What keeps breaking, and why?
- What would make next quarter easier than this one?
That is the difference between managing tickets and leading an engineering organization. Tickets tell you what the team did. Leadership determines what the team becomes.