Artofpm reviews: B&A and MSDN

Still seeing some reviews come in which I’m grateful for, 5 months after the book has been out. Most folks don’t know it but the window for books is small: if it’s not picked up in reviews soon after publication, odds are slim anyone will ever even hear about it.

My own interests aside, any time you write a blog post or amazon review for a book, it makes a huge difference to us authors. Even if sales don’t follow, it’s super validating to any author to hear the book meant something to someone. I hope to write more book reviews myself here.

MSDN Magazine had a short review of artofpm:

Scott gives you project management concepts in simple steps, using lots of examples of successes and failures from his own experiences, and he is always considering the “people” factor. With all the emphasis on tools and process that we have today, it’s refreshing to see a book on project management that spends as much time on human factors as it does on technical tools and metrics.

This book is a candid and honest piece of work written by someone who has really been there, done that, and is willing to share.

Boxes and arrows, a webzine about information architecture and UX, had this review:

This is a comprehensive, how-to book devoid of jargon and theory. The author gives direct advice from his own experience. The real value of this book, though, is that it is not about a single methodology for project management, nor is it just for project managers. Instead, Berkun is able to speak about project management at its highest-level without filtering it through a given approach. It is deep enough to keep seasoned project managers reading, but also appealing to non-project managers. I’d recommend this book to anyone looking to improve general project skills.

Free UI reviews: World usability day tommorow

World usability day

Tommorow is the first annual world usability day. Free events all over the world are taking place to promote ease of use and good design in everything.

I’m surprised not to see more events in the SF Bay area or Seattle (Nothing at Microsoft, Amazon.com, Zaaz, Blink, Real, Saltmine, Adobe ?) so I’ll do my part:

I’ll do 100% free expert reviews of the first 3 websites people submit in comments (I will likely do many more but I can only promise 3). It can be your website, your company’s, a site you use or something you think would be interesting (or entertaining) to have me critique.

Update: About ten in already but do keep them coming. I will do as many of these as I can tommorow and more over the next week. It’s not too late.

The data death spiral

Whenever data is misused as the only means for making decisions, a death spiral begins. Blind faith in data creates a false confidence that overwhelms reason. Decision makers forget their wisdom and wait for numbers, fueling an addiction to unnecessary, biased and distracting data. Cowardly decision makers thrive in unnecessary information, their fears can hide there, and the data can be used to the wise with blankets of endless numbers and facts of dubious value.

Data can be good: it can dispels ignorance and raises questions. But data doesn’t make decisions or find good ideas: people do. As soon as you discount people in the name of data, the downward spiral begins.

You know you’re in a data death spiral if:

  1. Confusion over what the hard part is. If you are working on anything challenging, data will only define the landscape. It won’t dictate a particular strategy: good data has different interpretations. If you present data to justify a decision you are emphasizing some data over others: which is an act of creativity and opinion, not fact and figure. Opinion is everywhere and is most dangerous when it’s hiding behind spreadsheets.
  2. No opinions are considered without data. Opinions are good if they come from smart thoughtful experts. If you are in a world where you, as an expert, can’t make obvious improvements without 10 pages of supporting material, guess what happens? Nothing happens. People spend all their time defending the obvious and the scale of work, and the energy to improve, drops dramatically.
  3. Creatives are hiding in the corner. Good designers and creatives know how to make things. Lots of things. They experiment and explore. When used properly they are a piston of progress. But if the landscape is data and analysis obsessed, creative types are relegated to refinement work, the least leveraged use of their talents. The team gets a fraction of their possible value.
  4. No one questions data. Not all data is the same. To collapse data down into “70% of our customers prefer green” requires several layers of simplification of the truth. Which customers? What alternatives were they shown (were there just 5 kinds of green)? How many customers were there? If no one every questions the data and understands its nuances the gates are open for people to throw more misinterpreted data at each other. You need data quality not just data volume.

Death spiral
How death spirals start

The spiral begins with ignorance. Leaders confuse the collection of research with thought. People who throw more data (not better) at problems are rewarded and others follow. Soon no idea can be suggested without a data armory. Meetings are data battlegrounds. Or worse, data massacres. When someone says “Morale is low. People are crying in the halls. We must do something.” another says “but where is your data?” and the conversation ends.

As the spiral bottoms out, people are proud of numbers and slide decks: not the results.

Steps to preventing death spirals

  1. Separate good data from bad. Good data self describes its biases. A smart person uses data with consideration for what things the data can’t tell you, and they include this understanding in their story. Encourage people to play devil’s advocate on their data and make data inquiry part of the discussion any time data is presented. Diffuse data obsession.
  2. Data and ideas are partners. Make sure developments happen both ways: ideas that are pulled out from data, and ideas that come from minds, with supporting data found later. At its best it’s an itterative process: you have ideas, you research data, you refine ideas, you research more, etc.
  3. Instincts matter. The Gladwell book Blink explores how our instincts serve us: are the instincts of your group serving you? Layers of process and data bury our hearts. Some people have better instincts about certain decisions and you want to harness that talent, not dilute it. It can be fine to say “Fred has the best perspective on this. It’s his decision.” And allow Fred to define how much or how little research is needed.
  4. Let go of the fear. Many people collect data to defend their choices should things go wrong. When bad things happen they point to the data and say “See! We did the right thing!” despite the results. This kind of paranoid, self-protective thinking weighs on a team: instead of ensuring success, people are protecting their asses. Most of us can smell it when a leader is in this mode and it puts the entire project on its heels. Insurance is for the birds: A good manager earns the trust of his team and lets them know that even in failure, he’ll take responsibility for what was done.
  5. Kill contrived group think meetings. Data obsession and consensus-driven teams go hand in hand. It’s on big, cowardly teams with leaders who demand everyone agree before decisions are made that people show up armed to the teeth with handouts and marathon presentations. Not everyone needs to agree to everything. Define who is in the best position to decide and give them the power. If necessary, pick a handful of people who disagree to go off and fight it out in private, reporting back when a decision has been made.
  6. People are better than data. Much of a person’s talent is difficult to capture in numbers. Their experiences, instincts and passions all factor into what makes them good at what they do. As a manager, I want to make sure I have channels open to these assets, channels that don’t require the same kind of data in order for me to listen. If I shut these things out, I’m denying myself the benefits of true expertise. If I’m working on something hard, and with tight deadlines, the more good decisions I can have my team make without days of research, the better off our team will be.

See also: