The Gap Analysis: A How-To Guide

by Kenneth Rau

We are often advised to do a gap analysis in situations where stakeholders -- anyone consuming the outputs of some function -- are unsatisfied with the current products or services. "Just do a gap analysis and figure out what needs to be done," we're told by these stakeholders, magazine articles, and consultants. But when is a gap analysis appropriate, and how is it done? In this Executive Update, I'll try to answer those questions when the dissatisfaction is with an organization's IT function; however, a gap analysis can just as well be conducted for any function in the organization that is not performing as desired (e.g., product development, engineering, sales, claims processing) using the same or a similar approach.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve your password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com, or you can Request Guest Access.
The Gap Analysis: A How-To Guide1 June 2007

Become a Member

Research and inquiry privileges, plus regular strategy meetings with Cutter's Business Technology Strategies experts are just some of the perks! Plus, CIOs can upgrade to include Cutter's CIO Suite. Talk to Cutter today about trial membership, including access to research, webinars, podcasts, white papers and more.

Request trial membership