My work life has been closely tied to Cisco’s success over the last 15 years and “Uncle” John Chambers has been my constant companion in that journey. Now that he has moved on to Chairman of the Board it is time to talk career tips that I learned from the master.
A common complaint about vendor certifications is that they don’t prepare you for the real world. Well of course not. Neither did high school or college. And thinking about it, my University education wasn’t much better.
I’m often involved in decisions, either on my own or as part of the team or providing information to someone else. When researching a product or a technology, I try to be conscious of how I perceive problems, how I react to the data I have available or whether I have the right data. I consider whether my current frame of mind is positive or negative, am I tired. Did some person from a particular company make me angry, or excite me ? Does this affect my perception of a vendor or their product ?
I’ve been asked a few times about how I organise my PDF files and keep track of documents. This post looks at my workflow for capturing, storing, tagging and organising my Knowledge Management system. This is Part 2
A few times I’ve mentioned about how I manage collections of PDF documents, Text files and the accreted detritus of a Network Engineer. Since a number of people have asked me to talk in more detail about how I organise this and what methods I use, here is some rough description of how I perform knowledge management.
A reader wrote asking about whether share options are a good bet. Answer: Only if you think winning the lottery is realistically possible.
One of the problems of working with the PRINCE2 practitioners is that the people tend to get highly focussed on definitions in the Scope of Works. A Scope of Works defines what the deliverables the customer is to received.
The problem with a Scope of Works is that it is usually prepared before the work is started and/or fully understood. maybe you have a Gap Analysis, or a Consulting Reports or a Requirements Document to setup the initial engagement (every company has their own name of the same thing).
Over the years, I’ve had many CIO/CTO deliver the news that the company plans to have twenty percent growth for the next five years. I’ve often noticed that most people in IT Infrastructure don’t find this staggering. I find it hard to believe that many people just blindly accept this and fail to make the differences when planning.