anxiety

Here’s one for a rainy Monday morning. 37signals’ experimental 4-day working week is going very well.

When I first compared this enlightened approach to people-management with the drive-them-harder style of Jason Calacanis, it triggered a massive debate, and I wrote a follow-up comparing the Calacanis approach to an evil cult. Last week 37signals reckoned that urgency is poisonous.

One thing I’ve come to realize is that urgency is overrated. In fact, I’ve come to believe urgency is poisonous. Urgency may get things done a few days sooner, but what does it cost in morale? Few things burn morale like urgency. Urgency is acidic.

Emergency is the only urgency. Almost anything else can wait a few days. It’s OK. There are exceptions (a trade show, a conference), but those are rare.

When a few days extra turns into a few weeks extra then there’s a problem, but what really has to be done by Friday that can’t wait for Monday or Tuesday? If your deliveries are that critical to the hour or day, maybe you’re setting up false priorities and dangerous expectations.

If you’re a just-in-time provider of industry parts then precise deadlines and deliveries may be required, but in the software industry urgency is self-imposed and morale-busting. If stress is a weed, urgency is the seed. Don’t plant it if you can help it.

I can’t agree more. A client phoned once, all a’fluster about an “emergency”. Before I could think, I blurted out the question, “Why? Whose life is in peril?”

Of course no-one was in danger. This client was operating in crisis mode, as usual: that anti-pattern also known as “firefighting mode”: “Dealing with things only when they become a crisis, with the result that everything becomes a crisis.” I’ve written about that before here and with my colleague Zern Liew.

Oh, I get it. Social media “guru” Laurel Papworth has to kill time before her Saudi trip gets sorted out. So what does this visionary of society’s future do? She ropes me into a blogging meme. How modern. How avant garde!

How… 2005.

Laurel was tagged three months ago and is only getting to it now. And they’re not even real ropes!

Is that enough slagging-off? Shall I get on with it now?

Actually this will be fun on a Saturday morning. It’s been ages since I’ve done one of these. Here goes…

Read the rest of this entry »

My notebook is full of references to the human mind.

Once, on a Saturday Night at The Duke last year, it was a written note by a chap who’d only just been released from jail.

This time (pictured) it’s ’Pong explaining certain basic neurological reflexes.

No, it doesn’t say “Eight High Freeze” — whatever that is! — but “Fight Fligh[t] Freeze”. This diagram explains it all, neurochemistry and everything. Uhuh.

I just love the way that sketched explanations only make sense at the precise moment they’re being created.

Maybe I should go back through that notebook…

It was Oscar Wilde or G B Shaw or — oh, somebody interesting — who, when accused of shocking people, replied to the effect that people should be shocked a good deal more often. Or offended. Anyway, I can’t find the right quote so here’s a different one.

I never travel without my diary. One should always have something sensational to read in the train.

That’s Wilde.

Yesterday we ruffled a client’s feathers. We were invited to tender for a web development project. Our response was, in essence, “Yeah we’re interested — but not if you’re going to do it that way. We don’t think that’ll work because [reasons]. We strongly recommend doing it [some other way]. Before we go any further, is it cool for us to tender that way, knowing that’s not what you asked for? Oh, and here’s the keys to our intranet, so you can see the dialog which led to this conclusion.”

Bang!

Someone’s worldview was gunned down ruthlessly! Politely, but we did use phrases like “high-risk death march”.

Now I should say that one of us worked with this client for almost a decade and the other has worked with them on two projects in the last year. So our comments were based on some knowledge of the organisation and its needs as well as our own professional opinions. Nevertheless, what we said was shocking.

I’ve always wondered why clear, direct communication is so rare in business. People seem almost afraid to say what they mean. “Don’t upset the client!” So a recommendation like “Process A is dangerous and you should change that immediately or risk almost certain failure” becomes a mealy-mouthed “Is everyone happy with the assumptions relating to Process A?”

All urgency is drained away. The project continues flying serenely towards the looming mountain.

But don’t upset the client.

If your recommendation is for major change, when do you broach the subject? Sign up to the “wrong” concept of the project and then try to change it? Leave it until people have spent more time going down the wrong path, and the deadline is closer? No, something so important should be communicated as soon as possible.

Organisations aren’t used to people speaking quite so directly. When it happens, it’s like a splash of iced water into the face. And sometimes, that splash into alertness is precisely what’s needed.