Cases / Aviation · PSS

One platform, one board: Kanban for an airline's PSS team

BEFORE

Work arrived through more than three channels; no shared backlog and no measured SLAs.

AFTER

One platform and one Kanban board; SLAs measured with real data (in progress).

Starting point

An airline’s passenger service system (PSS) team works with a main supplier, several smaller suppliers and internal teams. Requests came in through a ticketing system, shared mailboxes and chat channels. Work was owned by whoever received the request, not by the department, and progress lived in other people’s comments. There was no shared backlog and no shared definition of “on time”.

Approach: one platform, one truth

We set up a five-stage plan:

  1. Mirror the work. Integrate the ticketing system with the work tracking tool so all requests land in one place.
  2. Move the traffic. Use announcements and short training sessions to route requests to a single entry point.
  3. Close the side doors. Build integrations between tools with stakeholder teams.
  4. Fly on data. Shared flow and throughput reports; agree SLAs together with stakeholders.
  5. Keep it airworthy. Run change requests through the same system.

Success measures

  • From more than three channels to a single entry point
  • From no SLAs to standard SLAs agreed with stakeholders
  • No more “let me just ask someone else”
  • All reports coming from real flow data

Status

The work is ongoing. The real challenge is habit, not tooling: getting every internal and external stakeholder to adopt one environment. The first three stages lay the rails; the last two keep everyone on them.

More cases

All cases

Aviation · E-commerce

End-to-end flow in an airline's digital retail team

Before
Front-end and back-end teams worked with separate suppliers; there was no end-to-end process.
After
A defined end-to-end process; Kanban, visual flow and lead time tracking.

Aviation · SAP

Airline SAP team cuts its backlog in half

Before
A growing, ageing backlog; nobody could see where work was waiting.
After
With Kanban and weekly flow reviews, the backlog shrank by 50%.

In a 30-minute call, let's find the bottlenecks in your flow together.