Why Your First Internal IT Hire Could Become Your Most Expensive Mistake
- August 21, 2026
- Share
“Our MSP just isn’t keeping up anymore.”
“Let’s hire an IT Manager.”
When the Job Title Becomes the Strategy
A growing Winnipeg organization approached us some months ago after growing frustration with their external IT provider. Progress on projects was slow, internal teams were losing confidence, and leadership was convinced that technology was becoming a constraint rather than an enabler.
The decision had already been made before we entered the conversation. They wanted to hire an IT Manager.
At first glance, the request seemed perfectly reasonable. But as we began examining their technology environment, a very different picture emerged.
They had developed their infrastructure over a number of years without a consistent long-term plan. There was a lack of documentation for critical systems. There was no process to manage vendor relationships, and they had grown organically. Security duties were dispersed, and strategic decisions on technology ownership were missing.
The proposed IT Manager wasn’t being hired to lead an existing IT function. They were being hired to untangle years of accumulated technical complexity. Those are two entirely different roles. What the organization actually needed wasn’t another employee. They needed clarity.
Why Non-Technical Leaders Face an Impossible Hiring Decision
Technology hiring presents a unique challenge for executives because it often requires making highly technical decisions without having a technical background.
A Chief Financial Officer wouldn’t be expected to diagnose structural engineering issues before hiring an architect. Yet business leaders routinely find themselves expected to define cloud architecture requirements, cybersecurity priorities, infrastructure maturity, and leadership competencies before recruiting their first internal technology leader.
It’s an impossible expectation.
Leadership can clearly see the symptoms. Systems are slower than they should be. Employees are frustrated. Projects continue slipping behind schedule. Vendors appear to blame one another whenever something goes wrong.
What leadership cannot easily see is the architecture beneath those symptoms.
Without understanding that underlying environment, organizations often recruit based on assumptions rather than actual business requirements.
Growth Changes the Rules
One of the biggest misconceptions surrounding IT hiring is that technology requirements grow in a straight line. They don’t.
Technology complexity grows exponentially.
A company with twenty employees can often operate effectively using an outsourced support model. Double the workforce, introduce multiple cloud applications, remote employees, cybersecurity compliance obligations, digital customer platforms, and integrated financial systems, and the complexity changes dramatically.
Suddenly, technology is no longer simply supporting the business. It is becoming a business.
Across Canada, digital transformation continues to reshape organizations of every size. According to Statistics Canada, businesses continue to increase investments in cloud computing, cybersecurity, automation, and digital infrastructure as they modernize operations and respond to evolving customer expectations. At the same time, reports from the Information and Communications Technology Council (ICTC) continue to identify sustained demand for experienced technology professionals, particularly those capable of leading digital transformation initiatives rather than simply maintaining existing systems.
It’s particularly important for Manitoba businesses. Over the last ten years, the technology sector in Winnipeg has been growing steadily, and there has been a rising demand for expertise in the IT field in various manufacturing, professional services, healthcare, financial services, logistics, and public sector firms.
As technology becomes increasingly central to business operations, the cost of hiring the wrong leader becomes significantly higher.
The IT Manager Doesn't Exist
At least, not in the way many organizations believe.
One company’s IT Manager spends most of their day managing service desk operations and coordinating hardware deployments.
Another organization’s IT Manager oversees cybersecurity strategy, cloud migration, infrastructure architecture, disaster recovery planning, vendor management, budgeting, executive reporting, and digital transformation initiatives.
The title may be identical. The jobs are not. This misunderstanding creates one of the largest disconnects in technology recruitment.
Organizations recruit against titles instead of business problems. Candidates apply based on their interpretation of those titles. Everyone believes they’re discussing the same position.
They rarely are.
That disconnect often doesn’t become apparent until months after the new hire has joined the organization.
By then, expectations have already diverged, projects have stalled, and leadership begins questioning whether they hired the wrong person. In many cases, they did.
Not because the individual lacked capability, but because the role itself was never properly defined.
The Problem Isn't Always Your MSP
Managed Service Providers often receive the blame when organizations begin experiencing operational friction.
Sometimes that criticism is entirely justified. Sometimes it isn’t.
An MSP relationship that worked exceptionally well three years ago may no longer align with the organization’s current level of operational maturity. As businesses grow, they naturally require greater strategic ownership, stronger governance, faster decision-making, and deeper integration between technology and business objectives.
That evolution doesn’t necessarily indicate poor service.
It often signals that the business itself has changed. Replacing the provider without understanding that shift simply transfers the same underlying problems to a new employee.
An internal IT hire cannot compensate for the absence of governance, documentation, executive alignment, or strategic planning. Those issues need to be addressed first.
Before Hiring, Ask Better Questions
The Three Questions Every Manitoba Executive Should Answer First
- 1. Are you hiring for support or strategy?
- 2. Is your infrastructure documented?
- 3. What does success look like in 12 months?
The Financial Cost of Getting It Wrong
An unsuccessful executive appointment goes beyond just the pay. On average, Canadian human resources research has calculated that it costs 50 percent to 200 percent of a year’s salary to replace an experienced professional, depending on the complexity of the role, lost productivity, onboarding investment, recruitment cost, and the disruption that ensues. The added costs are even greater for technology leadership roles. Projects are suspended during a re-evaluation of priorities. Key projects stall out. Internal confidence declines. Conflicting instructions are given to external suppliers.
Future recruitment becomes more difficult because organizational uncertainty becomes increasingly visible. Perhaps most importantly, strategic opportunities are delayed.
In an economy where technology increasingly drives competitive advantage, lost momentum often costs more than recruitment itself.
Technology Debt Is a Business Problem
Technology debt is frequently misunderstood.
Many executives assume it refers to outdated hardware or legacy software.
In reality, technology debt is much broader. It includes undocumented infrastructure, inconsistent processes, unsupported systems, fragmented vendor relationships, security vulnerabilities, duplicated applications, and years of temporary solutions that gradually became permanent.
Like financial debt, technology debt accumulates quietly. Each shortcut appears manageable in isolation.
Collectively, however, those decisions eventually create an environment that becomes increasingly difficult to support, increasingly expensive to maintain, and increasingly risky to expand.
Putting a new IT leader into this environment without knowing its complexity is putting unrealistic expectations on the organization and the person. The technical aspect has to be clearly defined first, and then a recruitment strategy can be implemented.
The Winnipeg Reality
Manitoba’s technology sector continues to mature at an impressive pace.
Organizations are investing more aggressively in automation, cloud infrastructure, cybersecurity, artificial intelligence, enterprise software, and digital transformation than ever before. This growth has intensified competition for experienced technology professionals capable of leading organizations through increasingly complex operational environments.
The challenge isn’t simply attracting talent. It’s knowing exactly which talent the business requires.
Executive technology recruitment has become less about filling vacancies and more about organizational design. The strongest hiring decisions begin long before the first interview.
They begin by understanding how technology should support the future direction of the business.
A Different Way to Think About Your First IT Hire
Businesses often believe they’re recruiting a person. In reality, they’re making an architectural decision.
The first internal technology leader sets governance, establishes priorities, drives investment decisions, influences cybersecurity culture, gets the right vendors in place and decides how technology will help the organization grow for years to come.
That’s why successful organizations don’t begin with a job description. They begin with a diagnosis. They assess their current environment. They identify operational gaps.
They define strategic objectives. Only then do they determine which leadership profile best aligns with those goals.
Recruitment becomes the final step, not the first.
The Black Box Doesn't Have to Stay Closed
Technology doesn’t have to remain mysterious for business leaders.
Executives don’t need to become infrastructure specialists or cybersecurity experts to make informed hiring decisions. They simply need a structured process that translates technical complexity into business language.
That’s the purpose of this series.
At Lambert Nemec Group, we’ve intentionally shifted away from producing disconnected hiring advice in favour of real-world scenarios drawn from conversations happening across Manitoba every day. Behind every successful placement is a business challenge, a leadership decision, and a lesson that extends far beyond recruitment.
Because organizations don’t remember generic hiring tips. They remember stories that resemble their own. And perhaps the most important story we encounter is this one:
A growing company believes it needs an IT Manager.
After asking better questions, it discovered what it actually needed was a technology strategy. That distinction may seem small on paper.
In practice, it can save an organization hundreds of thousands of dollars, months of disruption, and years of technical frustration.
Before You Replace Your MSP, Pause
If your organization is beginning to outgrow its current technology model, resist the temptation to jump straight into recruitment.
Ask whether the business truly understands its infrastructure, its future direction, and the outcomes it expects from its first internal technology leader.
The answer may confirm that you’re ready to hire, or it may reveal that your next step isn’t recruitment at all.
Sometimes, the smartest hire is the one you delay until you fully understand the problem you’re trying to solve.
That’s how organizations move beyond reactive hiring and begin building technology leadership that supports long-term business growth.
