The Expert-N-Speak Says

The expert says no way! The cow says moo.

“The sun revolves around the earth” – A whole bunch of medieval theologians, scientists, and 18% of Americans in 2005

“…The automobile is only a novelty…” – President of the Michigan Savings Bank advising Horace Rackham (Henry Ford’s lawyer) not to invest in the Ford Motor Company in 1903.

“Heavier-than-air flying machines are impossible.” – Lord Kelvin, president, Royal Society, 1895.

“Who the hell wants to hear actors talk?” – H. M. Warner, Warner Brothers, 1927.

“There is no reason anyone would want a computer in their home.” – Ken Olson, President, Chairman and Founder of Digital Equipment Co. 1977

Operator, can you help me place this call

I’ve always been pretty fascinated by the allegory within the Genesis story the Tower of Babel, particularly the confusion/division of human language.

I think it’s because I’ve always been fascinated by the human challenge of communication – and why something so seemingly simple and so core to the human experience, seem so incredibly difficult. Especially in the workplace.

I have never researched or studied much in the way of what scholars have to say about the subject – or business experts, I’ve just observed, contemplated, praised, opined, complained about the nature of communication of groups and larger organizations that I’ve been in.

Every larger organization that I’ve been a part of had what everyone terms a “communication problem” of some kind. Every larger organization that I’ve been a part of has had a situation where they acknowledge the problems/challenges/opportunities – and they’ll talk about working on it, doubling efforts, forming focus groups, task forces, tiger teams, etc. to study the problem, make recommendations, write reports whatever. And sometimes it changes, but normally it doesn’t. It’s just an endemic thing that happens with groups and communication.

I’d like to tell you I know how to solve communication problems in organizations. That I know some fundamental secrets to getting information flowing. I’d like to tell you, but I can’t – because honestly I haven’t the faintest clue how you solve problems with two different people walking away from a conversation with two completely different interpretations of what just was said. I don’t have the faintest clue about how you solve the “signal degradation” as the report of a conversation goes from person to person to person. Or the problem of custom vocabularies between teams and the use of the same words that mean different things. Or issues of pride and fear, where people will just stay quiet on unclear points to avoid looking like they don’t know things. Or any of the dozens of other communication challenges between folks. I know how it happens, I usually recognize it. But I can’t solve it, or tell you how. (and frankly the people that tell you they can are delusional at best, liars at worst). At best, there are mitigation strategies, but there’s not much in the way of solutions. It’s a human thing. It’s why every culture has some variant of a “Tower of Babel.”

I can tell you though, that if you can’t even get to those problems, you can’t get through those problems. If you aren’t talking in the first place, you can’t even begin to have all those vocabulary and interpretation issues.

I do have one secret. One management-consulting-like little mantra that gets to the heart of at least one of the fundamental problems. Of course it’s an over simplification of a complex problem. But that’s how we roll in the workplace.

Here’s the personal form:

Ask Questions, Give Answers

Here’s one for you leaders:

Expect Questions, Expect Answers

Here’s really what it boils down to:

Never leave a question unanswered.

Here’s an expanded version of the above:

Never, ever, ever, ever leave a question unanswered. I don’t care how long it takes. I don’t give a flying damn how stupid the question is. I don’t care how many times it has been asked. I don’t care how many times it has been asked by the same person. I don’t care how much it ticks you off that you are being questioned. Go ahead and send the missive around to your peers that “OMG I CAN’T BELIEVE THAT QUESTION WAS ASKED AGAIN” Just answer the damn question. Period. End of Story. (p.s. “I don’t know” is an acceptable answer. “Because I said so” is not. Unless the questioner is 5 years old and only if they are asking why they can’t go to chuck-e-cheese for dinner for the 4th night in a row.)

Pretty much every successful communication exchange is about a question and an answer. But it’s not going to be successful if the question isn’t asked. And it’s sure not going to be successful if the answer isn’t given. I have seen over and over and over again that the questions don’t get asked. Or when they do, the questions are ignored. And worse, the questioner is treated like a pariah, and the flipside, the answer isn’t heard, or respected.

If your first response to all this is that I’m over-simplifying the issue – you’re right. And if you know me, I’m sure you can point out multiple times with me where I get annoyed as hell about being asked, or I give some gruff response about looking it up yourself. “Black” said the pot to the kettle.

But I do hope that you’ll have to look pretty hard for a time when I was responsible for being the person that gave the answer, that I didn’t give an answer (and in the process answered 50 other questions that you never had) And if I didn’t, or didn’t for a long time, where I didn’t apologize profusely for not doing so. It’s just something that’s pretty important to me, and it’s something I’ve found to be successful for making sure information is out there.

There’s a lot of other things you might be thinking. One I’ve run into a lot with leaders is that you might be thinking to yourself about that guy that you have in the group over in the corner, that you are completely afraid of your boss’s boss’s boss walking in because he’s going to ask some embarrassing question about some little minute detail that you think is too trivial to be asked. In that case you have a problem. No, not in your group. You have a problem. Your boss’s boss’s boss should know how to deal. And if they have a clue – they’ll say “I don’t know. But that’s a good question, I’ll get back to you on that, or make sure that someone does”

I’m not going to say that that you won’t have someone that does that. Especially if you are encouraging questions in your team. And you yourself are giving answers and asking questions. That’s life. There are ways to deal with that. But ignoring it isn’t one of them. When the answers stop, the questions stop, and when both stop, communication stops. And that’s the problem.

I’m not going to say that this isn’t a hard and time consuming thing to do. Answering some of the questions will take a tremendous amount of time and effort. Sometimes it’s hard, mainly because the questions themselves can require us to think and deal with things that we’d rather not.

But what things in life that are worth doing are easy or simple? Not many.

Ask Questions. Give Answers

You’ll be amazed how much the communication in your organization, your group, your team, maybe even your life improves.

There’s just life

One of my favorite movies of all time is Tombstone. It’s a somewhat rare genre for me to favorite, the story is not all that great, and story is what really drives me the most when it comes to movies. However, as “epic Western” it’s great.

There’s a quote from the movie that always been one of my favorite movie quotes. Doc Holiday asks Wyatt Earp “What did you want?” and Wyatt answers “Just to live a normal life” Doc responds:

There’s no normal life, Wyatt. There’s just life. You get on with it

That quote has stuck with me for a long, long, time. And I could use that particular quote to cover a multitude of topics about how we interact, how we come of age, answers that we seek in ourselves and others.

But one thing I want to apply it directly to is an ongoing misconception of the ways in which we act “online” and “offline.” Those still struggling with the changes in information dissemination and interaction that have happened with technology-mediated communication have an ongoing lament that somehow this communication is “less informed”, “less valuable”, “less real”. In fact, even those of us that have “grown into” the “online” (technology-mediated communication) world even tend to use language that excuses this, often calling that “offline” space “the real world” – as if “online” is something other than real.

Thankfully, those that have “grown up with” technology as opposed to “grown into it” don’t usually make this excuse. “Thankfully” because the future belongs to them.

The lament, of course, is foolish. Technology-mediated communication is different. As was television different than radio. And radio different than newspapers. And the telephone different than letters and hitching up the horse and buggy to drive into town. Which is of course different than marauding armies conquering nearby villages. I can carry the metaphor into all kinds of human history. But all that difference is really just different shapes and colors on top the same base way we all communicate. And as with all the methods in which human beings communicate, each carries with it benefits and drawbacks – mostly though, those don’t really matter much. Most adapt, and some lament. And that lament really is ignorance and/or prejudice and/or fear. All of which we humans are really good at when it comes to “different”.

And that’s where the words of the Tombstone Doc Holliday come back again. There is no normal life.

There’s just life.

Get on with it.

Creating your own Gem Server, redux

One of the most popular landing pages for (which isn’t saying much) – is a post I put together in April, 2007 about running your own gem server.

Unfortunately it’s outdated. Set let me revisit it for those landing on the old page and looking to put together their own gem server. The nice thing is, gem has (almost) all the tools you need.

Setting up your server

  1. You need a web server. (yes I know you can run gem_server, but get a real one). You are on your own for that one. You also need a rubygems install on that box. You are also on your own for bootstrapping rubygems on that box and any other ones.
  2. Decide where you will put your gems (say in a “mycoolgems” directory off the docroot for your webserver)
  3. $ mkdir [docroot]/mycoolgems/gems
  4. Copy your .gem files that you want to host to $ [docroot]/mycoolgems/gems
  5. The gem suite of commands includes a generate_index command to generate a yaml-based index of your gems, and other supporting files. See gem help generate_index for more information

Pointing your systems to your own server

This used to be a complete PITA that involved rebuilding the sources gem. No more! After you install rubygems – just make sure to do a:

gem sources --remove

and a

gem sources --add http://yourwaycool.gem.source

That’s All Folks (probably)

Voila! You just managed to point your server to your own gem server! Install away.

It’s good to keep one box pointed to – and take advantage of the new “gem outdated” command to keep track of changes in your installed gems that have been deployed to rubyforge.