In innovation, you aim to introduce something new; make changes in anything established. You could go right or could go wrong. Of course you do all preparations necessary to go right every time, but if you don’t, you take the lessons learned and be better next time.
Romeo Siquijor is a good friend and compatriot. He now heads Information Security in CEMEX in Mexico while I found my way to Houston after several stints in different countries. We both started as young IT managers in the Philippines. Our offices were adjacent. The thing I remember most was Romeo repeatedly telling his IT Operations team that “failure is not an option” — like it was their mantra. I did not disagree with him, but it was not the same message I would tell my team.
I headed the IT Business Processes group at that time. My department’s task was to enable and support IT solutions. For us, the mandate was to find new ways to do things, to innovate, and to test new tools with potential application to our business processes. Of course, I wanted my team to succeed but on the other hand, I did not want to have the fear of failure limit their quest for new things. I believe that sometimes the cost of finding innovation is failure – finding out what does not work on your way to finding out what does.
While working with our commercial department, we implemented a sales automation tool using handheld devices. Unfortunately, it did not fly when we piloted the project and we failed. We did not get the buy in because the tool was not user-friendly and robust. The sales managers simply did not use it. We explored another innovation we called mobile selling. Romeo helped design a simple technical architecture to run it. At the time, in 2003, text messaging or SMS was already big in the Philippines. It was a phenomenon and the use of it quickly became part of our culture. Our goal was to incorporate the use of texting to our sales process. We developed a tool that would allow our customers to request orders using SMS and they did just that. In just a few months, 60% of our sales orders were coming from our mobile channel. We were open to exploiting the best technology at that time by applying it to our sales process but we were not sure how our customers will react. We were willing to fail and so we took a risk and gave it our best shot.
When mobile selling was already operating, it became a mission critical application. The system was hosted by the IT infrastructure that my friend Romeo manages. In that perspective, I loved it when he told folks “failure is not an option.” I did not want any service interruptions to impact my mission critical applications. Romeo values productivity, availability and reliability. He wanted no failure and no surprises. He wanted things done yesterday, done better, faster and cheaper today.
My goal is to show you two different perspectives from two different functions in IT. “Failure is not an option” is a good mindset for day-to-day IT service delivery. Although, I would argue that this does not apply to areas whose mandate is to innovate. In innovation, you aim to introduce something new; make changes in anything established. You could go right or could go wrong. Of course you do all preparations necessary to go right every time, but if you don’t, you take the lessons learned and be better next time.
2 thoughts on “When Failure Is Or Not an Option”
Brings back the old days!!! My first day of work, i already heard Rom telling the DC operators this mantra 🙂 learned a lot from you both. Today, i’d still tell myself failure is the last resort
i remember…… even got a nasa lanyard saying “failure is not an option’……