What the Queue Taught Me: Uncertainty, Context and the Conditions for Real Transformation.
There is a particular kind of waiting that happens in Albanian banks. You find a seat and settle in, sometimes for over an hour, to pay a utility bill in cash. A transaction that in the UK would take no time on the phone or that is more often than not, handled by direct debit without you consciously having to engage with it. Here it requires your physical presence, your patience, and a willingness to surrender your assumptions about how administrative life works.
The first time, this is disorienting. By the third or fourth, something shifts. Not because you’ve become more efficient, but because you’ve stopped trying to be. You accept the queue. You bring a book. You notice the conversations and interactions around you. The resistance dissolves, not into defeat, but into a different relationship with time and process. This, I’ve come to think, is one of the more honest forms of adaptation: not solving the problem, but releasing the frame that made it a problem in the first place and working with it.
But that quiet recalibration is the easy version.
The Uncertainty We Don’t Talk About
Those of us who work in transformation and systems change are familiar with uncertainty. We’ve built frameworks around it: adaptive leadership, emergent strategy, complexity-informed practice. We talk about holding ambiguity, sitting with not-knowing, remaining flexible as conditions shift. These are genuine capacities and they matter.
But there is a kind of uncertainty that most of these frameworks quietly sidestep. Not uncertainty about outcomes; will the strategy land, will the coalition hold, will the intervention produce change, but uncertainty about the container itself. Whether the people gathered to do the work are actually ready to do it. Whether the trust exists. Whether the relational and contextual conditions are in place to hold the hard conversations that transformation requires.
This is the uncertainty that doesn’t appear on the risk register. And in my experience, it is the one most likely to determine whether transformation happens at all or whether what you get instead is its polished, professionally acceptable substitute: activity without shift, collaboration performed rather than practised, outcomes that remain stubbornly at the surface.
What the Container Actually Means
When I talk about the container, I don’t mean the institutional backdrop or the organisational chart. I mean the space where decisions actually get made. The question is whether the people you’ve brought together to design a strategy, to shift a system, to find a new way of working are actually ready to have the hard conversations. Whether they understand where each other is coming from. Whether there is enough trust in each other, in the process, in the institutions they’re working within, to go to the difficult places together. You don’t have to like each other to make things happen. But you have to have enough understanding of each other to work with what’s real rather than what’s safe to say.
This readiness is rarely assessed before the work begins. We convene the room, launch the process, and discover mid-conversation what we should have understood before we started. The container gets tested in the moment rather than diagnosed in advance. And when it can’t hold what we’re asking of it, the work retreats to shallower ground; not because anyone chose that, but because the conditions for going deeper were never established.
Adapting to What’s Actually There
Last week, I arrived at a flat I had agreed to rent, luggage in hand, ready to move in. The arrangement had been clear: some cash upfront, the remainder by bank transfer. A friend was with me. The owner arrived and announced, with no warning and no apology, that he wanted everything in cash. All of it. Now.
What followed was a shouting match in the street between the owner and the letting agent, neither of them particularly concerned with my presence or my luggage on the pavement. I stood there, in a country that wasn’t mine, watching an agreement I had made in good faith evaporate in real time. In a language I don’t understand. Yet.
I walked away. I found an Airbnb, absorbed the cost, and started again that afternoon.
That clarity came from something internal and visceral, a somatic knowing, a calmness, an understanding of my own values and what I was and wasn’t willing to accept. But here is what the situation also illustrated: I could walk away because I had choices. Money, flexibility, no dependents. That is privilege, not resilience. Somebody else in the same situation might not have walked. The calculus could have been entirely different.
Contextual Intelligence Is Not a Soft Skill
What my friend provided in that moment was contextual intelligence, a precise understanding of how that specific system works, what the behaviour signified beneath the performance of it, what my actual options were. Without it, I would have been responding to surface noise rather than structural reality.
This is what gets missed when we treat adaptation as a purely individual capacity. Contextual intelligence is relational and embedded. It is built through proximity, through relationship, through time spent inside a specific system learning its informal logics alongside its formal ones. It cannot be parachuted in.
In many contexts, the formal and informal operate together as two equally real dimensions of how things get done. The written rule and the actual practice coexist. Reliability is negotiated relationally as much as it is institutionally guaranteed. The system has its own coherence.
An outsider arriving without that knowledge is not facing a broken system. They are facing a legible one they don’t yet have the language for. The energy expenditure begins before they’ve reached the problem, not because the system is unpredictable, but because they are not yet fluent in it.
This is the difference that transformation work consistently underestimates. When we arrive in unfamiliar contexts with our frameworks intact and our assumptions unexamined, we are not bringing universal tools. We’re bringing foreign ones and presenting them as if they were local. The imposition is often invisible to us precisely because our own context feels like the default.
Respect, in this sense, is not a soft value. It is an epistemological position. It means beginning from the assumption that you do not know how this system works, that your prior experience does not transfer without translation, and that the people embedded in this context hold knowledge you cannot quickly acquire.
Difference Is Not Disorder
The bank queue is not chaos. It is Tuesday. The disorder is in my reference point, not in the system.
This distinction matters enormously for transformation practice. The same is true of every organisation, community or coalition you enter as an outsider, each with its own history, its own informal rules, a relational landscape that predates your arrival and will outlast your intervention.
Adaptation, real adaptation, not the performance of it, means letting go of the assumption that you already know what you’re looking at. It means unlearning before you can usefully contribute. It means asking what the container can actually hold before you design what you want to put in it.
This is not comfortable work. It requires a particular kind of humility. Not the performed humility of acknowledging complexity, but the operational humility of genuinely not knowing and being willing to find out.
Diagnosing Before Convening
This is where Conversation Architecture®️ sheds some light.
Conversation Architecture®️ is built on a foundational premise: that you cannot design a good conversation without first understanding the field it sits in. The relational history, the trust lines, the power dynamics, the unspoken rules, the cultural logics that shape who speaks, who is heard, and what remains unsaid. All of this must be surfaced before you convene, not discovered during.
The diagnostic work is not a methodological nicety. It is the difference between walking into a room with your assumptions intact and walking in with genuine understanding of what you’re working with.
When you skip it, when you assume the container is stable and ready enough to hold the conversation you’ve designed you are setting yourself up for surface outcomes. Not failure in any visible sense. Something quieter and harder to name; the work proceeds, the outputs are produced, and nothing fundamentally shifts.
The relational intelligence that local friends and colleagues extend when you’re working in unfamiliar contexts is exactly what the diagnostic instrument tries to surface. It asks: what kind of ground are we standing on? Whose logic governs this space? What do people need before they can genuinely engage? Where is the trust, and where are its limits?
These are not abstract questions. In low-predictability contexts they are survival questions. But they are equally urgent in contexts that look on the surface, more familiar and stable. The container can be unready in a boardroom in London just as it can be on the streets of Tirana surrounded by your stuff. The stakes look different. The dynamic is the same.
The Work Before the Work
Transformation does not fail loudly. It fails quietly, at the level of the container; when the conditions for real conversation were never established, when the contextual intelligence was never gathered, when the assumptions about what the room could hold turned out to be wrong.
Navigating uncertainty in systems change is not primarily about individual resilience, though that matters. It is about understanding what you are actually walking into. That requires diagnosis before design, contextual intelligence before intervention, and the genuine willingness to adapt to what’s real rather than impose what’s familiar.
The majority world has been navigating this in systems where the formal and informal coexist, where trust is relational rather than institutional, where the rules are held in relationships built over time, with a sophistication that rarely gets named.
The least transformation practice can do is take that seriously. Not as a lesson in resilience, but as a more honest account of what it actually takes to create change.