Inside-out vs. Outside-in approaches to improvements

Inside Out — The usual approach is to look at our existing problems (usually operational) and solve them or to look at the existing processes and change them to make them better, faster safer, or cheaper, in order to better serve customer needs. However, the link between the problem being solved, the proposed solution, and the customer need is frequently tenuous and usually based on unshared, unexamined, unproved assumptions. More often than not, the time and effort expended does not justify the eventual outcome.

Outside In — Start with the customer’s goals, determine what capabilities we need to meet those goals, and then what actions we need to take to build those capabilities. Actions could be changes in leadership styles, process modifications, or changes in organizational structures, rules, policies, norms, etc. This works really well for organizational transformations. For product development, techniques that can be useful are Gojko Adzic’s Impact Mapping and Tom and Kai Gilb’s Stakeholder Value & Product Quality Requirements defined in Evolutionary Project Management.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s