It’s January 2026, and the global order is collapsing in real-time. Trump just invaded a sovereign nation and kidnapped its president. Israel expelled every humanitarian organisation from Gaza. BRICS is building the infrastructure to bypass dollar hegemony entirely. International law has become a suggestion. Atrocities have become policy. Consequences have disappeared.
This is the world you’re building brand strategies for.
And if you’re still analysing consumer behaviour, positioning products, developing market strategies using approaches built for stable conditions - you’re practicing strategy for a reality that no longer exists.
Traditional strategic analysis assumes certain things. Rule of law. Institutional accountability. Some kind of moral floor below which systems won’t sink. Power structures that operate within agreed boundaries, however broken those boundaries might be. The five Cs were designed for markets with predictable dynamics, for understanding how things move within stable containers.
Those containers are breaking.
You can’t understand consumer behaviour without accounting for people processing atrocities during their morning scroll. You can’t position brands around values when the systems that gave those values meaning - human rights, justice, accountability - are being systematically dismantled. You can’t build strategies assuming continuity when every week reveals that the rules were always more conditional than we understood.
This isn’t about becoming more ethical. It’s about being accurate. Analysis built on obsolete assumptions fails when it meets reality. And reality has stopped pretending the old agreements apply.
I’ve spent two essays - “The Strategist’s Shame” and “Strategic Sociopathy” - making the case for why traditional practice is flawed. The professional callousness it requires. The consequences that get sanitised away. The performance of intelligence while avoiding actual thinking. That was the rage and the diagnosis.
What follows is the method. Not theory for someday when conditions improve, but practices for right now, in active collapse, within the constraints you actually face. Four analytical approaches that change what you see about the systems you’re working within, the reality your strategies will encounter, and your actual capacity to shape outcomes.
They make the work harder and more uncomfortable. But they make it accurate. And in breakdown conditions, accuracy matters.
Consequence Architecture
Before you engage with any strategic challenge, you need to understand power - who benefits if this succeeds, who pays the cost, who has no voice in the decision being made.
Most strategic analysis doesn’t ask these questions. Briefs focus on market opportunity, consumer demand, competitive positioning - clean variables that assume someone else worries about what happens next.
When systems are unstable, what happens next doesn’t stay neatly externalised. It comes back faster and harder.
I was working with one of the world’s largest retailers on positioning their climate-neutral fashion line. Straightforward brief - capture growing consumer demand for environmentally conscious choices.
Standard analysis would have identified market size, willingness to pay premium, competitive landscape. Clean, actionable insights assuming stable supply chains, predictable priorities, reliable offsets.
But when I started mapping who actually benefits and who pays, the picture got complicated. The company gains brand perception and premium pricing. Customers who can afford it get reduced guilt. But the garment workers in Bangladesh? Still earning the same wages, just producing different garments. Communities surrounding factories? Still dealing with the same production pressures and environmental impact, just with different materials attached. Cotton farmers switching to “regenerative” practices? Absorbing all the risk and cost of transition themselves. Delivery drivers and warehouse workers maintaining next-day shipping - the entire logistics infrastructure prioritising convenience over worker conditions and transport emissions. Future generations? Marginally better off if the calculations are accurate, but the model itself - make more, sell more, dispose more at unprecedented scale - remains unchanged. The ecosystems supporting the offset programs? Forests in the Global South turned into credits to justify continued production volume in the Global North.
None of this was in scope. The brief talked about values and category leadership. It didn’t ask whether success reinforces harm or creates openings for something different.
But I pushed anyway. I surfaced supply chain tensions. I suggested full transparency from end to end. I argued that at their scale, if they could get this right, they should open source the approach - make their economies of scale work for industry change rather than just competitive advantage. Use their market position to actually lead.
None of it made it through. Politely stonewalled at every turn. They wanted the perception of climate leadership without structural changes that would make it real. Marketing position, not operational transformation.
The architecture was clear. I just didn’t have the agency to change it.
But I could change my approach and my choices. And to be honest, this was my first time really mapping consequence architecture systematically. Since then, I’ve had much more success surfacing challenges, opening uncomfortable conversations, spotlighting bigger picture issues and critical points of potential failure. It’s opened doors to work I actually want to be doing - with clients who want those harder conversations, on projects that might actually shift something.
Here’s how it works in practice…
I map this out before I fully commit to a brief. Literally write it down - who benefits, who pays, who has no voice, does this reinforce or challenge harmful patterns. Sometimes during the initial call. Sometimes immediately after. Always before I’ve locked in my approach.
That mapping changes what I say in kickoff meetings. Instead of accepting the framing at face value, I articulate the tensions back to the client. “If we’re positioning this as climate leadership, we need to address the supply chain transparency question - it’s going to come up from journalists, activists, informed consumers. How do we handle that?”
Sometimes that opens conversations the client hasn’t had internally yet. Sometimes it shifts what they’re willing to commit to. Sometimes it clarifies they want perception without substance - which tells me what I’m actually being asked to do and whether I want to be involved.
It also changes my pricing and contract terms. Work where the consequence architecture reveals I’m essentially providing cover for decisions already made? I price that differently. Higher rate for the cognitive dissonance tax, or I decline it entirely. Work where the architecture shows genuine attempts at structural change? I’m willing to invest more effort, sometimes at lower rates, because the work compounds toward something that matters.
It also changes what I deliver. For that fashion project, once I understood the deal, I stopped pushing on structural changes I knew they’d never make. I focused on introducing friction where I could - language that was honest about trade-offs rather than purely aspirational, metrics that would require tracking actual conditions not just offsets, framing that made it harder to ignore supply chain realities later.
None of it fundamentally changed their strategy. But it meant I wasn’t wasting energy on unwinnable battles, I wasn’t surprised when contradictions I’d identified became crises, and I’d created small openings that others could push on later.
This practice isn’t about achieving moral purity or only working on perfect projects. It’s about seeing clearly enough to make informed choices about your involvement - knowing which battles to pick, what’s achievable, whether to adjust your terms, and where your participation genuinely improves outcomes versus providing cover for harm you can’t prevent.
Constraint Mapping
Which brings us to the next practice - understanding your actual capacity to shape what happens.
Seeing the consequence architecture clearly is one thing. Having the agency to do anything about it is another.
I’ve learned this the hard way: you can have perfect clarity about power dynamics, stakeholder impacts, and systemic effects, and still have zero capacity to change the strategy you’re being asked to develop.
Most strategists make this mistake. We create sophisticated recommendations as if we have freedom to design from scratch, when really we’re working within constraints so tight that most of the strategy is predetermined before we arrive. We confuse being asked for strategic input with having strategic agency.
I’ve started plotting every project across two dimensions: how much freedom I actually have to shape the approach, and how much influence the outcome will have on systems or culture. Those two factors determine what kind of practice is even possible.
I was brought in to develop positioning for a major tech platform’s new AI-powered personalisation feature. The brief seemed open - “how do we make users comfortable with this level of data capture?” But the product was already built. The data collection mechanisms were already in place. The business model required maximising what they captured. My job wasn’t to question whether users should be comfortable with it. My job was to find language that would make them feel comfortable enough to opt in.
High constraint, high influence. The platform had hundreds of millions of users. How this got positioned would genuinely shape cultural norms around data privacy and AI personalisation. But my freedom to challenge the fundamental approach was essentially zero.
In that quadrant - tight constraints, high influence - you’re not there to reimagine everything. You’re there for harm reduction and strategic subversion. Finding ways to introduce friction within boundaries you can’t change. Reframing language to include considerations the brief ignored. Introducing consequence mapping as risk mitigation rather than moral critique.
I tried. I suggested they build in meaningful user control rather than just consent theatre. I framed transparency as competitive differentiation - “be the platform users actually trust with their data.” I proposed metrics that would track whether users understood what they were agreeing to, not just whether they clicked accept.
Some of it landed. Not the structural changes - those were off the table. But I got them to include clearer language about what data was being collected and why. I got a commitment to revisit consent mechanisms if user understanding scores stayed low. Small wins that didn’t change the fundamental extraction model, but might make it marginally less harmful.
That’s the reality of high constraint, high influence work. You rarely get to design what you’d build from first principles. But you might introduce hurdles that makes the worst outcomes slightly less likely. You might create measures that force uncomfortable conversations later. You might build relationships with people inside who actually care and give them language to push back with.
Or you recognise your involvement is just providing the smokescreen, and walk away.
When you have freedom but low influence - working with a small brand that won’t move any systemic needles - the practice looks completely different. You’re not preventing harm at scale because the scale doesn’t exist. You’re building foundations. Clarifying principles. Creating proof points you can reference later. Positioning yourself for opportunities with more impact.
I worked with a small luxury beauty brand recently. They wanted to prove that luxury, ethics, efficacy, supply chain transparency, and labour equity could coexist. Not “clean beauty” marketing, but genuinely demonstrating you didn’t have to choose between premium quality and doing right by everyone in the production chain.
Low influence - they’re not transforming the beauty industry. But high freedom - they wanted hard questions, they were willing to experiment, they gave me room to design strategy that honoured consequence architecture.
We built positioning that was honest about costs rather than pretending ethical production comes free. We created growth targets based on retail partners willing to commit to supply chain transparency, not just how many stores would carry them. We designed tracking to prove whether the model worked, not just whether sales increased.
That work won’t change everything. But it creates proof that conscious practice is commercially viable. It builds capability. It positions me for rare moments when you get both freedom and influence.
And when you do get both - high freedom, high influence - that’s when you can experiment boldly. Test genuinely different models. Pioneer approaches that give voice to people typically excluded. Create case studies that show this doesn’t just prevent the bad, it creates the good.
Those opportunities are gold dust, I know that. Most of the time you’re in one of the constrained quadrants, trying to introduce friction at the margins or building capability for better opportunities.
The point isn’t that one quadrant is better. The point is being honest about which one you’re in, so you’re not developing strategies that require agency you don’t have or avoiding bigger swings when you actually have room to make them.
Constraint mapping prevents the fantasy that you can practice the same way in every context. It forces realism about what’s actually probable given where you are. And sometimes it shows you the most conscious choice is recognising when your involvement is no more than rolling a turd in glitter - and having the self awareness to say ‘thanks, but no thanks’.
Stakeholder Complexity Mapping
Consequence architecture shows you who benefits and who pays. But in unstable conditions, you need to map the full web of everyone affected - not just who carries the direct costs, but who bears indirect effects, whose voices are excluded, and what broader systems your strategy depends on.
Standard stakeholder analysis stops at customers, employees, shareholders, partners - the people with direct commercial relationships. When systems are breaking down, that narrow focus becomes dangerous. The people you exclude from analysis don’t disappear. They show up later as crises you didn’t anticipate.
I’m currently working on a youth sports ecosystem analysis where the brief explicitly asked for this - map the messy, complex nature of stakeholders and relationships, understand power flows, trace consequences. It’s rare to get a brief that actually wants stakeholder complexity surfaced rather than sanitised away.
The work is revealing just how tangled the ecosystem actually is. Direct stakeholders seem straightforward at first: young athletes and their families, clubs and leagues, brands and sponsors, facilities and infrastructure providers. But that’s where traditional analysis would stop.
Indirect stakeholders complicate everything. The kids being priced out as youth sports becomes increasingly commercialised and professionalised. Volunteer coaches being replaced by paid professionals, changing the community fabric of local sports. Schools losing enrollment in their programs as families shift to club systems. Neighbourhoods where public facilities decline because investment flows to private training centres.
Missing voices reveal the exclusions the system is built on. Families who can’t afford to participate anymore but whose exclusion reshapes what youth sports becomes. Kids who’d benefit from sport but never get access because the pathway requires resources they don’t have. Communities watching their local infrastructure erode while private academies thrive.
The power flows are fascinating and troubling. Resources flow up toward elite development pathways. Voice flows toward families who can pay. Decision-making power concentrates with organisations that can scale. The kids and communities with the most to gain from accessible youth sports have the least influence over how the ecosystem evolves.
This is what stakeholder complexity mapping reveals - not just who’s involved, but how power moves, whose voices matter, what consequences get transferred to people with no seat at the table.
When systems are relatively stable, narrow stakeholder mapping might work. The externalised effects get absorbed. Those who’ve been silenced stay invisible. The infrastructure holds despite erosion.
When systems are breaking, those excluded stakeholders become the fracture points. The families being priced out organise for access. The communities losing facilities push back. The systemic health problems youth sports are supposed to address accelerate instead of improving.
This isn’t theoretical. The Welsh government embedded this into policy. Their Well-being of Future Generations Act requires every public body to consider the impact of decisions on people who can’t yet speak for themselves - future generations who’ll inherit the consequences of choices made today. It’s law that you can’t make policy without factoring in stakeholders who don’t exist yet but will bear the costs.
If a government can mandate considering people not yet born, strategists can at least account for the people actually affected by their work right now.
Stakeholder complexity mapping means identifying four layers: direct stakeholders with commercial relationships; indirect stakeholders affected by operations but not represented in decisions; missing voices who should be in the conversation but aren’t; and system stakeholders - the health of broader infrastructure that enables the business to exist at all.
Not because you’ll always have power to address every stakeholder concern. You won’t. But because knowing where the tension points are lets you design strategies that are honest about trade-offs rather than pretending they don’t exist. And in unstable conditions, those fault lines become chasms faster than they used to.
Impact Horizons
Understanding who’s affected isn’t enough if you don’t understand when those effects show up. Most strategy operates on quarterly timelines, maybe annual planning cycles. Success gets measured in immediate market response - did sales increase, did perception shift, did we hit targets?
Consequences don’t work that way.
Impact horizons means evaluating decisions across four timeframes: sprint (immediate outcomes over months), season (behavioural and cultural shifts over one to two years), generational (precedents you’re setting over decades), and systems (contribution to or detraction from long-term human and planetary flourishing over a century or more).
I’m currently working with a company providing a privacy layer for the identity economy of AI and agentic commerce. Everyone’s excited about having virtual assistants - AI agents that handle shopping, book travel, manage subscriptions. But no one’s thinking about what that means for privacy, data sovereignty, safety. What it means when you’re handing over your kids’ passport details to an AI agent. What it means for tracking and identity into the future.
The immediate business logic is compelling. Agentic commerce is coming. Someone needs to solve identity and privacy infrastructure. Get there first, set standards, capture the market. Standard analysis would optimise for speed to market and adoption metrics.
But when you extend your thinking, different questions emerge.
Sprint timescale - Six months out: Are we creating infrastructure that genuinely protects privacy, or just adding a layer of perceived security that makes people comfortable handing over more data? Are early adopters tech-savvy people who understand trade-offs, or regular users who trust without understanding what they’re agreeing to?
Seasonal timescale - Two years: What happens when people realise how much data flows through these AI agents? When the first major breach occurs? When journalism reveals the “privacy layer” still enables surveillance capitalism, just with extra steps? What happens when governments start mandating digital identity infrastructure and our solution becomes the path of least resistance for state surveillance?
Generational timescale - Decades ahead: What precedent are we setting for intermediation between humans and daily decisions? What does it mean for a generation growing up with AI agents making choices on their behalf? What happens to human agency when algorithmic mediation becomes the default assumption? When opting out of tracked, intermediated existence isn’t socially or practically viable?
Systems timescale - A century forward: What world are we building when every transaction, choice, and preference flows through trackable digital systems? When infrastructure for total surveillance exists and just needs political will to activate it? When human privacy isn’t an option because the systems we’ve built make it structurally impossible?
NB - Brit ID should be terrifying to anyone thinking this way. Government-mandated digital identity being built right now, under the banner of convenience. Infrastructure for state surveillance being normalised as consumer technology. Ick.
The work we’re doing could genuinely protect people. Or it could just make the surveillance layer more palatable - adding legitimacy to systems that shouldn’t exist in their current form. The difference depends entirely on whether we’re designing for quarterly metrics or generational impact.
Indigenous communities have practiced this for centuries. The Seventh Generation Principle - from the Haudenosaunee Confederacy - requires considering impact on descendants seven generations forward. Roughly 150 years. Every major decision is evaluated not just for immediate benefit but for what world you’re creating for people in the far flung future.
When things are relatively stable, short-term thinking might work. Long-term consequences stay distant. Systems absorb externalised costs.
When things are breaking - when governments flout international law, when institutional trust collapses, when authoritarian playbooks get normalised - consequences accelerate. Privacy backlash when practices get exposed. Regulatory response to extraction models. Political backlash when people understand the surveillance systems they adopted for convenience.
In breakdown conditions, thinking in quarters gets your strategy killed within years.
Integrating These Practices
Consequence architecture, constraint mapping, stakeholder complexity mapping, impact horizons - they don’t replace how you already work. That’s not the point. Rather, they add what traditional analysis excludes.
When you’re doing standard analysis - market position, category dynamics, customer needs, competitive advantage, cultural trends - you’re asking a parallel set of questions. What systems does this company participate in, and what does its success mean for those systems? Is this category extractive or regenerative by design? Who else is affected by how we solve customer needs? What cultural patterns does this strategy reinforce or challenge? What happens across different timeframes, not just quarterly metrics?
You don’t abandon your existing frameworks. You stop pretending they show the full picture. You add the questions that reveal power dynamics, stakeholder impacts, consequences across horizons, and systemic effects.
And it doesn’t mean you automatically walk away when these questions reveal harm - sometimes the most conscious choice is staying and pushing for less extractive approaches within the constraints you face. But it means you’re making that choice with eyes open rather than pretending the harm doesn’t exist because it’s not in your brief.
These practices make the work tougher, more complicated, more confronting. But they make it true. They give you the analytical capacity to see what traditional frameworks filter out - the breaking points, the backlash, the crises that only become “unexpected” because you excluded the variables that would have predicted them.
The industry gives you two options: accept how things are and keep your head down, or abandon it entirely and build something completely different.
But if we’re honest, neither feels possible right now. One requires pretending the ground isn’t shifting. The other requires knowing what comes next when nobody actually knows what’s about to come hurtling around the corner.
This is the third option. The grey area. Practicing what we do, but with more clarity, more awareness, more maturity about what we’re actually participating in and what our work actually leads to.
It’s not perfect. It’s not pure. It’s not the answer to what strategy should become. It’s what’s possible to practice right now, in active breakdown, while we figure out what the next right move actually is.
Because that’s where we are. The old approach doesn’t work. The new approach doesn’t exist yet. What’s left is practicing with eyes open in the space between.
So this is what I’m doing. Figuring it out as I go. With whatever clarity I can manage while the world rewrites itself.
Would have loved job-shadowing you or chatting over a bottomless coffee, gleaning and asking questions with you. I love this topic and have deep musings over how everything should work in the world, where everyone benefits.
Keep it up!
Such a thoughtful and valuable article Zoe. I’m so impressed that you are always providing new thinking pathways for others and driving accountability over passivity while being honest that the way forward is neither easy or certain.