Latest / Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations / How a CTO Uses Wardley Mapping to See Strategic Options
Transcript
- Lucas: When a CTO walks into a whiteboard meeting and the conversation is about whether to build or buy a compliance engine, most frameworks will give you a cost comparison. Maybe a total cost of ownership spreadsheet. But there's a mapping technique that shows you something more important: where the market is heading, and where your team's energy will actually matter in three years. Luna: Wardley Mapping. I've seen it pop up in a few CTO circles, but honestly, it still feels niche. When does a map beat a simple decision matrix? Lucas: When the decision is strategic, not tactical. A decision matrix assumes the options are static. But a Wardley Map forces you to put your users on the left, their needs next, then the components that satisfy those needs, and then you plot each component on an evolution axis from 'genesis' to 'commodity'. Suddenly you see which pieces are becoming utilities that you should just buy, and which are still evolving — those are the ones your team should build to differentiate. Luna: So the map isn't about the answer, it's about the conversation. The CTO I'm thinking of, at a fintech processing about two million transactions a month, used this framing to decide on a compliance engine. They were spending six figures annually on a legacy vendor. Lucas: Right. So the compliance engine — AML checks, KYC, sanctions screening — those are actually several components. The CTO mapped them. The identity verification piece, for example, was rapidly moving toward commodity. There are half a dozen API providers that do it well. But the risk scoring logic — that was still in the 'custom built' phase for their specific use case. The map made it obvious: buy the identity verification, invest engineering in the risk scoring. Luna: And that's exactly what they did. They picked a managed service for the commoditized layer, freed up three engineers, and built a proprietary model that actually became a selling point for their platform. Lucas: That's the payoff. The map doesn't just tell you what to do now. It surfaces what Simon Wardley calls 'climatic patterns' — forces that are going to reshape the landscape. One pattern is the commodity trap: you build something custom, it works, but over time the market commoditizes it, and you're stuck maintaining a piece of undifferentiated infrastructure. Luna: Whereas if you'd mapped it early, you'd have seen that coming and either planned to migrate or invested in a different area. Lucas: Exactly. The CTO I spoke with said the map saved them from exactly that trap. They had been maintaining a custom document parser for years. On the map, it sat clearly in the 'product' phase, sliding toward commodity. They replaced it with an off-the-shelf OCR API in a quarter, saved two hundred thousand dollars a year, and reassigned the engineers to the risk model. Luna: So the build-versus-buy question becomes not 'which is cheaper?' but 'where is this component on the evolution axis and where is it heading?' That reframes the entire conversation. Lucas: And it shifts the power dynamic. A procurement department that only sees cost might force a build decision because the internal team can do it cheaper this quarter. But a Wardley Map shows the full context — the maintenance burden, the evolution trajectory, the opportunity cost of tying up talent on something the market will soon sell for pennies. Luna: I've also seen maps used for platform decisions. One CTO at a logistics company mapped their entire order management stack and realized they had three separate services doing essentially the same thing — address validation. All built in-house, all slightly different. That was a classic 'unnecessary custom' cluster. Lucas: Right. And the map makes those clusters visually obvious. You see the duplicates because they sit at the same position on the evolution axis and serve the same user need. The CTO I talked to said they consolidated onto one managed service and cut their incident rate by forty percent, because the third-party API was better maintained than any of their internal ones. Luna: That's a concrete win. But I imagine the mapping process itself takes some practice. It's not just drawing boxes and arrows. Lucas: It's definitely a skill. The hardest part is anchoring to the user. Most teams want to start from their existing architecture. But a Wardley Map starts from the user's need, then works backward. That alone changes how you think about priorities. And the evolution axis — genesis, custom built, product, commodity — you have to be honest about where each component actually sits, not where you wish it sat. Luna: So the CTO's job becomes facilitating that honest mapping session. And once the map is drawn, the strategic options become clearer. Lucas: Yeah. And you can update the map quarterly. It becomes a living strategic document. One CTO I know pins the latest map in the team's Slack channel and invites people to suggest changes. It keeps the whole org aligned on what's changing in the landscape. Luna: It's interesting — we've talked about decision logs and ADRs and cost of delay. But Wardley Mapping seems like the meta-framework that helps you decide which of those other frameworks to use when. Lucas: That's a great way to put it. The map gives you the context. Then you can apply cost of delay to the options the map reveals, or use an ADR to record the decision the map informed. It's not a replacement for those tools. It's the lens that makes them more useful. Luna: And it's free. No software needed. Just a whiteboard. Lucas: Or a shared document. The technique is open source, essentially. Simon Wardley published his book online for free. There's a whole community around it. But the adoption in engineering leadership is still surprisingly low. I think partly because it sounds academic until you see it applied to a real problem. Luna: Yeah, the fintech example made it click for me. The map gave them a clear 'buy for commodity, build for differentiation' split. That's something every CTO deals with. Lucas: And it's not just for build-versus-buy. It works for any strategic question: should we invest in a new platform? Should we migrate to the cloud? Should we build a data lake? The map shows you the landscape, and then the answers are often obvious. Luna: Alright, I'm convinced. Next time I see a CTO agonizing over a platform decision, I'm going to suggest they draw a map first. Lucas: Good. And if they want a starting point, there's a great mapping tool called 'Online Wardley Maps' that lets you collaborate in real time. But honestly, a whiteboard and sticky notes work just as well. Luna: We should note — today's episode is the hundredth in this series. We've covered a lot of CTO techniques, from cost of delay to chaos engineering. This one feels like a fitting capstone because it's about seeing the whole board. Lucas: It does. And speaking of that — a quick honest thing. We're able to keep making these deep dives, ad-free, because a small group of listeners chips in monthly through buy me a coffee dot com slash fexingo. That support literally covers the research and production time. If you've gotten useful frameworks from any of the hundred episodes, that's one way to keep it going. Luna: Yeah, we don't run ads, we don't have sponsors. It's just listener supported. And we're grateful for everyone who's already part of that. Lucas: So back to the map. One more thing: the CTO from the fintech told me that after they made the compliance engine decision, they started mapping every major initiative. It became their default way to think about strategy. And the engineers loved it because it gave them a clear reason why they were building what they were building. Luna: That's the mark of a good framework — it doesn't just help the CTO. It helps the whole team understand the why. Lucas: Exactly. And that shared understanding is worth more than any single decision the map produces. So, for anyone leading a technical organization, if you haven't tried Wardley Mapping yet, I'd say start with one decision you're facing, draw the map, and see what it reveals. You might be surprised. Luna: And if you do try it, let us know how it goes. We love hearing how these frameworks play out in the real world. Lucas: Alright, that's it for episode 100. Thanks for being with us through a hundred of these conversations.