When businesses run into operational friction, the first instinct is often to look for a better tool.
A new CRM.
A new project management platform.
A new automation system.
A new AI workflow.
And sometimes that helps.
But recently, Nesanel Moeller, Co-Owner of The Penguin Group, was helping a company troubleshoot what they believed was a major HubSpot issue.
“The platform was extremely slow, and everyone assumed HubSpot was the problem,” Nesanel explained. “But once we looked at the actual computers they were using, the issue became obvious. Their systems were running almost no available RAM on processors that were nearly a decade old.”
Once the team understood what was actually happening, the frustration made sense immediately — and so did the solution.
That experience highlights something we see often at The Penguin Group: The visible problem and the actual problem are often not the same thing.
Technology Often Exposes Existing Operational Problems
Most companies diagnose issues based on where the frustration appears.
If the slowdown happens inside the CRM, the CRM gets blamed.
If communication breaks down in project management software, the platform gets blamed.
If automation fails, businesses assume the workflow tool is broken.
But operational problems are usually more interconnected than they appear. Technology often exposes inefficiencies that already existed underneath the surface:
- inconsistent workflows
- poor communication between teams
- unclear ownership
- outdated infrastructure
- manual workarounds
- fragmented processes
Software doesn’t create those problems. It simply makes them more visible.
Operational Friction Is More Expensive Than Most Companies Realize
Research continues to show how much inefficiency exists inside day-to-day business operations.
According to Asana’s Anatomy of Work report, employees spend 58% of their time on “work about work” — things like coordinating tasks, searching for information, switching between apps, and managing inefficient processes rather than doing skilled, productive work.
Similarly, Atlassian found that employees lose an average of two hours every day searching for information or tracking down the people they need to work with.
Those numbers point to a much bigger issue than software selection alone. In many companies, the operational structure underneath the technology was never clearly defined in the first place.
Why Operations Matter Before Software
At The Penguin Group, this is one of the biggest reasons we focus heavily on operations and processes before recommending technology solutions.
Before implementing software, companies need clarity around:
- how work flows internally
- who owns which responsibilities
- where communication breaks down
- how approvals happen
- and where operational bottlenecks actually exist
Once those things become clear, the technology decisions usually become much easier — and far more effective. Because software works best when it supports a strong operational foundation.
Good Technology Still Needs Good Systems
Modern businesses have more technology available than ever before: AI tools, automation platforms, CRMs, project management systems, communication tools, and so on. But adding more technology without understanding the underlying operational issue often creates more complexity instead of less.
The companies that scale most effectively are usually not the ones chasing the most tools. They’re the ones that take the time to understand how their business actually operates before trying to optimize it.
Because when the root problem becomes clear, the right solution usually becomes clear too.