Confessions of a Failed Man
I was ignorant.
And to make a long story short – I utterly failed. In my naivety, I contacted IT who showed me a selection of the best software tools in the world. I spent a ton of money, I spent years of company resources, and yet I never finalized and delivered what the business users really wanted.
But I also learned a lot from my mistakes. If you, too, are embarking on a business solution project, there is a big journey ahead of you to turn “software” or a “technology tool” into a Business Solution.
Here, I bare my soul and share the first five insights that might help you in your upcoming BI investment decision.
- Lesson 1: You don’t know what you want.
The problem is that the person who is buying the solution (you) does not know exactly what all you will need before you are deep into the project and implementing a tool. And invariably, you must find a workaround because you chose a solution that won’t do what you need it to do. Lesson Learned: Choose software that is flexible, without programming.
- Lesson 2: The devil is in the details.
How mature is the product you are evaluating? How flexible is it? Instead of trying to look at features and functions, run through one of your business scenarios and check out the level of realistic details that the solution you are evaluating can support.
- Lesson 3: How rich in functionality is the tool?
Since you haven’t purchased and implemented such tools before, you can’t be 100% sure what to ask for nor do you know which functionality will make your life easy or what can turn it into a nightmare. Because I had to start from a blank sheet of paper, I’ve since collected requirements from hundreds of tenders and RFPs into a software selection guide. See here.
- Lesson 4: How agile is it?
In a fast-moving world where business is changing constantly, you need to check out the solution’s agility. How easy is it to change, what are the impact of the changes, who can do the changes and where are the changes made? Challenge the vendor on this! Business is always changing. You don’t want to have to wait for IT to re-code something to support your rapidly changing business.
- Lesson 5: How does it handle exceptions?
Business is full of exceptions. Does this sound familiar: “For this KPI all units should be aggregated except this one.” Or…” all should business units should have automatic status lights based on a formula except this unit, which is the corporate staff.” A business is full of these exceptions and your software solution should be able to handle that. Most software implementations experience 80% of the total cost arising from exception handling. Check out how exceptions are managed in the solution you are evaluating: Does it require programming or can the software handle it “out of the box”?
I’ll share the remaining 5 lessons learned in my next blog…stay tuned!