Chip Gliedman serves CIOs. See the full Analyst bio.
Visit Forrester.com to learn how we make CIOs successful every day.
Rethinking “Time To Value” For BT Initiatives
Posted by Chip Gliedman on March 8, 2012
- 371 Recommendations
- 5 comments
I had an interesting conversation with a Forrester client in response to an inquiry about the definition of “time to value” for technology solutions. When I received the question, I thought, “That’s easy!” While there is no “GAAP” definition of time to value, I was ready to say that it would be one of two things:
1- The time from project start to the start of business benefit accrual. So, if a project took 12 months to implement, and then three months for the business to adapt to it, the time until business benefits began to accrue would be 15 months.
2- The time from project start to the date at which cumulative business benefits exceeded the cumulative costs. In other words, the time until the “payback” of the investment.
However, in trolling around to make sure that I hadn’t missed anything, I stumbled upon a potential third definition (and I wish I could point back to the source). One commentator on the Web suggested something a bit different – and something that has a great deal of merit as we rely more and more on technology to drive business gains. In his definition, time to value represented the time until the business targets for the solution were achieved. So, rather than looking at the start of benefits, or the date we’re no longer cash-negative, we are now looking at the time until the full desired benefits are achieved. So this becomes:
3- Time to value is the time from project initiation until the projection of total business benefits is achieved.
This change in perspective has a number of implications:
- We may reconsider different implementation choices. A solution that may take longer from an IT point of view, but accelerated business benefit achievement may be the best for the organization.
- We emphasize the tie between technology, business processes, and business goals – leading to potentially better alignment between all three.
- We tie our business technology implementations to the ultimate business goals – moving an organization from internally IT-focused to externally BT-focused.
Please share thoughts here, and/or join us for CIO Forum (#CIOF12) in Las Vegas on May 3-4 or CIO Forum EMEA (#CIOE12) in Paris, France, on June 19-20. You’ll learn how rethinking IT strategic planning and innovation can change the way IT and the business partner for overall business success.
Categories:
search forrester's blogs
Lead with a "mobile first" strategy.
Attend the complimentary Webinar Provide Next Generation Services To Your Customers June 5, 2013, 1:00–2:00 p.m. EST
How do you reach perpetually connected customers?
Attend the complimentary Webinar Strategies For The Mobile Mind Shift June 5, 2013, 1:00–2:00 p.m. UK time
Master the digital business future.
Attend Forrester’s Forum For CIOs EMEA, June 10-11, London
Analyst Blogs
- Alex Cullen (5)
- Andrew Bartels (63)
- Bobby Cameron (2)
- Charles Golvin (27)
- Chip Gliedman (12)
- Chris Mines (35)
- Claire Schooley (39)
- Craig Le Clair (4)
- Dan Bieler (37)
- Dane Anderson (2)
- Doug Washburn (1)
- Frank Gillett (25)
- George Lawrie (1)
- Holger Kisker (1)
- James Staten (9)
- Jennifer Belissent, Ph.D. (96)
- John Brand (8)
- John McCarthy (16)
- Khalid Kark (5)
- Manish Bahl (19)
- Marc Cecere (9)
- Mike Gualtieri (1)
- Nigel Fenwick (72)
- Peter Burris (6)
- Philipp Karcher (6)
- Rob Koplowitz (35)
- Sharyn Leaver (32)
- Simon Yates (16)
- Stefan Ried (11)
- Ted Schadler (110)
- Tim DeGennaro (3)
- Tim Sheedy (20)
- TJ Keitt (38)
- Tom Pohlmann (9)
Top Categories
- Innovation (2)
- IT innovation (2)
- audio podcasts (1)
- BT (1)
- Business innovation (1)
- business technology (1)
- CIO (1)
- CIO Forum (1)
- CRM (1)
- Customer Service (1)
- See all
Archives
- May 2013 (1)
- February 2013 (1)
- January 2013 (1)
- October 2012 (1)
- September 2012 (1)
- June 2012 (1)
- March 2012 (2)
- September 2011 (1)
- January 2011 (1)
- September 2009 (2)
- June 2009 (1)
Comments
Project Start
There's another place to look for opportunity to decrease "Time to Value" - what is happening before the official project start? Organizations need to look the period from the idea to the official project start - their business case and capital allocation process. This can be just as long as the project time.
Project Start
I agree Paul, reducing the time it takes to move from idea to kickoff can significantly reduce time to value. Unfortunately we rarely get to consider this because likely business impact (value) is only determined after we have digested the idea and developed the strategy.
Agile
Agile methodology may also provide the advantage to improve time to value, via faster release, continuous communication with teams, and iterative interaction with customers.
Agile
You're right Pearle. Anything which reduces the time to market (implementtaion) can potentially increase value - but not always. Iterative implementations may not yield the full business impact and so the time to business impact may be longer. That's why in BT Staretgic planning we talk about time-to-buiness-impact (T2BI) as a critical way to weigh strategy choices. And a key part of a strategy is how you develop/implement the technology. For any strategy to achieve specific business impact goals there are four key factors to weigh: cost, risk, complexity and T2BI. The length of time it takes to achieve the expected results is factored into measures such as net present value (NPV) and discounted cash flow (DCF).
You talk about
You talk about develop/implement the technology... there is some interesting research going on in the Air Force. The research used LED technology as a case study, but could be applied to many fast changing technologies. It gives a differant perspective on the time value of technology.
TIME-VALUED-TECHNOLOGY: A LIGHT-EMITTING DIODE CASE STUDY FOR DETERMINING REPLACEMENT STRATEGY FOR HIGH TECHNOLOGY INFRASTRUCTURE ITEMS
http://www.dtic.mil/dtic/tr/fulltext/u2/a558288.pdf