Showing Posts From

It

Co-managed IT explained: who is really responsible?

Choosing how to run your IT infrastructure is one of the most important strategic decisions a business can make. However, many business leaders struggle with confusing terminology in the IT service provider landscape. Terms like co-managed IT, co-sourcing, fully managed services, and co-creation are often used incorrectly, leading to failed partnerships and unclear expectations. Understanding what these models actually mean, how responsibilities are divided, and how financial billing works is essential before signing any contract. The landscape of IT management models To make informed choices, business leaders must clearly distinguish between the different ways IT services can be delivered and organized. Under an insourcing model, a business handles all technology needs internally by hiring and managing its own personnel. Outsourcing, by contrast, transfers an entire process or department to an external provider who guarantees specific performance targets. Co-sourcing takes a staff augmentation approach by bringing in external personnel to work under your internal team's direction, adding temporary capacity without shifting operational control. Service delivery models also differ in scope and management approach. A standard managed service focuses on buying a specific functional outcome under a strict agreement, while remote managed services rely on software tools to monitor systems from a distance. Fully managed services go a step further by handing over complete operational responsibility for the entire IT environment to an external partner. Finally, co-managed IT involves an internal team and a provider managing a domain together, whereas co-creation focuses on jointly developing new digital products rather than managing existing systems. Deep dive into co-managed IT: what it is and what it is not Co-managed IT is often misunderstood in the service provider market, where it is frequently confused with buying extra staff or single software tools. In reality, a true co-managed setup is a joint operational partnership. Both the internal IT team and the external provider actively manage a specific domain together by sharing access to management platforms, support queues, and daily workflows. Both parties share equal accountability for system health, overall uptime, and cybersecurity. This approach is fundamentally different from other sourcing arrangements. It is not co-sourcing because co-sourcing merely supplies extra hands without transferring operational accountability to the vendor. It is also distinct from co-creation, which develops new intellectual property, and traditional outsourcing, which removes the internal team from daily operations entirely. Companies select co-managed models when they have a capable internal team that understands the business, but needs enterprise-grade tools, 24/7 coverage, and specialized knowledge. Financially, co-managed services usually rely on a predictable monthly fee per user or device, combined with set rates for project support. Deep dive into co-creation: what it is and what it is not Co-creation is another term that is often misused when organizations confuse custom software development with operational IT management. At its core, co-creation is a collaborative development strategy where a client and a technology vendor build a software tool together. The client provides domain expertise, practical feedback, and operational requirements, while the vendor contributes technical architecture, software engineering, and scalable infrastructure. This model should not be confused with standard custom software development, where a client pays the full cost to keep exclusive rights. Nor should it be mistaken for co-managed IT or co-sourcing, as co-creation focuses on building new digital tools rather than supporting daily IT operations. Businesses choose co-creation when standard commercial software falls short, but building custom tools alone is financially unfeasible. Financially, the client typically receives lower development rates or early software access. In return, the vendor retains the core intellectual property and creative freedom, allowing them to market and sell the solution to other commercial customers. The shared responsibility model: operational versus legal reality When working with an external IT partner, dividing responsibilities correctly is critical to avoiding operational gaps and legal surprises.IT Sourcing Model Operational Execution Operational Responsibility Legal Accountability Common Billing StructureInsourcing Internal staff Internal IT management Internal business board Internal salaries and capital spendOutsourcing External provider External service provider Internal business board Fixed monthly contract or service feeCo-sourcing Internal staff & external personnel Internal IT management Internal business board Time and materials or daily ratesCo-managed Shared internal and external team Joint shared responsibility Internal business board Fixed fee per user/device + project rateCo-creation Joint development team Joint development leadership Internal business board Discounted dev fees + IP retentionFully Managed External provider External service provider Internal business board Fixed monthly fee per user or deviceOperationally, you can delegate tasks and share daily responsibilities with a partner. In a co-managed environment, the vendor might handle backup management and software patches while your internal team supports end users. If a backup fails due to vendor negligence, the vendor is operationally accountable based on agreed service levels. However, legal responsibility works very differently. Regulators and courts hold your board of directors legally accountable if a cyberattack occurs or privacy laws are violated. While you can seek financial damages from a partner for breach of contract, ultimate legal accountability remains with your business. Closing thoughts Modern IT management requires a clear understanding of where effort ends and true responsibility begins. Misidentifying your sourcing model leads to operational confusion, unfulfilled promises, and unmanaged business risk. By defining roles, financial structures, and legal boundaries early, organizations can build effective partnerships that protect their operations. True IT partnerships are built on shared operational accountability, but business leaders must remember that legal responsibility can never be outsourced.