Skip to main content

What is "Business Impact?"


Before we can delve into deeper topics, we need an understanding of the concept of "business impact."  This blog entry will attempt to define this concept in clear terms.

Giving credit where it is due, this is derived from the amazing course by Force Management called Command of the Message and is but a drop in the massive bucket of knowledge that you'll get if you take their course.  (And I highly recommend it if you are interested in learning about this topic in substantially more detail.)

Essentially, every business is on a never-ending journey that can be represented by the following graphic.



To explain the graphic, there is no business that is completely happy with its current state.  In order to constantly provide value to its shareholders (or owners, if privately held) it needs to continually evolve.  This process of evolution involves identifying operating characteristics of the business in its current state that are not ideal.  In some instances, these can be downright detrimental to the business.

Once you've identified the negative consequences of the Current State*, the business then defines "what good looks like" as it relates to these Negative Consequences.  In other words, what would the new operational characteristics of the business be if the ones that resulted in the negative consequences were eliminated or changed for the better?  And once you've changed, what are the Positive Business Outcomes that are the result of this change?

Finally, businesses cannot simply wave a magic wand to transition from the current state to the Desired Future State.  The journey is often defined in terms of one or more years, and with a timeline of this length you not only need an understanding of how you are to accomplish your goals - Force Management calls these Required Capabilities - you also need to constantly assess where you are in the journey so that course corrections can be made if you stray from the path that you mapped out.  (These are uninterestingly called Metrics by Force Management.)

In this explanation of the graphic, business impact is therefore the journey from the current state to the future state.  Put another way, any activity that advances the journey in the correct direction toward the desired future state is considered to have "business impact."

This does not have to be viewed through the lens of strategic initiatives for an entire company, however.  In fact, I often coached my wife to ask the question "what's the business impact?" whenever someone would propose a new process in her organization or a significant change to an existing process.  If you cannot answer the question in a way that aligns with the financial goals of the business then you must also challenge the reasons behind the change request.

Thank you for taking the time to read this.  See you next time.

* Certain phrases have been capitalized and highlighted in a different color.  These are terms that are used specifically by Force Management in their course.

Popular posts from this blog

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ