COBIT Technology Role: IT's Role in Value Creation

The CFO looked at me across the conference table with barely concealed frustration. "We spend $12 million annually on IT," she said, tapping her pen against a stack of budget reports. "Can you tell me what we're actually getting for that money?"

The CIO shifted uncomfortably in his seat. He'd been in that role for eight months, inheriting a sprawling IT organization that nobody—including him—seemed to fully understand. Servers hummed in data centers. Applications ran (mostly). Tickets got resolved (eventually). But could anyone articulate IT's actual contribution to the business?

That was 2017, and that conversation changed how I think about IT governance forever.

After fifteen years of watching organizations struggle with this exact question, I've learned something fundamental: IT doesn't create value by keeping servers running. IT creates value by enabling business capabilities that would otherwise be impossible.

And that's precisely what COBIT's concept of "IT's Role in Value Creation" is designed to address.

The $12 Million Question: What Is IT Actually For?

Here's a pattern I've seen in over 40 organizations: IT departments get treated like utilities—necessary evils that cost money but don't generate revenue. Finance sees IT as a cost center. Business units see IT as the department that says "no" to everything they want to do.

This is exactly backwards.

Let me share a story that illustrates what I mean.

In 2019, I consulted for a mid-sized insurance company. Their IT department had 45 people and a $8.3 million annual budget. When I asked the executive team what value IT provided, I got vague answers:

• "They keep our systems running"

• "They handle our email and applications"

• "They fix things when they break"

Nobody mentioned that IT was the reason they could:

• Quote insurance policies in 90 seconds instead of 3 days

• Process claims 74% faster than competitors

• Reduce fraud losses by $4.2 million annually through predictive analytics

• Enable remote work for 60% of their workforce during the pandemic

The IT department was creating massive business value. But because nobody understood IT's role in value creation, IT was the first budget line item targeted for cuts during every financial squeeze.

"IT's value isn't measured in uptime percentages. It's measured in business outcomes that wouldn't exist without technology."

Understanding COBIT's Perspective on IT's Role

COBIT 2019 introduced something brilliant: the concept of design factors that customize IT governance to your specific situation. One of the most critical design factors is "The Role of IT"—how technology functions within your organization's value creation model.

After implementing COBIT across dozens of organizations, I've learned that IT can play fundamentally different roles depending on business context. COBIT identifies four primary archetypes:

The Four IT Role Archetypes

Understanding which role IT plays in your organization isn't academic—it fundamentally changes how you should govern, invest in, and measure IT.

Let me show you what this looks like in practice.

The Support Role: IT as Infrastructure Enabler

I worked with a traditional manufacturing company in 2020. They'd been making industrial components for 67 years. Their competitive advantage came from engineering expertise, manufacturing precision, and customer relationships—not technology.

For them, IT's role was Support: keep the lights on, enable basic business processes, and stay out of the way.

Their IT organization focused on:

• Reliable ERP system operation

• Email and collaboration tools

• Basic security and compliance

• Cost-effective infrastructure management

Here's what made this approach work: they weren't trying to be Amazon. They didn't need cutting-edge AI or bleeding-edge cloud architecture. They needed their systems to work reliably at the lowest reasonable cost.

When Support Role Makes Sense

I helped them implement COBIT controls appropriate for this role:

• Standardized service catalog

• Clear SLAs focused on availability and cost

• Outsourcing non-critical functions

• Minimal custom development

• Robust vendor management

The result? They reduced IT costs by 23% while improving service reliability. IT wasn't creating new business value—it was enabling the business to create value without IT becoming a bottleneck.

"Not every organization needs IT to be strategic. Some organizations just need IT to work, cost-effectively, without drama."

The Factory Role: IT as Service Delivery Engine

In 2018, I consulted for a regional bank with 200 branches. Their business model depended on consistent, reliable technology delivery across all locations. A system outage didn't just inconvenience employees—it meant customers couldn't access their money.

For them, IT's role was Factory: deliver standardized, highly reliable services at scale.

The difference between Support and Factory is critical. Support role IT focuses on cost. Factory role IT focuses on service excellence and scalability.

Factory Role Characteristics and Metrics

This bank's IT department ran like a manufacturing operation—and that was exactly right for their context. They measured:

• Transaction processing time

• System availability by service

• Incident resolution rates

• Cost per branch supported

• Compliance with change management procedures

We implemented COBIT processes that emphasized:

• Standardization: Every branch got identical technology

• Process discipline: Strict adherence to ITIL service management

• Measurement: Comprehensive metrics on every service

• Continuous improvement: Lean principles applied to IT operations

• Risk management: Preventing outages before they occurred

The outcome? Over three years:

• Branch system availability improved from 97.2% to 99.7%

• Incident resolution time dropped by 64%

• Cost per branch decreased by 31%

• Customer satisfaction with digital banking increased 28 points

But here's the key insight: they weren't innovating. They weren't disrupting. They were doing what they did exceptionally well, consistently, at scale.

And that created enormous business value.

The Turnaround Role: IT as Transformation Agent

Now let's talk about when everything changes.

In 2020, I got called into a retail company that was dying. Not metaphorically dying—actually circling the drain. Revenue had declined 34% over three years. Their primary competitor wasn't other retailers—it was Amazon.

The CEO understood they had maybe 18 months to fundamentally transform or shut down. IT's role had to shift from Support to Turnaround: using technology to enable a completely different business model.

This is where COBIT's framework for IT role becomes crucial. You can't govern Turnaround IT the same way you govern Support IT. The metrics are different. The risk tolerance is different. The investment model is different.

The Turnaround Transformation Journey

This retailer needed IT to enable:

• E-commerce platform (they had none)

• Real-time inventory visibility (they had batch updates overnight)

• Customer data platform (they had siloed transaction data)

• Mobile app (didn't exist)

• Buy online, pick up in store (impossible with current systems)

• Personalized marketing (they sent the same email to everyone)

The IT organization went from 22 people maintaining legacy systems to a 45-person team building new digital capabilities. IT budget increased from 1.8% of revenue to 4.7%.

But here's what made it work: we implemented COBIT governance specifically tuned for Turnaround role:

Different Risk Tolerance

• Support role IT: "Never break what's working"

• Turnaround role IT: "Fail fast, learn faster"

Different Investment Approach

• Support role IT: Minimize cost, extend asset life

• Turnaround role IT: Invest aggressively in new capabilities

Different Success Metrics

• Support role IT: Uptime, cost per user, ticket resolution

• Turnaround role IT: Revenue from digital channels, customer acquisition cost, time to market

Turnaround Role Success Metrics

The results over 24 months were dramatic:

• Online sales went from $0 to $47 million (31% of total revenue)

• Mobile app adoption: 156,000 active users

• Buy online, pick up in store: 23% of online orders

• Customer acquisition cost: 67% lower than traditional channels

• Overall revenue stabilized, then grew 12%

IT didn't just support the transformation—IT was the transformation.

"In a Turnaround situation, IT isn't a cost center or a service provider. IT is the strategic weapon that determines whether the company survives."

The Strategic Role: IT as Competitive Differentiator

Let me share the most fascinating COBIT implementation I've ever done.

In 2021, I worked with a software-as-a-service company that was born digital. Founded in 2019, they had never known a world without cloud infrastructure, agile development, or continuous deployment.

For them, IT wasn't a support function or even a transformation agent. IT was the business. Every competitive advantage came from technology. Every product feature was software. Every customer interaction was digital.

This is what COBIT calls the Strategic role: IT as the primary source of competitive differentiation and value creation.

Strategic Role Characteristics

Governing Strategic role IT requires completely different thinking. Traditional IT governance approaches—with their change advisory boards, multi-month approval processes, and risk-averse cultures—kill Strategic role organizations.

But you still need governance. You still need controls. You still need to manage risk.

This is where COBIT 2019's design factors become crucial. We customized their governance model:

Traditional IT Governance (Factory/Support Role)

• Change Advisory Board approves all changes

• Quarterly release cycles

• Extensive testing phases

• Risk avoidance culture

• Separate development and operations teams

Strategic Role IT Governance (This Company)

• Autonomous product teams with deploy authority

• Multiple deployments per day

• Automated testing with continuous integration

• Risk management culture (not risk avoidance)

• DevOps model with full lifecycle ownership

Strategic Role Governance Model

We implemented COBIT controls that made sense for their context:

• Automated compliance checking in CI/CD pipeline

• Infrastructure as code with version control

• Automated security scanning and vulnerability management

• Real-time monitoring with business impact correlation

• Post-incident reviews focused on learning (not blame)

• Risk registers tied to business objectives (not IT objectives)

The results?

• 847 production deployments in one quarter (vs. 4 deployments/quarter at traditional companies)

• Average time from code commit to production: 37 minutes

• Security vulnerability mean time to remediation: 4.2 hours

• Zero critical outages in 18 months

• Customer-impacting incidents: 99.4% resolved in <15 minutes

But here's the crucial insight: they had more control, not less. They just achieved control through automation, culture, and rapid feedback rather than through manual gates and approval hierarchies.

How to Determine Your IT Role: A Framework from the Trenches

After implementing COBIT across 50+ organizations, I've developed a practical assessment framework. Here's how I help organizations determine their appropriate IT role:

IT Role Assessment Matrix

I walk through this assessment with executive teams, and it creates fascinating conversations. I've watched CEOs realize their mental model of IT was 10 years out of date. I've seen CIOs discover they were governing Strategic role IT with Support role processes.

Real-World Assessment: A Case Study

Let me walk you through a real assessment I did in 2022.

Company: Regional healthcare system Revenue: $840 million IT Budget: $29 million (3.5% of revenue) IT Staff: 87 people

Initial Self-Assessment: Factory role "We need reliable systems to serve patients. IT should be a well-run service organization."

My Assessment After Analysis: Transitioning from Factory to Turnaround

Here's what I discovered:

The CFO had categorized IT as Factory because she thought about "keeping systems running." But the business was experiencing technology-driven disruption that demanded a Turnaround role.

We restructured their IT governance:

• Created digital innovation budget (separate from operational IT)

• Established product teams around patient engagement platforms

• Implemented agile governance for new digital services

• Maintained ITIL processes for core clinical systems

• Developed separate metrics for "run the business" vs. "change the business"

This is a critical insight: you can have different IT roles for different parts of your IT portfolio.

Hybrid IT Role Model

This hybrid model is increasingly common. Most organizations aren't purely one archetype—they're a portfolio of different IT roles serving different business needs.

"The mistake isn't choosing the wrong IT role. The mistake is thinking you only get to choose one."

The Value Creation Chain: Connecting IT to Business Outcomes

Here's where COBIT gets really powerful. Understanding your IT role is just the first step. The real magic happens when you connect IT activities to actual business value.

I developed a framework I call the Value Chain Traceability Model that I've used across dozens of COBIT implementations:

IT Value Chain Framework

The breakthrough happens when you can trace from infrastructure all the way to business outcomes.

Let me show you a real example.

Value Chain Case Study: E-Commerce Infrastructure Investment

A retail client wanted to invest $2.4 million in upgrading their e-commerce infrastructure. The CFO asked: "What business value does this create?"

Here's how we traced the value chain:

Infrastructure Layer Investment

• New cloud infrastructure with auto-scaling

• Content delivery network (CDN)

• Database performance optimization

Platform Layer Impact

• API response time: 847ms → 124ms (85% improvement)

• Page load time: 4.2 seconds → 1.1 seconds (74% improvement)

• Concurrent users supported: 5,000 → 50,000 (10x improvement)

Application Layer Impact

• Checkout abandonment rate: 34% → 19% (44% improvement)

• Search result relevance: 67% → 89% (33% improvement)

• Mobile app crash rate: 2.3% → 0.3% (87% improvement)

Process Layer Impact

• Average order value: $67 → $79 (18% improvement due to better recommendations)

• Conversion rate: 2.1% → 3.4% (62% improvement)

• Customer support tickets: 1,200/month → 740/month (38% reduction)

Outcome Layer Impact

• Online revenue: +$14.7 million annually

• Customer satisfaction (NPS): +23 points

• Operational cost savings: $890,000 annually

• Return on investment: 543% over 3 years

When you can tell this story—from infrastructure investment to business outcome—IT stops being a cost center and becomes recognized as a value creator.

Implementing COBIT Based on Your IT Role

After all these years implementing COBIT, here's my practical guide for getting started:

Implementation Roadmap by IT Role

Quick-Start COBIT Processes by Role

Support Role - Focus on These 5 COBIT Processes

1. APO02 - Manage Strategy (Align IT to business, minimize cost)

2. BAI10 - Manage Configuration (Standardize environment)

3. DSS01 - Manage Operations (Keep systems running)

4. DSS02 - Manage Service Requests (Efficient service delivery)

5. MEA01 - Monitor Performance (Track costs and availability)

Factory Role - Focus on These 7 COBIT Processes

1. APO02 - Manage Strategy (Service excellence strategy)

2. APO09 - Manage Service Agreements (Define and measure SLAs)

3. BAI01 - Manage Programs (Service improvement projects)

4. BAI06 - Manage Changes (Rigorous change control)

5. DSS01 - Manage Operations (Operational excellence)

6. DSS03 - Manage Problems (Root cause analysis)

7. MEA01 - Monitor Performance (Comprehensive service metrics)

Turnaround Role - Focus on These 8 COBIT Processes

1. APO02 - Manage Strategy (Transformation strategy)

2. APO03 - Manage Enterprise Architecture (Target state design)

3. APO05 - Manage Portfolio (Investment prioritization)

4. APO12 - Manage Risk (Transformation risks)

5. BAI01 - Manage Programs (Transformation initiatives)

6. BAI03 - Manage Solutions (Rapid development)

7. BAI07 - Manage Change (Business change management)

8. MEA01 - Monitor Performance (Transformation metrics)

Strategic Role - Focus on These 10 COBIT Processes

1. APO01 - Manage Strategy (Continuous strategic alignment)

2. APO03 - Manage Enterprise Architecture (Technology evolution)

3. APO05 - Manage Portfolio (Product portfolio management)

4. APO08 - Manage Relationships (Stakeholder engagement)

5. APO12 - Manage Risk (Innovation risk management)

6. BAI03 - Manage Solutions (Continuous product development)

7. BAI04 - Manage Availability (Service reliability)

8. DSS05 - Manage Security Services (Security as code)

9. DSS06 - Manage Business Process Controls (Embedded governance)

10. MEA01 - Monitor Performance (Product and business metrics)

Common Mistakes I've Seen (And How to Avoid Them)

After fifteen years, I've seen every mistake possible. Here are the big ones:

Mistake #1: Implementing the Wrong IT Role

The Problem: A traditional manufacturer tried to govern IT like a tech startup because "everyone should be agile and innovative."

The Result: $3.2 million wasted on failed initiatives, demoralized IT team, confused business stakeholders.

The Lesson: Be honest about your business context. Support role isn't inferior—it's appropriate for certain business models.

Mistake #2: Static Role Definition

The Problem: A retail company defined IT role as Support in 2015. By 2020, they needed Turnaround role but still governed like Support.

The Result: Competitive disadvantage, loss of market share to digital competitors, eventual acquisition at depressed valuation.

The Lesson: Reassess your IT role annually. Business context changes. Your IT role should evolve.

Mistake #3: One-Size-Fits-All Governance

The Problem: A healthcare system applied Factory role governance to their innovation lab.

The Result: Innovation velocity dropped 73%. Talented staff left. Digital transformation stalled.

The Lesson: Different IT portfolios can have different roles. Segment your governance appropriately.

Mistake #4: Metrics Misalignment

The Problem: A Turnaround role IT organization measured by Support role metrics (cost reduction, uptime).

The Result: IT delivered cost savings while the business lost market share. Board questioned IT effectiveness.

The Lesson: Your metrics must align with your IT role. Strategic role IT measured by cost efficiency is doomed.

The Future: How IT Roles Are Evolving

Here's what I'm seeing as I work with organizations in 2024:

Trend #1: Role Fluidity Organizations are getting better at shifting IT role dynamically. I worked with a company that operates Factory role IT 360 days per year, then shifts to Strategic role during their annual innovation sprint.

Trend #2: Portfolio Segmentation Most organizations now explicitly segment their IT portfolio with different roles for different systems. This allows appropriate governance without bureaucracy.

Trend #3: Platform Models Companies are creating internal platforms that allow different roles to coexist. Core platforms operated as Factory, product teams operating as Strategic, all on shared infrastructure.

Trend #4: Value Stream Focus The next evolution of COBIT focuses on value streams—end-to-end flows from customer need to delivered value. This makes IT role even more explicit and measurable.

Your Action Plan: Getting Started

If you're ready to clarify IT's role in value creation, here's your roadmap:

Week 1: Assessment

• Complete the IT Role Assessment Matrix above

• Interview 10 business stakeholders about IT's value

• Review IT budget allocation and strategic initiatives

• Document current IT governance processes

Week 2: Analysis

• Compare current IT role to desired IT role

• Identify gaps in governance approach

• Map IT investments to business outcomes

• Calculate current IT value creation metrics

Week 3-4: Planning

• Define target IT role(s) for different portfolio segments

• Select appropriate COBIT processes for each role

• Design role-appropriate metrics

• Create governance adjustment plan

Month 2-3: Implementation

• Communicate new IT role to organization

• Adjust governance processes

• Implement new measurement systems

• Train IT and business teams

Month 4-6: Optimization

• Monitor results against new metrics

• Adjust based on feedback

• Document lessons learned

• Plan next iteration

Final Thoughts: Value Creation Is a Choice

That CFO who asked me about the $12 million IT budget? We worked together for 18 months implementing COBIT with a clear understanding of IT's role.

Last quarter, she presented to the board about IT's business impact:

• New digital revenue stream: $6.8 million

• Process automation savings: $2.1 million

• Reduced time-to-market: 67% faster

• Customer satisfaction improvement: 34 points

• IT cost per revenue dollar: Down 29%

"I used to think IT was an expense," she told the board. "Now I understand IT is an investment—and we're getting exceptional returns."

That's the power of understanding IT's role in value creation.

IT doesn't create value by accident. It creates value through intentional design, appropriate governance, and clear alignment with business strategy.

Your IT organization is creating value right now—or it's destroying it. There's no neutral position.

The question isn't whether IT matters. The question is whether you understand how IT creates value in your specific context, and whether you're governing it appropriately.

Choose your IT role intentionally. Govern it appropriately. Measure it accurately. And watch as IT transforms from a cost center everyone resents into a value engine everyone depends on.

Because in 2024, every company is becoming a technology company. The only question is whether you're doing it intentionally or by accident.