WORK

What it looks like in practice

Every case is different, but the pattern holds: the problem is rarely effort. It's usually structure, sequence or trust. Here's what that has looked like.

Doing More With Less Without Burning People Out

Situation. A regional, mission-driven food business facing rising labor costs, softening demand, complex weekly production and thin margins. Hiring more people wasn't an option.

The real constraint. The team worked hard. The problem was structural:

bottlenecks hidden inside weekly rhythms
systems that didn't fit how people actually worked
constant last-minute decisions that drove rework

What we did. Stabilize first, then build capacity.

Redesigned production and fulfillment flow to remove recurring bottlenecks
Upgraded routing and delivery without disrupting customers
Reshaped staffing so fewer people could do higher-quality work
Invested in tools that reduced friction instead of adding oversight
Said no to changes that added noise without relieving the constraint

Results. No increase in headcount, while improving pay, tools and reliability:

Higher productivity per person (smaller team produced more each week, delivery costs decreased as high as 10% in one location, meals were consistently delivered earlier )
Less week-to-week volatility (large swings in orders week to week moved toward more consistent, repeat ordering)
More production capacity and menu volume (~ 20 items to as high as ~50)
Better customer retention through a drop in demand (~12% AOV increase, 3% relative bump in retention after delivery upgrade, increased multiple orders per month cohort)
A calmer operation for leadership

Takeaway. Clear systems, good sequencing and margin for people to think often unlock capacity you already have.

Case Study: Modernizing Critical Systems Without Breaking Trust

Situation. A nonprofit organizations faced an acute squeeze:

Insufficient technology and immediate challenge to core methods
Pandemic pressure to modernize fast
Little tolerance for disruption, and relationships that could be damaged by a misstep

The real constraint. Change was necessary, but poorly sequenced change would damage credibility and erode trust. Sound decisions fail when implementation outpaces stakeholder confidence.

What we did. Limited the damage any one change could do before changing anything.

Diagnosed root system failures instead of reacting to surface complaints
Selected and implemented the right tools and platforms
Sequenced upgrades so services never went down
Explained decision logic clearly to non-technical stakeholders
Secured governance and regulatory compliance before acting

Results.

Multi-campus network rebuilt: ~16 Mbps → ~150 Mbps across dozens of buildings
Reliable remote learning through pandemic disruption
First-ever virtual annual meeting with secure, compliant voting across two countries
No extended downtime during any transition
Stronger stakeholder confidence in leadership

Takeaway. Systems change succeeds when sequencing, communication and trust are treated as seriously as the technology.