About the Author
In the beginning…
I was born and raised in
I had a quick stint at a research lab finishing my thesis project when I got a call to come and work in a giant fast food US company as their systems analyst. It went well until I finished school and they decided not to raise my pay check as promised. Soon after that, I left in protest not before making a study to show they needed three full time people for the IT department, not one part time freshman.
It was my first experience learning about what the corporate world was about. If it is not in writing you can pretend it was never said. But after sometime I met some former colleagues that told me I probably made the best decision as they recounted how the morale had gone down since then. After doubting about the decision now I felt it was the right one. That first job was in essence do-it-all kind of thing. I managed everything in Information Technology (IT). Network, computer support, email, point of sales systems, everything; I always had some taste for having a broad knowledge for technology and I was been given the chance to put it into practice. I did not know how important that would be later on.
Soon after, I was called for an opportunity to do some training courses as a consultant to an oil company -- a big one that is. I did not think too much about it, they pay was huge compared to what I was making. Months before I met a top executive at another oil company that ignited my desire to be in the oil business, so I already had my mind set into it. The project: A huge migration from Apple to PC and we were the ones training everyone in the office. I was about to witness my first large full scale IT project. That would not be very unique if I didn’t tell you the migration was for two thousand plus people in less than three months. That is an enormous undertaking for any size of company.
They trained us how to train users, and it definitely helped me tune up my presentation skills plus a little of British accent refinement. I remembered how the trainers crinched when I kept coming with “gonna” instead of going to. Now, what it really made the difference in this learning process was that they brought a professional camera guy to film us so that we could see how we looked. Some people felt they looked like clowns. In summary, it was a hard and eye opening experience. At the end, the project was a tremendous success. Soon after I was transferred to work as a support analyst and part time Webmaster. As I said, the Internet was all the rage, and the top job you could think about on an Internet environment was being a Webmaster. What I did not know was how hard it was to become one. You had to know five different programming languages, and all sorts of additional skills, as in the beginning, the Internet was a big piece of “something” putted together with duct tape (the five languages). That means a lot of things failed. So you had to be very technical, but at the same time had to know about design and building “beautiful” looking pages. It was odd to me but a great challenge.
The guy doing the Webmaster juggling decided to leave to
Meanwhile I had to deal with this tool for document management that looked pretty interesting but that I did not see much of a future in the webmaster area (How wrong I was). The tool was called Livelink. In the late 1990’s I went from webmaster into being the tech lead guy for a big time project implementing Knowledge management technology (the Livelink product I mentioned) to the entire organization. In that time, KM was unknown to many people including corporations as the Internet was all the rage and this particular oil company was arguably the leader in implementing best practices due to their operational liability issues. This was-is a big and large oil and exploration company down in
In our culture, we are kind of afraid about money matters, so it was unusual for the tech lead to come up with a 1.5 million dollar budget. Given the risks involved, I made big numbers to counter those risks. That probably saved us from a disaster. In other words, if you know you are going to fail, just make sure you fail BIG as they say in
But for some reason the top guy up there believed that I was responsible of the problems the project was having. That did not make me feel too good, so I decided to start looking for something else rather than waiting for the hammer to fall on my head. I was sure warned about it. It looked typical management stupidity where you start looking for the scapegoat (Shoot the messenger syndrome) instead of looking at how the project is structured. Luckily for me, my boss and managers from the consulting company where absolutely clear that instead of guilty I was brave enough for dealing with a crazy project like that. In the end it was straightened out by a very competent project manager—the third in a row. My first big lesson in project management: Make sure you know what you are doing, if not, bring the experts or don’t try it unless you are ready to fail.
Implementing the technology was exciting, new ways of dealing with information, figuring out how to best organize, capture, retrieve data, create workflow processes, etc. The number of things involved was growing and growing big in complexity. We were learning about the importance of interfaces, the users aspect of it, and how delicate was to migrate information from one side to another. There were unseen hidden links between groups of people that proved difficult to deal with without prior research. But again, I learned from the technical perspective as well as the business side.
After that, I’ve got an offer to come to the
Ok, so the reason the previous manager was removed, was because he did not agree on the way they wanted to move their information to this new technology. And he was probably right. But I had to do it anyway, so we went ahead and moved all files and folders into the system in less than a month. We did it, but with a lot of errors, because the tools used were not designed for that kind of massive uploading and there was no planning what so ever. Next, I found my self with another challenge; spitting out a fully detailed project plan with no lead time. I had no idea about how to come up with it because you cannot possibly foresee a plan without knowing where you are, their current state of matters, where you are going, and a team of people. In other words, you have to be there since day one as project manager to be able to figure out why, what, how, when, etc to do it and plan it right, but I did it anyway. I can think back now and tell you how crazy everything was. I do not know if heads rolled from the client stand point, but being a consultant kept you in a somewhat safe spot, at least in my case. Luckily they knew that just bringing in a new project manager and doing the same thing would not cut it; another hard lesson in the pocket but very valuable. I was sure learning the hard way how NOT to do Knowledge Management from customers and companies shooting up in the air. That was probably the time I started asking my self why they were doing it like that, and began to step back. I guess that is the way we learn about new things. We fail and fail until we learn a new way that works better.
After a couple of other small jobs 9/11 came and we got a (Sadly) 3 month vacation as everything and I mean every single project was shutdown. When I’ve got the offer for interview in New York later that year, everybody in my family had the terror look saying to me “Are you sure you want to go there?”, I thought to myself that probably the best place to be after 9/11 was precisely in NY, and there could not be any other safer place on earth.
In NY I was offered a two year contract, so we decided to move from our temporal residence in
It has been 10 years now, so let’s look at the lessons from the past and how I looked back to try finding a clear picture of what is wrong with KM and the definitions behind. Here are the lessons I’ve learned so far.