Strategy is, at bottom, a theory about how a firm creates value that others cannot easily replicate. For most of the industrial era that theory rested on physical assets, proprietary processes and privileged access to capital, distribution or information. Each of these was expensive to build and slow to copy, and the resulting frictions were where advantage lived. A strategy was, in effect, a wager on which frictions would endure.

Digitisation has eroded several of those frictions at once. Information, once costly to gather and to move, is now abundant and nearly free to reproduce; the marginal cost of another copy, another transaction, another user approaches zero. Coordination that once required ownership can increasingly be achieved through interfaces, so the boundary of the firm, the question Ronald Coase posed of what to do inside the organisation versus buy from the market, has become negotiable in ways it was not before. Capabilities that used to be integrated into a single company are unbundled, offered as services, and recombined by others into propositions their originators never imagined.

The strategic consequence is not that physical assets cease to matter. It is that advantage migrates towards whatever remains scarce when information is not: proprietary data and the learning loops built on it, the trust and switching costs embedded in a relationship, the orchestration of an ecosystem, and the sheer speed at which an organisation can sense a change and respond to it. A firm that continues to defend the old frictions while its competitors build on the new ones is not merely behind on technology; it is executing an obsolete theory of value. This is the reason digital transformation cannot be delegated downward as an IT concern. Properly understood, it is a revision of the strategy itself, and it belongs on the agenda of the people accountable for that strategy.

It is worth being precise about the word, because much of what passes for strategy is planning in disguise. A plan is a sequence of actions towards a fixed goal under assumed conditions. A strategy is a coherent set of choices, about where to compete, what to offer, and how to win, that remains sound as conditions change. The distinction has always mattered; it matters more now, because the half-life of the assumptions has shortened, and a plan whose premises expire mid-flight is worse than no plan at all, because it commands confidence it has not earned.

Two implications follow. The first is that strategy can no longer treat technology and data as implementation detail to be handed to a delivery function once the ‘real’ decisions are made. The evolution of a technological component, from novel, to bespoke, to product, to commodity utility, changes what is worth building, what is worth buying, and where advantage can still be found. A component that is a genuine differentiator today may be an undifferentiated utility in eighteen months; a strategy blind to that movement will over-invest in the soon-to-be-ordinary and under-invest in the genuinely scarce. Reading that evolution, knowing which parts of your landscape are commoditising and which are still contested, is now a strategic competence rather than a technical footnote.

The second is that strategy must be expressed in a form that can be executed and tested. A strategy that cannot be translated into a small number of measurable objectives, a map of the capabilities required to meet them, and an honest account of what the organisation will therefore not do, is an aspiration wearing a strategy's clothes. Our work begins by forcing that translation early, not to constrain ambition, but to make it concrete enough to act on, argue about, and hold to account.

Several movements in the landscape are consequential enough that a serious strategy should take an explicit position on each rather than absorb them by osmosis.

The composable enterprise. Monolithic systems delivered on multi-year cycles are giving way to modular business and technology capabilities, packaged, interchangeable, and recombined as strategy demands. This is liberating and dangerous in equal measure: it shortens the distance from idea to capability, but without discipline it produces a sprawl of loosely governed parts that is harder to reason about than the monolith it replaced. The strategic question is not whether to compose, but which capabilities are core enough to own and shape, and which are context to be assembled and, later, replaced without regret.

Data as a strategic asset. The rhetoric of data as ‘the new oil’ has aged badly, but the underlying point holds: proprietary data, and the learning loops built upon it, are among the few sources of advantage that compound over time rather than decay. The practical shift now underway is away from centralised lakes that accumulate everything and serve no one, and towards data treated as a product, owned by an accountable team, documented, quality-controlled, and readily consumable by the parts of the business that turn it into value.

Artificial intelligence as operating capability. AI has crossed from experiment into the daily operation of the firm. The instructive surprise is where the difficulty actually lies: not in the models, which are commoditising quickly, but in the data they consume, the decision rights they touch, and the governance that keeps them accountable and explainable. Organisations that treat AI as a procurement exercise are reliably disappointed; those that treat it as a question of data quality and decision architecture are not.

Platforms, ecosystems and the boundary of the firm. As coordination through interfaces grows cheaper, more strategies turn on orchestration rather than ownership, assembling partners, developers and complementors around a proposition and capturing a share of the value they create. The choice to make, to buy, or to partner is now a first-order strategic decision with long consequences, not a sourcing detail to be settled after the strategy is fixed.

Sovereignty and regulation. In Europe especially, the regulatory perimeter has become an architectural input rather than a compliance afterthought. Data protection, the AI Act, operational-resilience regimes such as DORA, and the broader question of digital sovereignty together shape where data may reside, how automated decisions must be explained, and which dependencies are prudent to take on. Treating these as late-stage constraints, to be bolted on once the design is settled, is a dependable way to build the wrong thing efficiently.

From projects to products. Perhaps the quietest but most consequential shift is in how the work is funded and organised. Financing temporary projects that stand up, deliver and disband trains an organisation to optimise for completion rather than for outcome, and to disband the very teams that have just learned the domain. Financing durable, cross-functional teams around long-lived products and capabilities aligns the money with the way value actually accrues, continuously, and through people who remain long enough to compound what they know.

Between a sound strategy and a realised one sits a set of design decisions that quietly determine whether the strategy can be executed at the speed it assumes. We hold to a small number of principles that consistently separate transformations that compound from those that stall.

Strategy precedes systems. We begin from the outcome the business must achieve and the objectives that would evidence it, and only then ask which combination of capability, process and technology serves them. Technology chosen to justify a prior purchase is the most expensive kind, because its costs arrive later and elsewhere than its business case anticipated.

Preserve optionality. Because the assumptions decay, we design so that decisions can be revisited: loosely coupled capabilities, clear interfaces, and commitments deferred to the last responsible moment rather than fixed early for the comfort of a plan. This is real-options thinking applied to architecture, paying a modest premium to keep valuable choices open, and recognising that flexibility has a price worth paying precisely when the future is uncertain.

Separate the stable core from the fast-changing edge. Different parts of an enterprise evolve at different rates, and should be governed accordingly. The systems of record that confer identity and trust ought to change slowly and deliberately; the systems of engagement should track the customer; the experimental edge should be free to move quickly and to fail cheaply. Collapsing these layers into a single cadence, governing a pricing experiment as though it were a change to the general ledger, is a common and costly error that makes the whole organisation move at the speed of its most cautious part.

Treat data as a product. Data that is owned by no one, documented nowhere and trusted by few cannot support the decisions a digital strategy depends upon. Assigning clear ownership, contracts and quality expectations to data is unglamorous work, and it is decisive; most of the value attributed to analytics and AI is in fact created or destroyed here.

Architecture is a constraint on speed, and the organisation is part of the architecture. How data moves and where decisions are made determine how fast the firm can change later. Conway's law, that systems come to mirror the communication structure of the organisation that builds them, is not a curiosity but a design input. Where the desired architecture and the current organisation disagree, one of them must give, and it is usually cheaper and more honest to shape the teams than to force the software into an unnatural form and pay for the mismatch indefinitely.

Prefer reversible decisions, and spend governance on the rest. Most choices are two-way doors that can be walked back cheaply; a few are one-way doors that are expensive to reverse. Treating them alike, subjecting the reversible to the scrutiny only the irreversible deserves, is how organisations become slow without becoming safe. We reserve deliberation for the decisions that genuinely warrant it, and let everything else move.

Buy the commodity, build the differentiator. Effort spent building what the market already supplies as a utility is effort not spent on what would set you apart, and it saddles the organisation with maintenance that confers no advantage. The corollary is equally important: what is genuinely differentiating should rarely be outsourced wholesale, because to outsource it is to rent your advantage from a supplier who is free to let it to your competitors next.

It is often easier to describe good strategy by the failures it avoids than by the successes it claims. A handful recur with enough regularity to be worth naming plainly.

The technology-first transformation. A platform is purchased, frequently after a compelling demonstration, and a strategy is then reverse-engineered to justify the expenditure. The tell is a programme organised around a product name rather than a business outcome, and a business case that grows more elaborate as the results grow more elusive.

The big bang. A multi-year replacement of a core system, defended by the sunk cost of its own business case, that must be substantially right at a single distant moment of cut-over. Such programmes concentrate risk precisely where it should be dispersed, and they tend to discover their errors far too late to correct them at a bearable cost.

The portfolio without a thread. Dozens of initiatives, each individually reasonable, with no legible line of sight from investment to outcome. Activity is mistaken for progress; the organisation is genuinely, exhaustingly busy without becoming measurably better, and no one can say which of the initiatives could be stopped without loss.

Governance theatre. Steering committees that review status without holding decision rights, so the decisions that matter are taken elsewhere, later, and without accountability. Governance that cannot actually decide is merely overhead with a standing invitation in the calendar.

Ignoring the operating model. Treating transformation as a change to systems while leaving the organisation, its incentives and its decision rights untouched, and then expressing surprise that the new capability goes unused. Conway's law does not negotiate, and neither do incentives.

The pilot that never scales. A proof of concept succeeds in a controlled corner of the business and is then quietly starved of the data access, integration and operational ownership it would need to matter at scale. The demonstration was never the hard part; the hard part was everything the pilot was permitted to ignore.

Our work in this area is deliberately upstream, and deliberately concrete. It is easy to be abstract about strategy; the value is in making it specific enough to act on.

We begin by listening rather than proposing. Before recommending anything, we map how decisions are actually made, where value is created and where it leaks away, and which constraints are real as opposed to merely habitual. A good deal of what an organisation believes to be fixed turns out to be convention, and a good deal of what it treats as settled turns out to be quietly contested; both are worth establishing before a single line is drawn on a roadmap.

From that understanding we help articulate a defensible strategy and translate it into a small set of measurable objectives, the few things that, if achieved, would constitute evidence of success. We then map the business capabilities required to meet them, and from that map we derive, rather than assume, the technology and sourcing decisions. This ordering is the whole point: capabilities first, then the systems that serve them, never the reverse.

We sequence the work into a phased roadmap in which each increment is designed to stand on its own, usable, measurable and reversible, so that value arrives early and risk is discovered while it is still cheap to address. We establish governance with genuine decision rights, so that the plan can adapt to what execution teaches without dissolving into improvisation. And we remain engaged through delivery, because the first months in production teach more than any quantity of planning, and because that is exactly the moment at which a strategy is most likely to drift from its original intent.

Throughout, we keep the measurement honest. Each objective carries a few indicators agreed in advance, so that progress is judged against the outcome the strategy promised rather than the volume of activity expended, and so that an initiative which is not working can be stopped early, without embarrassment, and its resources redirected to one that is.

We are multidisciplinary by design and independent by principle. Our teams combine strategic, operational and architectural literacy, so that the conversation moves without translation loss from the boardroom to the systems that must carry the decision, and back again. We hold no allegiance to a particular vendor or stack, which means our recommendations answer to your strategy alone rather than to a partner's licensing model. And we do not leave when the deck is signed off: we remain through the execution that turns a decision into a result, which is both the harder part and the part most advisers decline.

There is also a practical corollary that changes what the work is permitted to assume. When an engagement calls for a capability that does not yet exist, it need not wait on a procurement cycle or a vendor's roadmap. The Nashua 360 Enterprise Platform is built to accommodate almost any feature at pace, through extreme vibe coding: what is needed is described in plain language and generated quickly, but always within firm architecture principles and under stringent quality assurance, so that speed never comes at the cost of coherence, security or control. The effect is strategic rather than merely convenient. It moves the make-or-buy line, keeps optionality cheap, and lets the architecture follow the strategy rather than the strategy bending to whatever happened to be on a shelf.

None of this is exotic. It is the discipline of insisting that digital change answer to a strategy, that the strategy be expressed in a form that can be executed and tested, and that the architecture and the organisation be shaped together so the strategy can move at the speed it assumes. Done well, the result is not a transformation that impresses in a boardroom and disappoints in production, but a strategy that survives contact with delivery, and an organisation that owns it.