Last week I was at the supermarket in the very long queue at the “12 items or less” checkout station, when I glanced over at the adjacent self-checkout station. The store had installed it a few months ago but I (and most other shoppers) had never tried it – thinking it looked a bit confusing and not worth the hassle of learning how it worked, perhaps due to fear of not picking up quickly enough on how to use it. But the queue was so much shorter there, so I decided to try it. Although there was a learning curve to understand the process, for example to follow the on-screen instructions and to also get the knack of scanning barcodes properly, it wasn’t as bad as I thought. I’ll definitely use the self-checkout again.
While performing the recent seven day challenge of climbing Mount Kilimanjaro, there was time during the daily six – eight hours of walking to reflect on various subjects of life. On one of these days I was struck by the strong parallels between “Team SYSPRO” and “Team Kili” as we affectionately called it.
I recently upgraded my cell phone (or mobile phone, for some people). I used to have a feature phone, but the opportunity arose for me to change to a new phone that runs the Windows Phone 7.5 (aka Mango) operating system. Getting used to the physical phone, from one with real keys to one with a keyboard display, wasn’t the biggest adjustment – but getting used to the new way of doing things, actually doing everything, was an enormous challenge for me. In tech speak it’s called changing the UX (user experience). The last time I had such a challenge was moving from a DOS-based PC to one running the first version of Windows.
The other week my family banished me to the attic with instructions to get rid of all the stuff I had put up there “that might be useful one day.” I soon found myself sitting amidst piles of cardboard boxes reminiscing about school days and my early career in the computer industry. I even found my old beer mat collection from the ’70s!
Selecting a project team for your Enterprise Resource Planning (ERP) implementation is all too often done on the basis of job role, rather than who is best for the project. What actually makes a good ERP team player? In my opinion there are four requirements: competency, skill, knowledge, and position – in that order.
Ownership of an Enterprise Resource Planning (ERP) system is much more than the signing of a contract at the time of purchase. In order to deliver value it must be the consequence of a long term strategy of ownership, and that means a long term commitment to data integrity, solution design and education.
Part 1: Building a house on a solid foundation
You can hardly miss it these days: questions about why Enterprise Resource Planning (ERP) projects hit problems, or worse, fail, appear on so many websites. I have seen many ERP implementations and thought I had some answers, but it was only after I had been involved in building a house that I could see the similarities between building projects and ERP implementations, and why we don’t see buildings collapsing in the same ways some ERP projects fail.