The Briefing.
Strategic Briefings.
Your leadership team has five different ideas of what the new system, or the data strategy, actually means. None of them quite match. That isn't a strategy problem. It's a language problem. And language problems compound through every decision that follows.
Data and systems briefing · Transformation workshop · Board session
When your team
needs shared language.
The System-Selection Confusion
A replacement is on the table. Everyone means something different by 'the new system.' Operations think process, finance think cost, IT think integration. Nobody's wrong. Nobody's aligned.
The Frozen Team
Too many vendors, too many demos, too many frameworks. The team can't commit to a direction because they can't agree on the problem.
The Pre-Launch Moment
A migration or go-live is about to start. Before execution begins, the leadership team needs a shared picture of what success looks like, and what it doesn't.
The Board Briefing
Investors, trustees or board members need a clear, credible picture of your data and systems position. Not a deck to nod along to. A real conversation.
The Data-as-Afterthought Reframe
Data and reporting are treated as IT's problem, a cost centre, a thing that happens at the end. You want to change that framing across the leadership team before it hardens into culture.
The Annual Kickoff
A strategy day, an offsite, a new year. The moment to set shared language and direction before the team disperses into delivery.
What I do
A single session or a short engagement. I cut through the noise on the system, data or operations question in front of you, and close with one thing: a shared language the team can actually deliver against.
What it produces
A team that stops debating what the programme means and starts deciding what to do about it.
What it isn't
Not a vendor pitch. No tools, no platforms, no upsell. Just the clarity your team needs to move.
Keynote or workshop format · Built around your situation · No vendor agenda
A practitioner's view,
plain-spoken.
I have spent over a decade leading the data and systems programmes that run core operations: migrations, implementations, reporting and analytics, and the operating models that hold them together, across sectors and across ERP, finance, CRM and data platforms. I have sat with the leadership teams trying to make sense of them.
A briefing from me isn't a generic overview of digital transformation. It's a practical, plain-spoken framework built around the actual decision your team is facing, from someone who has been accountable for the outcome on the other side of it.
If this is
your situation.
Tell me where the language is breaking down. I'll design the session around it.
What people
ask first.
- What is a strategic briefing for a leadership team?
- A focused session, in keynote or workshop format, that gives a leadership team a specific, actionable perspective on a complex topic. My briefings cover data strategy, system selection and replacement, transformation, and business operations, built around the audience's actual situation rather than a templated talk.
- What topics do you cover?
- Data strategy, choosing and replacing core systems, migration and integration risk, reporting and analytics maturity, data governance, business operations and operating model design, and what it takes to make transformation actually deliver.
- How is a briefing different from a vendor workshop?
- A vendor workshop is, in the end, about the vendor's product. My briefings have no product to sell. The goal is for your team to leave knowing what they think and what they should do, not feeling sold to.
- Who is it for?
- Leadership teams, boards and programme teams facing a system, data or operations decision, and audiences who want a practitioner's view rather than a sales pitch.
- How do I book one?
- Get in touch to talk through the topic, the audience and the format. We'll agree the shape of it in an initial call.