What “do less with less” actually requires

“Do less with less.”

It’s a phrase that’s showing up more and more right now.

On the surface, it makes sense. Resources shift. Priorities change. Organizations have to adapt.

But for teams that have spent years building high standards, strong service models, and a deep sense of pride in their work, this isn’t a simple shift.

Because when you’ve been trained to care deeply about your work, to show up with consistency, quality, and intention, it’s not always clear what “less” is supposed to look like.

It raises questions like:

• What do we stop doing?

• What does “less” actually mean in practice?

• How do we maintain quality while reducing workload?

Without that clarity, the message can start to feel like something else entirely.

Lower your standards. Care less. Accept less.

And that’s where tension shows up.

Not because people don’t understand the reality of change, but because they don’t have a roadmap for how to adapt without losing what made the work meaningful in the first place.

Why this shift feels so difficult

For high-performing teams, the challenge isn’t willingness.

It’s identity.

When you’ve spent years raising the bar, improving systems, and delivering high-quality work, those standards don’t just disappear because circumstances change.

They become part of how you define good work.

Part of how you define yourself professionally.

So when expectations shift without clear direction, the result is often:

• overextension, trying to maintain previous standards

• uncertainty around what to prioritize

• or disengagement when the work no longer feels aligned

None of those outcomes are the goal.

What’s often missing: a roadmap

This kind of shift only works when it’s paired with clarity.

That means:

• What are the new priorities?

• What work is no longer essential?

• What can be simplified, streamlined, or removed entirely?

Without those answers, people are left trying to solve for reduction individually, while still holding themselves to collective standards that no longer fit the reality.

That’s where frustration starts to build.

Evolving the work, not lowering the standard

Doing less doesn’t have to mean doing worse.

But it does require a shift in how work is structured and supported.

In many cases, the opportunity isn’t to reduce care.

It’s to reduce unnecessary effort.

That might look like:

1. Reducing repetition

Turning common tasks into templates, frameworks, or reusable workflows so teams aren’t starting from scratch every time.

2. Using automation intentionally

Automating routine communication, scheduling, or administrative steps that don’t require human decision-making.

3. Leveraging AI to support the work

Using AI to draft, summarize, or organize information. Not to replace thinking, but to reduce time spent on low-value tasks.

4. Standardizing where it makes sense

Creating consistent processes so work can move more efficiently across teams without constant reinvention.

5. Protecting human effort for what matters most

Focusing time and energy on the parts of the work that require judgment, creativity, and connection.

This isn’t theoretical for me

As I was writing this, I realized something: I’ve spent most of my career doing exactly this.

For over a decade, my role was to figure out how we could operate at a high level without always having the tools, training, or resources to match.

So I built systems.

I developed training and shared it across my organization, and eventually more broadly across the industry, to create a consistent baseline for how we approached the work.

I advocated for tools that made collaboration easier and processes that made work more repeatable.

And I taught my team to think differently about effort.

We didn’t need to recreate the wheel every time. We could build templates. Create frameworks. Find patterns that allowed us to work more efficiently without sacrificing quality.

We called it R&D (my favourite stolen term) — rob and duplicate.

Not as a shortcut, but as a way to reduce unnecessary effort and focus energy where it actually mattered.

Because the goal was never to do less carelessly.

It was to create systems that allowed us to do meaningful work, consistently, without burning out in the process.

And over time, that became our standard.

The reality behind these shifts

None of this happens automatically.

It takes:

• time to learn new tools

• space to experiment

• and support to rethink how work actually gets done

And that’s often the missing piece.

Because asking teams to change how they work without giving them the time or guidance to do so doesn’t reduce pressure.

It shifts it.

We’re not meant to figure this out alone

We also need to stop trying to figure all of this out on our own.

Across teams and organizations, people are finding small ways to work more efficiently. Better workflows. Smarter processes. Practical uses of automation and AI.

But too often, that knowledge stays hidden or hard to access.

So maybe part of this shift is building a culture where we share what works.

Not just ideas, but real, usable processes.

Documented. Accessible. Easy to build on.

Because the more we share, the less time we spend starting from scratch.

A different way to think about it

Maybe the conversation isn’t just about doing less.

Maybe it’s about:

• doing fewer things, more intentionally

• designing work that is sustainable

• creating systems that support people, not drain them

Because when teams have clarity, structure, and support, they can still deliver meaningful, high-quality work.

Just in a way that is more focused, more efficient, and more sustainable.

Final thought

Doing less with less isn’t just a directive.

It’s a design challenge.

And if we approach it that way, there’s an opportunity not just to reduce workload, but to rethink how work happens in the first place.