The 55% Threat Perception
Fifty-five percent of internal IT teams view MSPs as a job threat rather than a partner. CIO.com surveys reveal the depth of resistance that organizations underestimate when engaging managed services.
The perception isn’t irrational. MSP engagements sometimes do lead to layoffs. Even when jobs are secure, responsibility shifts feel like status erosion. The internal team that once owned the entire stack now shares ownership with outsiders.
The Pocket Veto Phenomenon
Information withholding, sometimes called the “pocket veto,” delays MSP project completion by 20-30%. The internal team doesn’t actively sabotage. They simply fail to provide timely information, escalate appropriately, or cooperate efficiently.
| Resistance Behavior | Impact | Detection Difficulty |
|---|---|---|
| Delayed information sharing | Project slowdowns | Medium |
| Missing meeting invitations | Coordination gaps | Medium |
| Incomplete documentation | Knowledge transfer failures | High |
| Bypassing MSP for internal fixes | Metric distortion | Medium |
| Negative framing to leadership | Relationship undermining | High |
The behaviors look like normal friction. Distinguishing resistance from operational challenges requires pattern recognition over time.
The Knowledge Hoarding Defense
Internal IT’s primary leverage is knowledge. They know the environment. The MSP doesn’t. Knowledge hoarding preserves that leverage.
Signs of knowledge hoarding:
Undocumented procedures. “It’s always been done that way” replaces written process.
Personal credential control. Passwords known only to specific individuals.
Relationship gatekeeping. Vendor contacts not shared with MSP.
Historical context withholding. “You wouldn’t understand the history” blocks transfer.
Exception complexity. System quirks become defense mechanisms.
The defense is understandable. Knowledge is job security. Sharing knowledge feels like eroding protection.
The Role Conflict Architecture
MSP engagement changes internal IT roles. The change isn’t always clear or welcomed.
| Before MSP | After MSP | Emotional Impact |
|---|---|---|
| Firefighter, hero on incidents | Escalation point, support role | Loss of crisis identity |
| Decision maker on tools | Recommendation role | Control reduction |
| Vendor primary contact | Shared or secondary contact | Relationship loss |
| Full stack owner | Partial stack owner | Scope reduction |
| 24/7 on-call | Backup escalation | Relief but also marginalization |
Role transition requires explicit acknowledgment. Pretending roles don’t change breeds resentment when reality diverges from expectations.
The Trust Erosion Cycle
Once resistance begins, trust erodes cyclically.
Initial incident: MSP makes mistake (inevitable with new environment).
Internal reaction: “See, they don’t understand our systems.”
Withdrawal: Internal team reduces cooperation “to prevent further damage.”
MSP struggle: Less cooperation means more mistakes.
Reinforcement: Additional mistakes confirm initial skepticism.
Deepening resistance: Cycle intensifies.
Breaking the cycle requires intervention. Leadership must acknowledge the pattern, address legitimate concerns, and enforce cooperation norms.
The No-Fire Guarantee
Explicit “no-fire” guarantees during MSP transition preserve knowledge retention by 60%. The guarantee directly addresses the job security anxiety driving resistance.
Effective guarantees specify:
Protected positions. Which roles are guaranteed?
Duration. How long does protection last?
Conditions. What would void the guarantee?
Evolution path. How will roles change over time?
The guarantee must be credible. Promises from leadership with layoff history carry less weight. Contractual provisions or written commitments provide substance.
The Power Dynamic Shift
MSP engagement redistributes power within the organization:
| Power Element | Before | After |
|---|---|---|
| Budget control | IT controls IT spending | Shared or executive-controlled |
| Vendor relationships | IT owns all vendors | MSP owns managed vendors |
| Incident heroics | Internal saves the day | MSP expected to save the day |
| Strategic input | IT drives technology strategy | Shared with MSP recommendations |
| Access to executives | IT reports through chain | MSP may have executive access |
Power redistribution without acknowledgment creates underground resistance. Explicit discussion of changed dynamics enables adaptation.
Managing the Transition
Organizations that successfully integrate MSPs with internal IT share practices:
Early involvement. Internal IT participates in MSP selection, not just receives announcement.
Role design. New roles are designed, not assumed. Clarity precedes execution.
Quick wins. Early MSP contributions that clearly benefit internal team (not replace them).
Relationship investment. Joint team-building, not just transactional interaction.
Feedback channels. Internal IT can voice concerns constructively.
Executive visibility. Leadership monitors integration health, not just cost metrics.
The Collaboration Mandate
Mandating collaboration without enabling it fails. Enablement requires:
Shared tools. Both teams work in common systems.
Joint accountability. Success metrics that require cooperation.
Integrated workflows. Handoffs designed into processes.
Communication norms. Expected response times, meeting participation.
Conflict resolution. Path for addressing friction without escalation.
The mandate must come with resources. Time for collaboration. Budget for integration. Permission to invest in relationship.
The Integration Timeline
Integration isn’t instant. Realistic timeline expectations prevent premature judgment.
| Phase | Duration | Expected State |
|---|---|---|
| Orientation | 30-60 days | Learning, high friction |
| Adjustment | 60-180 days | Finding patterns, reducing friction |
| Normalization | 180-365 days | Stable relationship, occasional tension |
| Optimization | 12+ months | Efficient collaboration, mutual respect |
Judging the relationship at 90 days captures adjustment friction, not long-term viability. Organizations that abandon at first difficulty never reach optimization.
When Resistance Wins
Sometimes internal IT resistance succeeds in driving out the MSP. The victory is pyrrhic.
Short-term: Internal team regains control.
Medium-term: Workload that prompted MSP engagement returns.
Long-term: Burnout, under-investment, capability gaps return.
The underlying problem that led to MSP consideration doesn’t disappear when the MSP leaves. It returns, often worse for the delay.
Leadership’s Role
Leadership determines whether resistance succeeds or integration occurs:
Visible commitment. Executive support for MSP engagement must be clear and sustained.
Resistance recognition. Acknowledge resistance exists rather than hoping it dissipates.
Root cause addressing. Security concerns need real answers, not dismissal.
Consequence clarity. Sustained resistance has career implications.
Success celebration. Joint wins get recognized publicly.
Leadership that treats MSP engagement as an IT department matter delegates the outcome to the team least likely to drive success.
Sources
- IT team threat perception: CIO.com surveys
- Pocket veto delay impact: MSP onboarding studies
- Knowledge retention with guarantees: Workforce transition research