Patterns from
the field.

The Organisational Dynamics

Two market leaders merged. One design-led, one engineering-driven. Six months in, the all-hands meetings had gone quiet. Decisions that should have taken a day were cycling for weeks. The Slack channels had split along old company lines. The leader responsible for making this work could feel it. Something had shifted, but there was no single incident to point to, no memo to cite, no crisis to name. Nobody declared war. The organisation just quietly produced an ‘us vs them’ dynamic that was shaping every interaction, every handoff, every hire. Meeting notes captured decisions that eventually came by authority rather than cohesion. People clustered in hallways afterward, sometimes to figure out how to get it done, other times to share strategies for doing it their way regardless of what had just been decided.

The Deeper Pattern

The integration plan had focused on systems and processes but had missed the cultural collision entirely. Both teams were brilliant, operating under different dynamics: the design team’s culture rewarded exploration and discovery; the engineering team’s culture rewarded certainty, stability, and precision. Neither was wrong, but without shared ground rules, every meeting became a contest between two legitimate but incompatible logics. Each side operated all or nothing. There was no safe-to-fail. Whiteboard sketches weren’t debated. Only polished, robust solutions were considered deliverables. Edge cases were discarded rather than recorded. Anomalies were buried so deep in the backlog they could grow mushrooms, and the organisation lost perspective one sprint at a time.

The Approach

We didn’t start with a framework. We started by listening, mapping the interaction patterns, the invisible alliances, and the forces shaping behaviour on both sides. Then we designed facilitated sessions that shifted the dynamics: bringing both cultures together around a shared artifact: the customer. By building rapid prototypes with real customers in the room, we created the right environment where both teams’ strengths could coexist.

The Shift

Product velocity recovered within two quarters, allowing them to ship a critical new feature a full quarter ahead of the revised schedule, capturing key enterprise accounts and adding $2M in ARR. Decision-making became faster and more decisive. The approach became a self-sustaining model. New ways of working the organisation could maintain long after we stepped back.

The Organisational Dynamics

A mobile kidney stone treatment company had outgrown its third-party software. Bad data was flowing through broken workflows, creating compliance risks that kept the legal team up at night and undermining the AI models that were supposed to be the company’s competitive advantage. The leader who owned this problem could see it everywhere and nowhere. Every department had a version of the story, and none of them matched. Two divisions, clinical operations and AI engineering, were locked in a pattern of competing priorities, each convinced the other was the bottleneck. Sluggish systems meant people wrote data down by hand and entered it later, often with errors that fed into billing, scheduling, and treatment data analysis. When someone didn’t know where to enter data, or a field for new data didn’t exist, the information migrated to comment fields, captured but invisible to any analysis.

The Deeper Pattern

The technical problems were symptoms of a deeper organisational dynamic. Two groups of capable people were operating under fundamentally different assumptions about what ‘good data’ meant. The clinical team needed accuracy and compliance. The engineering team needed clean, structured inputs. These aren’t the same thing, and the organisation had never created the environment for that conversation to happen.

The Approach

We started with the data, but we worked through the interactions. We facilitated cross-functional discovery sessions that helped both teams see the problem through each other’s lens. The first day surfaced inconsistencies in data capture, transformation, and analysis that neither side had fully understood in isolation. We redesigned the data workflows, not just the technical architecture, but the human processes and handoff points where the organisation was producing friction. We shifted the dynamics around data entry, validation, and integration.

The Shift

Fixed data pipelines eliminated compliance risks and enabled the AI models to function as designed, directly unlocking the company’s ability to pursue FDA clearance for its AI-assisted diagnostic tool. Reduced operational costs by removing redundant manual processes. Once the workflows were mapped together, each side developed a deeper perspective on the other’s day-to-day reality, and shared language for how data should be captured consistently across interoperable systems. New ways of working that survived the engagement.

The Organisational Dynamics

A technology company was acquired cross-border. The product had strong traction in its original market, a well-understood buyer base with established procurement patterns and clear use cases. Post-close, delivery drag set in. Timelines slipped, and the core product fell behind schedule. Revenue targets didn’t move with it. The leader who stepped in to drive the integration forward found a company already in motion, just in too many directions at once. Under pressure to show income while the core stalled, leadership began greenlighting small projects in an adjacent, highly-regulated market. Sales engineers, highly skilled, well-compensated, and incentivised to close, rose to it. They co-created V1 releases directly with customers, sometimes working through the night to solve a use case no other product could meet. Each win brought in revenue. Each one was also bespoke. Once the sale closed, the engineer moved on. Supporting the custom build fell to sustaining teams who rotated in with fragmented documentation and wiki pages overloaded with ticket threads. Every rotation meant a restart. Customers liked their custom solutions but noticed when support slowed down. Original engineers kept getting pulled between current deadlines and urgent requests from past customers. Renewals stalled until further investment was made in each instance. What emerged wasn’t a product strategy. It was a growing collection of side quests. And each one pulled engineering further from the core product, which created more drag, which created more pressure to take on more one-offs. By the time a consolidated version launched into the adjacent market, it met the wall almost immediately. Built, shipped, and shut down.

The Deeper Pattern

The internal logic behind each project held up on its own. The technology could do what these buyers needed, and the engineers who closed the deals were rewarded for solving the immediate problem. But the original market and the adjacent one didn’t just have different buyers. They had different classification systems, with different assumptions about what the product was, what it was for, and what deploying it meant. That’s an ontological gap, and the company underestimated the distance. In the adjacent space, the same capability was dual-use. It carried a different name, a different weight, and a different set of questions attached to its deployment. Buyers weren’t evaluating features. They were evaluating implications: regulatory exposure, reputational risk, end-use destination. The cumulative cost and risk was overlooked or downplayed because the revenue was needed now. And because the company had drifted in one tactical project at a time, nobody was monitoring the accumulating exposure, including reputational and regulatory risk in a space they hadn’t navigated well. The rapid shutdown made visible what the bespoke phase had obscured: the market hadn’t rejected the technology. It had rejected the product’s identity in that space. The path forward was made by pausing to look back at each path that led to this moment, then picking the most promising insights to map a way forward.

The Approach

We started with how each market actually categorised the product, examining what the company thought it was selling versus what buyers understood they were buying. We designed rapid, low-cost probes with buyers, channel partners, and investors across both markets to surface their language, their procurement logic, and where they drew the line between value and exposure. We mapped those signals against the sunk costs still in play after the shutdown. Then we facilitated sessions with product and leadership to make the full picture visible: where the core product drag was compounding, which pieces of the adjacent-market work had broader signal behind them, and which were consuming resources against demand that would never scale. Every instance had someone in the room who had built it. But the probes gave leadership something no internal post-mortem could: the market’s own voice telling them what it would actually buy.

The Shift

The remaining instances were assessed against the probe findings. Two were ring-fenced with defensible revenue but no path to broader demand. One surfaced capabilities that mapped to a pattern across multiple buyers; those became the seed of a shared product backbone, rebuilt with the market’s classification system in mind rather than the company’s. Engineering capacity returned to the core product, and the drag that had started the cycle began to ease. The probes also surfaced a segment the original one-offs had never reached, one that shared the product’s technical foundation without carrying the dual-use exposure that had shut down the first attempt. Within two quarters the sales pipeline started to respond more favourably. The real-time workshops changed how teams worked. Contributors with different assumptions sketched problems and solutions on shared surfaces, broke down disagreements to find the next step, and left behind living artifacts that illustrated the problem-solving itself. Not finished work. Not captured notes. The thinking made visible. When new crews rotated in, those artifacts ramped them to shared context faster than chasing threads across Slack, Jira, and support tickets ever could. A group of highly talented individual contributors who had been pulled in every direction started to function as crews, finding cohesion over alignment, and navigating towards a shared vision together.