Technology operations — the ongoing work of maintaining, supporting, and evolving deployed technology — typically consumes 60-80% of total technology budget across most organizations. The operational decisions that govern this spending substantially affect organizational outcomes but receive less analytical attention than initial selection or implementation decisions.
This article presents a framework for technology operations decisions grounded in operational research and IT economics literature.
The decisions that drive operational cost
Several decision types disproportionately affect technology operations cost:
1. Build versus buy decisions. Whether to develop capabilities internally or acquire commercial solutions. Affects ongoing maintenance cost, vendor dependency, and capability flexibility.
2. On-premises versus cloud decisions. Where workloads run and who operates the underlying infrastructure. Affects capital structure, scaling characteristics, and operational responsibility allocation.
3. Standardization versus flexibility decisions. How much variation is permitted across organizational units. Affects support cost, integration cost, and operational complexity.
4. Internal versus outsourced operations decisions. Whether operational work is performed by internal staff or contracted to external providers. Affects cost structure, capability development, and organizational risk.
5. Maintenance versus modernization investment decisions. How budget is split between maintaining existing systems and developing new capabilities. Affects long-term operational cost and organizational capability.
Each decision type has well-developed analysis methodology but is often made heuristically rather than systematically.
The build versus buy methodology
Build versus buy decisions have substantial research behind them. The framework that consistently produces defensible outcomes:
Build when:
- The capability is competitively differentiating
- The capability requires deep integration with proprietary systems or processes
- Commercial alternatives have substantial functional gaps for the specific use case
- The organization has sustainable internal capability for ongoing development
Buy when:
- The capability is operational rather than differentiating
- Mature commercial alternatives exist with appropriate functional fit
- Internal development capacity is constrained or expensive
- The capability has scale economies that single-organization development cannot achieve
The most consequential build versus buy mistakes are usually in the "build" direction — building capabilities that should have been acquired commercially. Internal development understates ongoing maintenance cost and overestimates internal capability sustainment.
The cloud versus on-premises methodology
The cloud versus on-premises decision has evolved substantially. The simple "cloud is cheaper" narrative of the early 2010s has given way to more nuanced analysis showing that cloud economics depend substantially on workload characteristics and operational maturity.
Workloads favoring cloud:
- Variable utilization with substantial scaling requirements
- Geographically distributed access patterns
- Rapid deployment requirements
- Limited internal infrastructure operations capability
Workloads favoring on-premises:
- Steady-state utilization at substantial scale
- Specialized hardware requirements
- Data residency or regulatory constraints
- Mature internal infrastructure operations capability
The actual decision is rarely binary. Most organizations operate hybrid environments with workload-specific allocation. The methodology should evaluate workloads individually rather than applying organization-wide policies.
The standardization versus flexibility methodology
Standardization decisions affect operational cost substantially but receive less analytical attention than they warrant. The trade-off:
Standardization benefits:
- Lower per-system support cost through volume effects
- Reduced training cost
- Simplified integration
- Better vendor leverage
- Reduced operational complexity
Standardization costs:
- Suboptimal fit for some organizational units
- Reduced flexibility for evolving requirements
- Concentrated vendor dependency
- Slower adoption of innovation
The right standardization level depends on organizational characteristics: highly heterogeneous organizations gain less from standardization than homogeneous ones; rapidly evolving operational requirements favor more flexibility; mature stable operations favor more standardization.
Most organizations standardize too little rather than too much. The hidden costs of variation are substantial and undermeasured.
The internal versus outsourced operations methodology
Outsourcing decisions involve trade-offs across cost, capability, risk, and strategic flexibility. The research suggests several principles:
Outsource when:
- The operational activity is commodity rather than differentiating
- External providers have meaningful scale advantages
- Internal capability development would require disproportionate investment
- The activity has volatile capacity requirements
Retain internally when:
- The activity is strategically important or competitively differentiating
- The activity has high integration with internal operations
- External provider markets are immature or unreliable
- Internal capability has long-term value beyond the specific activity
Outsourcing decisions are often less reversible than they appear. Once internal capability is dispersed, rebuilding it requires substantial investment. The decision should account for this asymmetry.
The maintenance versus modernization investment methodology
Most organizations underinvest in modernization and overinvest in maintenance, producing technical debt that compounds over time. The research suggests several principles for investment allocation:
- Sustained modernization investment of 15-25% of operational technology budget tends to maintain reasonable technical health
- Below 10% modernization investment, technical debt accumulates faster than it is retired
- Above 30% modernization investment, operational continuity may be compromised
- The right level depends on organizational age, technical debt level, and competitive context
The investment allocation decision should be made at the portfolio level rather than project-by-project. Project-level decisions tend to favor immediate operational needs over modernization, producing systematic underinvestment.
The takeaway
Technology operations decisions accumulate into substantial organizational cost and capability over time. The framework above identifies the highest-leverage decision types and the methodology for each.
For organizations experiencing chronic technology operations cost growth or capability gaps, the diagnosis is usually inadequate operational decision methodology rather than inadequate technology. Systematic operational decision-making typically produces meaningful improvement in both cost structure and operational capability.
Source notes
Synthesis of published research on IT operations economics, sourcing strategy, and technology portfolio management from major analyst firms and academic literature, 2018-2024.
