Tag Archives: Cisco

Why Can’t You Learn, Old Dog?

I am both amazed and highly disappointed at the number of people who believe the ability of colleagues to talk to each other via a tool that is either fairly ephemeral and basic (e.g. MS Communicator) or more persistent and inclusive (e.g. MS Yammer or Cisco Jabber) is a waste of their time. One of my least favorite things to hear is “I’m too busy to learn how to do that” or “I don’t have the time to waste on these things.”

Tin Can Phone

How can I help you?


“These things” are designed to improve our ability to share what we know and to find out what others know; not as a lark or just because, but in support of the work we do every day. How often have you remembered there’s some information that’s available to help you out, but you can’t quite recall where you last saw it or who told you about it? Imagine being able to essentially broadcast a question and have it reach dozens or more people, any one of whom might be able to answer the question for you. How is that a waste and in what way is spending 10 or 15 minutes to learn how to use a tool wasteful given how much time it can save in the long run? Even if you only saved 5 minutes per month, you’d be in the black after only a third of a year.

The business world is changing; grudgingly – at least in many places – but nevertheless changing. A long time ago one of my colleagues who had been a student of Deming’s and who was deeply involved in the understanding of systems, offered his belief that the main reason we survived as a company wasn’t so much because of how good we were at what we do. Rather, it was in large part due to the reality that everyone else was much worse. He wasn’t talking about our organization’s technical skills, but rather about our systems and procedures, most all of which exude bureaucracy from every corner.

I believed him then, and I’ve seen nothing to dissuade me from believing it still – even after a nearly five year hiatus and having been back for over six months now. I’m not sure how much longer any organization can continue doing business the way they’ve always done. I can’t possibly predict when it will be too late to change; when another business will match our technical skills and outperform our organizational skills, leaving us – eventually – in the dust.

It will undoubtedly take longer in aerospace than it would in, say consumer electronics, but even with long-term contracts and government funding there has to come a time when failure to learn and modify how things get done, especially those things that rely on people talking to and working with one another, will mark the end of an organization’s viability. I don’t dwell on it, but I do find myself occasionally listening for that other shoe to drop. You?


Just Flew In. Boy, Are My Arms Tired!

Equipping my new cubsicle

I got a phone and a Dell desktop with Windows 7 and IE . . . while I was there.

I survived my first day back on the job, reasonably intact. I knew I would get a bit of a workout just walking from my car to my desk, but I ended up walking about 3/4 of a mile and climbing around 10 flights of stairs. The first flight I climbed was a mistake. I ended up at the end of a hall where there was a secured door to a clean room. I knew that was the wrong place to be and had to turn around a go back.

I saw close to two dozen former colleagues, the majority of whom I hadn’t seen in nearly five years. Amazing how many of them remarked on how the company would let anyone back in. 😉 They know me well.

I am prepared to put up with a boatload of shit coming from what I know is a very old-fashioned aerospace enterprise, but I think it’s going to be even worse than I imagined. Not so much because of the hierarchy, the layers and layers of rules many have forgotten the origin of, or the command-and-control mentality that I know still informs the actions of many of the org’s leaders. There are other, more subtle reasons.

One of the first things I noted was everyone communicating with email; for everything. This wasn’t all that surprising, but it was a bit disconcerting to discover I had a shortcut to Cisco’s Jabber and nobody seemed to know anything about it. I have my work cut out for me. Bottom line, really, is I’m thankful for the opportunity and it couldn’t have come at a better time financially. The fact that it puts me smack dab in the middle of the struggle to be more effective as a team, a community, an organization makes this all the more sweet.

I’m going to try to share what I learn as I learn it. I hope some will find it useful. It’s possible just sharing it will improve its utility to me and, if that’s all I accomplish, I will consider the effort a success.


%d bloggers like this: