Working together
Understand the business. Decide what matters. Stay with the work.
Technology problems rarely arrive neatly separated from people, priorities and commercial pressure. The starting point is the reality of the business: what needs to change, what is getting in the way and what the team can reasonably take on.
No proprietary maturity score, unnecessary assessment theatre or transformation programme before there is an agreed problem to solve.
Prototype: the activities and outputs below describe a proposed way of working. Scope, responsibilities and pace would be agreed for the particular engagement.
Understand.
Find the real constraint.
Start with the people doing the work and the commercial commitments they are trying to meet.
Explore the understand stageA late release might reflect fragile architecture, unclear ownership, competing priorities or a decision nobody has the authority to make. Treating the symptom as the diagnosis can add more work to the same bottleneck.
Conversations across leadership and delivery, a look at how work moves and a review of the relevant systems help connect the different accounts of the problem. Existing evidence matters; gaps and disagreements should remain visible.
A useful point to reach
A shared account of the constraint, the commitments it affects and the assumptions still to test. Enough clarity to choose a next step, without claiming to have understood every part of the business.
Decide.
Make the choices visible.
Turn technical possibilities into decisions that the business can own.
Explore the decide stageA recommendation should explain what it makes possible, what it costs the organisation and what it leaves unresolved. Keeping the current approach is an option too, with consequences that deserve the same scrutiny as a new platform or a team redesign.
Put practical options in front of the people responsible for the outcome. Make the risks, dependencies and trade-offs explicit, including the work that must stop or wait if a new priority is accepted.
A useful point to reach
A clear choice with an accountable owner, an achievable first move and measures that matter to the business. Record what would cause the decision to be revisited, so a change of direction can follow evidence rather than drift.
Execute.
Stay with the work.
Connect the decision to everyday delivery, then review what actually changes.
Explore the execute stageA strategy only becomes useful when people can act on it. Lead the change with the team: clarify responsibilities, resolve dependencies and keep the technical detail connected to the outcome the business chose.
Review progress honestly. If delivery reveals that an assumption was wrong, return to the decision rather than protecting the plan. A new process, tool or reporting rhythm earns its place by helping people do the work.
A useful point to reach
Visible progress, understood risks and a team better equipped to continue. Transfer context and decision-making capability throughout the engagement, rather than leaving the organisation dependent on an adviser.
A sequence, not a fixed programme.
The stages give the work a direction. They do not prescribe a timetable or require a large discovery exercise before anything can improve.
An urgent operational problem may need immediate action alongside a closer look at its causes. An investment decision may need focused analysis and a clear recommendation. Ongoing leadership may move through all three stages repeatedly as the business changes.
The discipline is to keep the connection intact: evidence informs the choice, the choice informs the work, and the work supplies new evidence.
What would we agree before starting?
- The business problem, why it matters now and the existing commitments to protect.
- Who can make decisions, who will do the work and where responsibility remains with the internal team.
- Access to the people and information needed to form a grounded view.
- The first useful output, how progress will be reviewed and when to reconsider the scope.
What needs to change?
Bring the decision, delivery problem or opportunity you are facing. A useful starting point is what is happening today, why it matters and what you have already tried.
Start a conversationPut the approach in context
- Find the kind of support that fits
- Read about changes to delivery and ownership
- Explore executive and investor-facing work
Past work provides context, not a forecast. Outcomes depend on scope, team, starting point and constraints.