Skip to main content

To have or not to have; Why did we buy this solution?



The Roman Empire was originally poor and small, unique and austere of virtue. With time it became corrupt, spoilt and rotten from its vices. Thus, at its fall, its acts of grandeur were obscene to both man and God.  
A virtually unknown presidential aspirant in the run up to the 2013 Kenya elections, spoke in metaphor when he theorized “when you want to be healthy, eat when hungry, and when you are hungry you do not fill your belly with food, you need a third for food, a third for water and then the other third should be breathing space”.  
If you will allow me, I would like to break down this statement into something that makes sense to someone who drives information technology in any organization.
One of the conclusive declarations one can make about technology is that there is a progressive trend and “new” is always the norm, it is also a fact that what is innovative and essential today, may become defunct and unnecessary tomorrow. Having made that statement there is a caveat, not all products that come to market, manufactured by top technology companies, are necessarily critical to your organization.
Steve Jobs famously quipped that it was really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them.
The fact is, that most of the products and services brought to the marketplace have a specific niche market in mind ( I stand to be corrected by firms that don’t do market research and have a machine gun approach to product and service delivery), the bigger the product and the more expensive it is, the more constricted the market.
Given that vendors at the end of the day want to make the most money out of a product, they will milk it, cobble it with other modules, introduce superfluous features, and sell it to all and sundry who can tune in to their hallucinogenic sales pitch.
It pains me to see a big budget ERP acquired by an organization in the third world and five years later, the people on the ground don’t even understand what the solution is meant to achieve let alone even remember its name.
Before you go into a shopping spree, and I do mean the one that starts with you accepting courtesy calls from vendors who have backing from well-heeled multinational technology firms, start listening to your internal heart beat (know if you are “hungry” in the first place) appreciate the needs of your organization to a point where you can fanatically recite it as a poem. If you know your business’ ins and outs, it is probable you may find out the springs and the cogs that are miss-placed in the corporate engine.
Having said that, I have to add my voice to the stadium of people who normally throw a vendor product or service at a problem, rather than get muddy in trying to unclog the system and find a cohesive solution. It is the easiest way out.
If you take the long term route where you are fully invested in discovering your organization’s needs, challenges, or problems, more often than not you will find it is deeply seated, and your analysis will be a precursor to something bigger, take time and involve the relevant stakeholders while you are at it.  
The worst thing would be to acquire a solution that only unravels the symptoms of the problem. In all things, always review, engage and converse with the potential stakeholders, while fully appreciating the comprehensive workflows and processes that define the organization. When you arrive at a critical mass in this process, then you will have a clear picture of whether or not you need a technology to solve the issue, and when and how it can be acquired and deployed.
Never forget in all this the “Big Bang Theory”, which evolutionists claim brought about dinosaurs extinction (don’t be one). Do things gradually and in step and if the project is too big, chew what you can in bits.  
Remember, more than 20% of the solutions you find in the market today do not bring any intrinsic and specific value to your organization, even if it is being used by a Fortune 500 firm.  
Many of these solutions require you to train your people in a specific manner and the business value is lost in a clutter of business idioms like “efficiency, effectiveness and cost savings”.
I beseech you; next time you want to acquire a solution, make sure it is very clear in no uncertain terms where the efficiencies, effectiveness and cost savings come from, and this should be expressed in your organization’s language, where every stakeholder is clear on what it means to them, even before you commit to acquire any specific solution. Here, I am assuming you will have already determined your needs way in advance.
The final picture you need to have in your gallery of achievements is one where your organization has only acquired products and services that meet your specific needs and are not an attrition point for your revenues, thus avoiding the nagging and haunting question, “Why did we buy this solution?”
  
Article was done for the CIO East Africa March 2013 Issue 
@edwin_moindi

Comments

Popular posts from this blog

A Crush that Never Was, A Book Never Read

I was standing there with a rose. At least that's what Mr Patel told me it was. It was red and spiky. "Watch your hands and heart," he said. I was too flushed to say anything. The edges were wilting. I was sure I was a novice buyer for Mr Patel.     I walked into the restaurant and sat at the table closest to the door. I looked strange, a ten-year-old on a first date. My uncle had chided me for looking presentable, I wore a white shirt, trousers, socks and shoes. My nose assaulted by Brut, 'the essence of men'. So here I was nervous, and my heart pounding. This went on for a while before worry took over. "Had the girl forgotten to come? Was she held up in traffic?" Outside was a Saturday afternoon. The two streets in Nanyuki were deserted. I sighed, trying to calm down. My thoughts went back to when I had seen her. She was a new girl in our sister class, and the most beautiful person I had ever seen. Flawless dark skin, and teeth as white as dair

I Shall Live by Sight

My ears were sensitive to the noise and babel outside - loud music blaring, and cars honking. We were seated in a small room, deprived of light. There were other sounds, not as loud, of crawling creatures scurrying around. We were on the second floor of a building, that had sucked in air, to fit between other buildings that lacked a hint of design or flair in their construction. For a moment, I remembered the mason who did odd jobs at our house and wondered if he had constructed the buildings in this part of the city.   I looked outside the window, the lone window that allowed in reflected light. The lone window from which you could never see the sun, but still sense its presence. I wondered if a prisoner in solitary confinement desired the sun, the way I desired to leave that office.   Yet, we were there for a good reason. Seated beside me was my father, in a polo shirt and khaki slacks. He was relaxed and seemed oblivious of the surrounding. I looked across the tiny table. Th

The Key Heist

We all had those days, weeks, and months when something snapped, and we went a bit crazy. This is one such story I kept in the recess of my mind. I was barely ten years old.   "The phone is really nice and shiny," I said, reaching up. It was placed on a high cupboard, in a corner right outside my parent's room. It was kept there so we could also receive calls since our parents were always away working.   Unlike the one before, a quaint rotary system, this one was white and had buttons. It looked so light caged and padlocked in a metal contraption that held it down, hiding the buttons.   Big Sis was standing on a chair beside me engrossed. Her focus was on the manacles holding the phone buttons out of access. With no social media back then, and with little interest in television, Big Sis was looking at her only source of entertainment. The brightest girl in Laikipia District, based on her last award, was stumped. My eyes moved from her to the phone and wondered wha