Serious Learning & Development

09/09/2026

Seeing is Solving: Translating Factory Floor Visuals to Virtual Customer Support

How techniques born on the assembly line can save modern help desks from the chaos of invisible workflows.

Toyota Manufactured vehicles in Australia for 54 years from 1963 until 2017 when the last Toyota Camry rolled off the production line at their Altona plant.

Toyota's decision to close its Altona manufacturing plant was the result of a "perfect storm" of economic and structural factors that made building cars in Australia financially unviable. Toyota plants are strictly judged on safety, productivity, quality, and cost. In the four years leading up to its closure, the Altona plant successfully achieved every single one of its global Key Performance Indicators; It was actually Toyota’s best performing plant. The plant's closure had nothing to do with the quality of its cars or the performance of its workers, but rather the insurmountable economic factors of building cars in Australia.

Toyota offered daily free tours of its Altona plant and I took this opportunity on several occasions. Every visit was rich with learnings. Walking into a Toyota factory you can, with a quick glance tell exactly how production is going. You see components arriving just in time at each workstation and flashing lights indicating issues that require interventions. The status of the work is completely visible at every stage of the production process and problems are highlighted and dealt immediately they occur. What is most impressive is the slow but continuous “flow” of value-add, with the entire plant operating to a synchronised rhythm. There are whiteboards everywhere, used for constant updates and communication both within and between teams. Finally, there is a steady flow of finished products rolling off the end of the line; the ultimate indicator of productivity.

Now, imagine walking into a modern customer support centre. That is if you can find one in these times of virtual teams! Much more likely is that you will have to log into a distributed support team’s Slack channel. What do you see? A queue and a barrage of instant messages? The overall workflow itself, its individual stakeholders and participants, the angry customers, the software bugs, the information requests, the backlog of hundreds of tickets, is for the most part invisible. It exists only as database entries and management dashboards in tools like Zendesk, Jira, or Intercom.

When work is invisible, bottlenecks go unnoticed until they become crises requiring escalation. Individual support operatives quietly drown in their overloaded siloes.
You may say that is all very well for factories which have all activities and people in one centralized location but the principles of Visual Management are valuable independent of location and can be applied to virtual teams and workflows allowing all participants to benefit by transforming abstract isolated data points into clear, actionable, visual cues.
The Roots: Toyota and the Power of the "Andon"
To understand how to fix modern virtual workflows we have to look back to post-WWII Japan and the origins of Lean Manufacturing at the Toyota Motor Corporation. Taiichi Ohno, the father of the Toyota Production System (TPS), believed that abnormalities should be instantly obvious to everyone and dealt with at source. If a problem was hidden or passed along the line it couldn't be fixed there and then but instead would manifest itself further down the line or worse still be delivered to the customer.
He introduced two core visual concepts that changed Toyota’s operations forever:

• Kanban (Signboard): Physical cards used to signal the need to move materials within a manufacturing facility. It limited excess inventory by ensuring a station only requested inputs when it had the capacity to process them.

• Andon (Paper Lantern): A physical cord above the assembly line. If a worker spotted a defect, they pulled the cord. This triggered a visual display (a lit board) showing exactly where the problem was, and it usually stopped the entire line until the issue was resolved.

Customer support teams can adapt these exact principles. Instead of physical cars, they are managing digital tickets. Instead of physical lightboards, they are using live dashboard monitors and automated digital triggers.

Visual Workflows: From Assembly Line to Help Desk
Translating physical visual management into the digital service space requires a shift in how we display data. Here are three ways that you can employ Lean visual techniques today.

1. Digital Kanban and Work-in-Progress (WIP) Limits
In traditional support setups, agents are often able to cherry-pick easy tickets, or conversely, get assigned dozens of complex issues simultaneously. This leads to massive task and context switching and high burnout.
Virtual teams can utilize digital Kanban boards where tickets move through distinct visual swimlanes (e.g., Triage -> Investigating -> Waiting on Customer -> Escalated to Dev -> Resolved). More importantly, they implement WIP Limits. By turning a column background red when an agent exceeds their limit of 5 active tickets, the system visually forces the team to finish existing work before pulling new tasks. It shifts the team from a "push" system (dumping tickets on agents) to a "pull" system (agents taking tickets when they have capacity).

A Cross-Industry Analogy: Kitchen Display Systems (KDS)
Think of a fast-casual restaurant kitchen. In the past, paper tickets were easily lost. Today, digital Kitchen Display Systems (KDS) break down complex orders into visual blocks. As an order ages, it turns from green to yellow, and finally flashes red. This tells the expediter instantly which order is bottlenecking the line. Tech support operates on the exact same premise: a ticket flashing red on a dashboard tells the support manager exactly where to intervene before a customer explodes.

2. Dashboards as “Gemba”
In Lean, a business mindset and continuous improvement approach focused on maximizing customer value while systematically identifying and eliminating waste across all operational processes, Gemba is "the real place" where value is created. Leaders are encouraged to go to Gemba to see the work happening. In a remote or globally distributed tech support team, Gemba is a virtual space: the real-time operational dashboard.
Effective visual management dashboards don't just show historical metrics (like yesterday's CSAT scores). They show real-time, actionable reality: How many calls are currently waiting? What is the longest wait time right now? Which tier 2 agents are currently online?
Service Level Agreements (SLAs) are the lifeblood of enterprise tech support. Missing an SLA can mean financial penalties and lost contract renewals.
Visual management turns SLAs into digital Andon cords. Through dynamic color-coding, a ticket might enter the queue as White. At 50% of SLA time consumed, it turns Yellow. At 90%, it turns Red. Team members can proactively manage before breaches occur and fewer escalations are required. The dashboard explicitly shares real time status just like the lights on the Toyota factory floor.

A Cross-Industry Analogy: ER Patient Status Boards
In emergency healthcare, whiteboards (and now digital screens) track patient flow. Color codes indicate bed availability, lab results pending, and triage severity. A triage nurse uses this visual board to direct the chaotic flow of incoming trauma. Similarly, a Tier 1 Support Lead acts as the triage nurse, looking at the team dashboard to route incoming P1 (Priority 1) outages to available Tier 3 engineers without having to message them to ask, "Are you busy?"

3. Performance Matrices
Performance Matrices are a highly effective workplace measurement tool developed in 1983 by Glenn Felix & James Riggs and designed to track any performance dimension be it quality, quantity or safety. They do this by connecting outcomes directly to the specific, observable behaviours and actions. Performance Matrices can therefore be used to translate any type or combination of performance metrics into a single graphical representation of progress against targets. They are an incredibly effective system for keeping teams on target and on time allowing prioritisation by clearly showing that not all actions are of equal importance. They encourage collaboration and self-management within teams, enabling everyone to know exactly what they need to work on and when to work on it.
Probably most usefully they can track anything and everything whether its quantitative, such as the achievement of a KPI or SLA, or qualitative, such as the use of a newly developed competency or the change of a behaviour.

The Psychological Impact of Visual Clarity
Beyond operational efficiency, visual management profoundly impacts employee well-being. Tech support is notoriously stressful. When a queue of thousands of tickets is hidden behind a single dropdown menu, it creates chronic, low-level anxiety due to the constant feeling of overload coupled with a disconnect from the bigger overall “why” of the end to end process.
Visual management chunks that overwhelming infinity into manageable, explicit states. It answers the fundamental questions every worker has: "Am I making progress today?" and “Is my work meaningful?”. By making the work visible, teams can celebrate when the board is clear, immediately swarm to help a struggling teammate whose column is glowing red and maintain a sustainable pace of problem-solving.
However, it is important to note that providing visual performance clarity in environments where employees feel psychologically unsafe due to having been punished for missing targets may initially be greeted with some level of fear and skepticism. This can only be overcome by consistent using the performance clarity provided by the system to respond in a positive way to whatever status is revealed whether is it desired or not.

Conclusion
Ultimately, whether you are building cars or debugging enterprise software in the cloud, the principle remains the same: You cannot manage what you cannot see. By bringing the invisible into focus, modern virtual support teams can also show that the best way to solve a problem is to see it immediately, make it impossible to ignore and deal with it at source.

A happy postscript
In an interesting twist, a form of local manufacturing has returned to Altona. Starting in early 2024, Toyota Australia began using the facility to assemble and distribute stationary hydrogen fuel cell power generators (the EODev GEH2). These generators use the exact same fuel cell system found in the Toyota Mirai to provide zero-emission power for off-grid locations. It also hosts a broader Centre of Excellence continuing to house Toyota Australia's product planning and development teams. While they aren't building Camrys on an assembly line anymore, the site is used to design, modify, and test vehicles and accessories specifically for the harsh Australian environment before they are sold nationwide.
© Serious Consulting Pty Ltd 2026

23/08/2026

End to end optimisation - SIPOC is the way!

Ever wondered why the self-checkout experience feels so broken? 🛒 ...

23/08/2026

Why Your Customer Experience Looks Just Like Your Org Chart: Conway’s Law in Service Industries

I am old enough to have forgotten much of what I learned in my earlier career (most of which was focussed on large scale software and system engineering). Therefore it is always nice to be reminded of something “old” and realise it is still incredibly relevant and applicable today.

My latest re-discovery is the phenomenon known as Conway’s Law. While originally coined in the field of software engineering, Conway’s Law is the key to understanding why service industries so often deliver fragmented customer experiences—and why methodologies like Design & Lean Thinking can be used to fix them.

For example, we have all been there; You contact a service provider because you have a problem. First, you must navigate an automated system seemingly designed to deter you and eventually if you persevere you manage to speak to a human in a contact centre. They then transfer you to tech support. Tech support decide the issue is a billing error, so they transfer you to that department and so on, at every step, you must re-verify your identity, explain your problem from scratch, and wait on hold. Sometimes the call is inexplicably cut-off and you have to start all over!
Your customer experience is disjointed because the company’s internal departments are disjointed and specifically require multiple handovers.

What is Conway’s Law?
In 1967, computer scientist Melvin Conway observed that:
"Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations."

In plain English: The product or service you deliver will end up shaped exactly like your company's org chart. If your internal divisions don't talk to each other seamlessly, your customers will feel every single one of those internal seams (they are sometimes even chasms!).

Customer Journey Mapping Exposes the Org Chart
A service is simply a sequence of interactions. In Design Thinking, teams use a tool called Customer Journey Mapping to visualize an end-to-end user experience across every touchpoint.
When you lay out a service journey map, Conway’s Law becomes glaringly obvious. Every time a customer experiences friction—a redundant form, a long wait, a request for information already provided, or a dropped call transfer—you are almost certainly looking at an internal organizational boundary. The journey map acts as a diagnostic mirror: customer pain points highlight the communication gaps between your internal departments.
When teams don't communicate well internally, the burden of bridging those internal gaps is inevitably pushed onto the customer.
Let’s look at two examples of how Conway’s Law manifests across differing service sectors.

Example 1: Healthcare and the Fragmented Patient Journey
As a young student every vacation I worked as a hospital porter in a large London teaching hospital. This gave me first-hand experience of a complex organisation where lives are at stake. Hospitals are notoriously siloed, traditionally structured around deep medical specialties (Cardiology, Radiology, Oncology) and administrative silos (Admissions, Billing, Outpatients). Looking back my role was to move patients between departments and, except for my cheery disposition, I did not add much that was positive to a patient’s experience; it usually began and ended with a long “wait”.

The Conway Effect: Because these departments operate as highly specialized, separate entities with distinct communication chains, the patient experiences a highly fragmented service. A patient might have to give their family medical history to the intake nurse, repeat it to the attending doctor, and repeat it again to the specialist. Later, they receive three separate bills from the hospital, the radiologist, and the lab. The patient's healthcare journey is an exact copy of the hospital's internal departmental boundaries.

Example 2: The B2B SaaS Onboarding Trap
In business-to-business (B2B) services, companies are often cleanly divided into Sales, Implementation/Onboarding, Finance and Customer Support,

The Conway Effect: The Sales team promises the client the world but doesn't document the client's specific technical needs because they don't talk to the Implementation team. The Implementation team sets up a generic template because they don't know what Sales promised. Finance push to go live (often prematurely) so that invoicing can commence. Once “live” the client has an issue and calls Customer Support, who have no record of what the Implementation team did. Everyone involved including the employees and the client experience pain.

To succeed, service design requires the Inverse Conway Manoeuvre: intentionally restructuring internal teams to mirror the ideal customer journey map. Design Thinking advocates for empathy-driven, human-centred design—focusing on user needs rather than internal corporate convenience. However, if your company's structure remains rigid, even the most elegant design thinking sessions will fail during ex*****on because Conway’s Law will drag the service back into internal silos. This is where Lean Thinking comes in. Conway’s Law diagnoses the structural cause of friction in a system, while Lean provides the framework to eliminate it.

Hand-Offs Are the Primary Location of Problems
A core principle of Lean is the relentless elimination of waste such as delays, errors, and over-processing. Conway’s Law reveals the root cause of this waste in service delivery. Whenever a service process crosses an organisational boundary, for example moving a ticket from front of house to second-line support, communication breaks down and context is lost. In Lean terms, every departmental “seam” predicted by Conway’s Law is an active waste-generator.

Value Stream Mapping vs. The Org Chart
Lean relies on Value Stream Mapping to visualise how value actually flows to the customer. Conway’s Law serves as a direct warning: if your communication pathways remain locked in functional silos (e.g., separate intake, processing, and billing departments), your value stream will inevitably stall at those internal borders. To optimize value flow, you cannot just optimize individual departments; you must dismantle the communication barriers between them, so the service moves continuously without stopping at organizational hand-offs.

Creating "Service Cells" to Achieve Flow
To achieve continuous Flow, traditional Lean manufacturing replaced functional departmental batching (putting all stamping machines in one hall and all paint booths in another) with "work cells"—arranging different machines in sequential order around a specific product. In service industries, Lean applies this same logic by grouping multi-disciplinary staff into dedicated customer-value teams. By organising people around the flow of value rather than functional titles, you rewrite the communication structure using Conway's Law to automatically yield a seamless, waste-free customer experience.

Design Thinking gives you the approach to map a seamless customer experience, and Lean Thinking gives you the tools and continuous improvement methodology needed to survive Conway's Law. You cannot fix a broken service experience with a surface-level redesign. To change what customers experience at the end of a journey on the “outside”, you must first align the communication structure on the “Inside.”
© Serious Consulting Pty Ltd 2026

The Author as Hospital Porter in 1984 (just like Douglas Adams!)

21/08/2026

Neurobiologist and Nobel Prize winner Rita Levi-Montalcini reminds us that good judgment requires warmth and logic:

"Rare are those people who use the mind; few use the heart; and really unique are those who use both."

Source: WIRED Interview (March 2009)

11/08/2026

Aldous gets it...........

FaceCulture Podcast: https://bleav.com/shows/faceculture-giving-you...

08/06/2026

https://www.instagram.com/reel/DZKxkPXsW3n/?igsh=dmw2NDZnZHF3azVn

19/05/2026

why not........

12/05/2026

https://www.youtube.com/shorts/KW_bvB33kBc

284K likes, 11K comments. "The most beautiful invention of all time"

02/05/2026

Not Gordon Ramsay but a top NZ chef Ben Shewry who cleary understands and applies SIPOC learnings correctly.........