amer.catic@projectvisit.org dagb@projectvisit.org +46 31 322 7207
PV Project Visit

Reducing Cycle Time Through Continuous Improvement Of Visual Workflows

Shorter cycle times rarely come from asking people to work faster. They usually come from making work easier to see, reducing avoidable handovers and improving the way decisions are made. A visual workflow gives teams a shared picture of demand, priorities, blocked tasks and available capacity.

This approach is relevant across Australian organisations, from manufacturing plants in Melbourne and Adelaide to engineering teams in Brisbane, logistics operations in Sydney and project environments supporting mining in Western Australia. Each setting has different constraints, yet the core problem is familiar: work enters a system faster than it can be completed.

The Chalmers Electronic Lean Research Team, known as Celean, examines these issues through digital visual planning, Kanban, visual project management, enterprise systems and lean processes. Project Visit provides a useful window into this research and its industry connections, including collaborations involving organisations such as Volvo. Its ideas can be applied thoughtfully in Australian workplaces without treating software as a substitute for operational judgement.

Why Cycle Time Starts With Visibility

Cycle time measures how long a work item takes to move from an agreed starting point to completion. It differs from lead time, which can include waiting before work begins. A purchase order, engineering change, maintenance request or customer issue may spend most of its life waiting in queues rather than being actively processed.

Visual workflow management makes those queues visible. A board can show each item’s status, responsible team, priority and age. When the board reflects reality, teams can distinguish active work from waiting work and identify where flow is slowing. This changes improvement conversations from general complaints into specific observations.

Visibility also helps leaders see the cost of excessive work in progress. When five urgent tasks are started at once, each task competes for attention, information and approvals. Finishing fewer items before starting new ones can feel uncomfortable, particularly in deadline-driven environments, but it often reduces total completion time.

For Australian organisations, this visibility is especially valuable when teams are distributed across cities, regional offices or remote sites. A digital workflow can connect a design group in Melbourne with suppliers in Geelong, a customer team in Sydney and a production site in South Australia without relying on long email chains.

Map The Workflow As It Really Operates

A workflow should be mapped from the perspective of the work item, not the organisation chart. Begin with the point where a request becomes actionable and follow it through analysis, approval, execution, review and release. Include queues, rework loops, missing information and external dependencies.

Many teams create an idealised process map that omits the informal steps people use to keep work moving. A request may sit in an inbox while someone waits for a verbal decision. An engineer may maintain a private spreadsheet because the enterprise system does not display an important dependency. These workarounds are valuable evidence: they show where the designed process fails to support actual work.

A simple service-level expectation can help distinguish normal variation from harmful delay. For example, a team may record how long a safety review, design check or procurement approval usually takes. The aim is not to punish variation. It is to understand whether the workflow needs clearer entry criteria, better prioritisation or a different allocation of specialist capacity.

In Australia, mapping should account for practical conditions such as supplier distance, regional freight schedules, weather disruptions and site access requirements. A workflow for a Brisbane construction project may include cyclone-related planning constraints, while a mining support process in Western Australia may involve roster changes, travel windows and limited access to subject-matter experts.

Design Kanban Around Flow

Kanban is most effective when its board represents the decisions and constraints that shape flow. Useful columns might include Ready, In Progress, Review, Waiting and Done, although the exact design should reflect the work. Too few columns hide important delays; too many create administrative effort without improving understanding.

Work-in-progress limits are a central control. A limit of three items in a testing column, for example, signals that the team should help clear testing before pulling in more development work. The limit creates a prompt for collaboration rather than a hard barrier applied without context.

Policies should be visible beside the board. These may define when an item is ready to start, what information is required for review, who can approve an exception and when an overdue item is escalated. Clear policies reduce negotiation at every handover and help new team members interpret the board consistently.

Digital tools can extend this practice across enterprise systems, but integration needs care. A dashboard that updates automatically from a project system may appear precise while excluding phone calls, field work or informal approvals. Teams should compare digital records with observed work and revise the workflow until the visual model is trustworthy.

Measure Flow Without Creating Noise

Cycle time is useful when measured consistently. Track the elapsed time for completed items, then examine the distribution rather than relying only on an average. A small number of very old items can be hidden by a mean, while a percentile view can reveal what a typical or difficult item experiences.

Other flow metrics add context. Throughput shows how many items are completed in a period. Work-in-progress reveals how much unfinished work is competing for attention. Blocked time identifies waiting caused by approvals, dependencies or missing information. Together, these measures help explain why cycle time changes.

Teams should also record the age of current work. An item that has been open for twice the usual cycle time deserves attention even if it has not technically breached a service target. An ageing chart or simple visual marker can make this risk visible during daily coordination.

Metrics must remain connected to improvement decisions. If a measure does not change how work is prioritised, staffed or reviewed, it may be reporting rather than helping. Avoid using cycle-time data to rank individuals. The relevant unit is usually the system of work, including policies, queues, tools and dependencies.

Flow Measures Worth Reviewing

Improve The System In Small Experiments

Continuous improvement works best as a sequence of bounded experiments. A team might change the entry criteria for maintenance requests, introduce a review lane for urgent safety work or reduce the number of approval points for low-risk changes. The experiment should have a clear purpose and a limited review period.

Before changing the workflow, record a baseline. This might include the current median cycle time, the number of items in progress and the main reasons for blocked work. After the change, compare the new pattern with the baseline and check for side effects, such as more defects, hidden overtime or work being pushed into another team’s queue.

Retrospectives should focus on system conditions. Useful prompts include: Where did work wait? Which policy caused confusion? What information was missing at the start? Which handover added the least value? These questions help teams improve the workflow rather than assigning blame for individual delays.

A practical rhythm can include a short daily flow review, a weekly analysis of ageing items and a monthly experiment review. The cadence should match the work. A customer support team may need frequent inspection, while a capital project team may review trends around key stage gates.

Conditions That Support Sustainable Improvement

Connect Visual Planning With Daily Work

A visual board becomes powerful when it supports real conversations. During a daily review, the team should focus on items closest to completion, blocked work and decisions needed to keep flow moving. Reading every card from left to right can turn the meeting into a status recital.

Leaders also need to use the board as a decision-making tool. If work is repeatedly blocked by a specialist, the response may be to change sequencing, develop capability, reserve capacity or simplify the review. Asking people to clear the queue without changing the constraint will rarely create lasting improvement.

Australian workplaces often combine office, workshop, field and remote settings. A visual workflow needs to accommodate toolbox talks, shift handovers and mobile access rather than forcing every participant into a desktop process. In a manufacturing or logistics environment, a large physical board may remain useful on site while a digital record supports coordination between locations.

Workplace Health and Safety obligations also matter. Under Australian WHS legislation, workflow changes should not encourage unsafe shortcuts, excessive fatigue or work outside a person’s competence. A faster process that increases incidents, near misses or unreported hazards is a failed improvement, regardless of its cycle-time result.

Protect Information And Respect Local Requirements

Digital visual planning creates records about tasks, people, customers, suppliers and performance. Australian organisations should consider the Privacy Act 1988 and the Australian Privacy Principles when collecting, displaying or retaining personal information. A board may need a task identifier instead of an employee’s name, particularly when performance data is visible across a broad audience.

Access controls should match the sensitivity of the work. A project team may need detailed commercial information, while an executive dashboard may require only aggregated flow measures. Retention rules, audit trails and integration permissions should be reviewed before connecting a workflow tool to an enterprise platform.

The Fair Work Act 2009 and relevant industrial instruments may also affect how work is allocated, monitored and changed. Consultation with employees and representatives is important when a new visual system alters roles, rosters, performance expectations or reporting practices. The board should make work clearer, not create a mechanism for constant surveillance.

Local market conditions add another layer. Australian organisations may depend on overseas components, small specialist suppliers or long domestic transport routes. A workflow can distinguish internal delay from external lead time, making it easier to decide whether to change stock policies, supplier agreements or planning horizons rather than blaming the delivery team.

Start With One Workflow And Learn

A useful pilot begins with a workflow that matters, has a manageable boundary and generates enough work to reveal patterns. Examples include engineering change requests, customer onboarding, purchase approvals, maintenance planning or software release coordination. Select one team and one class of work rather than attempting an enterprise-wide transformation.

Document the current process in plain language, create a board with explicit policies and collect a small baseline of flow data. The first version does not need to be visually impressive. It needs to be accurate enough for the team to identify waiting, rework and competing priorities.

Research and prototype work from Celean highlights the value of treating visual management as a socio-technical practice. People, process rules, information structures and digital tools must fit together. A dashboard alone cannot solve unclear priorities, overloaded specialists or decisions that sit with no owner.

After several weeks, review what the pilot has shown. Keep changes that improve flow and work quality, revise those that create unwanted effects and remove features that add effort without insight. Then document the learning in a form that another team can understand, while allowing for differences in customers, risks and operating conditions.

The first concrete step is to choose one workflow this week, map its actual stages, and record the start date, finish date and current blocker for each active item.