Most organizations don’t struggle because they invest too much in technology — they struggle because they can’t clearly explain what they are getting back from those investments.
Traditional ROI works well for straight forward discrete projects, but it can overlook threats in the real world of technology. Security, reliability, productivity, customer experience, and risk reduction don’t always show up cleanly on a spreadsheet — yet they directly affect revenue, valuation, and leadership credibility. It requires digging deeper to get the facts.
That’s where Return on Technology (ROT) comes in.
ROT is a more comprehensive way to evaluate technology investments. It looks beyond short‑term cost savings to answer a more important question:
Is technology measurably improving the business — and can leadership defend that conclusion with evidence?
The Define–Measure–Plan–Act (DMPA) framework is a practical way to operationalize ROT. It creates a repeatable process to decide where to invest, why it matters, and how impact will be measured — so technology becomes a growth lever, not a leap of faith.
1. Define
What this stage is:
The Define stage establishes what problem you are actually trying to solve and why it matters to the business. This is where organizations step back and instead look at the growth of the business (or lack of it), business risk, productivity, or service levels. The goal is to find what are challenges to the business model that will improve customer engagement, sales, delivery or service. Eventually as you get better at this process you can find blind spots early—before they become reputational or financial surprises.
Ideas to create a strong Define stage:
- Overall financial performance: Trends in revenue, margins, cash flow, and how technology enables or constrains growth
- Customer feedback: Service delays, late deliveries reliability complaints, security concerns, or lost deals tied to technology
- Employee feedback: Friction points, workarounds, shadow IT, burnout caused by unreliable systems
- Competitive analysis: Where competitors are faster, more visible in the market place, high level of positive customer reviews, or more digitally mature
- Vendor information: Contract risks, end‑of‑life systems, single‑vendor dependencies
- Security and continuity posture: Known vulnerabilities, insurance requirements, audit findings
- Leadership concerns: “What would embarrass us if it failed tomorrow?”
Outcome of Define: A short, plain‑English problem statement tied to improved business performance.
2. Measure
What this stage is:
Measure turns gut feelings into evidence. This stage answers the question: “How bad (or how good) is it really?” without drowning leadership in metrics that don’t matter. Measurements should be stable, repeatable, and explainable to non‑technical stakeholders. What gets measured gets fixed.
Basic measurement examples to use:
- From financial performance: Margin per project, margin per product or service line
- From customer feedback: Number of complaints or escalations, number of late deliveries
- From employee feedback: Process mapping, number of bottlenecks, workarounds, etc.
- From IT: System uptime and frequency of outages – cost or revenue impacts
- From maintenance or engineering: Mean or average time to resolve issues. Quantity, or time in minutes, hours or days
Key principle: If a metric can’t inform a decision or reduce uncertainty, it doesn’t belong here.
3. Plan
What this stage is:
The Plan stage determines what will change, how customers will benefit, why it will work, and how productivity or service will improve or risk will be reduced. This is not about chasing the newest technology—it’s about choosing predictable improvements with clear outcomes. Plans should be phased, cost‑aware, and define how technology will move the needle.
Basic planning elements:
- Clear objective tied to the Define stage risk
- One or two priority improvements (not ten)
- Budget range and cost predictability
- Risk reduction or reliability gain expected
- Ownership and accountability
Examples of small‑business technology plans:
- Improve delivery time by resolving internal bottlenecks and track resolutions and implementation. Is data available consistently? Is data accurate? Replace or update software or hardware or network to improve data accessibility or accuracy.
- Reduce number of service complaints by updating or changing how tickets are input, processed, resolved and closed with customers. Update, replace software or retrain staff as determined by data and analysis.
- Improve sales cycle by improving time to proposals. Review steps involved, review and determine product or service aligns with revenue goals. Understand acceptable timeframe to present proposals. Are the right software tools available? Is the right hardware available for staff and are the there tech or security issues to resolve?
Outcome of Plan: Leadership can calmly explain why this investment was approved and what risk it mitigates.
4. Act
What this stage is:
Act is execution with feedback loops. The focus is consistency, documentation, and visibility—so progress is observable and surprises are minimized. This is where organizations prove they can improve without creating chaos.
Basic measurements during Act:
- Did the planned metrics improve?
- Were there unexpected costs or disruptions?
- Did risk exposure decrease in a measurable way?
- Are stakeholders more confident, not just informed?
Outcome of Act: Technology becomes quieter, more reliable, and easier to defend—without leadership needing to micromanage.
How This Works as a Continuous Loop
Once Act is complete, the organization returns to Define—but now with better visibility, better data, and fewer unknowns because risks start to become visible. Honestly it may not work as expected the first time, and it takes lots of time and patience. But it builds over time, it increases organizational maturity, reduces accumulated risk, and ensures technology supports—not threatens—business credibility.
Why Return on Technology Matters
For leaders, the real risk isn’t spending money on technology — it’s not being able to explain the return later.
ROT provides a structured, evidence‑based way to ensure technology investments:
- Support growth
- Improve productivity and service
- Reduce friction and avoidable disruption
- Strengthen the organization’s long‑term value
As more improvements are made through this process, returns compound. Technology becomes increasingly aligned to the growth strategy, reinforcing business performance rather than distracting from it.
The result isn’t flashy IT.
It’s measurable progress, predictable outcomes, and leadership that is never caught explaining decisions in hindsight.