Building a Lean Compass for Roadmaps That Actually Hold
Strategic roadmaps rarely fail in the planning workshop. They fail in the months afterwards, when supplier quotes slip, a resource project rewrites its scope, a customer changes priorities, and a delivery team quietly reinterprets what the plan meant. The document still exists, printed and laminated, while the work itself drifts somewhere else entirely.
That drift is the central concern of the Celean research team at Chalmers University, whose Project Visit platform documents how digital visual planning, Kanban and lean process design shape real delivery. Their work with industry partners including Volvo demonstrates that a plan survives or dies according to how visible it is to the people executing it. The idea of a lean compass is a practical answer: replace the static roadmap with a live, shared direction that a team can see, question and correct.
The slow drift between plan and reality
Consider a capital project in the Pilbara, where a contractor mobilises a FIFO crew from Perth and a second crew from Kalgoorlie, each working a fortnight on, fortnight off roster. The site hut has a printed programme on the wall from mobilisation day. By week nine, the programme shows activities that finished in week three, packages that were never started, and a critical path that exists only in a document in the client's Perth office. Nobody lied. The schedule simply decayed through handover and silence.
Australian delivery environments accelerate this decay. Cyclone season on the Darwin coastline pushes structural work into a narrow window, so downstream trades arrive late regardless of the baseline. Christmas and Boxing Day closures at suppliers in Melbourne and Sydney remove a fortnight that the programme never modelled. Resource and construction work in the Hunter Valley, Mackay and Muswellbrook deals with daily production targets that compete with the project schedule for the same crews. Even a well-run engineering organisation in Brisbane can lose a week to a client approval that sat unanswered in an inbox, because the plan assumed decisions would happen quickly rather than actually happen quickly.
The underlying issue is that most roadmaps are written in a language of dates and assumptions, while the work is executed in a language of constraints, queues and conversations. When the two languages diverge, the roadmap becomes a record of intent rather than a working instrument.
What visual planning contributes to strategy
Visual planning converts intent into something a team can read in seconds. A card on a board shows work in progress, its state, its owner and its age. A limit on that board says how much work may be in flight. The abstraction disappears: instead of reading a paragraph about priorities, a delivery lead points at the board and asks why a package is still open when three others are waiting behind it.
The Celean team's examination of reducing project slippage describes this mechanism in detail. Slippage is not primarily a productivity failure; it is an information failure, and visual flow exposes the point at which information stops travelling. A constraint becomes visible, the team stops starting new work, and the schedule consequence of that decision becomes obvious early enough to manage. Hiding the constraint, by contrast, pushes it downstream where it costs more.
This is why a board outperforms a spreadsheet in a delivery environment with heavy contracting and shift work. A spreadsheet requires a person to open it, filter it and interpret it. A board can be photographed at the morning toolbox talk, reviewed with a client at the weekly meeting, or checked by a supervisor in a site office in Adelaide. The same artefact serves the team doing the work and the stakeholders funding it, which removes the translation step that causes most planning errors.
Turning a board into a compass
A task board is not a strategy. It becomes a compass only when every card can be traced back to an outcome that somebody has committed to. The Lean Compass approach borrows the language of direction-finding used in lean manufacturing, where a plant measures its output against a true north and uses that reference to judge whether an improvement moved the operation forward or merely made it busier.
In practice, the compass has three layers. The first is the horizon layer: a small number of outcomes expressed as measurable conditions rather than activities, such as first concrete pour completed before the wet season, or a commissioned line running at rated capacity. The second is the horizon layer's translation into yearly and quarterly goals, each expressed as a target the organisation can actually influence. The third is the operational layer, where work is pulled toward those goals through visible priorities and explicit limits rather than through a sequencing plan that assumes perfect flow.
Between the layers sits the discipline most roadmaps lack: alignment. A card that cannot be linked to a goal is either a necessary piece of hygiene work or an unmanaged distraction, and the board should make that distinction arguable rather than assumed. In Toyota's production system, the catchball exercise between levels does something similar, translating a target into tasks and returning with the obstacles that would prevent achievement.
Digital tools have widened what a board can do. Paper remains valuable on a FIFO camp, where power and connectivity are unreliable, and the move to tablets and dashboards in a Melbourne operations centre or a Sydney control room adds live capacity data, ageing indicators and constraint alerts. Practitioners can also explore the mechanics of this through resources published by Ampersand and Dance, which show board behaviour in motion rather than in principle. The point of digitising is not to replace the physical conversation; it is to make the board's state legible across distance.
Transparency as the engine of delivery
Visual management boards have a cultural dimension, and it is the dimension that decides whether a compass is trusted. A board that is used to assign blame gets used to hide problems, because hiding becomes rational. A board used to surface constraints becomes used to solve them, because surfacing them pays off visibly.
That shift begins with leadership behaviour. When a senior manager asks a board "what is going wrong here?", and the answer is repeated on the board the following morning with an owner and a date, people learn that the board records reality. When the same question is answered with a vague reassurance and the board is cleared by an administrator every Friday, people learn the opposite. Australian project environments are well known for this kind of quiet optimism, where an update reads green while three packages are actually trending red.
The companion review on culture of transparency describes what it takes to move an organisation from the first behaviour to the second. Practices such as publicly owned ageing, visible escalation rules and a shared definition of done do most of the work. They sound simple, and they are, but they require management to accept the discomfort of an accurate picture rather than the comfort of a flattering one.
A useful test is whether a client or regulator can walk into a site office in Perth or a planning room in Brisbane, look at the board and understand the state of delivery without anyone briefing them. If they cannot, the board is a reporting artefact rather than a management system, and the compass has no needle.
A blueprint for rolling out a lean compass
The rollout works best when the board and the strategy are introduced together, so that the connection between daily work and direction is established before anyone can reasonably ask why the board exists. A short set of practices covers most of the ground.
- Anchor the board to a small number of measurable outcomes, stated as conditions rather than activities, so that every card can be traced upward and every escalation can be justified.
- Set explicit limits on work in progress, agreed by the people doing the work, and treat a breached limit as a signal to solve the constraint rather than to accelerate everything.
- Publish ageing on the board, with colour that reflects time against target, because in Australian project settings the cost of a late package compounds fast through roster changes, weather windows and supplier shutdowns.
- Agree a single definition of done across engineering, procurement and construction, so that handover problems appear on the board instead of surfacing at commissioning.
- Keep the strategy layer visible on the same surface as the task layer, using a simple goal cascade that a new starter or a fly-in supervisor can read without coaching.
- Review the board with the people who fund the work, weekly, on site where possible, so that decisions get made in front of the constraints rather than in email threads afterwards.
Introduce this gradually. A pilot in one delivery team, with the roadmap broken down to fortnightly horizons and a physical board in the site office, produces more useful learning in a quarter than an enterprise rollout attempted across the whole portfolio.
Where the practice lands
The gains are unglamorous and repeatable. Slippage is caught earlier, because the constraint appears on the board while it is still cheap to address. Dependencies become negotiated instead of assumed, because two teams can see the same queue. Strategy stops being a document that a small group maintains and becomes a set of conditions that a large group can act on.
For organisations operating across Australia's dispersed project landscape — mining and resources in the Pilbara and Hunter Valley, infrastructure in Queensland, manufacturing in Melbourne and Geelong, and the supply chains that keep Woolworths and Coles shelves stocked through a Christmas peak — that visibility is worth more than another planning cycle. A lean compass does not predict the future better than a conventional roadmap. It makes the present legible enough that the team can steer, and steering is what roadmaps are supposed to enable.
The practical takeaway is straightforward: pick one active roadmap, choose a single measurable outcome, and put that outcome on a board beside the work in progress, with limits and ageing visible and with a review that the funding stakeholders attend. What a team can see on a wall in a site office or a control room is what a team will actually deliver, and a direction everyone can read is the only kind of strategy that survives contact with a roster change, a cyclone season or a supplier's Christmas shutdown.