Millie Summary:
- Managed services should do more than maintain technology; the right partner should continuously improve cost, reliability, security, performance, and automation.
- Strong IT partnerships combine 24/7 operations with expertise across cloud, applications, data, and AI while creating more capacity for internal teams to focus on strategic priorities.
- IT leaders should measure partners by outcomes, not activity, by asking whether their environment is measurably better and their technology organization more effective because of the relationship.
The traditional definition of managed services was relatively straightforward: keep critical systems available, respond when something goes wrong, meet agreed service levels, and provide technical expertise when internal teams need support. Those responsibilities still matter, but they are no longer enough to define a successful technology partnership.
The environments IT organizations manage have changed considerably. Cloud infrastructure is dynamic. Applications are released more frequently. Data platforms have become operational dependencies across the enterprise. AI introduces new production requirements involving model performance, data quality, governance, security, and infrastructure consumption. At the same time, IT leaders are expected to control costs, strengthen resilience, reduce technical debt, and create capacity for new initiatives.
In that environment, simply keeping systems running is a low bar. A managed services provider can meet its SLAs, close tickets on time, and maintain availability while the underlying environment becomes more expensive, more complex, or increasingly difficult to change.
IT leaders should periodically ask a more consequential question: Is our technology organization better because this partner is here?
Five Questions to Assess Your IT Partner
#1 – Does your partner find opportunities before you ask?
The easiest managed services work to measure is reactive. An incident occurs, monitoring generates an alert, a ticket is created, and someone resolves it. Response time, resolution time, and SLA attainment make this process visible, which is one reason these measures dominate managed services reporting.
Good execution of a reactive process, however, does not necessarily produce a good technology environment. If the same incidents recur, cloud consumption steadily increases, engineers continue performing tasks that could be automated, or capacity problems are discovered only after users are affected, the provider may be responding effectively without addressing the underlying issues.
A stronger operating model looks upstream. It uses telemetry, engineering expertise, and accumulated knowledge of the environment to identify risks and opportunities before they become client requests. In cloud operations, that could mean finding underutilized resources or abnormal spending patterns. In application management, it could mean eliminating the root cause of recurring failures. In DevOps, it may involve automating a manual release process that has become an unnecessary source of delay or risk.
This reflects the broader evolution of technology financial management. The FinOps Foundation positions optimization, anomaly management, forecasting, architecture, and governance as ongoing disciplines designed to maximize the business value of technology investments.
There is a simple way for IT leaders to assess whether their partner is operating this way. Look at the improvements made during the past two quarters and separate them into two categories: those your organization requested and those your partner independently identified.
A strong managed services relationship should contain a meaningful amount of the latter.
At MILL5, 24/7 monitoring and incident response provide an operational foundation, but they are not the end goal. Our managed services teams use what they learn from operating an environment to continually identify opportunities to improve cost, reliability, security, performance, and maintainability.
Explore MILL5 Managed Services
#2 – Is the environment measurably better than it was six months ago?
Technology environments do not remain static simply because an organization stops deliberately changing them. Cloud services evolve, applications accumulate dependencies, usage patterns shift, vulnerabilities emerge, data volumes increase, and business requirements change. Production AI adds another layer because models, infrastructure, and the data feeding them require ongoing monitoring and management.
As a result, maintaining the status quo is not necessarily a neutral outcome. An environment that is merely being kept operational can gradually become more expensive, more fragile, and more difficult to change.
Six or twelve months into a managed services relationship, there should be observable differences. Perhaps more processes are automated. Recovery times have improved. Recurring incidents have declined. Observability is stronger. Cloud economics have improved. Deployments are faster and more reliable. Technical debt has been retired. The exact measures will vary, but there should be evidence of progress.
Google’s DORA research provides a useful model for software delivery. Its framework looks at both throughput and stability, using measures such as deployment frequency, change lead time, recovery time, and change failure rate. The principle applies more broadly to managed operations. Establish the measures that matter, understand the baseline, and expect improvement over time.
What this looks like in practice
MILL5’s work with Olympus demonstrates what can happen when engineering and ongoing operations are treated as parts of the same technology lifecycle.
MILL5 has worked with Olympus across AI and machine learning, edge computing, Azure, data analytics, software development, and managed services. Among the results, Olympus achieved a 30% reduction in operating room turnover time, while other modernization efforts reduced its on-premises footprint and associated operating costs. The relationship has continued through managed services and additional technology initiatives rather than ending after the initial implementation.
The lesson is broader than the specific technologies involved. Ongoing technology operations should create measurable improvement rather than preserve the environment exactly as it was when the engagement began.
#3 – Can your partner bring the right expertise to a problem as it changes?
Enterprise technology problems rarely remain within clearly defined service boundaries. An application performance issue may originate in infrastructure configuration. An AI application that appears to have a model problem may actually be affected by an upstream data pipeline. Rising cloud costs may require changes to architecture, application design, and operating practices rather than a simple infrastructure adjustment.
This creates a weakness in managed services models organized around narrow technical responsibilities. Each provider or team may satisfy its contractual obligation while leaving the client to diagnose where the problem belongs and coordinate the people required to solve it.
IT leaders should therefore consider the range of expertise available through the relationship, not simply the resources assigned to an account. When the nature of a problem changes, the partner should be able to bring in the appropriate expertise without forcing the client to initiate another vendor search.
This is increasingly important as AI moves into production. Building a model and operating one are different disciplines. Production AI introduces requirements around data engineering, infrastructure, observability, security, governance, application integration, and model lifecycle management. MLOps and AIOps need to work within the broader technology environment rather than operate as isolated disciplines.
MILL5’s managed services model reflects this reality. Our capabilities extend across CloudOps, DevOps, DataOps, MLOps, AIOps, applications, infrastructure, data, and AI, supported by engineers with certifications and experience across these disciplines. The value is not simply having a broad list of capabilities. It is being able to follow a technology problem wherever it leads.
A useful question for the next service review is this: when an issue moves outside the expertise of the team currently supporting you, who is responsible for finding the right person to solve it?
Ideally, that responsibility belongs to your partner.
#4 – Is the relationship creating capacity for your team?
One of the most valuable outcomes of managed services is also one of the least likely to appear on an SLA dashboard: the capacity it creates within the internal IT organization.
Experienced technology professionals often possess knowledge that is difficult to replace. They understand the company’s architecture, business processes, data, regulatory requirements, and technology history. Yet those same people can spend significant portions of their time responding to incidents, maintaining pipelines, administering infrastructure, resolving recurring application issues, and working through operational backlogs.
That work is necessary, but it carries an opportunity cost. Time spent on repetitive operational work cannot be spent improving architecture, addressing technical debt, moving AI initiatives into production, modernizing applications, or solving new business problems.
A strong managed services relationship should change that equation. The goal is not to remove the internal organization from its technology. It is to extend its capacity. The partner assumes responsibility for areas where operational scale, automation, 24/7 coverage, and specialized engineering expertise create leverage, allowing internal teams to focus their institutional knowledge on higher-value priorities.
This is also why the quality of the relationship matters as much as the number of resources assigned to it. A provider that requires constant coordination, repeated escalation, extensive oversight, or continual explanation of the environment can consume much of the capacity it was hired to create.
There is a useful way to measure this. Ask what your internal team can accomplish today that it could not accomplish before the managed services relationship existed.
The strongest answers will not be about ticket volume. They will be about engineers returning to product development, architects spending more time on modernization, data teams pursuing new use cases, or technology leaders gaining room to address strategic priorities.
#5 – Can your partner connect operations to outcomes that matter?
Managed services generate an enormous amount of measurable activity. Availability, infrastructure utilization, alert volumes, ticket counts, response times, and SLA performance can all be tracked precisely. These metrics are important for managing the service, but they do not necessarily answer the question senior technology leaders care about most: what is actually getting better?
Fewer incidents matter because they can mean greater reliability and less disruption. Lower cloud consumption matters when it improves the economics of delivering technology. Faster deployments matter when teams can respond more quickly without increasing operational risk. Better observability matters when it reduces the time required to identify and resolve problems.
Effective reporting should therefore operate at two levels. The first explains how the service is performing. The second connects that performance to outcomes such as cost, reliability, security, delivery velocity, employee capacity, and application performance.
From Technology Implementation to Measurable Outcomes
MILL5’s work with Emerson illustrates this connection. The initial challenge involved modernizing an aging SCADA environment and creating cloud connectivity for legacy equipment. The work expanded into a cloud-based Industrial IoT architecture and a SaaS fleet management capability.
According to the MILL5’s Emerson client success story, the resulting platform connected more than 10,000 devices, generated more than $1 million in operating cost savings, supported more than 1,000 clients, and helped enable a new revenue stream through predictive maintenance.
These are business outcomes, but each remains connected to specific technology capabilities. That connection matters. IT leaders should not have to choose between technical metrics and business metrics. A mature technology partnership should be able to show how one contributes to the other.
Raising the Standard for Managed Services
None of these five questions diminish the importance of operational fundamentals. Availability, security, responsiveness, and 24/7 coverage matter when the business depends on systems that operate around the clock. A managed services partner that cannot execute those responsibilities consistently will not earn the opportunity to contribute at a more strategic level.
The distinction is that these capabilities should increasingly represent the foundation of the relationship, not its ceiling.
As technology becomes more central to how organizations operate and compete, IT leaders should expect more from the partners entrusted with managing it. A strong partner should accumulate knowledge of the environment, anticipate problems, introduce automation, bring specialized expertise when requirements change, and create capacity for the internal organization. Over time, the technology environment should become more reliable, efficient, secure, automated, and easier to evolve.
That philosophy guides MILL5’s approach to managed services. We combine ongoing operations with the engineering expertise required to improve what we operate, spanning cloud, applications, data, infrastructure, and AI. The goal is to eliminate the artificial boundary between keeping technology running and making it better.
For IT leaders evaluating an existing relationship or considering a new one, the five questions provide a practical starting point:
- Does the partner identify opportunities before you ask?
- Is the environment measurably improving?
- Can the partner bring the right expertise as problems evolve?
- Is the relationship creating capacity for your internal team?
- Can the partner connect operational activity to meaningful outcomes?
If the answers are consistently yes, the organization has something more valuable than outsourced technology operations. It has a partner contributing to the performance of the technology organization itself.
That should be the standard for modern managed services. Explore how MILL5 approaches Managed Services
