You've been working on a potential sourcing transaction for months. It's not going well and you have to at least consider giving up. Not a pleasant thought, but why is it so hard to make the decision?
Putting aside the personal embarrassment that can come with a decision to shut down any project, what are some of the things that make it so hard for companies to decide not to do a deal?
If we step back and think about the key hurdles that any good deal has to overcome, there are three. First, it has to have positive economics. Second, it has to be feasible to implement. And, perhaps most relevant to this topic, it has to have strategic positioning.
If a potential deal is floundering, it is often because of the economics or implementation feasibility. We can spend inordinate amounts of time trying, or to borrow that common phrase "turn a sow's ear into a silk purse", before we determine that in some cases, unfortunately, that just won't be possible.
That's when the real challenge begins. Given the strategic positioning that was anticipated from a deal, simply coming back with a "no" answer is insufficient; one needs another alternative. However, the skills and budget to craft that alternative are often not within the scope of the "deal project".
I wonder, is that what makes this such a difficult decision? It can seem like a decision to "give up", which has a distinctly negative feeling.
Find out who you should be spending your IT budget with
Bailing out before you start
An early, but informed, decision "to give up" will save a lot of money and demotivational frustration and waste of resources further a long the line. It's an important decision, which can turn a business around on the longer term, by re-shaping the focus and resources on other more fruitful ideas who's been queing up in the potential projects pipe-line. It's an evolutionary principle, proven successful in life and nature for millions of years, thus we should learn and master this also with a project analysis background.
It will only be suggested (or in the worse case only silently understood amongst the "knowers" without anyone daring to dissapoint stakeholders, if the business project owners are relatively newcomers to IT projects) by the bold, brave and experienced key project/IT Specialist member.
It's understandable that you can grow fond of your project, and thus get almost emotionally and stubbornly attached to see it through. Therefore its even more important to also analyse and conclude the risks, costs, delays, loss of benefits/strategic win potential at the same time as making the final "bailing out" decision.
Posted by Jan K. on Wednesday, June 04 2008 05:25 PM