“Stewardship is the ear on the hum.”

You know the person. Every engineering org has one. They’re not the loudest in the room and they’re probably not the strongest architect. Maybe not even the best engineer. But before anyone makes a hard call, someone walks down the hall and asks them what they think.

Nothing important ships without their nod. Their inbox fills up with “got a sec?” Their calendar is half-occupied by meetings nobody invited them to formally. They have no title for the function they actually perform, and the org chart has nowhere to put them.

That person is a steward. The role is the highest-value non-manager position in your engineering org, and you don’t have it.

Most engineering orgs have governance for whether code is correct. Almost none have governance for whether code should exist. That’s the gap.

What the Role Actually Is

Stewardship is taste applied to systems. That’s it.

Most leaders hear “stewardship” and think compliance. Rule-following. Process. That’s the wrong picture. Compliance is about whether the rules are being followed. Stewardship is about whether the rules still fit.

The standards exist. The RFCs exist. The architecture review board meets every other Tuesday. Every commit follows the rules. The architecture rots anyway, because the rules were written for the system that existed when they were written, and that system is gone. The hum’s tune shifted, and nobody was listening for it.

Think of it like Rick Rubin. He can’t engineer a record. Most days he’s barefoot on a couch. But he’s produced some of the most successful albums of the last forty years because he has an ear, and artists trust that ear enough to let his call decide whether the take goes on the record. He’s the one whose judgment matters more than anyone else’s. The steward is that figure on the technical side. They’ve been right enough times that people listen.

Who Isn’t Already Doing This

So who plays Rubin on the technical side? The two answers companies reach for are the CTO and the senior architect. Neither holds up.

The CTO is supposed to own this. At any company past fifty engineers, they can’t. Drift is the slowest-burning failure on their plate, and it loses to everything louder. Stewardship ends up on the CTO’s job description while nobody performs it.

Architects can’t either. They have the judgment for it, but they don’t have the protection. An architect who critiques too many designs and prices too many costs stops being seen as a partner and starts being seen as an obstacle. They learn this fast and stop pushing. Companies assume architects are filling the role anyway. Drift accelerates while everyone congratulates themselves on having governance.

The steward is the lieutenant who closes the gap. Reports to the CTO, operates with the CTO’s authority, and does nothing else. Same logic that produced Controllers under CFOs and Chiefs of Staff under CEOs.

A Navigator, Not an Auditor

Taste is what the steward brings. Navigation is what they do with it.

An auditor checks the log after the voyage. By the time the report matters, the ship is already in port or already on the rocks. Useful, but late.

A navigator works the entire passage. Reads the conditions. Accounts for drift. Adjusts heading continuously. The corrections are small, constant, mostly invisible. Nobody notices them until they stop, and then the noticing happens all at once.

Stewardship gates the slow accumulation, not the individual transactions. The drift, not the deviation.

Cost, Not Patterns

A steward who can only say “this breaks the pattern” cannot move decisions. Engineering objections in engineering language stay inside engineering. To move a decision, the objection has to be denominated in something leadership already tracks. “This creates nine hundred hours of annual unbudgeted operational work.” “This increases mean time to recovery and exposes us to service credit penalties.” “This creates compliance exposure we haven’t priced.” Same concern, different currency.

Taste without translation is aesthetics. Taste with translation is governance.

Authority or Theater

A CFO who can’t block a transaction is a bookkeeper. A steward without authority is a complaint department.

Three properties have to hold or the function collapses. Explicit authority to demand the operational cost of a decision before it ships. Power to delay or block decisions that lack that accounting. A reporting channel that can’t be silenced by whoever is feeling the deadline pressure.

Most organizations grant the first informally, the second occasionally, and the third almost never. A gate that can be walked around is not a gate.

Identifying One

You probably already know who it should be.

It’s the engineer who calculates the long-term cost of a shortcut before anyone asks them to. The one who treats technical debt like a moral failing. The one whose objections, even when annoying, consistently predict the next problem.

But not every difficult engineer is a proto-steward. Some push back because they’re territorial. The difference is whether the pushback translates to operational impact. A proto-steward frames concerns in terms of incident risk, maintenance burden, capacity cost. Someone who just likes arguing frames concerns in terms of elegance and correctness.

Track record is the test. If their objections consistently predict where problems actually emerge, you’ve found your steward. If they’re mostly aesthetic complaints, you haven’t.

The Bottom Line

“Tastemaker” is showing up in engineering job descriptions. Senior engineers are being evaluated on what they reject, not what they write. The discourse is converging on a skill the steward has been quietly performing for years.

AI is going to force this role into the open whether you’re ready or not. When producing code costs nothing, what’s left is whether the code should exist. That’s taste.

Architecture has a hum. Someone has to be listening for it.

Name the role. Give it real authority.

Or accept that the decision that locks in three years of operational cost will keep crossing an engineer’s screen as a pull request, in front of a reviewer with no authority to do anything about it. And stop being surprised by what that produces.

boring (n.): A system whose hum still makes sense, because someone’s been listening.