Intensive workshop · Transformation
What has to come first
A roadmap is not a list of projects with dates on it. It is the sequence that recognises what depends on what, and how much change the operation can absorb at one time.
- Duration
- 4 hours 30 min
- Delivery
- On site · Virtual
- Participants
- From 8 to 20 participants
- Investment
- Request a quote
Investment depends on scope, number of participants and delivery mode. We prepare a proposal at no obligation.
The problem it solves
A project list sorted by priority is not a roadmap. It is a list with numbers beside it. Sequence appears when somebody asks what has to exist before the next thing can start, and that question is rarely asked in the meeting where the list is assembled.
What follows is recognisable. Two initiatives begin at once and both depend on the same piece of information, which still has no owner. A third is finished and cannot be used because the process it feeds has not been redesigned. A fourth jumps the queue because the department that asked for it carried more weight in the room. Each reports progress separately and the whole thing fails to move. Leadership reviews activity rather than dependencies, and the conversation turns into an account of effort.
The bill arrives as rework. A system gets connected to a process that is redesigned months later, so the connection is built twice. A team is trained in a way of working that changes before it settles. And the organisation learns something worse: that order is set by whoever pushes hardest. From then on, pushing becomes the normal way to obtain priority.
What it covers
The workshop builds the sequence out of the group's own initiatives rather than an illustrative case. It opens with the inventory: everything proposed, approved or half-built, written on cards that can be moved around. Before anything is ordered, the group has to say what each initiative exists for and what would remain unsolved if it were never done. Several do not survive that question, and that is already part of the result.
The second part is the dependency map. In a group exercise, participants trace what requires what: which process decision has to be settled first, which information has to exist and have an owner, which skill has to be present in the team, and which other initiative has to be finished. The map usually reveals that half the list hangs on two or three things nobody put in the plan because they did not look like projects.
The third part introduces the constraint that orders everything else: an operation cannot take change continuously. Using a worksheet, the group marks the parts of the year when the business tolerates no interruption, works out which people each stretch would tie up, and adjusts the sequence until it is sustainable. This is the point where an ambitious roadmap becomes a defensible one.
The closing section works on decision gates. For each stretch the group agrees what has to be true before moving on, who verifies it and what happens if it is not met, including the option of not continuing. Through scenario analysis the sequence is tested against two likely disturbances, a delay and a new priority imposed from outside, and the group watches which parts collapse and which hold. Participants leave with the written sequence, the dependency map and the agreed gates.
What participants learn
- Identify the real dependencies between initiatives: which decision, which information and which skill must exist before each one.
- Design a sequence of stretches with decision gates, named owners and written conditions for moving on.
- Analyse the windows in the year when the operation can take change and the ones best left untouched.
- Prioritise initiatives by what they unblock rather than by the weight of the department that proposed them.
- Evaluate how the sequence holds up against a delay and against a priority imposed from outside.
Agenda
- The difference between a prioritised list and a sequence
- Dependency mapping: decisions, information, skills and prior work
- Operating windows: when the business cannot take change
- Stretches, decision gates and conditions for moving on
- What unblocks what: ordering by effect rather than urgency
- The cost of the wrong order: rework and training that expires
- Revising a sequence without rebuilding it from scratch
- What gets written down and what is deliberately left open
What the organisation leaves with
- A written dependency map across the initiatives currently on the table.
- A sequence of stretches with owners and agreed conditions for moving on.
- An explicit list of what does not start in this cycle, with the reason recorded.
- A one-page format for revisiting the sequence when a priority changes.
Programme details
- Format
- Intensive workshop
- Also available as
- Workshop · Corporate training day
- Languages
- Español · English
- Includes
- Participant workbook
- Action plan
- Post-training resources
- Facilitation
- ALUD Consulting LLC — Global Business Transformation.
Who it is for
- Leadership teams with several approved initiatives and no agreed order among them.
- Operations managers who receive the change and had no say in when it arrives.
- Project leads who discover dependencies only after execution has started.
- Owners who want to decide what does not start this year and need a defensible argument.
Frequently asked questions
- Can we come without having defined our initiatives?
- You can come with loose ideas, but the workshop returns far less. The work consists of ordering concrete candidates; with no candidates, the session turns into portfolio design, which is a different exercise. An honest list is enough, however roughly it is written.
- Is the sequence produced in the workshop final?
- No, and it should not be presented that way. A sequence holds only while its assumptions hold. What does stay fixed is the way it gets revised: what is examined, who decides, and how often the map is opened again.
- Does this work when our initiatives depend on an outside supplier?
- It works particularly well. An external dependency is still a dependency, except that it cannot be accelerated from inside. The map makes it visible and forces a decision about what happens meanwhile, instead of discovering it once two stretches are already stalled.
- Does leadership need to attend, or is the delivery team enough?
- It can be run with the delivery team alone, and the result will be a proposal rather than a decision. If leadership is not in the room, the group leaves with a sequence somebody else can overturn in the next meeting, and the work is lost.
Request this programme
Tell us the context and we will prepare a proposal tailored to your organisation. No obligation.
Working this inside the organisation
If this challenge will not be settled in one session, ALUD Consulting LLC works it as consulting: management consulting, human resources, strategy, organisational design, leadership development and business transformation.