There is a particular kind of meeting that exists inside too many mid-to-large companies and is a special kind of madness. Twenty people. Half multitasking with laptops open. A deck that begins with “Current State” and ends with “Next Steps” that have the life expectancy of a mayfly. Somewhere in the fog of it, the CIO sits quietly refereeing a turf war between operations, marketing, sales, and finance over a system none of them actually understand, none of them built, and all of them want to control.
This is what the job often becomes. Not builder. Not strategist. Traffic cop.
And the really rough part, the part that should keep people up at night but mostly doesn't because the process has been so thoroughly sedated, is that nobody stumbled into this. It was engineered. Layer by careful layer, by serious people in serious meetings who convinced themselves that governance and leadership were the same word.
They are not. Governance is a whistle. Leadership is knowing when to throw it into oncoming traffic.
CPG companies deserve a special mention here because they have perhaps elevated this dysfunction into something approaching high art. Decades of intake processes, prioritization councils, cross-functional steering committees, technology architecture reviews, cybersecurity gates, brand team shadow technologies, and redundant finance checkpoints. Each arrives with an email explaining why is is absolutely necessary and each one becomes another coat of lacquer on a surface that was already four coats deep. After enough years the lacquer is the structure and nobody moves without passing through it. In short, every decision becoming a hostage negotiation.
The CIO ends up as the keeper of this system. Making sure the process is followed, the risks catalogued, and the stakeholders aligned. God help us with aligned; as if alignment were a destination rather than a word organizations to remove accountability from functions and individuals.
From the outside it looks like leadership. From the inside it feels like standing in the middle of a four-way intersection with a whistle while your competitors are already three miles up the road in a roundabout doing what roundabouts do, which is move everybody through without requiring a single human being to stand in the middle of it feeling important. And the traffic cop CIO is still out there in their safety vest, arms waving, completely convinced that without them the whole thing collapses. It will not collapse. It will just go around you.
Markets are feral and selfish. They wait for no one. They do not wait for your alignment meeting. They do not pause while procurement takes a few months to chisel down a vendor and legal takes a few more to get comfortable. The companies that survive the unpredictabillity of the market are not the ones with the cleanest governance diagrams. They are the ones that can smell something changing before it shows up in data, make a decision without convening a committee, and live with a bias for action while everyone else is still scheduling the kickoff.
That requires a different animal entirely.
Call it the CIO as Translator. Not because it sounds better than traffic cop, though it does, but because it describes something genuinely, brutally harder.
The Translator CIO sits with a commercial leader and actually listens, which sounds simple but is in fact rarer than iridium. Listening not to what they are asking for but rather to what they are trying to survive. The request comes in polished and reasonable: we need a new personalization engine. What it actually means, if you are paying any attention, is that conversion has gone flat, media costs are chewing through budget like a rat infestation, and someone two floors up is asking questions that do not have good answers yet.
That is a different problem. And in many, many instances does not need a new platform.
It needs someone who understands business as much as technology and is willing to look at the data already collecting dust in the building, ask why no one is using it, fix the part that makes it all work, and do the thing in 60 days instead of 18 months while the original problem metastasizes into something worse.
The Translator doesn’t open an intake form or throw up metaphorical hands. The Translator picks up the phone and says I think I know what this is actually is, let me show you.
And when the decision needs to get made, it gets made. One owner. Not always a senior one. Putting skin in the outcome. Clearing guardrails. Authorized to move. Not a committee. Not a socialization tour. Not a meeting to discuss scheduling the meeting where the decision will eventually be discussed. One person, with their name on it, accountable for whether it works.
This is the moment when organizations show you what they are really made of. Because the moment you try to compress a decision that used to require twelve people into a small room with three, the bureaucracy comes alive in ways it rarely does for anything else: risk questions that are actually comfort questions, requests for more alignment that are actually more covers to avoid being wrong in public, risk aversion dressed up as consensus.
If you want to win, you have to be willing to disappoint that instinct. Repeatedly, without apology, and without a taskforce to study the disappointment.
And then there is the technology addiction, which deserves its own examination because it can be grim.
The corporate hunger for the elegant comprehensive solution that is always, somehow, arriving slightly later than anyone expected. The platform that lands with great fanfare 24 months after the request was raised. The roadmap that looks like something between art and prophecy in the deck and its dead eyed receipt by commercial leaders who needed leverage five quarters ago and have been misled so many times they have stopped processing the information.
The Translator CIO kills this by asking one question that clears the room: what can we put in place in 60 days that actually moves something?
Not the vision. Not the full architecture. Not the final deliverable. The thing that works well enough to generate a real signal from a real human being making a real decision. And if it does not move anything, you kill it without a funeral. No lessons-learned document. No retrospective designed to make everyone feel okay about the money. You kill it and you go find the next thing.
Ship. Learn. Kill or scale. That rhythm builds credibility faster than any roadmap ever rolled out on a conference room wall.
And for the CFOs in the back of the room raising hands and asking about cautionary tales worth weighing into the discussion. What about financial discipline? What about the companies that moved fast and set their margins on fire chasing the wrong thing?
Fair enough. Speed without judgment is just expensive chaos. But here is the thing, slowness dressed up as rigor is also expensive. It just kills you quietly enough that nobody calls it a failure until three years later, when the postmortem reads like a case study in slow suffocation. The goal is not to break things. The goal is to move fast enough that you are still in the game when the thing actually lands. Most governance frameworks cannot hold that distinction in their heads. They were not built to.
Many organizations will tell you with complete sincerity that they want the Translator. It shows up in the strategy deck. It gets a respectful nod in the all-hands. And to their credit, they’re not wrong to want it. But the Translator isn’t a slogan you can paste into a slide and call it progress. It only comes alive when the system around it is modified and built for movement. Clear decision rights. Fewer layers between problem and action. Stong trust between players and leadership. A shared understanding that the goal isn’t genteel alignment, it’s outcomes that actually move the business.
That kind of environment doesn’t arrive because you hired the right title though. It shows up when the organization makes a few deliberate, grown-up choices about how work gets done. Decision forums get smaller and sharper. Processes lose some weight and start working for speed instead of ceremony. Roles evolve as the work shifts closer to where it can be acted on. And the CIO steps forward as a visible decision-maker, not just the air traffic controller in the tower, but someone willing to call the play in the open and own the result. That visibility and decisioning is the engine. It’s what turns all that good intent into something that actually moves.
There is no framework for that. No offshored system integrator. No multimillion dollar Big Three year-long engagement. No interla transformation program with a clever name and a logo that gets you there from here.
There is just the moment when someone in the room looks at the whistle they have been blowing for years and understands, finally and without comfort, that the whistle was never the point.
Setting it down is the job.
Everything else is theater.
Originally Published April 14, 2026