Year: 2008

Win prizes! – Why do designers fail SURVEY

Posted on in designby Scott Berkun

After a most interesting thread and side e-mails, I’ve developed a survey to more deeply explore the reasons why designers fail. There are now over 40 specific causes offered, and I need 5 minutes of your time to better understand how these causes relate to the real world.

Details:

  • The survey is open to designers and non-designers.
  • Goal is to better understand both causes and perception of causes of failure.
  • Prizes: $100, $50 and $25 Amazon.com gift certificates.
  • Survey has 7 questions, all multiple choice, and should take less than 5 minutes
  • You can be anonymous, but it you want a shot at prizes, put in your email.
  • Results will be presented at UIE13 next week – and on this site

Act now, the survey closes EOD FRIDAY. 

Survey – Why do designers fail? [Survey CLOSED]

(Note: If you try to take the survey twice on the same computer, it wont let you. You’ll get a “Thank you for taking the survey” page).

Why do designers fail? Input wanted

Posted on in designby Scott Berkun

I’m finishing up my slides for a talk next week at UIE 13 in Cambridge, MA. The title is “Why designers fail and what to do about it”.

I’m sure there are a zillion reason’s designers, like any professionals, fail. What I’m looking for are habits you’ve identified in designers you think sets them up not to achieve what they seem to want to (making great, easy to use, things).

Here’s a sample of the long list I’ve identified:

  • Assuming other people understand design and care about good design
  • Not seeking power when power is required to deliver on an idea
  • Being shy / passing opportunities to pitch ideas
  • General incompetence (not as good at designing things as they think they are )

My goal isn’t to bash designers here, and in the talk I offer solutions & positive examples.

Instead here’s what I’m hoping for: there are many proffessional designers in the world, but not many things we can buy that are designed as well as i-phones and Porsches – why is that? How do designers fail, whether it’s their fault or not, to bring great things to the world?

I’m thinking there are 3 categories: Failures of the designer’s psychology, Failures of the designer’s skill, and failures of the organization.

Love to hear your opinions – thanks.

RSS/Feed issues: Fixed (details)

Posted on in this siteby Scott Berkun

For a few hours today my nice little RSS Feed, with close to 20k subscribers, was replaced by a pile of ads for some record label called True Tiger Recordings.

As much as I often consider ditching the whole writing/speaking career to be a lead singer in a rock band, that’s not what happened today.

A few kind folks, Peter, Kirill, Dave, Adam, Neil, Greg, Meh (hey, that’s the name you left) – let me know almost immediately that something strange was up, and as I don’t check my own RSS Feed often, and they saw it well before I did. Thanks guys, I’m in your debt.

Continue reading →

Wednesday linkfest

Posted on in linkfestby Scott Berkun

How to run a bug bash

Posted on in Software/Web developmentby Scott Berkun

Running a bug bash is a dirty secret of software development. You won’t read about them in software engineering classes, or in agile method workshops. But some managers, when overwhelmed with undocumented bugs and not sure what else to do, demand the whole team stop what they’re doing and get as many bugs into the bug database as possible. This is what’s known as a bug bash, and often they’re a waste of time.

It’s true that a proper QA effort, or test-driven development, minimizes the need for this sort of thing, but few software organizations truly qualify. Hell, many so called “first class” organizations don’t have any testers, or a quality assurance plan at all. I bet bug bashes are one of the most common QA techniques used in the world.

And they can be useful – but the most common mistake is doing them by half. A half-assed bug bash sends the message software quality is lip-service. But doing it the right way can turn a project around, raise morale and sharpen a team’s ability to find and manage issues.

How to run a successful bug bash:

  • Don’t create panic. If you say “Tomorrow! Everyone find bugs! Aaaah!” You are creating a panic and look like an idiot. You should know a week or more in advance that the bug counts are soft, or the database needs scrubbing, and line up leads and key players to support the effort.
  • Freeze the build. You can not do a bug bash on a moving target: you invalidate repro cases and bug findings. Pick a build, freeze it, and make sure no one, NO ONE touches the live codebase during the bugbash. This should go without saying, but you never know. If it’s your first team wide bugbash make sure the entire programming team understands this basic rule.
  • Show what good bug reports look like. Remind everyone crappy bug reports create extra work. Provide two bug report examples: one good, one bad. In the good example show well written description, clear repro steps, and a search for duplicate bugs. In the bad, show incomprehensible descriptions, impossible repro steps, etc. If you don’t provide examples, don’t expect people to magically know what you’re looking for. Finding 1000 crappy bugs that need to be heavily cleaned up is a waste of everyone’s time.
  • Have an area or type of bug to focus on . Saying “find bugs” is a shot in the dark. It shows you have no clue what’s going on in your project. Think through what the weakest areas are, or what types of bugs you are most afraid of, and designate them the primary goals of the bug bash. Or offer bonus points (e.g. bugs in area 6 are worth x2) for people who find the specific type of bug most valuable to you.
  • Clear the afternoon from everyone’s schedule. A bug bash should be an entire team activity and a half-day is the perfect amount of time. Everyone should be working on the same goal: getting good data into the bug database, and getting that database in shape. If it’s voluntary, or only half the team is asked to do it, the bash will fail. People will smell you’re not serious about the effort, and will contribute accordingly. Get permission to reschedule all team meetings for that afternoon to later in the week, and send out a new meeting invite to the team for the entire bug bash time slot. Include details (see below) on where bug bash HQ is, what the prizes are, etc.
  • Get support from big shots. Brad Silverberg, my VP on Internet Explorer 4.0, used to file bug reports regularly. When bug bashes started he’d set the tone: everyone gets involved. With the support of leaders it sets the tone of how important the activity is, and eliminates the BS excuses people find not to participate (“If Fred, our best programmer is doing it, I should be doing it too”). Find the key players on your team, either key leaders or the star programmers, and get them to help promote and contribute.
  • Have a bug bash HQ. Finding bugs can be a social activity: have a bug bash headquarters. Grab a conference room, order pizza and beer, and invite people with laptops to hang out and find bugs together. This invites people to help each other find repro-cases, share knowledge and bug database tricks, makes keeping a scoreboard easy, and makes the bug bash a proper morale event. A case of beer and few pizzas costs $60. Well worth it.
  • Keep score and have real prizes. Geeks are competitive. Use this to your advantage. Any bug database allows queries for open bugs by date: Get this up on a website or hallway monitor and show it in real time. Buy some nerf weapons, dinner gift certificates, or even some X-box video games, and have them visible at HQ – give them away as prizes, or set up a betting pool: $10 per person, and the winner gets the pot. You can get fancy and have special prizes for most twisted bug, the bug least likely to ever get fixed, etc.
  • Create rival teams. If you are totally poor, use ego prizes. Have the designers challenge the programmers, or the marketing team challenge the management team. Throw down: “I’ll bet the whole marketing team dinner at Ruth Chris’ my 3 reports can find more bugs than your whole team can”. If you don’t have cash, bet embarrassment: loser shaves their heads, has to dress in costume the next day, has to wash the opponents cars, etc. Get two sets of people who have some built in animosity or rivalry, especially if it’s well known, to openly challenge each other. This rivalry will draw more people in, if only to follow along. Do this once and you’ll have a tradition to build on for the next bug bash.

New video: How to make things happen

Posted on in design, Making things happen, Management, Microsoftby Scott Berkun

When Making things happen came out in March, I did a few talks here and there to help promote the new edition, including a stop at a little place called Microsoft, in Redmond, WA. They videotaped the talk and it’s now available online.

You need to be running IE, or using the IE plugin for firefox, for the video to play. Sadly it appears to run on Windows only (I know, I know – its not my choice):

Title: How to make things happen

Description: What are the secret tactics used by successful project managers? How can people in any role, from development to management to design, benefit from their playbook?This fun, fast-paced, and interactive talk, loosely based on the bestseller Making Things Happen (formerly known as The Art of Project Management), explains how to make good things happen, and how to triumph over powerful people who are annoying and frustrating. Bring your toughest questions and situations for the Q and A, where Scott gives away signed copies of the brand-new, updated edition of Making Things Happen.

Watch the video for How to make things happen

How to start writing a book

Posted on in mailbag, Writing Wellby Scott Berkun

Every artist was first an amateur. ~ Ralph Waldo Emerson

I get hundreds of comments and emails in response to the post on how to write a book. Here’s another interesting, and life-grounding, question from the mailbag:

I found your website hand thought it was awesome. I watched your videos and decided I could use some advice from you.

My house burnt down 3 weeks ago in Burnsville, Minnesota. I lost a 38 foot RV, a 69 Plymouth Fury Convertible, and monster truck and trailer in the driveway and my 16 years old sons car he worked on so hard and never got to drive. I also lost 5 animals in the fire and that really hurts. I still have my 3 children ages 23, 16 and a 10 year old daughter who is having night mares with all this life changing overnight experience. Guess what? I want to write a book about my life and how it changed so quickly. I am very grateful we are all alive and ok. Like everyone else I dont know where to start. I am living my worst night mare in a hotel gong on a month. We have nothing but the cloths we were wearing that day. Any advice would be greatly appreciated. Please contact me.

Very sorry to hear about your loss. I do hope there are local government agencies or non-profits that can offer you some assistance. Books aside, I do wish you and your family well.

On starting: there is no single easy way. Everyone is different. There are tricks I list in this essay on writing hacks, but some or one will work for you. The truth is how you start doesn’t matter, but if you wait for a perfect way you’ll never get started. If that essay doesn’t help, here’s additional advice:

  • Plan to write every day. Writing a book is a marathon. It’s more important than you work a little every day, than how much you work on any particular day. Are you good with self discipline and forming new habits? If yes, great. If not, that is likely the real skill you need to learn.
  • Plan to come back. One trick is to remember that the real work in writing is editing, something that only begins when you finish a first draft. I plan to come back later and revise, cut, rewrite and do all kinds of work for the second draft. The “writing” part is just the beginning. Having faith in the next draft has a freeing effect. There’s no pressure to get things right, or even to make them good, on the first draft.
  • Take a course or find a coach. There any many teachers and experts willing to help you along. Start with Jane Friedman and her recommendations.
  • Go chronological. In your case you’re writing about things that have happened, or are happening to you. Great. Pick a date, say a week before the fire, and write about what happened every day from them to now. It could be as simple as two or three facts per day, or memories per day, or your recollection of your thoughts on those days, whatever you like. But anchor on time as the spine of your writing. It creates an easy way to divide up your memories, and to trigger thoughts or recollections. You then might choose to go to your family and friends and get their stories and recollections on every day, giving you even more material to work from.
  • Draft an outline. An outline can be one page long or fifty. It depends on how much detail you feel you need to get going. If it’s your first book, I’d strongly recommend writing a two page outline that covers, at a high level, all of the major events or points you want the book to cover. It’s a good test: if you can’t write two pages, you probably won’t be able to write a book. If you can write a two page outline, put it aside for a day or two and then come back and re-read the whole thing. Is there a better order to explain events? If so revise. And then pick one of the chapters and get to work. Repeat.
  • Keep a notebook with you. Have a place to write down ideas and thoughts about your experience and keep it with you all the time. Your rule should be whenever a thought crosses your mind, no matter how strange or personal, you write it down. Worry later if its good or interesting, but in the moment, commit yourself to writing something down. I have piles of old notebooks, and go through one every few weeks.
  • Read books like the one you want to write. Learn from other writers by reading their work. For every “how can I?” question you have go find a book and see how a successful writer solved the problem. If your book is a memoir, many great writers have written books about their personal experience with tough times. Check out Joan Didion’s The year of magical thinking, about her experience with having two loved ones become seriously ill at the same time. It can help to see how other writers have tackled the same type of writing you’re going through.
  • Write every day. Even if it’s just for 5 minutes, even if it’s just a sentence or a few words, sit down and write every single day. You have to get used to how it feels to sit there and that only happens if you put your ass in the chair every single day. Find a slot in your schedule that you can protect (early mornings or late nights often work) and ask family to respect that time.
  • Have a plan for staying motivated. A book will take 500-1000 hours of work to write. That sounds scary, but most people watch 1000 hours a TV every year (4 hours a day).Writing is straightforward to do, but you have to keep showing up. Think about your reasons for staying motivated. Create a writing calendar where you can leave a note, or a mark, every time you sit down to work. This will help get some positive feedback every time you put in some effort, even if you’re not very productive on a given day. Your output from any writing session doesn’t matter much provided you continuing to work on it day after day.
  • Work towards a complete first draft. You can only write one draft at a time, so focus on the one in front of you. Don’t worry about how many drafts you’ll need. A draft needs to be complete enough that someone can read it and give useful feedback to you. If an entire draft is too, work towards having a complete chapter. Then two. Then more. Ask for feedback from people whose opinions you trust. And with that feedback you’ll be able to decide how to revise for your next draft.

I hope that helps get you started. Best wishes.

If you’re thinking about how to publish:

Have a question for the mailbag? Leave a comment or contact me here.

A million dollars for your best idea

Posted on in Creative Thinking, Innovation, Uncategorizedby Scott Berkun

Google, as part of their 10 year anniversary, is launching Project 10100, offering millions of dollars to the best ideas they can find for helping people.

From their FAQ:

What is Project 10100? Project 10100 (pronounced “Project 10 to the 100th”) is a call for ideas to change the world, in the hope of helping as many people as possible.

Why is Google doing this? The short answer is that we think helping people is a good thing, and empowering people to help others is an even better thing. Here’s the long answer.

How many ideas are you funding? We have committed $10 million to fund up to five ideas selected by our advisory board.

As best I can tell you don’t need to execute the idea or even have a plan. They are paying for the idea itself. A creative thinkers dream! Except of course you likely lose control over the idea after you win your cash.

Read the full FAQ here. Deadline is October 20th.

(Seattle) InfoCamp 2008 this weekend

Posted on in design, Seattleby Scott Berkun

Hadn’t heard of this before, but there’s a design unconference here in Seattle this weekend: InfoCamp 2008.

$50 gets you in for two days of DIY sessions on information architecture, user-centered design, librarianship, and information management. According to their description, It features an egalitarian, community-driven format in which presentations are designed and delivered by attendees.

Their website has a wiki, full schedule, blog and info on registration. If you’ve never been to an unconference before and work in design, check it out.

If you’re thinking about running a session at an unconference, check this out.

How hard to immigrate into the U.S? Awesome flowchart

Posted on in design, politicsby Scott Berkun

I can’t say how accurate this thing is, but it’s both a great piece of design (By Terry Colon, formerly of Suck), and a polarizing commentary on immigration policy: this will either anger you or make you happy. I know for sure my great grandparents would never have made it through this – Instead of being here writing this, I, like they were, would probably be a peasant farmer somewhere in Eastern Europe.

And here’s the blog post it comes from with it’s own comment thread (Hat tip, metafilter)

What I’d like to see are: 1) similar flowcharts for other first world countries. 2) Similar flowcharts for 50, 100, and 150 years ago in the U.S.

Microsoft & the social network wars

Posted on in Web 2.0 / social softwareby Scott Berkun

Interesting analysis by fellow Harvard Business blogger John Sviokla about Microsoft’s missed opportunity to enter the social network game:

Microsoft’s Outlook may be the world’s Rolodex, but they have not figured out how to link up all the latent connections that sit inside our Outlook address books. Put another way, they have the ends of the network, but don’t know how to tie them together!

In your email is a latent network of most of the people you know, and how often you talk with them. The Outlook add on – not made by Microsoft – called Xobni (pronounced ZOBNEE, and named for Inbox spelled backwards) looks through all the mail on your machine and figures out who knows whom by who is copied on which emails. In other words, your emails naturally contain your social network. It would be easy for Microsoft to simply ask your permission to contact the people in your email list, and Outlook contact database, and ask them if they were willing to join your Microsoft social network.

(Sviokla’s full post)

There is a ton of social network data in our cell phones (who do you call/text most often? Talk longest with?) and email applications, and a simple app could mine that data and build, or at least enhance, networks from it.

The problem is that for many people Outlook is no longer the primary contact list. Anyone using Linked-in or Facebook depends on those sources as virtual contact lists. Facebook wisely offers to import contacts from many sources when you create your account.

The surprising thing to me is that there isn’t a wikipedia, or craigslist, of social networks. A free, non-corporate, social network that protects it’s users by charter against the pressures of corporate raiding of personal social information.

What wall street should be required to do

Posted on in Uncategorizedby Scott Berkun

I don’t write much about politics and the economy, but the recent bailout makes that impossible. Best thing I’ve read so far, pragmatically speaking is this list of suggestions from Robert Reich:

My five nominees:

1. The government (i.e. taxpayers) gets an equity stake in every Wall Street financial company proportional to the amount of bad debt that company shoves onto the public. So when and if Wall Street shares rise, taxpayers are rewarded for accepting so much risk.

2. Wall Street executives and directors of Wall Street firms relinquish their current stock options and this year’s other forms of compensation, and agree to future compensation linked to a rolling five-year average of firm profitability. Why should taxpayers feather their already amply-feathered nests?

Read the full excellent, and thought provoking, post here.

How to free your inhibitions

Posted on in mailbagby Scott Berkun

Here’s a recent item from the mailbag/comment bag:

How do i free myself, kill my inhibitions and break away from any kind of mental consciousness i keep facing every time i want to do something really badly. I’m simply afraid, man. Afraid, i might hurt somebody or offend someone who i care for, might come across as selfish. Your talks are fun and exciting and an adventure in itself. Now, please help me in figuring out a way to just free myself from my other self. The lamb leads the lion in me so to speak. How do i reverse that relationship? I eagerly await your reply. Thanks so much man. You’re the Man!

I’m not a self help guru, but that might be a good thing here as I don’t have a nice, kind, warm fuzzy fluffy answer for you.

 

I recently went to a bachelor party at a rented house on a lake in Texas. On top of the boat dock, 20 feet off the ground was a swing: you grabbed the trapeze handle, swung out over the lake, and dropped into the water. Sounds cool, but it looked terrifying. Something about the angle of the water from that vantage point made it look unnatural. The result? A gaggle of 30-something year old men, standing on the edge, trying to build up the guts to jump.

One guy had done it. And when it was my turn to try I knew I had to turn off my brain in order to do it. Switch it right off – and decide before I put my hands on the trapeze that I was going to just jump without thinking. And that’s what happened. I jumped, and it was not nearly as scary doing it as it was thinking about doing it.

Two of my friends however spent the next hour, literally 60 minutes, standing on that ledge, the hot Texas sun beating down, looking down, trying different ways to think through the problem. A strategy set up to fail as this was not about thinking. While they never jumped, it was impressive to watch them fight a battle in their own minds for that long.

For some things in life there is no planning. No way to rationalize. It is either done, or not done. And the trap is the more you think about them, the larger the fear of doing them becomes. The trick is to be able to turn off that voice and operate without it. Create courage by denying the rational mind. And its a kind of self-knowledge to recognize when shutting off your mind is the only way to achieve what you want to achieve.

In your case things are perhaps easier. You can test your fear. Ask your friend if they’d be hurt if you wrote a book. Ask the people you care for if they can support you in trying to live your life differently, or to take a certain risk. GO AND ASK. If you never ask then the fault is yours. If you do ask for support and don’t get it from your closest friends, then you need to find new close friends. Ones who want to help you grow and be happy. Either way, in taking action you win. But in being passive and worrying, complaining, imagining, you make your own mind a trap, like my friends by the ledge.

Got a question you want answered? Ask Berkun or put it in the mailbag.

Need a new web host – recommendations?

Posted on in this siteby Scott Berkun

I’ve finally had enough of dealing with dreamhost. Love their features, but man, does stuff go down often. And today, not for the first time, all incoming email is bouncing. Just plain unacceptable.

I’m looking for a new webhost and could use recommendations. It doesn’t seem there is a decent source of web host reviews, and even the best i’ve found is thin – so I’ll hoping for advice from you folks, as you actually might care to see this site nice, stable and healthy.

My needs:

– I’m willing to pay more for reliability and decent support.
– WordPress is my life. Prefer hosts that understand WP, or offers it by default.
– Need medium level bandwidth support.
– Easy non-geek management a plus. I’m smart, but want to spend as little time in shell/Unix as possible.

I’d also love to find a website transfer service that, for a fee, moves all of my domains and stuff from one host to another. Am I in fantasy land?

Suggestions much appreciated – Cheers.

How to work better in ten easy steps

Posted on in Managementby Scott Berkun

This bit of pithy advice is floating around the web. It’s so nice, tight and simple, much more useful than many of the self-helpy business books I’ve seen in the last few years. I mean, what percentage of your co-workers do even half of what’s on this list?

Found it here, but this seems to be the original source (Much like Corita Kent’s list of creative rules, there are many unattributed postings).

  1. Do one thing at a time
  2. Know the problem
  3. Learn to listen
  4. Learn to ask questions
  5. Distinguish sense from nonsense
  6. Accept change as inevitable
  7. Admit mistakes
  8. Say it simple
  9. Be calm
  10. Smile