« Technology vs. Culture | Main | The Secret Life of Scope Cuts »

Saturday, May 07, 2005



Another way to look at it (inverted) is "if everyone knows what you do," then you do commodity work. "I work at Target, I teach biology, I drive a bus, I prepare taxes."

If it takes some explination, "I manage cost and schedule for low earth orbit space vehicles" then it is likely not everyone is doing this. Unless of course you're in a crowd of local aerospace employees.

In our neighborhood some responses than answer both include, "I work at IBM Global Services," "I work for Lockheed," "I'm a professor at CU." It broadens the "do" part while positioning the work in a general area - not too technical, not too vague.


By the time they came to use they had already purchased the software. They came to us to help them deploy it so we did out best to make sure that they addressed the cultural and process issues that the Sig, Hugh, MarkN conversation brings up. I had a post here about that conversation as well. We tried to make sure that while they were deploying the software that they were addressing the larger process issues.

PS - I'm in software development, and I can't even explain what I do to my wife, let alone the neighbours!

"They think the problem is that they don't have good PM software tools" ... so do you sell them the PM tool they can't use, or give them the advice about how to set up a PM mindset so that the tool becomes useful? The answer to this question harks back to the conversations with Hugh, Sig, MarkN and Rockster about trust/integrity/transparency. In the longer term is it more valuable to 'give away' the advice in return for a deeper trusting relationship, or sell them the product that probably becomes shelfware?

The comments to this entry are closed.