Twitter beyond the Tornado?

Every once in a while, I get delusions of grandeur and think I can understand the world.
Given the latest major pieces of news about Twitter, I get the impression it’s that time again.

The other day, I was studying “Inside the Tornado” once again. (See Inside the Tornado: Strategies for Developing, Leveraging, and Surviving Hypergrowth Markets)

With that fresh in my mind, latest news about Twitter seem to ring a bell…

Continue reading Twitter beyond the Tornado?

by-nc-nd

Motivation 2.0: Daniel Pink on the surprising science of motivation

The other day, a friend of mine recommended another TED-Video to me: “Daniel Pink on the surprising science of motivation” (~18 Minutes). I think everybody who’s into management and/or leadership should have seen it.

It’s clearly worth watching, because Daniel is a truly gifted speaker. Still, for the hurried reader, here are the core points as I picked them up. The main theme is

There’s a gap between what science knows and what business does.

What he’s referring to is the “candle problem“: A cognitive performance test dating back to 1945. This test and a range of other examples Daniel quotes clearly shows that “sticks and carrots” (aka incentive plans etc.) actually reduce performance in cognitive tasks.

Incentives do work for mechanical tasks (which were predominant through much of the 20th century). They do not work for cognitive tasks, which dominate the 21st century. That’s the gap Daniel is talking about, and I’d like to add that this especially applies to the business of software

While science knows for more than 60 years that a bonus plan, say, for managers, reduces effectiveness, businesses reach out to higher and higher incentives in the areas where they are known to work least. One could say: They don’t know better. How else to motivate people?

And Daniel has an answer to that question: Purpose, Autonomy and Mastery.

In the video, he goes on to explain purpose – the topic in its entirety is covered in Pink’s book, Drive: The Surprising Truth About What Motivates Us.

Since then, I keep asking myself: Do you create a sense of purpose in the people you are working with?

by-nc-nd

Lost+Found quote: “What’s going on in the project” (Ward Cunningham)

For questions like, “What’s going on in the project,” we could design a database. But whatever fields we put in the database would turn out to be what’s not important about what’s going on in the project. What’s important about the project is the stuff that you don’t anticipate.

(Ward Cunningham, founder of the first Wiki)
Found at artima developer: “Exploring with Wiki” – A Conversation with Ward Cunningham, by Bill Venners;
October 20, 2003

by-nc-nd

Everybody, Somebody, Nobody. Anybody?

Anybody, Nobody, Everybody, Somebody: A picture called "Nobody's portrait" - a face with glasses, without hair, eyes, nose or mouth. Who is it? - Nobody...I think everybody knows the following story. Still, it has turned out both fun and useful for me. Regularly. 🙂

This is a story about four people: Everybody,
Somebody, Anybody, and Nobody. There was this
important job to be done and everybody was asked
to do it. Everybody was sure that somebody would
do it. Anybody could have done it, but nobody did
it. Somebody got angry about that because it was
everybody’s job. Everybody thought that anybody
could do it, but nobody realized that everybody
wouldn’t do it. It ended up that everybody blamed
somebody when actually nobody asked anybody.

Image: Flickr / нσвσ

by-nc-nd

Image and Reality

La Trahision des Images
The Treachery of Images as an example for the mis-match between the actual staus and the reflection of the status.
One frequent mishap in larger organizations is exaggerated confidence in KPIs.

It is interesting to note that the literature on management, spends little to no attention on the accuracy of the measurement, while the literature on leadership barely mentions such KPIs at all. When discussing topics that are easy to measure, like manufacturing, taking the accuracy of KPI measurements for granted may make sense – however, the business of software is so far largely resisting meaningful, repeatable measurement. KPIs are so important because, often, KPIs are tied to people’s bonuses, which immediately invites, encourages … tuning of KPI actuals.
Continue reading Image and Reality

by-nc-nd

Anecdotes for Project Managers: Cargo Cult

Another anecdote that is really working miracles is Richard Feynman’s story about Cargo Cult. I have to admit that I’m telling my own version. I’ve researched it on my own and massaged it a little bit to focus on the point I’m trying to make.

The situation where this anecdote works best is at milestone meetings, at larger companies: large companies have processes, even for project management. Project management processes typically focus on special milestones with special deliverables and a range of bored senior managers who have to take the decision.

The other day, I started one such meeting by telling the following story:
Continue reading Anecdotes for Project Managers: Cargo Cult

by-nc-nd

HDWKTWD – a User Story for Tasks

Have you ever experienced that a task has been agreed, and half-way through somebody comes back beaming with the statement “it’s done!”?

Every once in a while, this happens, and it happens more often in distributed teams than in localized ones. The point is: there was no real agreement about when the task is done. I’ve started a new experiment in my teams, I’m starting to add to every task a little “HDWKTWD” section.

What’s “HDWKTWD”? – It’s short for “How Do We Know That We’re Done”. A good task assignment already does that implicitly (compare “discuss the schedule for XYZ” to “agree on a schedule and inform everybody in an email.”), but sometimes it helps to be even more explicit 🙂

User stories deal with the user observable behavior of a system. Who says that this characterization of user stories should apply purely to programming? The trick is: If I’d make a movie – would an outsider be able to judge whether the goal has been reached or not?

In the example: “discuss the schedule”, everybody would be able to see that a discussion has happened – but that’s not the desired outcome. The desired outcome is an agreement. However, the agreement is not visible to an outsider until it’s documented in an email. Hence the re-worded HDWKTWD…

My first impression is that “user observable behavior” ‘s doing good for project management, too.

by-nc-nd

Decision Analysis III

It’s already a while ago that I presented my Influence Diagram to our sponsors (one may remember the Decision Analysis II article). The main value of the presentation was – as so often – in its preparation:

  • I’ve had my own mind clear on what I suggest and why
  • In the preparation meetings, peers and sponsors had to wrap their head around the entire topic.

So, eventually we had an engaged discussion about a situation most people had pretty well understood. While we didn’t really go through the presentation, we still arrived at – from my point of view – the right conclusions.

And a few days after the meetings, I received an email with four words: “good meeting – unlike most”.

It works.

by-nc-nd

The Essence of Making Software