All Case Studies
Case Study
From Slow, Fragmented Delivery to a Clear Operating System That Accelerated Execution
Problem: Operational Visibility
Company
A Large Australian Technology & Transport Company
Industry
Enterprise / Technology & Transport
Problem
Delivery inside the organisation had become painfully slow. Projects regularly took nine months or more despite capable, motivated teams.
What we built
- • OKR-based strategic alignment framework
- • Team structure and role clarity redesign
- • Leadership and execution cadence
- • Organisation-wide visibility system
Outcome
- ✔ Delivery cycles reduced from 9+ months to ~12 weeks
- ✔ Division scaled from 70 to 130 team members
- ✔ Employee engagement score rose from 3.7 to 4.5
- ✔ Leadership gained clear progress visibility
The Situation
Where things stood
A large Australian transport and digital payments company was expanding its internal technology and digital product division.
Demand for new digital products and platform improvements was growing rapidly.
However, delivery inside the organisation had become painfully slow.
Projects regularly took nine months or more to deliver, despite the teams being capable and highly motivated.
Inside the division several symptoms were emerging:
• Delivery timelines were unpredictable
• Teams struggled to coordinate across functions
• Leaders lacked clear visibility into progress
• Accountability between teams was unclear
• Employee engagement was declining
The organisation had already adopted Agile tools and modern project management practices.
But despite everyone working extremely hard, execution remained slow and frustrating.
The problem wasn't effort.
The organisation had grown quickly, and the operating system behind how work moved through the business had never been properly designed.
The Bottleneck
What was actually in the way
When we stepped back and mapped how work was actually happening, the issue became clear.
The problem wasn't project management.
It was a missing operating framework connecting strategy, teams, and execution.
Several structural gaps existed:
• Company priorities were not clearly translated into team-level goals
• Accountability across teams was unclear
• There was no shared operating rhythm for leadership
• Work was tracked inconsistently across teams
• Progress visibility across the organisation was limited
Because of this:
• teams often worked in different directions
• decisions were revisited repeatedly
• leaders struggled to understand delivery progress
The organisation had talented people and strong ambition.
But without a clear operating system guiding execution, projects took far longer than necessary to complete.
The Fix
What we built
To resolve the delivery bottlenecks, we rebuilt the division's operating framework so strategy, teams, and execution were clearly connected.
1. Strategic Alignment Through OKRs
We introduced Objectives and Key Results (OKRs) to connect company strategy with day-to-day execution.
Leadership could now clearly define:
• the most important company objectives
• measurable outcomes defining success
• how each team contributed to those outcomes
For the first time, teams had a shared understanding of what mattered most.
2. Team Structure and Role Clarity
Next, we redesigned how teams were structured and how responsibilities were defined.
This included:
• clearer role definitions
• improved ownership of initiatives
• stronger accountability between teams
This removed confusion around who was responsible for delivering key outcomes.
3. Leadership and Execution Cadence
We introduced a structured operating rhythm across the division.
Instead of reactive conversations and ad-hoc decisions, the organisation adopted:
• quarterly planning cycles
• structured progress reviews
• defined decision-making frameworks
• leadership execution check-ins
This created a consistent flow between planning, execution, and review.
4. Visibility Across the Organisation
To support the new operating rhythm, we implemented a system that made goals, progress, and feedback visible across the division.
Teams could now easily track:
• progress against OKRs
• project milestones
• team sentiment and engagement
This transparency allowed leadership to identify problems earlier and support teams more effectively.
Tool Layer
The operating system was supported by a small number of enabling tools.
15Five
• company and team OKR tracking
• regular progress check-ins
• visibility across teams
• employee engagement measurement
The tool created a simple way for teams and leaders to stay aligned around goals and progress.
The Outcome
What changed
- ✔Delivery timelines improved dramatically — project cycles reduced from 9+ months to approximately 12 weeks
- ✔Visibility across the division improved substantially
- ✔Leadership could identify and resolve issues faster
- ✔The division successfully scaled from 70 to 130 team members
- ✔Employee engagement score increased from 3.7 to 4.5
The Human Payoff
What it actually meant
The biggest change wasn't just operational — it was how the team experienced their work.
Before the new operating system:
• teams felt overwhelmed by unclear priorities
• leaders struggled to track progress
• decisions were constantly revisited
Once the new operating rhythm was in place:
• teams had clarity about what mattered most
• leaders could support teams more effectively
• people felt more confident and engaged in their work
Instead of constantly reacting to problems, the organisation now had a shared operating structure that allowed people to focus, collaborate, and deliver with confidence.