- Client
- Urban Mobility International (Volkswagen Group)
- Role
- Ways of Working & OKR Cadence Design
- Timeline
- 2019–2021
- Industry
- Mobility / Automotive
- System
- Operating
- Domain
- Mobility
- Design Lever
- Cadence
- Primary Outcome
- Alignment
- Framework
- Operating Cadence System
Executive summary
A startup-to-scale transition with a fixed launch window across three cities. Leadership was spending 540 minutes a week in standing meetings before work could move.
Result: Decision latency cut from 2.6 days to 1.1 days. Five chapters running a shared cadence. Three-city launch, on schedule.
Key outcomes
- Defined chapter-level OKRs and leadership OKRs with measurable review points
- Replaced ad-hoc syncs with a weekly stand-up rhythm across five operating chapters
- Cut leadership time trapped in standing meetings while preserving decision quality
- Aligned execs and heads of department on one launch narrative under a 90-day horizon
Principles
- Meeting load is a design variable — organizations choose coordination mechanisms; standing meetings are a default, not a law of physics.
- OKR cadence must match decision frequency, not fiscal calendar convenience; quarterly goals with weekly reviews outperform annual goals with quarterly panic.
- Scale-ups fail when operating systems lag geographic expansion — launch new cities on a cadence the organization can sustain.
- Decision quality and decision speed are not trade-offs when accountability structures are explicit; they are trade-offs when they are implicit.
Operating cadence vs. meeting load
Coordination efficiency across operating structures
Over-engineered
Too much process
Healthy operating rhythm
Structured with low drag
Meeting chaos
High overhead, weak rhythm
Under-coordinated
Low alignment
High meeting load·Low meeting load
Integrated cadence
Ad hoc cadence
Directional assessment · mock operating units · pre/post engagement synthesis
WeShare
Urban Mobility International (UMI) — Berlin, Hamburg, and European rollout

Key metrics
540
Leadership and chapter meeting minutes per week (before my enagement)
90d
Launch runway for the three-city go-live window
5
Chapters running shared OKR reviews and weekly syncs
3
Cities in the coordinated first-wave rollout
Framework
Operating Cadence System
The Operating Cadence System transforms team structures, OKR cycles, and cross-functional dependencies through a ways-of-working framework — producing reduced meeting load, faster decisions, and sustainable team alignment. WeShare proved that mobility scale-ups inside corporate ecosystems can redesign their operating rhythm without waiting for a reorganization.
Inputs
Core System
Ways-of-working framework with cadence design, meeting optimization, and alignment rituals
Outputs