Before Tech, Explore Context & Impact
Part of a "Software Engineering Enchiridion": Platform Engineering
This software engineering enchiridion entry comes directly from the “Mastering Platform Engineering – from Design to Value” workshop coming to DevOpsCon NYC, JAX London, W-JAX Munich & DevOpsCon Munich.
Most failed platforms don’t collapse because the tech was weak. They collapse because the curators forgot the world outside the code. You can write the cleanest APIs in the hemisphere, with the sweetest internal orchestration options, but if you ignore context, people, and climate, you’re just creating sand castles on a beach waiting for the tide.
A platform is not just tech. It’s a product. And every product is a change intervention. You’re poking a living system—teams, processes, regulations, politics, egos. That system will push back. Pretend it’s simple, and you’ll drown. Treat it as complex, and you might just learn to surf.
At the heart of things is cognitive load is the silent killer. Developers don’t ignore platforms because the YAML is too ugly. Ok, they might. But they definitely will leave if every step drained them. Reduce their mental tax. Remove clutter. Give them flow. Team Topologies call it autonomy and clarity; I call it respecting people’s bandwidth.
Empathy is the sharpest tool you have. Not sympathy. Empathy. Go see where your users live. Sit in the real situation. Watch how they fight with brittle build pipelines or compliance fire drills. Active listening isn’t a TED talk skill—it’s a survival tactic.
And then: climate. Every business has weather—regulation storms, cultural inertia, competitive droughts. Platforms don’t live in isolation. They live in the thick soup of capitalism and bureaucracy. Ignore the climate and your brilliant design will become tomorrow’s fossil.
Focus on context before code. Map needs, listen hard, reduce friction, and anchor your platform in the climate it must survive.
Great platforms are castles built on bedrock, not sand. One key difference is context and how the platform’s impact meets that context. Treat your platform as a product in a living system. Reduce cognitive load. Build with empathy. Map your climate. If you skip this, you’re coding castles in the tide.
Aphorism
Great platforms are never just about tech. They are about context, people, and climate.
Because platforms exist to solve human and business problems inside complex socio-technical systems.
Practices
Use Wardley Mapping to map out users, needs, and evolution.
Measure cognitive load with developer experience surveys.
Explore autonomy and flow through value stream mapping
Practice “Gemba”: go see, listen, and learn.
Some Pitfalls to avoid
Building for technical curiosity, not business need.
Overloading developers with “platform tax.”
Confusing sympathy with empathy.
Ignoring the complexities of your business climate.
Checklist
Did we map our users and their needs?
Can we explain how our platform reduces cognitive load?
Have we gathered empathy-based insights from Gemba?
Did we identify business climate forces (regulation, competition, culture)?
Further Reading
Simon Wardley, Wardley Mapping
Matthew Skelton & Manuel Pais, Team Topologies
Nicole Forsgren et al., Accelerate
Dave Snowden, Cynefin Framework
If you enjoyed this article in the Software Engineering Enchiridion series you might also enjoy:
