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

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 t...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

Overcoming Imposter Syndrome

Imposter Syndrome is a cruel partner in your professional journey.  If you're not familiar with the term, it is essentially the feeling that you do not belong in a particular profession or that you do not deserve a specific role or set of responsibilities.  (You may read more in the Wikipedia article .)  I did not hear the term myself until I participated in a mentoring group for young employees at my current job - some of the young employees said they had this, and I won't deny a bit of surprise when I read what it is. If you feel this way, you're obviously not alone.  A good friend of mine suffers from this in no small amount in spite of the fact that she's an upper mid-level manager at her company with an organization of approximately 40 people reporting to her.  She feels this way because she never completed college, but fails to realize that her hard work and dedication to being the best that she can be is why she has been repeatedly promoted through the ra...