Synergy IT Solutions logo Synergy IT Solutions logo
  • Services
    • IT Navigator
    • Compliance as a Service
    • Modern Work
    • Device as a Service
    • Technology Sourcing
  • Industries
    • Education
    • Finance
    • Healthcare
    • Legal
    • Local Government
    • Manufacturing
  • Insights
    • Blog
    • Resources
  • About
    • Leadership
    • History
    • Careers
  • Request a consultation
    • All
    • Cybersecurity
    • Leadership
    • Compliance
    • AI
    • News
    • Strategy
    • IT Advisors
    • Remote Work
    • Technology
    • Asset Lifecycle Management
    • Device as a Service
    • IT Navigator
    • Synergy
    • Unified Communications
    • fintech
    • Hybrid
    • Microsoft Teams
    • Operations & Performance
    • SOC II
    • localbusiness
    • phishing
    • Automation
    • Awards
    • Deployments
    • Integrated IT Management
    • Modern Work
    • Native Cloud
    • Systems & Integration
    • Work
    • assessments
    • small business
  • Leadership

What Worked in 2026: Lessons from High-Performing Organizations

John Ende John Ende Nov 16, 2026

This past summer, I had the opportunity to hear Dr. Leidy Klotz speak at the Tugboat Institute Summit. His talk had a real impact on me, beginning with a story about playing with LEGO bricks with his young son.

Klotz had built a bridge with a support on only one end and asked his son to make it symmetrical. Instead of adding another support, his son simply removed the existing one.

It was a simple solution, but not necessarily the one most of us would think of first. When we want to improve something, we tend to look for what we can add. His son saw an opportunity to subtract.

That idea is a useful lens for reflecting on the past year. A lot changed in 2026. New tools, new initiatives, and no shortage of activity. But when you strip all of that back and ask what actually drove improvement rather than just movement, the distinction that matters is not how much an organization did, but how deliberately it chose where to focus.

The patterns are not especially complicated or surprising. They are just less common than they should be.

Focus as a Performance Driver

Focus is more than a stated priority. It is the practice of choosing a small number of areas that have the greatest bearing on how the business operates, and concentrating effort there instead of spreading it thin across a dozen competing priorities.

That kind of focus creates clarity, and clarity turns out to be worth a lot. Teams know what matters. Efforts line up instead of pulling against each other. Progress compounds rather than getting diluted. And once momentum builds in one area, it tends to make the next improvement more achievable.

The difficult part is deciding what will not get your attention. Without that choice, every new priority risks becoming one more thing competing with the work that matters most.

Why Removing Things Mattered More Than Adding Them

Simplification kept coming up as a theme, and it's worth sitting with why. Most organizations accumulate complexity gradually and without much fanfare: a new system here, a workaround there, a process that made sense once and then just stayed.

The natural response when something isn't working is to add something to fix it. Klotz's story offers a reminder to pause before doing that. Does the business need another layer, or does something already in place need to come out?

That might mean eliminating unnecessary steps, streamlining processes that have grown bloated, or aligning systems that have been operating in parallel for no good reason. The payoff isn't just efficiency in the narrow sense. It's that the business becomes easier to run, with fewer obstacles between people and the work they need to do.

Technology as a Means, Not an End

Technology played a meaningful role in a lot of these improvements, but the opportunity wasn't always in adopting something new. Often, it was in getting more out of the tools already in place.

The starting point should be the outcome the business needs to achieve, followed by how technology can support it. That distinction is easy to underestimate.

Technology adopted in pursuit of a specific outcome gets configured with intention, used deliberately, and adjusted as you learn. Technology adopted because it seems promising can end up partially implemented, quietly underutilized, and eventually absorbed into the stack of things that are technically running but not really doing much.

The question is not simply whether a tool can do more. It is whether it helps the business accomplish what matters.

Improvement as an Operating Mode, Not a Project

Another important lesson is how organizations approach change itself. Improvement shouldn't be something you do periodically when things get bad enough to warrant attention. It should be part of normal operations: an ongoing expectation built into how the business runs.

That means revisiting processes regularly and adjusting systems as the business evolves. There should be a standing assumption that things will keep changing, and that staying current requires continuous attention rather than occasional overhauls.

That mindset can make it easier to adapt when circumstances shift and help prevent small inefficiencies from becoming accepted ways of working.

What to Take Into the Next Year

None of these lessons are particularly novel. Focus on what matters. Simplify how the business operates. Connect technology to outcomes rather than adopting it speculatively. Treat improvement as ongoing work rather than a project with a finish line.

Knowing these principles is not the same as putting them into practice. They require sustained commitment, not occasional enthusiasm.

As you consider your priorities for 2027, ask not only what your organization needs to add, but what it could remove. Which processes no longer serve their purpose? Which tools create more work than value? What could your team stop doing to give its most important work the attention it deserves?

I recommend Klotz's book, Subtract: The Untapped Science of Less, to anyone thinking through those questions. His talk stayed with me because it challenged a familiar assumption: that making something better means adding something to it.

Sometimes, the better answer is what you take away.

Topics discussed

  • Leadership

Related Posts

Subscribe via email

Subscribe to our blog to get insights sent directly to your inbox.

Subscribe Here!

Subscribe via email

Subscribe to our blog to get insights sent directly to your inbox.

Subscribe Here!

footer-logo

Locations

Buffalo

452 Sonwil Dr.
Buffalo, NY 14225

716.250.3200

Rochester

3500 Winton Pl., #4
Rochester, NY 14623

585.758.7100

Syracuse

6443 Ridings Rd, #130
Syracuse, NY 13206

315.457.4444

Ithaca

25 Dutch Mill Rd.
Ithaca, NY 14850

607.257.3524

Explore

  • Services
  • Industries
  • Blog
  • About
©2026 Synergy IT Solutions. All rights reserved.
Privacy Policy Terms of Service Trust Center
  • LinkedIn
  • Facebook
  • Twitter