Different Maps, Same Ship
Walking into a large, traditional organization after years in the high-velocity "fintech" world, I expected the technology landscape to look different.
Different history. Different constraints. Different scars.
I anticipated the stronger governance and the very different relationship with risk. What I didn’t expect was how quickly I would be reminded that “red tape” is rarely about slowing things down for the sake of it, it’s just what happens when people are using different maps to navigate the same ocean.
The Clash of Maps
To engineering teams, modernization is a solvable systems problem. We see friction and want to automate it. We see slow feedback loops and want to tighten them. For us, the map is built on adaptability: build smaller, deploy more often, learn faster.
But to governance, finance, and actuarial disciplines, the map is built on predictability. In these worlds, risk is not a theoretical "bug" in a sprint; it is measured exposure that exists long before it becomes visible to a developer.
Modernization, to them, can look like an invitation to chaos.
Neither perspective is wrong. But somewhere in the gap between "Move Fast" and "Don't Fail," trust begins to erode. And when trust erodes, specialists start drifting into each other’s disciplines.
The Cost of Defensive Steering
This drift isn’t usually malicious; it’s protective.
- Engineers start trying to "do" governance to bypass hurdles.
- Governance starts trying to "direct" engineering to feel safe.
- Architecture starts compensating for delivery uncertainty with 100-page specs.
Eventually, the room becomes full of highly intelligent people trying to prove they are steering responsibly, while the ship itself barely turns. We spend so much energy on "territorial correctness" that we forget the rudder is supposed to be connected to the water. We spend so much time steering defensively that we lose momentum.
Visibility as the Bridge
Large ships turn slowly because they carry real weight. That weight matters—it’s the legacy, the customers, and the stability of the institution.
But for people to stay bought-in, they need to see that the ship is actually turning.
An MVP that takes a year to arrive doesn't feel like movement; it feels like a presentation. A transformation strategy that never hits production isn't a direction; it’s a hallucination.
In my notes, I keep coming back to a specific image: The underwater camera.
If the people on deck can’t feel the turn yet, we need to show them the water moving against the rudder. We need telemetry, small wins, and visible code that proves our "engineering optimism" is backed by "actuarial reality." When movement becomes visible, the need for "defensive steering" begins to evaporate.
A Tablespoon of Humility
It is easy to walk into an established organization and assume the ship should just turn faster. That is usually a naive perspective. There are reasons things evolved the way they did. Some are painful relics, but many are lessons that you only get to learn from winning a 3-day battle with some code in survival mode with a Monster or two.
The bridge between these disciplines isn't a better methodology; it’s a tablespoon of humility.
It’s training ourselves to look for the good intention behind the "red tape." It's realizing that if we are all on the same ship, proving who is the smartest person in the room matters a lot less than making sure we aren't all steering in different directions.
For now, my strategy is curiosity. I want to understand the maps the other disciplines are using. I want to celebrate the small, visible wins that create shared belief.
Because once the goal becomes attached to blame, people stop moving toward it. But once the goal is shared, and the movement is visible, even the largest ship starts to feel like it’s finding its way.