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

Lessons from a Swedish Tech Startup's Lean Visual Management Rollout

In the basement of a co-working space in Gothenburg, a small software team began replacing its sprawling Jira boards with hand-drawn Kanban cards pinned to a sheet of plywood. The change looked almost primitive, yet over twelve months the startup reported a 38 percent drop in cycle time and a noticeable lift in team morale. Researchers from Chalmers University of Technology followed the rollout closely, treating the experiment as a living case study in how lean visual management behaves outside the manufacturing halls where it first matured. Their notes, later published through Project Visit, offer an unusually granular view of a young company trying to balance autonomy with discipline.

For readers in Australia, the story lands closer to home than it might first appear. Distributed software teams in Sydney, Melbourne and Brisbane wrestle with the same friction between personal flow and shared visibility, often across time zones that stretch from AEST to AWST. The startup's journey, captured in plain language rather than consultancy slogans, gives practitioners here a template to argue for visual systems without resorting to corporate theatre. It also helps explain why lean thinking keeps turning up at industry meetups from Cremorne to the Perth mining-tech corridor, where small teams are quietly redesigning their daily routines around what they can see on the wall.

Why visual management mattered to the team

The startup had grown from six engineers to twenty-three in just over a year, and the founder openly admitted that no one on the leadership team could honestly say where every piece of work sat. Sprint reviews had become storytelling sessions, with status updates reconstructed after the fact rather than tracked in real time. Visual management was introduced not as a cultural upgrade but as a survival tactic, the same way a Sydney fintech builds incident dashboards after its first production scare rather than before it. The team needed a way to make bottlenecks visible to everyone, including the part-time investor who dropped in on Fridays and wanted a five-second answer to whether the quarter was on track.

The Chalmers research team, working alongside the company, framed the intervention around three questions often overlooked in vendor pitches. Where does work actually spend its time? Whose responsibility is it when a card stalls? And how do you keep the board honest when deadlines slip and engineers quietly absorb the slack? Those questions echo through countless retrospectives in Melbourne and Brisbane offices, where local engineers complain that their "single source of truth" is in fact a dozen tabs, three chat threads and a forgotten spreadsheet. By centring the rollout on those questions rather than on tools, the Swedish team avoided the trap of mistaking the board for the system.

Mapping the workflow before the first board went up

Before any card was written, the researchers and the startup's engineering lead spent three weeks tracing how a feature actually moved from idea to production. They followed pull requests, sat in support rotations and watched how designers handed work to developers. The exercise exposed several unofficial queues that nobody had drawn on paper: a Slack channel where ideas quietly decayed, a Friday review ritual that acted as a hidden gate, and a testing bottleneck caused by a single overstretched engineer in the team. Mapping these flows in plain ink on butcher's paper turned the conversation from abstract methodology into a shared portrait of reality.

The mapping phase also produced a small but important cultural shift. People who had never spoken up in planning meetings started pointing to stages on the diagram, explaining where they felt overloaded. One senior developer compared the experience to the first time he watched a slow-motion replay of his own surfing at Bondi: confronting, but clarifying. By the time the team sketched its first Kanban board, the columns reflected the company's real rhythm rather than a textbook five-stage pipeline, and there was broad agreement about what each column meant. Researchers noted that this honesty at the design stage is what separated the rollout from the dozens of Kanban installations that look perfect on day one and quietly drift by day thirty.

Designing boards that survive daily standups

Physical boards were chosen over digital ones for the engineering floor, on the grounds that a screen cannot be glanced at from the kettle or noticed by the founder passing through. The plywood sheet was divided into columns labelled Backlog, Ready, In Progress, Review and Done, with swimlanes for product, platform and integrations. Cards carried a brief description, an owner and a coloured magnet for priority. Crucially, the team imposed a work-in-progress limit of three per person, a rule borrowed directly from lean manufacturing and adapted for a context where engineers often juggle production support alongside new features.

What kept the board alive, according to the research interviews, was the discipline around the daily standup. Rather than gathering around the board in a circle, the team stood in an arc so everyone could see both the columns and the people's faces. Updates lasted no longer than ninety seconds and always pointed to a specific card. When someone was blocked, the conversation moved offline immediately rather than turning into a group therapy session. The rules felt strict, yet they produced a rhythm that engineers compared to the cadence of a Big Bash innings: bursts of intensity punctuated by quiet recovery, with everyone able to read the score at a glance.

The researchers also noted a quieter benefit that resonated with operators thousands of kilometres away. The board became a shared artefact that freelancers and contractors could read on their first day, reducing the awkward onboarding window that often stretches for weeks in fast-growing startups. One contractor based in the same Gothenburg hub said the board let him contribute meaningfully within two days, a contrast with previous gigs where he spent a month translating tribal knowledge. Australian teams familiar with the challenges of onboarding contractors across AEST and ACDT, or coordinating with partners in Southeast Asia, will recognise the value of that shared visibility immediately.

Behavioural shifts inside a small engineering culture

Lean visual management is often sold as a tooling change, but the Swedish case study shows it is really a behavioural one. Engineers who had been quietly absorbing delays started surfacing them, because the WIP limit made hiding impossible. A card sitting in the Review column for three days triggered a conversation, sometimes uncomfortable, sometimes productive, but always visible. The team's lead compared the change to the cultural adjustment Australian cricketers make when moving from club grade to the national side: the scoreboard no longer forgives sloppy technique, and accountability becomes collective rather than personal.

Another shift was in how the company handled interruptions. Production incidents, customer escalations and last-minute investor requests used to land in shared inboxes and gradually strangle feature work. Once the team adopted a separate "expedite" lane on the board, with a strict cap of one active card, the cost of context switching became legible. Engineers could see when their flow was being eroded, and product managers became more selective about what they labelled urgent. Researchers who observed the rollout noted that this small design choice probably saved more hours than any of the more dramatic visualisations.

There were also growing pains. Two engineers left during the first quarter, citing the new transparency as "too much pressure". The leadership team chose not to roll back the practice, arguing that the comfort of opacity was exactly what had slowed them down in the first place. That decision mirrors a debate playing out in Australian tech hubs, where founders of rapidly scaling companies weigh the benefits of radical transparency against the risk of losing talent who prefer quieter workflows. The Swedish team eventually stabilised, replacing the departures with hires who actively cited the visual system during interviews.

What Australian operators can take from the Gothenburg experiment

The most portable lesson is that visual management is not a software purchase but a shared habit, and habits take longer to build than dashboards. Teams in Melbourne and Sydney who try to copy the layout without copying the daily ritual around it see the same drift documented in the Chalmers study. Equally, teams that begin with mapping rather than with board design tend to land on column definitions that everyone actually recognises. Australian readers interested in the original research notes and prototype tools can explore further through Project Visit, which hosts the team's publications and ongoing work.

A second lesson is to design for the hallway, not the screen. In a country where office footprints in Perth and Adelaide often stretch across large floor plates, and where hybrid work means many team members join standups from home, the physical board still earns its place by giving the in-office team a shared reference point. Remote participants can join via a simple camera feed that points at the board rather than at someone's face, an arrangement that the Gothenburg team refined over several months. The point is not to romanticise sticky walls, but to recognise that visibility is a design choice with cultural consequences.

Practitioners looking for a structured starting point often benefit from connecting with researchers who have already walked this path. Direct lines to the Celean team are available through their contact page, where requests for study visits, prototype access and collaborative pilots can be raised. For those curious about the broader lean research conversation, including work on visual planning, Kanban and enterprise systems, additional reading and related industry studies are linked from vhodvlk, a useful companion resource.

Recommendations for teams planning their own rollout

The Swedish experiment shows that lean visual management rewards teams willing to be a little uncomfortable in exchange for a clearer picture of their own work. Australian software organisations navigating scale across Sydney, Melbourne, Brisbane and the mining-tech corridors of Western Australia carry similar pressures and similar opportunities. The boards will not solve the underlying tensions around priorities, capacity or funding, but they make those tensions discussable rather than deniable. The clearest thing to take away is that visibility is a discipline, not a deliverable, and the teams that treat it as the former tend to be the ones who quietly outperform their peers.