Prototyping a mobile app for on-the-go kanban updates

Field supervisors in regional Queensland often stand in front of a paper card wall before dawn, photograph it for absent colleagues, and then drive two hours to the next site where the wall does not exist at all. Across construction corridors in Sydney, mining camps near Kalgoorlie, and hospital maintenance hubs in Perth, the same pattern repeats: a beautifully maintained board lives in one room while most of the team works somewhere else. The gap between the board and the worker is exactly what a pocket-sized kanban interface tries to close.

For lean and agile teams, the discipline of visual management only delivers value when the visualisation is actually seen. A card wall that nobody can reach is a status meeting without the participants. Chalmers Electronic Lean Research Team has been exploring how digital tools can preserve the immediacy of the physical board while extending it onto the phones that already travel with every supervisor, foreman, and team lead.

This piece walks through the prototyping journey of one such mobile kanban tool, the research choices behind it, the conversations with Australian practitioners that shaped its features, and the lessons that emerged when the prototype was tested on real work sites. It also offers a short set of recommendations for anyone considering a similar build for their own distributed teams.

Why mobility matters in visual management

Lean practice treats the kanban board as more than a tracking artefact. It is a shared cognitive surface where bottlenecks, queue lengths, and work-in-progress limits become visible at a glance. The problem begins when the team is split across buildings, shifts, or suburbs. Photographed boards, end-of-day email digests, and printed status sheets reintroduce the very delays that lean thinking tries to remove. Workers carry powerful computers in their pockets, yet the visual workflow that anchors their daily coordination often lives behind a desktop login on a single shared screen.

In Australia, the geography amplifies the problem. Projects regularly span thousands of square kilometres, and fly-in fly-out rosters mean that the team present on Monday may be a thousand kilometres away by Thursday. A site engineer in Adelaide cannot manage work on a wall located in a Darwin industrial estate, and a maintenance crew on a Pilbara rail line has no physical board at all. Mobility, then, is not a luxury feature but the difference between a board that informs and a board that is ignored. Tools and learning material curated at the lean production resources centre show how widespread this interest has become across operations, manufacturing, and service teams worldwide.

That realisation shaped the framing brief for the prototype. The goal was never to replace the physical card wall, which remains valuable as a shared anchor in team rooms. The goal was to give the same workflow a portable companion that respects the affordances of a phone: thumb-driven gestures, glanceable cards, and reliable behaviour on patchy regional networks.

Talking to operators across Australian projects

Before drawing a single screen, the research team ran structured interviews and shadowing sessions with practitioners in Sydney, Brisbane, and Melbourne. The participants came from construction, healthcare facility management, and software delivery, which is the most common cluster for lean work inside Australia. The aim was not to confirm a hypothesis but to learn which features practitioners would actually open during a shift.

Three themes emerged quickly. First, supervisors wanted to see and update the board without leaving the conversation they were having on site. Second, they cared more about reliability than richness. A simple, fast, always-available view beat a feature-heavy tool that occasionally dropped data. Third, Australian workplaces operate inside the Privacy Act and the Australian Privacy Principles, so any prototype handling personal workload data had to make consent, retention, and access controls visible and configurable.

The interviews also surfaced habits that would shape the prototype's tone. Australian supervisors tend to be informal communicators who use short, direct phrasing. They expect software to match that register rather than the formal corporate voice common in older enterprise tools, and this influenced copy across the interface, from button text to notification wording.

Designing the interface around cards and gestures

A kanban interface on a five-inch screen has to make peace with the limits of that screen. The prototype adopted a strict one-column-per-swimlane layout, with each card representing a single work item. Tapping a card reveals its full details, while a long press opens quick actions such as move, block, request review, or attach a photo. Swiping a card horizontally moves it between columns. These gestures mirror the physical act of pushing a paper card along a board, which helps teams cross the mental bridge from the wall in the team room to the screen in their hand.

Cards were designed to carry only the information needed for a quick decision. Work item type, owner avatar, age in days, and a coloured blocker tag are visible without expanding the detail view. This emphasis on glanceability reflects a principle discussed in research literature: visual cues compete for cognitive load, so the most important signals need the most visible position. The deeper reasoning behind that principle is laid out in the cue research itself, which the team revisited throughout the design phase. Subtle cues like ageing colour, blocker icons, and overdue markers were tuned carefully to communicate without shouting. Notification design followed suit, using badge counts and silent vibrations rather than disruptive banners, so that supervisors on a busy site could see what changed without losing focus on the work in front of them.

Building the prototype with an offline-first architecture

Reliable behaviour on regional Australian networks was the single most demanding technical constraint. 4G coverage is strong in metropolitan areas but uneven on remote sites, and underground or enclosed work zones regularly drop signal entirely. The architecture treats the phone as the source of truth for the worker's own interactions and synchronises with a central server whenever a connection becomes available. Conflicts are resolved using last-writer-wins for simple moves and a manual merge interface for more delicate cases such as simultaneous blockers.

The prototype stack uses a lightweight cross-platform framework so that updates can be shipped quickly to both Android and iOS devices. Local storage is encrypted at rest to support the privacy expectations set out by the Privacy Act, and access tokens are scoped to the worker's specific project memberships. Background sync is throttled to respect battery life on long shifts, and a visible sync indicator tells the user exactly when their last update reached the rest of the team.

Pilot testing across Australian workplaces

The prototype moved from lab to site over an eight-week pilot. Two construction supervisors in Western Sydney used it on active apartment projects. A maintenance coordinator in Brisbane trialled it across a portfolio of hospital buildings. A small product team in Melbourne embedded it in their daily standup routine alongside their existing physical board. Each pilot site agreed to share feedback under privacy terms negotiated before the trial, consistent with the Australian Privacy Principles around collection and disclosure.

The Sydney construction team found the most value in photo attachments. Foremen snapped site conditions, attached them to specific cards, and the design team could see the exact issue without leaving their home. The Brisbane maintenance team valued the blocker workflow most, because their distributed technicians needed a low-friction way to flag waiting conditions on parts or approvals. The Melbourne product team liked the silent notifications and used the mobile board to keep remote teammates connected to the rhythm of the physical wall in the office.

Across all three pilots, reliability mattered more than features. Participants tolerated rough visual design and unfinished edges far more readily than they tolerated lost updates or confusing sync states. That signal has influenced every subsequent iteration of the prototype, and the full set of pilot notes is being shared through Project Visit as part of the team's commitment to open research practice.

Practical guidance for prototyping a similar field tool

Field experience from a real pilot is worth more than any number of design assumptions. The following points emerged from the Australian trials and the wider research literature on mobile lean tooling.

• Start with shadowing, not screen designs. Spend at least three days observing how supervisors actually check status before opening a design tool.
• Treat the physical board as a partner, not a rival. The mobile interface should feel like a host when the worker can attend the board and an alternative when they cannot.
• Optimise for the worst network, not the best. Build for offline-first behaviour and test on real regional coverage rather than office Wi-Fi alone.
• Keep cards lean. Age, owner, type, and a single blocker indicator are usually sufficient on a small screen.
• Match local register. Australian supervisors value direct, plain-spoken copy over formal enterprise language.
• Plan the pilot's privacy terms up front. Make consent, retention, and withdrawal clear and easy, and align them with the Australian Privacy Principles.
• Measure reliability, not features. Track sync success, time to update, and battery impact as core metrics rather than feature usage.

These points are starting positions rather than finish lines. Every site, team, and sector will tune them differently, and that tuning is where the real learning happens.

The work continues to evolve as the prototype enters its second pilot round, with a sharper focus on photo-rich workflows and on integration with enterprise systems already used by industry collaborators. Each iteration is shaped by the same principle that has guided the research from the start: visual management is only valuable when the people doing the work can actually see the work.

The thing to take away is that a mobile kanban interface is not really about software. It is about giving every worker, no matter how far from the team room, a way to see the work, move the work, and stay connected to the rhythm that lean thinking was always meant to provide.