Embedded Files
More With Less:
One of the more interesting patterns in my career is that I've consistently been asked to improve output while working within tighter constraints. Sometimes that meant budget reductions. Sometimes it meant layoffs. Sometimes it meant inheriting teams that had outgrown their systems.
None of those situations are ideal, but they're incredibly common.
I suspect that's why I've become so interested in operational excellence.
The phrase more with less has developed a pretty negative reputation over the years. It often feels like corporate shorthand for reducing resources while expecting employees to absorb the difference. That's never been my approach.
I've always viewed it as a resource allocation problem rather than a cost-cutting problem.
The goal isn't to squeeze more work out of people. The goal is to determine whether the right work is being performed by the right people, supported by the right processes and technology.
That perspective changes everything.
When I evaluate an operation, I don't start with tools. I follow the work. I want to understand where it originates, who owns it, where it changes hands, and where it slows down. I'm particularly interested in workarounds because they're often pointing toward a larger operational problem.
A spreadsheet outside the CRM.
An inbox that's become a workflow engine.
An employee manually copying information from one system to another.
Those are clues.
One example involved a software platform that leadership had already identified as a candidate for elimination. The challenge wasn't recognizing that the technology no longer justified its cost. The challenge was replacing the functionality without disrupting the business during its busiest season.
We rebuilt the functionality inside systems we already owned while simultaneously reviewing the broader technology stack for additional opportunities to consolidate tools and reduce unnecessary spending.
That experience reinforced something I still believe today: every investment should earn its place.
At another organization, I developed a framework for evaluating outsourcing opportunities. We focused on transactional work that could be separated from higher-value activities requiring deeper institutional knowledge. The objective wasn't replacing employees. It was creating capacity.
Contractors serve a different purpose.
I've always viewed contractors as a short-term capacity strategy. If demand arrives in predictable annual surges, contractors provide flexibility without creating a permanent staffing commitment. If demand is recurring throughout the year, outsourcing often becomes the better solution. And if the work is strategic, specialized, and unlikely to be automated, investing in full-time employees remains the right choice.
There's no universal formula.
One of the most challenging examples came during a period of organizational restructuring that included promotions, team transitions, changing departmental ownership, and workforce reductions. We had to rethink how work was distributed while continuing to support the business.
One of the team's biggest frustrations was phone coverage.
Employees responsible for project-based work were also responsible for answering phones. The constant interruptions created frustration and made focused work nearly impossible.
We redesigned the process from multiple angles. We protected uninterrupted work blocks, redesigned the phone tree, expanded call coverage, and eventually transferred ownership to the team that was already handling much of the inbound volume.
The phones never stopped ringing.
The work simply moved to the people and processes best equipped to support it.
That's operational excellence. Not working harder. Redesigning the work itself.
I've spent more than a decade working across sales operations, marketing operations, and revenue operations. I've negotiated technology contracts, redesigned processes, implemented workflow automation, introduced AI into operational processes, leveraged outsourcing, expanded contractor models, and developed employees into strategic operators.
The common thread isn't technology.
It's intentionality.
The answer isn't always AI.
The answer isn't always automation.
The answer isn't always another hire.
Operations sits at the intersection of people, process, technology, and business strategy. The best solutions usually borrow from all four.
More with less isn't about cutting resources.
It's about building an organization that understands how to deploy them wisely.
Google Sites
Report abuse