Dromologue

Evolve your operating model as fast as technology changes.

Organisations have historically been cautious in making deep operating model changes in response to new technology. That changes now.

Everyone is faster. The company isn’t.

This is what Dromologue helps you do: address the factors that hold back the release of AI value.

Technology adoption and business adoption of AI are misaligned

Business maturity in using AI plotted against the maturity of the AI technology implemented. The line where the two keep pace runs at forty-five degrees; the path most firms take falls away beneath it, and the distance between them is the expectation gap. x = y: business keeps pace the path most firms take Expectation gap the distance below the line Ungoverned use the business uses AI tools the platform does not govern PENETRATION PLATFORM PERFORMANCE MATURITY OF AI TECHNOLOGY MATURITY OF BUSINESS USE OF AI
  1. 1

    The line, x = y

    Where the business’s use of AI matures exactly as fast as the technology it has implemented. No firm stays on it.

  2. 2

    The path

    Technology matures by buying and building. The business matures only by working out how its work should change to use it, so its path falls away beneath the line.

  3. 3

    The gap

    The distance below the line is the expectation gap: what the technology now makes possible that the business does not yet know how to use. It widens through performance, and only a change in how the firm works closes it.

  4. 4

    Above the line

    The business adopts AI tools faster than the platform can govern them. Bringing that use under governance after the fact creates frustration on both sides.

Bolt AI onto old work and you leave the value behind

Measured value over time since adopting AI. Value first dips below where it started. Firms that redesign the work climb well above it; 62 per cent of their AI initiatives are deployed. Firms that leave the work unchanged barely recover; 12 per cent are deployed. MEASURED VALUE TIME SINCE ADOPTION value before AI The dip. People feel the gains; the accounts don’t show them. Work redesigned 62% of AI initiatives deployed Work unchanged 12% deployed

The dip. People feel the gains; the accounts don’t show them.

Work redesigned: 62% of AI initiatives deployed.

Work unchanged: 12% deployed.

Sources: BCG 2025; the J curve after Brynjolfsson, Rock and Syverson 2021.

Use cases don’t transform companies. Teams do.

A use case is the unit of delivery: it ships, and its value is measured. It is not the unit of transformation. The team is.

The myth · the use case transforms

Use case 1Use case 2Use case 3
technology platform: improved by every use case
team formed, dissolvedteam formed, dissolvedteam formed, dissolved
practices that released the value: learnt, then lost

The platform gets better either way. The way of working that released the value leaves with the team.

The reality · the team transforms

Use case 1Use case 2Use case 3
technology platform: improved by every use case
the team, kept together across the use cases
practices that released the value: documented, made the way of working

The team documents the practices that released value and makes them how it works. Only a team that persists can do that.

Dromologue helps you identify the use cases that will release value, and builds the teams that deliver them. Their new ways of working pay back more with every use case.

AI changes the whole company, or a competitor will

An operating model is how you sustainably deliver value over time.

Practice sits at the centre, with arrows out to the four other parts of the operating model: people, product, process and platform. PEOPLEculture: how people actually work PRODUCTwhat is made and sold PROCESShow information flows PLATFORMthe technology everything runs on PRACTICEhow each activity moves uscloser to our vision

Practice shapes the other four.

Your practices embed the lessons from the market and from the organisation, so that every activity moves you closer to your vision.

You cannot change culture by announcement, product by decree, process by diagram or platform by purchase. You change the practices, and the other four follow.

Nine disciplines. AI changes every one of them.

The practices that shape the other four Ps live in nine disciplines, in three domains.

organise Structure Talent Finance
build Architecture Engineering Data
assure Risk Security Ethics

each discipline holds practices; each practice has a test

Target practices, tested and proved.

Dromologue works with you to define the target practices that will change your operating model.

Then it tests and proves the value of each change, release by release, so the operating model evolves on evidence rather than on a plan.

If you don’t know where you’re going, any road will do

After Lewis Carroll, Alice’s Adventures in Wonderland

106

We arrive with a strong point of view: 106 starter practices across the nine. Then we work with you to define your practices, and prove their effectiveness one use case delivery at a time.

  • Pods of five roles; the domain expert dedicated, not lent.
  • Each pod owns its full cost and shows its value.
  • Decision rights written; funding per pod, not per platform.
  • The platform is funded as a product the pods consume, not a cost centre.
  • Everyone builds; data, security and infrastructure are capabilities a role holds.
  • Capabilities classified and owning their data; pods work on them.
  • Ship often, run what you build; specification over code.
  • Grows one use case at a time; every release leaves a capability behind.
  • Risk inside the pod; a named human behind every agent.
  • Obligations codified as policies that can stop a release.
  • Every control runs from development, or it is advice.
  • Guardrails codified in the platform, so a control can stop a release.

Why nine

  • Complete.

    Any AI failure a firm has had or fears lands in one of them.

  • Not org structures.

    A practice belongs to no department, so each one forces the organisation to think across its own boundaries.

  • Testable.

    Every practice is true of a team or it is not, and the test runs on each release.

  • Yours.

    The 106 are where we start the conversation, not where it ends. The practices you adopt, amend or decline are your operating model.

Prove it on one team before you bet the company

1 · Prove it on one use case

One team · one valuable use case
team owns its full costobligations codifiedweekly release to production

two or three target practices, tested on it

Every release measured on four metrics

Value per costare we adding more value
Backlog to productionare we building faster
Obligations dischargedare we getting safer
Practice conformanceis the operating model improving

Releases 1 to 6 · one increment

2 · Find and fix what blocks it

a practice that stays false names an organisational blocker

  • nobody may approve a weekly releasedecision right rewritten, in the record
  • cost sits in three budgets, owned by noneone person named as the cost owner
  • the obligation lives in one person’s headpolicy codified with risk; it can stop a release

Each blocker is an open action with a named owner, never a gate on the release. Resolved once, it is resolved for every team that follows.

3 · Then scale to many teams

1 team
3 teams · one increment

9 teams · the next

Each new team starts with the practices already proved and the blockers already cleared, so it starts where the last finished.

The same four metrics for every team and for the board: trends only, teams never ranked.

We don’t hand you a model. We prove one with you.

Advisory

sets the inputs

  • AI strategyhow AI must differentiate you
  • AI pipelineuse cases that pay and grow the team
  • Practiceswhat good looks like, and evolving it

Sets the inputs: how AI must differentiate you, which use cases deliver value and build team maturity, and what good looks like.

Practices and culture

carries the change into the teams

  • Coaching in the teamson the target practices
  • Change leadershipwith the executive

The critical one: coaching in the teams on the target practices, and work with leaders on the change that carries them.

Software

agents that gather the evidence

Working teamsreal releases, real workAgentAgentAgentDid the new practice work?the four metrics, per team, per release

A collection of agents that collect the data to test whether the new practices work, on real working teams.

Evolve your operating model as fast as technology changes.

Keep up with what is changing. Sign up to our AI Feed, a daily read of what matters in AI for the enterprise.

One subscription to both: the AI Feed each morning it publishes, and each new essay on the day it is published. We send a confirmation link first, and every message carries an unsubscribe link.