TIME Analysis for fun and profit
Prioritize your IT roadmap more better, much effective.
Prioritization frameworks are a minor obsession of mine. A proven favorite is the TIME Analysis, a mental tool for directing attention toward where it’s needed the most.
As a business leader responsible for investment in technology, I use this tool to manage our roadmap of software applications. The end game: Informed priority. What manner of love does each application in my portfolio need? Where should we direct our limited resources and effort?
I’m not sure where I first heard of this method, but LeanIX has the best write up I can find online. I’ve shared this many times with many people.
Step 1: Make a list
Make a list of your applications! If you don’t have an inventory yet, this is your sign from the universe to make one. Don’t overthink it, just write down every application under your purview. Spoiler alert: this list is always longer than you expect.
Step 2: Assign ratings
For each application, assign two scores on a 1-10 scale: Technical Fit and one for Functional Fit.
Y-axis: Technical Fit — What is the technical quality of this application? i.e. What’s the measure of security, reliability, and performance? How much do your users love or hate it? How much does your IT and security admin love it or hate it?
X-axis: Functional Fit — What is the value to the business? How well does this system perform the business purpose? I.e. How much do your users depend on this system to deliver on their work?
Don’t overthink it. What do your users complain about? What systems are commonly discussed in operational support? Use data if you have it. Trust your intuition if you don’t.
Consider comparative ranking as you go. Make sure each item is appropriately lower/higher than another when compared to one another.
Step 3: Profit! (aka, Chart it.)
Once scored, chart it. This is a classic two-axis, four box grid. Every application will fall into one of four quadrants:
Tolerate: High technical quality, low functional fit.
GEMO! (Good enough, move on.) Don’t spend your time here.
The high technical quality of these applications should mitigate risk while the business maintains status quo and focuses effort elsewhere.
Invest: High technical quality, high functional fit.
These are your high-performing assets. Every dollar spent here is moving you forward.
If you’re coming off a season of investment, you may be able to let these investments mature and begin to realize your intended return.
Migrate: Low technical quality, high functional fit.
These demand your attention — applications that the business relies on, yet technical performance is unreliable or the user experience is poor.
Every dollar spent here should mitigate risk and pull you out of technical debt.
Work here may not be sexy, but will be necessary. Failure to take action here may see painful outcomes among business-critical tools.
Eliminate: Low quality, low fit.
The dead weight dragging your portfolio down.
Every dollar spent here might feel wasted, but you’ll reap benefit in time, attention, and reduction of risk.
Addition by subtraction. Close these systems and move on.
A few considerations
This tool is: A means to clarify the big picture and drive communication. TIME takes very rough qualitative data (a list of applications and two scores) and turns it into perspective. Your mileage may vary.
This tool is not: A plan, a timeline, or a cost-benefit analysis. It cannot dictate what to do first or what should be done at all. All of these quadrants represent effort and work. Let this be a data point to compare what kind of work may be appropriate.
Garbage in, Garbage out: Your analysis is only as strong as the data and context you bring to it. Consider this:
Completeness — Is your inventory thorough? Is anything missing?
Bias — Be honest about how subjective your scores may be. If they’re pulled from your point of view, own that. Where aggregating input from business and/or technology specific stakeholders, own that too.
Customer Voice — Tap into existing feedback mechanisms. Where you have data, use it. Volume of support requests? Volume of errors and issues? Talk to stakeholders to validate your quantitative and qualitative assessment — does it feel right?
Go forth and prosper
TIME Analysis doesn’t give you all the answers, but it’s a powerful starting point. For those of you in a position to decide priority, it shines a spotlight on what’s working, what’s failing, and where you may want to focus your energy.
I’ve found it useful. Hopefully you do too. 🖖🏻