Published: 25 April 2016
I have recently found myself wondering if we have fundamentally mis-identified the core value proposition of business analysis, or if my view of the issue is skewed by past experience? So I thought I would lay out my thoughts and see what others have to say.
First, let's look at the IIBA definition of business analysis from the BABOK v3:
Business Analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders.[emphasis mine] 
And while we're at it, let's check the PMI definition from their recent Business Analysis Practice Guide:
In short, business analysis is the set of activities performed to identify business needs and recommend relevant solutions; and to elicit, document, and manage requirements.
Since the PMI definition is virtually identical other than tacking on an explicit function around requirements, let's use the IIBA definition from here on.
The first thing I take from the definitions is that both the IIBA and PMI seem to identify the core purpose of Business Analysis as being the practice of defining needs and recommending solutions.
But what is the core value proposition of Business Analysis?
that deliver value could be read in two ways, in my opinion. Do we read the emphasis as
by defining needs and recommending solutions that deliver value, in which both the need defined and the solution can deliver value to the stakeholder? Or should we read the emphasis as
recommending solutions that deliver value in which the value lies in the solution that is recommended? Given that so much of the perception and discussion of Business Analysis revolves around solution requirements, I would say that the community seems to take that latter view that the core value proposition of Business Analysis lies in the solution delivered.
This is somewhat supported by the IIBA definition of value which is:
The worth, importance, or usefulness of something to a stakeholder within context.
Value can be seen as potential or realized returns, gains, and improvements.
The first part of that has no relation to
solutions as value, and indeed it just states that value is found in
something by a stakeholder. But the second sentence at least seems to imply that value is realized by at least the identification of a specific change, or more likely an implementation of that change.
This idea seems to be supported by other BA's where much of the discussion of
delivering value focuses around
delivering the solution. I'll pick on Laura Brandenburg as an example of this and use a post on her web site titled
How Does Business Analysis Create Value? as an example. In that post she presents this formula and states: 
Return on Investment = [Value achieved through the solution] – [Cost of the solution]
As business analysts, we can impact both of these variables. We can increase the value achieved through the solution to the business problem and our activities actively reduce the cost to implement the solution.
Additionally, this concept of value being realized only through implementation of change is further seen in the focus of Agile methodologies on functional code being the primary metric by which business value delivered is determined.
However, this mindset that value lies in the solution has implications. One of the main ones is that all of the activities that come before needs identification and solution definition are treated as sunk costs with little or no value. They are merely precursor steps that happen before actual value is achieved by
defining needs and recommending solutions. As such, I'm sure I am not the only BA who has a hard time convincing stakeholders that allocating time to current state analysis is time well spent. Or who hears statements like
you've been working with the business for X months, when are we going to start delivering a solution so that we can show value from your time?
But what if this belief that the primary value of Business Analysis lies in the delivery of a solution is wrong?
Let us explore this question via the following scenario:
Given that scenario, the question I ask is
Have you done Business Analysis? as it is currently defined?
You might say that this is basic current state analysis and of course it's business analysis. But in the scenario above you have neither identified any needs nor identified any potential solutions. So is it business analysis as the community seems to have defined it? My answer is that based on the community definitions above you have NOT done business analysis.
Now let's ask the harder question,
Have you provided value? as it is currently defined?
This one is harder. But at first glance since you have not delivered any solution, or even identified any needs or recommended solutions, the answer seems to be no if evaluated by the metrics the community seems to be using at the moment.
But in my opinion both of those answers are wrong.
I would instead like to argue that the primary value of business analysis lies not in the identification of needs or recommending solutions; but in the provision of actionable knowledge to decision-making stakeholders of the current business, its environment, and the problems it is experiencing.
That decision-making might include initiating efforts to identify potential changes the organization might make. It might include decisions that initiate process or technology projects to actually implement change. It might include decisions to re-do strategic planning exercises based on information provided. Or they might include a decision to do nothing because the information provided makes that a reasonable decision to make. But none of those decisions change the value of analysis that was done.
If there is a decision to move forward with identifying change options or to move forward with a specific change, then that knowledge the BA assembled can be used to define needs and recommend solutions, but it does not lack substantial value without those steps. Indeed, without that current knowledge the identification of needs and solutions is problematic at best.
I would instead argue that the primary value of business analysis lies in providing all of the following to decision-makers:
The item in bold is one of the greatest values I see that never gets discussed.
Needs will come from strategic choices made by decision-makers based on the environment. They don't arise out of the organization or even out of the environment, they arise from decisions the organization makes. The BA can then have a substantial role in identifying and refining the needs that arise from decisions, but most of the work should be around refining needs and determining the operational factors of those needs.
What I do know is we currently seem to drastically underestimate the value of current-state analysis, well-thought out future state scenarios, and the benefits having that information bring to organizational decision-makers.
I don't know how many times I've heard from senior stakeholders how much they liked the outputs of current state work because
it enabled me to see what we do in a holistic way or
… in a new way. Or how much value they got from efforts to identify business problems, even before we got to identifying
needs, just because it gave them a much better picture of the environment they are operating in and enables them to make better decisions.
I would argue that the Business Analysis community may want to re-orientate on a definition of Business Analysis that focuses on analysis itself and less about project-oriented outputs of analysis like needs, requirements, and solutions. Maybe we can adapt something from the definition of Intelligence Analysis below that comes from Wikipedia?
… the process of taking known information about situations and entities of strategic, operational, or tactical importance, characterizing the known, and, with appropriate statements of probability, the future actions in those situations and by those entities.
The ability to provide a strongly analyzed
outsiders view of an organization or problem to decision-makers should not be undervalued. Nor should the massive time saved by decision-makers by having a BA do that work. Unfortunately, I think both are values that the Business Analyst community currently ignores outright with the current definitions and statements on what business analysis is and how it delivers value.
Yes, defining needs and recommending solutions are important. But are they the primary function of Business Analysts? Are they the primary way we deliver value? Are they even possible to do well without the identification and analysis of organizational and environmental conditions we currently seem to undervalue so much?
I don't disagree at all that they are important functions that Business Analysts provide, but are they core of what we do? Are they the only way we deliver value, which seems to be the current consensus of the community?
I would argue that virtually every major problem identified as a
requirements issue can probably be traced back to a failure to do enough current and future state analysis before a desired change was identified, let alone initiated.
too longto answer critical questions in an agile project? Not enough knowledge of the current state and desired future state.
We seem to really undervalue the time, effort, and results that go into
enterprise analysis. That is the complete understanding of the current state, the likely environment changes, the desired future state, and the identification and root cause analysis of the problems that block our ability to achieve that future state.
What do you think?