the Bridger

October 10, 2009

Don’t forget about innovation

The first part of any project involves defining  the problem, deciding where to look for the solution and how to proceed with the search and finally defining the solution, validating it and getting agreement from stakeholders.

Now the nature of Technology is such that few of us are aware of what is possible and even fewer are able to see the impacts of these suggested solutions over and above the promised outcome.

Not only are few of us equipped to access the best solutions, but even fewer are able to recognise when we have a problem.  In technology speak a problem is closer in meaning to a mathematics problem , it doesn’t necessarily cause that irritating pain that our marketing colleagues like to focus on.   

E.G.  Let’s say chief zongawonga is worried that with 19 more children due this spring, he won’t  be able to catch enough fish.  His bright young progeny identifies the problem and suggests metal arrow heads that are more effective and mean they can quickly make extra spears so everyone can join in. That represents a problem known and tackled.
However, Zongawonga doesn’t know that monofilament nets are cheaper than arrowheads and one child can feed the whole tribe with one net.  Until he becomes aware of the nets, he won’t know he has a problem, or until his wives start leaving for the easy life with his neighbour who doesn’t expect them to fish.

The process involved in definition of problems and solutions differs not at all from the age old problem of effectively searching a global mountain of unstructured content as described below.

First you have to arrive at some fundamental conclusions about the problem, the possible solutions and how and where to go looking. Consider this example and then have a read through the innovative solutions put forward by Zyra and see if you don’t begin to question the stuffy, stuck in the mud methods of innovation and improvement that have become embedded in most modern businesses.

 ”just what are you looking for, anyway?”

  •  A known needle in a known haystack
  • A known needle in an unknown haystack
  • An unknown needle in an unknown haystack
  • Any needle in a haystack
  • The sharpest needle in a haystack
  • Most of the sharpest needles in a haystack
  • All the needles in a haystack
  • Affirmation of no needles in the haystack
  • Things like needles in any haystack
  • Let me know whenever a new needle shows up
  • Where are the haystacks?
  • Needles, haystacks — whatever.

http://www.zyra.org.uk/needle-haystack.htm

 

The answers you give to the questions above will have a profound effect on how you approach the project, how you define success and your likelihood of succeeding.
Furthermore, whether you are in charge of developing  market leading products, or keeping your company  at the cutting edge, taking a little time out to consider these questions and address them  innovatively will take your performance to the next level.

March 26, 2009

Where has all the money gone? – you wouldn’t believe it

Part one – why?

Previous installments:
IT investment for the small businessman and novice
Why the SMB/SME holds all the aces when it comes to IT
In our last instalment we talked about the advantage an SME/SMB has over it’s bigger rivals when it comes to implementing technology, especially around the aspects of communication, business change and lack of red tape. 
Don’t let this reference to red tape fool you. It is mission critical to understand the difference between vital  process and red tape and it’s not always immediately obvious.
The key to cost cutting in any area is knowing what to cut. The word we are after is waste, but even that can be misleading.  In the world of Lean everything outside of the critical value adding moment is deemed to be waste, but nobody imagines that you can eliminate most of it let alone all.
The best approach is to look at where the money goes in a typical systems implementation.
Let’s take ACME  cash registers.
They have a turnover of 200 million and they have countless systems handling different aspects of their relationship with customers.  Nobody in the organisation has the full picture at any time bout any customer.
Sales people call with an Upsell proposition within an hour of the customer complaining bitterly to support.

  • Customer enquiries get written on cards and handed to salespeople who then lose a percentage or forget to mark them up so 14% of leads are never followed through. (any of this sound familiar)
  • The last time they tried a mass emailing they only had email addresses for 34% and two thirds of those were returned undelivered. This resulted in their IP address being registered as a spam house and for three months their emails were being destroyed by a robot and never arriving.

Ok this is just the tip of the iceberg, but you get the picture. The new VP of sales has read the riot act and reluctantly he has been promised that they will try and find some budget to help out. Where do we go now?
In our next contribution we will provide an insight into how not to approach it and the we will move on to  look at a simple model for getting this job done.
Requirement gathering the first big mistake

  About the author

 

March 25, 2009

Why the SMB/SME holds all the aces when it comes to IT

I know you probably wanted me to tell you how unfair and inequitable the world is and how tough it is to be small. We’re in that sort of phase just now. Well you are going to be disappointed, but I challenge you to read on anyhow.
Not only is it easier, cheaper and less risky to implement state of the art IT, but rarely do your big brothers tap into the advantage effectively once they have implemented it. Now there is a new twist that puts the smaller business back at the cutting edge.

Small is beautiful when it comes to costs

When I rolled out a nine million pound IT investment for a government department, I spent more than a million getting the messages through to the workforce that things would be changing and preparing them and yet another million fighting the bonfires to get it rolled out and accepted.
When I rescued a large project a few years ago, they had already spent close on a million on feasibility and had got nowhere with it.
Implementing a mission critical system for a huge nationwide organisation, I got to roll-out stage and not even the CEO could make IT go any faster, we waited three months while they  put us off with new problems each day and they negotiated for increased budgets for running the system that would have supported a medium sized island, despite having agreed all of this previously at planning stage. Each slight effort from IT requires forms, a process and a very long wait.(Partly justified, because bigger IT comes with bigger risks).

Small is beautiful when it comes to change

Bringing about even fairly small changes in a very big organisation is slow, very expensive and not at all guaranteed.  The employees have no sense of connection to anything , or anyone, it’s just a huge employer and change is inconvenient. Customers have a stronger relationship with the brand than employees with their management and shareholders. Established employees can easily resist change without suffering any consequences and often do so just to prove that they can.

When a big business is forced to compete with small business on a level playing field, it is like a train attempting to  catch a rabbit.  Trains are only good for long straight and fairly even roads. While the train is moving the tracks, the rabbit is enjoying the grass on a greener slope.

Business case

The average cost of a feasibility study and business case for a large business today is estimated at around £60,000. There are more stakeholders with more complex propositions and communication grinds to a slow shuffle. There is usually little or no true big picture and everything you produce then has to be reviewed on the basis of, “do I really look like that that?” .I recently completed a feasibility and prepared a business case for a large SME/SMB and it cost just  £7k.
Rapid painless implementation
When that business described above comes to implement their plans, the system will be hosted on the cloud without a single click of a mouse by their IT department and it will be running and operational in a one day.
It will have world class back-up, disaster recovery, failover and  all the things an SME/SMB struggles to afford and  it will be maintained 24/7.
They won’t buy any hardware or purchase anything up front and their modest budget will be spent on improving their business to take advantage of the new system’s capability, communicating their requirements accurately to the service provider, training people to make their lives easier and their jobs more secure with this new super tool and getting their data into good shape to take maximum advantage.
 Dynamics of IT investment for the SME/SMB
 Where has all the money gone?
 About the author

 

 

 

March 15, 2009

IT investment for the small businessman and novice.

Previously:

The advantages a small or medium business has  over their larger competitors and how they can save vast amounts of money in implementing high productivity software and gain the benefits faster.

1. It investment should never cost you money, it is an investment and the ROI should be clear.
 Build a business case professionally and then invest with confidence. 
The question to ask is; who would you rather trust with your capital, your own business, some investment bank, or maybe a fund manager?

2. Cash invested in your own business via IT systems or any other properly planned investment is always going to outperform any other investment and it remains within your control.

3.  In a free market economy, you always have to match the performance of the market leaders sooner than most of your competitors, or you are out of business. It’s not optional.  If they have automated successfully, you are at risk until you follow suit, or outdo them.

Types of IT investment

One thing every business man/woman or at least his/her CTO should understand is the dynamics of costs and returns  for different types of IT investment in different sizes and types of organisation and for different purposes.

There is absolutely no broad sweeping brush that can be used here and there are few reliable rules of thumb.  There are huge risks for the unwary and there are massive opportunities for the savvy, there are things that are not optional and things that are very much optional.

IT infrastructure versus productivity systems

The first big source of confusion is between the purchase or replacement of networks, servers and workstations, printers, operating systems and office systems like Microsoft Office.  The risks of a failure are dramatically less in this area and the potential to realise benefits and make gains are also much less.

Putting off the upgrade of workstations or operating systems by a year will rarely have any effect on bottom line unless you are losing time due to stoppages and unreliability.  This is an area where business cases need to be scrutinised with great care.

1.       Unless there is real risk of lost productivity, or very high maintenance costs, it is going to be hard to justify not keeping the old stuff as long as possible.

2.       Upgrading to smarter tools with new cool features will only benefit the one or two geeks on the team unless you take steps to train people on the new capabilities. Is that included in the business case?

Automating process

This is what business systems are really all about. The database replaced the card index and made it possible to share that information with colleagues globally, to search on fuzzy logic and to send a message at a single mouse click.  This was a pretty easy decision on hindsight and the business case is obvious now, but at the time, ditherers and weak leaders continued with their card indexes until they saw their customers walking into their competitors arms.
Plenty of leaders continue in the same vein today and every new step forward in technology will have innovators, early adapters, last minute Harrys and hard luck stories.

Technology is not the enemy

Since records began, businesses have had to find ways to deliver better products or services, do it at lower costs and win and keep more customers. There’s a percentage at the top end of this battle and there’s a percentage on the way out, the rest are headed in one direction or the other .  Businesses that choose to close their eyes to the importance of technology in this struggle have already consigned themselves to the scrapheap.

Face facts and make the most of it
Success at harnessing technology requires understanding a few basic rules and working with people you can trust to deliver.

Strategic advantage or state-of-the-art

The first big differentiator between software systems is their status in your market segment.
If you are considering a system that you hope will bring you in line with the main players, then this is probably “state of the art”, though if you are a long way down the pecking order it may still be classed as “strategic advantage“.
E.G.  If you run a large business carrying out maintenance type work like Sky TV maintaining satellite dishes, you will have automated scheduling that plans the shortest routes and sends jobs directly to the engineers PDA or mobile.   This has cut operating costs by 25% on average for these businesses and is a fast maturing industry.   If you want to bid for sizeable projects then you won’t stand a chance of winning competitive bids unless you have this in place.  That’s “State of the art” IT.
If you run a local cleaning business with a few dozen teams in vans and you are growing and ambitious, you probably don’t have this systems yet and your direct competitors probably don’t, so to you it is still probably “Strategic advantage” IT. If you are serious about growing, guess what you will be planning now!

Not only will the ambitious smaller firms be scrambling to get this competitive advantage, but the guys at the top are already planning to push the bar up higher and guess what you will have to do when that happens!

There’s one fact that is simply unavoidable whether it thrills you or fills you with horror;
Competing and winning in business in the 21st century is primarily about winning the technology battle.
 Where has all the money gone?
 About the author

  

 

 

 

 

 

  

 

 

 

 

 

January 23, 2009

Is there still a case for IT strategic planning?

 The earth is flat in any case

Unless you’ve been asleep, in denial or on medication, you will have noticed, at some level at least, that in the last few months the key assumptions underlying our post industrial survival have been proven flat wrong.

To put that in content, the earth is not round but flat and the universe is merely mirror images of the earth reflected on a layer of slightly opaque gasses. The landing on the moon happened in a closed off section of MGM and hamburgers are good for you.

It no longer matters how much we borrow because we probably won’t be around to pay it back, only nobody will lend it of course because they are keeping it to line their pyramids with.

What’s the point in getting up?

You could easily be pardoned for asking the question and I can see some beginning to think like that.
That, in truth is what recession really is.
An end to economic growth is no big deal, we probably couldn’t survive without taking the odd breather. The bad bit is when sensible people suddenly decide that it’s not worth bothering, then we all suffer and what was a diet quickly becomes bulimia.
Read on and I will convince you that there bigger opportunities than ever, they just need a different approach

So how do you build a business case for IT investment and sell it to the board?

Realism
If you want to be taken seriously, you can’t base any investment on predictions of returning to normal in a few months or pretending the problem doesn’t exist.
You must recognise it and spell it out in terms of a clearly risk managed approach.
It’s unlikely that you are in a business where you can afford to make risky investments with long payback periods, so you need ROI fast, or even faster and you must prove that your eye is on the ball.

Prudence
Getting the financials right is critical, but that’s not the whole story by a long way, here’s a selected list of other issues in no particular order that are extra important.

· Make sure your initiative addresses the bulls eye in terms of business initiatives, not peripheral or even sort of important, but right up there.

· Make sure this is best deployment of scarce capital.  Remember it is no longer in unlimited supply.

· Time to market is very important and can easily be disguised behind impressive returns. Include timing in this calculation. Limping in a month behind your main rival is a great way to blow your big chance.

· Competitive advantage can be a critical factor that is easily missed. If all your competitors are cutting 20% off cost of sales and your initiative wipes 5% off, you might find the idea is less successful than you had hoped.

· Don’t suggest a major new 22nd century architecture if your goal can be achieved reliably with duct tape and scaffolding. This is about surviving today, not ideas or principals or fancy technology.

A little audacity goes a long way
Take a look at tiny little Porche and compare them to giant GM. Porche are busy taking over VW, to create the third biggest car manufacturer in the world and asking nobody for help, but using the downturn to make it possible.
If you are good at what you do and you can improve costs and capabilities, then watch out for all the leftovers of those overweight beasts that are shedding customers and reputation and be ready to take advantage of the opportunities that a downturn creates. In a ten horse race there are nine opportunities and one risk for the bookmaker. Don’t focus in on the risk and blind yourself to the opportunities.

Outside the box

There’s a great awkward purple elephant sitting on the board table and let’s stop pretending he’s not there.
The GAPE I’m talking about is the contradiction between thinking out of the box and following the strategy, the corporate plan and the processes, those things so beloved of civil servants and Ops directors. Let’s just say it:
How the hell can you be a process man who works to the plan and also think outside the box?

Well of course you can’t, it’s that simple, so you have to come out from behind whatever you are hiding behind and take a chance or two. Be up front about it that acceptance of your new proposal means revision of the agreed strategy and the current plan. That’s why they are there, not as straight jackets.
Delivering benefits on the cheap can upset lots of people, especially some members of the IT department, preferred suppliers and business analysts who have carved out cosy corners for themselves, but if that is the price, then accept it and pay it. Here’s a few examples:

· Be prepared to ignore the Enterprise architecture and do it the cheapest way.

· Be prepared to bypass the developers in the corner and buy something a bit scruffy and poorly documented, but supported from outside the business.

· Be prepared to find a few freelancers in Russia and get it done cheaper.

· Learn about mashups that can deliver the same result as an enterprise bus for a tiny fraction of the cost and get your show on the road.

· Get to know someone who knows about opensource solutions that are a bit ugly in places and awkward to install but are FREE and once you get them working they eat no corn.

· If you don’t know about agile methods, speak to someone who does and consider it for appropriate situations.

· Look for SaaS products that can start delivering returns in days rather than months

· This is a no brainer, but rarely done. Make sure your people know how to get the most out of the systems you already have.

So there is a new strategy after all

Yes there is a strategy for the current climate and I believe it has a valid legacy to take forward into the good times also.
Don’t stop looking for opportunities, but look harder, look outside the box and examine them more closely before committing. That usually requires an external input, but it is well worth it.
Don’t plan for a decade, but for this year, who knows what next year will be like, but this strategy will still be serving you whatever it looks like. That means dumping or revising much of the strategy and plans you are currently strangling yourself with. Do it sooner rather than later and free up your thinking and your energy.
Look for silver linings until it becomes a habit
Remember not to get complacent in the next bull market
 About the author

July 12, 2008

When is a business case not a business case (part 4)

 Read part one  Read part two Read part three  Read part four

In our previous instalments we discussed the preparation of a business case and calculation of the data needed to prove it.

Today we will be discussing the art of delivering the business case in such a way that it competes on a level playing field with all other initiatives currently on the agenda.

There a re a few fundamental rules to bear in mind when presenting any proposition:

1.       Recognise and understand your audience so that you can directly target a known need or desire with your proposition.

2.       Use the appropriate language and context to present your proposition.

3.       Get your timing right.

4.       Demonstrate understanding of and sensitivity to the operating environment.

 The first paragraph should always be entitled ‘Executive Summary’, but it should be the last one written.

The next paragraph should be a backgrounder that demonstrates succinctly and understanding of the operating environment, I.E. political, environmental, social, technological.  Make sure you don’t fall into the trap of contradicting the CEO. Work form the five year plan or current year plan or what ever is the most relevant document and if there have been significant changes in the operating environment since it was written then discuss it with senior people so that you reflect it accurately and delicately.
You may find for example that the CEO published a plan for robust growth ina bullish market three years ago and the CFO is now investing inwardly in cost avoidance projects while they watch the news with interest for an indication of the way forward.

In this case you need to be able to reflect this in your businss case so that it sets the scene for your cost reduction proposal.
 When it comes to writing down your propositions, bear in mind that there will be two distinct audiences, those who want to scrutinise the details and those who want the bottom line only.
The latter type will very often be relying on the former to take care for the detail for them so it is very important that you address each in the appropriate manner, presentation and language.
In part two we drew a map that linked features to benefits. In this section we will expand this idea further and we will map those benefits to stakeholder driven propositions.

Here is a simple example from my own experience.

Strategy and KPI mapping

 Strategy and KPI mapping

 In the diagram above we can clearly see that the CEO has published a key goal for the current period which is to improve net profit margins by 1 %.
 The CFO has a related KPI called indirect costs/sales volume and he is hell bent on improving this KPI by 1 point in order to meet the CEOs  goal.
The Operations Director is working on a goal to reduce the paperwork element  involved in picking, packing and shipping products, while maintaining or improving delivery success rates

In your business case the value propositions would address each of these stakeholders in his/her own terms and use context to draw an accurate picture of the scale of benefits.
E.G.
The proposed system will positively increase net profit margins by a factor between .2 and .4% in it’s first year of operation and reach breakeven in the first quarter of year 2.

In achieving this, it will increase the costs/sales volume KPI by a factor of around .3 through virtually eliminating the paperwork involved in the picking, packing and shipping aspect of operations.
Additional benefits will be reduced propensity for error in this area that we have not attempted to quantify.
For detailed breakdown, see the financial analysis section.
You will note that this sentence describes the system in terms of benefits that can be readily understood and appreciated by each individual stakeholder.
By quoting KPIs the scale of the benefit is immediately put into context so that you capture the attention of your target readers.

Presenting the figures.
You don’t need to be a financial analyst to figure out that bringing in benefits early has a dramatic affect on the financial results of your project.  If you cast your mind back to part three when we talked about Net Present Value (NPV), you will realise that bringing in, or saving  a million next year rather than the following year, supposing a discount rate of 10% will deliver an extra 100,000 in benefits.  Not only that but it reduces the total investment required, thus improving ROI and freeing up capital for other important projects.

This simple exercise will help you optimise your business case by bringing forward benefits where it can be done.  You may remember that in part one we talked about listing the features and benefits that make up your projects and creating metrics for each feature.
Here is a simple tool we use to prioritise these features.

Tool helps with prioritising features

 If you need to analyse more complex and more data rich cases, then a Pareto chart can be an excellent way to single out the low hanging fruit.
For non financially aware people you may be able to put the benefits in context by taking the ROI and calculating how much extra revenue it would take in order for the business to deliver that same return through extra revenue generation.
In order to make this case rock solid you need to also present at least one potential alternative tactical solution and a do nothing scenario.
In your final analysis, you will compare the do nothing scenario, the tactical solution and the proposed solution and demonstrate clearly the basis for your proposal. 

Project plan
An indicative project plan should be included in order to demonstrate the likely timelines including benefits realisation activities, implications for personnel, budget and  team structure.

The executive summary.
In this section we always place two things:
1.       Our proposal, stated in direct no nonsense language aimed at all relevant stakeholders jsut as we discussed earlier.

2.       Our paragraph of analysis that briefly describes the alternatives and the rationale behind our proposal.

The executive summary should contain nothing but the bare facts and concise value propositions, no rambling intros or winding up paragraphs. It is a business document and it is about cold hard cash so keep it clean and factual and get straight to the point.

Sign off sheet
Don’t forget a sign-off sheet so that they are very clear of the immediacy and urgency and the fact they will be expected to make decisions as opposed to having a discussion.
Presentation

n order to present the business case, our strong recommendation is that you produce three artefacts.

1.       The full business case

2.       A one page summary including the executive summary  and financial conclusions

3.       A presentation of four or five slides demonstrating pictorially, the background, the benefits, the financial analysis, the project outline.

The first  communication should be the short summary sent by email to the stakeholder list along with an invite to discuss it in a formal setting.
The second communication should be a presentation of the business case with opportunities for questions and answers and the full business case handed out about half way through the presentation once the key points have been presented.

  Read part one  Read part two Read part three  Read part four

 

Reblog this post [with Zemanta]

July 5, 2008

When is a business case not a business case (part three)

Read part one   part two Read part three  Read part four

In this part I will be talking about  the importance of the financial analysis and the practicalities of putting the figures together.
After all the bottom line in any busines case is going to be financial although individual stakeholder priorities and concerns will play important parts as will the organisation’s history with similar projects and even good old office politics will often play a part.

At this point I would caution that despite the importance of the figures, it would be foolish to present a business case without taking into account the stated aims of the business in it’s short and long term plans and the key performance indicators and critical success factors of the key stakeholders.

If you are able to tie your benefits very clearly and distinctly to the corporate goals and to the personal KPIs of your individual stakeholders, then you stand a much greater chance of getting their attention and you may even be able to enlist their help in fleshing out your arguments.
You will also have an aopportunity to spot delicate or contentious areas that are best played down or avoided.

The approach to financials

Financial decision based on Cost v benefit v risk

When approaching financial analysis for a business case, three subjects immediately emerge as important topics:

  1. Cost benefit analysis
  2. Quanitfying and presenting intangible benefits.
  3. Risk/reward analysis

The reasoning behind our approach is simple.
Ultimatey, your business case is about costs versus benefits so a good estimate of costs is critical alongside of a realistic estimate of benefits.

The majority of projects bring benefit that are not easy to measure in reduced costs or increased profits, but are nevertheless important and valuable.

Given that some benefits are easier to hook and land than others, it makes perfectly good sense to have an indicator of how likely you are to succeed in delivering the benefits and to stay within cost estimates.
This way you are able to cherry pick the projects that suit your organisation’s current appetite for risk and you have an option to delve further into risk management if the potential reward is particularly attractive.

 Positioning the business case
It  is important to position your business case and calculations correctly from the outset and to put in the appropriate level of analysis and checks in collating the figures.
This activity will begin as an outline business case offering your best estimates based on hard data where available and tacit input form key stakeholders to fill the gaps and make adjustments where appropriate. This type of estimation is often described as stake in the ground estimation. It’s purpose is to decide whether a initiative is worthy of pursuing further.

Later after you have received appoval to proceed, you will continue to refine all the estimates until you arrive at a baseline part of the way through the project.

Doing the mathematics

Rule number one;  Unless you are trained in financial analysis, put somebody else in charge of this part of the work and act as the collector of data. If you can’t delegeate it then you are still going to need close cooperation from the finance department to get access to key numbers and you will need them to scrutinise your figures before you show them to anybody else. 

The financial benefits can generally be described as either of Cost avoidance, or Increased revenue. These events have very similar effects on Return On Investment (ROI).
A key measure for most organisations will be ROI and a simple viewpoint can be that the project represents an investment of capital in the hope of achieveing better returns than it could achieve elsewhere.
One of the options for investment of retained capital would be the equities market though the key indicater here is the organisation’s Cost of Capital.  This figure is unique to every organisation so you need to find it out.

Costs

First you need to do some good old stake in the ground estimating of costs. Use as many reliable and respected opinions as possible to get ballpark figures at the start and refine this with as much verifiable data as you can get hold of. You can also try some online tools like Gartner TCO analyst, WIPRO TCA tool, or a number of services available online.

Look through old project budgets if you can and learn from experience to make sure that you don’t leave important costs out. Nothing can erode your credibility quite llike having a glaring ommission pointed out to you in front of the board.

 If you are estimating costs for a new  CRM system for example,  you can begin with internet research and you will find detailed case studies and benchmark costs there, which give a very useful starting guide once you factor in comparisons of scale and other knowns.

Next you can look at the organisation’s history of deliveirng similar projcts. This is a critical sanity check, because not all organisations have the same capabilities and you need to estimate realistically. Look at similarly sized projects and similarly complex projects and look for overall time, scope creep, cost escalations and the obvious areas of weakness.

Factoring this information into your initial estimates will give you a very sound footing for moving forward to attempting an actual breakdown of costs:
Typical project deliverables are a useful way of making sure you cover ebverything; Project planning, management, requirements analysis, licensing, etc until you have a comprehensive list.
You wil then need to seperate the ongoing costs form the capital costs. E.G. Support, annual licenses etc.

In the case of an IT investment I would generally expect to have three columns in my spreadsheet to cover three years going forward.
Now total up all of your costs for each year and make sure to account for indirect costs with a best estimate.
The last step in calculating costs is to apply a confidence level to each calculation based on the maximum you expect it to slip. E.G. you predict that testing will cost £100,000 and you expect that the most it could slip by is  8%. Your confidence level  8% the max figure is 108,000

Tangible benefits

Once you have finished calculating the costs, you can begin to calculate the tangible benefits.
In most cases this is a fairly simple set of calculations such as 20% reduction in returned goods.
cost of a single return = n total saving per annum = n * 20% *average returns level.

Always remember to do simple cause and effect analysis to determine what extra benefits might accrue that could be included and to be aware of any adverse effects that might result. The approach should be the same as with costs, the more collaboration you do, the more beleivable your results wil be and the more buy-in you will get.

Intangible benefits

Bit by bit organisations are coming to accept that intangible benefits are important and should be measured and accounted for. The difficulty is that measurement is as yet not a science and the responsibility of signing off large budgets without masurable benefits is too great for many senior executives.

The reality however, is that intellectual capital, the real classification of these intangibles is a major part of the calpital of every organisation and becomes especially noticeable when valuing a business for sale or valuing an equity. The business with an innovative loyal staff, an attractive location and great reputation is infinitely more valauable as an assett than an identical organisation without these attributes.

Physical and intellectual capital in an organisation

Above is a view that illustrates in a very simple way the part played in an organisation’s value by intellectual capital. The type that might be dismissed as intangible unless you make the attempt to represent it correctly.

One area where some progress has been made is the company Brand.
E.G. A favourite areas of disagreement used to be the expenditue on building and maintaining a brand.  CFOs were reluctant to sanction spendng on what they often saw as “pink and fluffy stuff ” that delivered nothing at the bottom line. 
Recently Coca Cola had their brand revalued to $67.5 billion dollars and you can bet your last dollar that it appears on the balance sheet.
Today it is easier to get  formula for calcualting the value of the brand than it is to get a sensible definition of what a brand is, so don’t be put off by apparently intangible benefits. Tackle them and tame them.

There are three approaches that we tend to use most:

  1. Take the same aproach as brand valuation, I.E. how much more would the business be worth with a better reputation in the recruitment market and first call on the brightest talent.
    This type of calculation can be easier to do than seems apparent at first. If you can get hold of competitive analysis reports it will be easier still because the strengths and weaknesses of immediate competitors wioll be listed there and you can aim right at the bulls eye.
    Once you have made an estimate add a sensible confidence level to it and run wih it.
    Once again, remember to be collaborative and to bear in mind the language and culture of the orgnisation.
  2. Identify a KPI that will be significantly afffected by the benefit and discuss it with the owner of that KPI.  Perhaps the HR director is tasked to reduce staff churn and has a KPI measuring this.  Ask her to help you work out the value to the business of imporving that KPI by 1 point.
    Armed with this estimate, predict how mny points you expect to improve it by and then calculate the financial benefit. Again apply a sensible confidence metric.
  3.  Track benefits via impact analysis, represent this on simple fishbone charts and then quantify the bottom line beenefits that can be identified.  E.G.  Improved reputation as an employer -> reduction in churn -> reduced costs of recruitment (£) + More skillful staff -> win bigger projects from competitors ->(£)

Now that you have done the figures it is a simple matter of presenting them in a table so that they can be easily evaluated.

In my example you will notice that I have included my confidence levels on a seperate row so that the reader can take whichever view point he/she wishes.

The only  calculation we use in a standard business case is the NPV. This represents the Net Present Value of a sum of money, I.E the value of that money in todays currency after factoring in Cost Of Capital.
E.G. It is infintely better to have a poundt in your hand today than to receive it in three years, because it will purchase less in three years.  In the NPV calculation we use the same thinking except that rather than inflation we use a Discount Rate that is based on cost of capital, because to better represents the investment options for that capital.

It is key to get the cashflows right i.e. to work out a benefits schedule, because you need to know when cash is coming in and going out if you are to calculate NPV.
Once you have this in place you can use the NPV function in Excel to calculate the NPV for you.

The Payback period is a straightforwar and obvious calculation and the Internal Rate of Return (IRR) is just an interest rate representing the return on the investment of capital.

 

Year 1

Year 2

Year 3

Delivery costs

 (£6,256,871)

 

 

Delivery incl. risk (n%)

(£917,142)

 

 

Ongoing costs

 £0

 £0

£0

Ongoing incl.  risk (n%

£0

£0

£0

Benefits

 £11,896,000

£11,896,000

 

Benefits less risk (n%)

 (£4,664,800)

(£4,664,800)

 

Net Cash flow

 (£7,174,013)

£7,231,200

 £7,231,200

Options

(£1,600,000)

 £66,650,000

£66,650,000

Options risk

 (£45,060,000)

 (£45,060,000)

 

Net options

 (£1,600,000)

£21,590,000

£21,590,000

Discount rate

 15%

 

 

NPV

£3,984,186

 

 

Payback (months)

12

 

 

IRR

 63%

 

 

 Risk analysis

As you will have noticed we built the risk analysis into the individual calculations as opposed to applying it to the whole calculation at once.
If this is a sensitive area, then it is a simple matter to calcualte these elements as an overall cost risk and overall benefits risk and look at best and worst case scenarios.

 At this point we have a fit for purpose finacial proposal and now we need to set about optimising the presentation.

 

 

 

June 28, 2008

When is a business case not a business case (part two)

Read part one   part two Read part three  Read part four

In this section I will be talking about benefits, why they are so important to the business case and how they can be tracked right through the project, thus making the business case  a key document in successful project delivery, rather than just a tool to get the budget released.

Benefits map diagram expains the bridger method of mapping requirements to benefits

The model above illustrates our basic theory of benefits delivery.
On the left side of the diagram, we represent high level requirements.
This is intended to illustrate the level of requirements that is generally outlined in the business case.

This requirement is then tied indirectly to the composite benefits illustrated on the far left of the diagram. These benefits are the ones providing the key arguments for action.
That part of the model is very simple and intuitive. We have high level requirements and we expect to deliver the identified benefits.  The denotes that this metric is to be measured.

A key element of this approach is to remember at all times is that the requirement exists in the business case only to deliver the identified benefits and any change to the requirement or surrounding circumstance that impacts it’s ability to deliver these benefits is a red flag issue and must trigger a business case review.

The devil may be in the detail

 Between the high level requirement and the composite benefit, naturally, lies a lot of very important detail.  While this detail is not represented in the business case, but in other documents such as requirements specifications and benefits realisation plans, the exploration and bottoming out of this detail, will be critically important to the final conclusions of the business case process.


We look at this benefits mapping activity in terms of feature level requirements I.E. identifiable succinct features of the product or deliverable and with this we associate two things:

  1. The measurable benefit that is expected as a result of this feature, along with a suggestion of how it might be measured.
  2. The risks management attached to realising this benefit.  We describe it as risk, because we want to confine the change management activities to those that are necessary in order to deliver the benefits.

By taking this approach, we are proactively testing the likelihood of our successfully delivering the benefit and we are planning the change activities required to ensure that they are delivered.

Benefits realisation example

E.G. In the CO2 example, we may have assumed a fuel saving of 1000 gallons per month resulting in a measurable reduction CO2 emissions.
In order to actually realise these benefits, we might have to take steps to ensure that all the lean cars are not last to be taken from the car pool, while the big luxury ones are first choice. The approaches can vary considerably, but they have to be planned and in many cases included in the costs of the project.

Without this risk assessment and change management activity, the likelihood is great that the potential impact of replacing luxury cars with lean ones will deliver little or no benefit to the environment or to the organisation, No ROI and a project failure.

Now if we look again at our diagram, it may become obvious that we will have quite a few of these feature level requirements and that each will have it’s own mini business case including the level of ROI and the level of risk attached to delivering benefits.

 As the project takes shape and more is learned about each of these requirements, this mini business case needs to be constantly reviewed and updated so that poorer candidates can drop off the radar and stronger ones get promoted to a higher priority.

Approaching the business case in his way and continuously managing it as the development continues from outline business case to full business cases will keep the business in control and minimise the likelihood of pursuing projects that perform below expectations.

 Read part one   part two Read part three  Read part four

 

May 16, 2008

When is a business case not a business case?

Read part one   part two Read part three  Read part four

  1. When it establishes that there is no case for the proposed initiative.
  2. When it fails to identify and present the benefits of the propsal sufficiently well to win support.
    Both of these situations have the same result only the second one is a lost opportunity for the business.
    A process for deveoping the business case for IT change

You can talk to five different people who have that word in their CV and each one will probably have a different take on what a business case is for, who should prepare it and what it should contain.
In fact, you could say that  the whole science around business cases, especially those involving IT investment has moved on substantially in the past two or three years.

Many of the concept of benefits were rarely discussed ten years ago, let alone benefits realisation.  Today all that has changed. Some examples of the importance this subject has achieved is the Cranfield university  Benefits Dependency Network Tool  and more recently the Microsoft REJ framework.
Here is a simple explanation that takes into account more recent developments in thinking and puts a simple framework around what a business case is and is not.
1. A business case must live up to billing and make a case for the proposed project. That means demonstrating how the project will deliver benefits for the business
2. A business case should take three forms,
a. Initially it should be an outline business case. This is a non detailed and very tacit explanation of why some very knowledgeable stakeholders feel that this is a very good idea.
b. A full blown business case with detailed cost benefit analysis and detailed financial calculations such as ROI, EVA, IRR,NPV etc
c. A one page summary of the final business case for people with little time for detail.
3. A business case must take a analytic view and not be an excuse to purchase my new toy, hence it should examine tactical solutions and doing nothing.
4. A business case should take into account political ,economic, sociologic and technologic trends likely to impact on the projects ability to deliver
5. It should take account of the organisations ability to deliver the project and realise the benefits.
6. The business case should always be a living document that is carefully managed by someone who carries a key responsibility for the project.

The diagram above shows a simple process for producing and managing a business case.
The top section represents the activities that generally occur prior to going into the implementation phase of the project .
The bottom section represents the activities that continue during and after implementation.
The first priority is to expand a little on the initial concept and capture high level requirements.   In dong this it will be key to get an understanding of the benefits hoped for by stakeholders and to abstract form them the knowledge and experience that has lead them to this conclusion and the assumptions that are underpinning it.
Next a high level examination of the potential solutions, include the ones that are likely to be already suggested, a do nothing scenario and a tactical solution.
From here an outline business case can quickly be created that encapsulates all the motivations, expectations and tacit understanding of the problem and potential solutions and provides a building block for stakeholder mapping.
In the next instalment we will look at some of my favourite tools for helping to create a business case that serves it’s purpose.

Read part one   part two Read part three  Read part four

 

Reblog this post [with Zemanta]

Powered by WordPress