The failure of Scolidays

With the end of year coming around, my highlights and lowlights for 2007 are coming to mind. One clear failure was my Scoliday project. In 2004 I set about creating my own holidays, to honor what I thought was important. I did them that year, fell off in 2005, and the started again in 2006 with a new list of days, some of which I celebrated.

Somehow in 2007 I didn’t even try.

I know a few folks did their own flavor of this idea, including antigeek, Konrad West, and more, and I hope they’ve faired better than I have.

I’m reading through my journals for 2007 and trying to see if I can figure it out.

Thoughts so far:

  1. I didn’t have any partners in crime. As an author/speaker dude, I work solo most of the time and suffer from solo project fatigue. Having a holiday buddy or something would probably up my odds.
  2. Perhaps I need a holiday every few months called called Celebrate all the holiday’s you’ve missed so far day. Build in a way to recover part way through the year.
  3. Use this blog as a forcing function – post a note on the day, and if I didn’t celebrate it, hang my head in shame online or donate money to charity for each day I let fly by.

I’m still in love with the idea – but trying to learn from my mistakes, and improve my commitment level for 2008.

The new name for the artofpm book is…

Three months ago, I asked all of you to help me decide the name of the revised edition of the art of project management (if you want to know why we’re changing the name, read that last post).

After more than 300 votes, here’s what won: Making things happen

booktitlevotes4.jpg

After many discussions with the fine folks at O’Reilly, the final name is Making things happen: mastering project management. I’m excited about the name! My favorite chapter in the book is #12, the one called how to make things happen, and now it gets top billing.

For those interested in the behind the scenes drama: this was not a fun process. Like naming a child, naming a book is something one only expects to do once. If you don’t like the outcome, or the fact that there is a name change, I understand, but do consider this was 20 times less fun for me to deal with, than it was for you.

What’s most interesting is this – behold the power of the web! You guys say it and it happens! I must thank all of you who took the time to vote: the ability to point to data from actual customers played a key role in my discussions with the editors at O’Reilly Media on the new title.

The revision is well underway, and I’ll post more about it, and its timeline for release, soon. In related news, the existing book will be out of print soon, so pick it up if you want a collectors item.

For fun, here were some of the best, and funniest, write in votes:

  • TBFKATAOPM2 (The book formerly known as…)
  • What the #$!#!@$% is Project Management and How Did it Get inside this book?
  • Projects. Managed. Berkun’s Way.
  • Kill the messenger
  • Who stole my project manager?
  • Real world project management
  • How to make enemies and derail projects in 5 minutes a day
  • OH MY GOD, HOW DID I BECOME THE PM?
  • The bible of mastering the zen and art of agile project management for dummies
  • From bad to worse: how bad managers become horrible
  • Who stole my project manager?

The art of project management – going out of print

The time has come. As mentioned a few weeks ago, the book formerly known as the art of project management will be going out of print. A revised edition, with a new title, will be out in 2008 (If you want to know why, read the post).

If you’ve been waiting to buy a copy of the book, you should do so soon. Amazon and other retailers already have limited inventory (noted by 5-10 day ship times). The used inventory on amazon and e-bay look good, but I don’t know how out of print status will effect that.

Once the book is out of stock, you’ll have to wait for the new edition, which will be out next year.

The 8 challenges innovations face

In chapter 3 of The Myths of Innovation, I explore why innovation methodologies are prone to fail. It’s not their fault – there are many factors involved that are out of the control of any individual. You can do many things right and still fail.

There are dozens of challenges that must be overcome, but to be handy I distilled them down into 8 basics. This provides a handy checklist for evaluating why ideas die, why a start-up failed, or where the real tough spots are in making innovations happen.

  1. Find an idea. Historically this is easy. Ideas are everywhere and anyone who can consider a problem for an hour can come up with possible ideas for solving it. Creativity is rarely the hardest challenge.
  2. Develop a solution. The gap between an idea and a working prototype is HUGE. So what if you think something can be done, go and do it. Until you can show the manifestation of the idea, it’s still just an idea. Thousands of brilliant minds have conceived brilliant ideas, but failed, despite years of dedicated effort, to successfully prototype them.
  3. Find a sponsor and funding. Even with a kick-ass prototype in hand you need resources to develop the prototype into a product. Whether an entrepreneur or a middle-manager, odds are good that to finish a prototype, or make a product out of it, you’ll need someone else’s approval. (Even if it’s your wife’s permission to spend nights working, a friend who will let you live in their basement, or a bartender willing to run you a tab).
  4. Reproduction. Making one of something is not the same as making a thousand. I happen to have an amazing mousetrap: his name is Vincent and he’s my 15lb cat. But I can only sell one, as cloning him would cost $50,000 and that’s more than anyone would pay for a good mousetrap. Having an innovation and having an innovation than can be reproduced economically are not the same thing. Software is generally easy to reproduce, but many innovations are not. When it comes to the web, reproduction often means scale: can your server handle 50000 people using your innovation at the same time? This is a different technical skill set than creating the prototype.
  5. Reach a customer. This is where the skill set required to make a successful innovation changes dramatically. OK. So you’ve overcome the first four challenges – but now the challenge has nothing to do with domain expertise, prototype brilliance, or even funding. Now someone has to inform potential customers that your innovation exists, persuade them to be interested, and convince them to pay money for it. Wow. What does this have to do with breakthrough thinking or a brilliant prototype? Very little. Those things help, but the challenge is now about persuasion, not creation. Up until this challenge, most innovators are deliberately hiding from the world in fear of idea theft, but now they have run in the opposite direction.
  6. Beat competitors. Every idea has competitors. Even if you successfully reach customers, you won’t be the only one trying to reach them, and in the pursuit of customers things get ugly. Thomas Edison, in the war over electricity, tortured animals to convince the world his DC current was safer than Westinghouse’s AC (they were equally dangerous). How to position, advertise, make partnerships, sign deals and distribute a product is complex, unpredictable, and has little to do with the quality of the idea being sold.
  7. Timing. This is the challenge that crushes innovators souls. A huge number of things can happen on any of your important days that a) decides your fate and b) you have no control over. Imagine what happened to all the start-up companies that announced their new product to the world on Sept 11, 2001. No one knows their names, and many of those companies did not have the resources to stage another launch. WWII had a huge impact on innovation: many ideas that weren’t war related were mothballed for years, including broadcast television in the USA. Timing impacts product launches, business deals, cost of goods, and dozens of other decisions innovations depend on.
  8. Keep lights on. And of course, while you’re doing all of the above, someone has to pay the bills and keep whatever daily business there is running.

The book digs deeper into these challenges, and how succesful innovators overcame them, so if you dig this view take a look at the book, The Myths of Innovation.

Usability review: parkingfriend.com

#2 on the free review list comes from Geneva Switzerland, at parking-friend.com, a site for valet parking at the airport and other places.

parking-original.jpg

Summary:

  • Designed like a poster. The visual elements are strong and dominate the page. This would great for a poster where you need to draw attention, but if someone is on the web page you already have their attention. The large P element on the left and the price star on the right overpower the rest of the design. The P alone consumes 100+ pixels of width, purely for cosmetics. If the site were high style (shoes, clothes, etc.) maybe you could argue for the style value, but this is a parking site – a utility experience.
  • Choices are hidden and links unclear. The page works by showing/hiding one of three choices: airport, event or other. Airport is chosen by default, but to see the option options you have to click on the right question. With only 3 choices there’s no reason to hide UI: radio buttons work very well for handling this kind of decision making.
  • Colors and sizes are too strong . Trebuchet is known to be a good web design font, but if you split sentences into two colors and default to 20pt text, it gets hard to read (See the Terms page). Whitespace is increasingly important with difficult fonts or large sizes, but the text heavy pages on this site have few paragraph or line breaks. The purple/orange theme is good and works well, but it doesn’t need to be followed through within sentences – two color phrases are hard to read.

The squint test: One visual design trick is to squint your eyes and see how the page balances. The two dominant elements stand out like this (see below). The problem is that neither one earns it’s prominence, and they demand this first order attention on every single page.

parkingblur.jpg

Simplified redesign:

Taking into account the above, this design simplifies the grid. The visual elements now fit the page, instead of demanding an unwarranted amount of pixels and attention. All text is one color, the hide/show UI is replaced by a simple radio button scheme. I also cleaned up the navbar, moving the language choices and log-in into a tighter layout.

Before and After:

parkingbeforeandafter.jpg

A few things I missed:

  • The price should be restated in the text, or before the book now button. Messages in graphics are often missed, as they’re offered parsed as secondary information, and the star on the right is the only place the fee is currently mentioned.
  • Credibility should be emphasized. Why should people trust their cars to this company? The pitch for credibility should be stronger. There should be photos of the lot, of the service crew, statistics on how many satisfied customers there have been or how many years it’s been in operation, etc. on the front page (even if put behind a prominent “Why trust us” link).
  • Radio button layout is dull. With more time I’d play with the text and radio button layout. Leading with a form is never sexy, but it gets straight to the primary task of this website: make a reservation. Looking at other parking websites shows similar form centric designs.

Usability review: iwethey.org

I got hit with a case of the lazies, and didn’t get to my promised free usability reviews until now. These will be high speed reviews: 10 minutes of analysis, and the rest of my time (30-45 minutes per site) spent explaining the issues and offering alternatives.

Drew Kime submitted this homemade forum software, used by iwethey.org, which is cool since my own forums are still locked in search of a forums package that doesn’t suck.

iwethey600.jpg

Summary:

  • The core design is *ok*. The basic threaded forum UI is familiar to many, and most of the problems this site has are ignorable, not fatal. However there is a general lack of basic UI knowledge here, as layout and prioritization are mostly ignored, wasting everyone’s time.
  • Basic layout issues. The top 10% of the screen is what people will see first, and on every page. But this design is a scramble: there are no easy columns for eyes to follow, important links wrap around lines, and the logo itself forces people’s eyes to do much too much work (never cover part of a letter with an image). Basic layout should always follow a grid: all left edges align, and any new columns align (See Before and After below).
  • Lack of prioritization. There are nearly 25 links in the top area of the screen, and no attempt is made to prioritize them. What percentage of users will need the source code for the forum? I’d say less than 2%. How about a list of changes to the source? I’d say less than 1%. Then why have these two links as the first ones on *every* page? The most frequently used links should be the easiest and fastest to find. Move info about the software to the footer.


iwetheybeforeaftersmall.jpg

$1544 raised for Hopelink!

We walked. We walked. And then we walked some more.

And thanks to all your contributions, we raised over $1500 for folks who need some help this holiday season. Awesome! Thanks for helping us make a difference.

We’ll be sending out the signed books and artcards on Dec 2nd.

If you feel guilty now, you can still donate online until Dec 2nd: and donations of $25 or $50 get special gifts from Jill and myself – to find out more, go here.

Thanks – you guys rock.

Writing quote of the day

A scrupulous writer, in every sentence that he writes, will ask himself at least four questions, thus: What am I trying to say? What words will express it? What image or idiom will make it clearer? Is this image fresh enough to have an effect? And he will probably ask himself two more: Could I put it more shortly? Have I sad anything that is avoidably ugly?

But you are not obliged to go to all this trouble. You can shirk it by simply throwing your mind open and letting the ready-made phrases come crowding in. They will construct your sentences for you – even think your thoughts for you… and at need they will perform the important service of partially concealing your meaning even from yourself.

From the essay Politics and the English Language, By George Orwell

Debunking The Top Thanksgiving Myths

During research for the The Myths of Innovation I read many history books, particularly ones exploring popular falsehoods about the past. Books like Don’t Know Much About History, provided guidance on how to tell true stories in the face of popular falsehoods.

With the big U.S. Holiday of Thanksgiving coming, here’s some fodder for fun dinner conversation, as when pleasant myths collide with the real history surprises are sure to happen:

  • The success of the Mayflower settlement depended more on smallpox than the Pilgrims. Years before the Mayflower landed, Europeans had already brought smallpox to America, killing most of the indigenous population (An event the Pilgrims called “an act of god”). This made the early settlements far easier to construct (reusing areas already developed), and forced the remaining natives (most notably Squanto) to consider cooperation with settlers, teaching them many survival skills. The Pilgrims stole corn and other supplies from natives during their first year. They were desperate and struggling.
  • From the Native American perspective, Pilgrims were invaders. They say history is written by the victors, but no matter who writes it, it’s always a matter of perspective and often important ones are ignored when it’s convenient. The heart of the Thanksgiving Myth imagines an existing civilization kindly inviting a new nation of white people to come and “settle lands” they already occupied. And the story is detached from the century long genocide that would follow as  America continually broke treaties and willfully took land.
  • Half of the Pilgrims died in the first 5 months. They were untrained, unprepared, did not know how to farm or hunt in America, and chose a difficult location for their first settlement (they wandered off course crossing the Atlantic). By the time of the first thanksgiving those still alive were happy not to be dead – the fact that they had food to eat was more than worthy of celebration.
  • The Pilgrims did not eat turkey, mashed potatoes or pecan pie. Thanksgiving was not an official U.S. holiday until the 1860s, and we are celebrating the eating habits of people from the 1860s, not the 1600s. It’d be more accurate to eat venison than turkey. It’s not documented what was eaten on the first Thanksgiving, though it’s pretty certain they ate their meal with their hands. It’s likely only cranberries that were native food at the time.
  • Thanksgiving is an ancient native concept, not Pilgrim or American. As you’d imagine, the folks who actually knew how to work with the land, the natives, had their own set of customs for giving thanks back to nature: some tribes had 6 festivals every year dedicated to giving thanks, only one of which we know as Thanksgiving. The spirit of today’s holiday is wonderful: be thankful. But we forget how much of holiday, and the fate of the Pilgrims, depends on previous cultures and customs.
  • The Pilgrims were not Puritans. Both groups were radicals who wanted to escape persecution in England. But the Pilgrims were more egalitarian and tolerant – they had non-believers on the Mayflower, and even more in their settlement (they came over later). The Puritans wanted reform, but wanted the Church to change to reflect their views (whereas the Pilgrims abandoned the Church entirely). The Pilgrims were on the Mayflower, but the Puritans didn’t arrive in America until several decades later.
  • The Indians and Pilgrims did not get along very well. Around the time of the first thanksgiving, The Plymouth settlement was converted into a fort, hardly an act of thanks, nor giving. As you’d imagine, the relationship between these two groups was complex, with different skirmishes and crimes by factions on both sides. While there were times of peace, tension grew over the years and led to King Phillip’s war, the end of any pretense of peace, a few decades later.

There certainly are some things to celebrate in the true story: the leadership and struggles of the settlement, some of the motivations of the Pilgrims themselves, and the acts of peace by parties on both sides, but these aren’t in the mythologized version most American’s know.

References:

[Minor updates: 11/26/2020]

Help me help folks in need

turkey150.jpgInnovation shminovation – some folks out there have trouble feeding their kids and staying warm. There are real problems out there that I often forget about.

This Sunday my wife, myself and our two goofy dogs are doing a 5k walk for the non-profit Hopelink.org. Unless you’ve recently done something cool for folks who need help, I’m inviting you to chip in and sponsor us on the walk.

They set up a personal website for my team, and it’s easy,safe and fast to donate. You’ll feel better. And most important of all: My dogs Max and Griz will think better of me, and you.

What to do: Go here and donate $1, $15 or more for our team, by paypal or credit card. Donate more than $50, and I’ll send you a signed, first edition copy of the Myths of Innovation.

If you can’t spare the cash, I hope you’ll find another way to make a difference this holiday season.

More info on the event, including creating your own team: Hopelink Turkey trot 2008.

Update: Donations accepted until December 2nd 2007.

Innovation Myths in Schoolhouse Rock

newton.jpgWhen lecturing about creativity I often ask the crowd how they know what they know – How do we really know Edison invented the lightbulb, or that Newton got hit by an apple? A common answer from audiences of my generation is the popular cartoon Schoolhouse Rock. It’s curious how we dismiss things by saying “it’s just for kids”, but what happens when those kids grow up?

I loved Schoolhouse rock as a child, and it’s probably the only reason I know what a conjunction is. But in watching a local performance of the musical based on the TV show, I found some problems with the stories that I learned, stories I researched for The Myths of Innovation.

The story of Newton, and epiphany in general, is the subject of chapter 1 of the Myths of Innovation, titled The Myth of Epiphany which you can read about here.

Myths of Innovation: #4 on Amazon’s best of 2007

mythstopsmall1.jpgAmazon.com just posted their best 100 books of 2007. In the Business narrative category, Myths of Innovation shows up at #4.

On the full top 100, Myths slides in there at #99.

They don’t explain exactly how they chose their books, which editors were involved, or how they voted, but I’m not complaining. There is a separate list of 100 customer favorites for 2007 that I assume is purely based on sales.

Thanks to all you blog readers for your support – this kind of stuff doesn’t happen for me without your help spreading the word. Cheers.

The best public speaking tip ever

This is it. This is the big one. It’s the best, simplest advice I’ve ever heard about public speaking: Videotape yourself speaking and watch it.

That’s it. That’s the whole thing.

This is not new (title says best tip, not the most original), but most people are terrified of this and never do it. Well guess what – if you’re afraid to do it, how should your audience feel? Would you hire an accountant that doesn’t do their own taxes? Well, if you’re a speaker, you should, once in awhile, be your own audience.

We’ve all seen thousands of professional speakers, actors and presenters on tv and in the workplace making us all excellent critics of presentations. But what most of us lack is the most basic feedback on how we perform ourselves.

If you watch even 5 minutes of yourself presenting, you can catch:

  • Lazy speaking habits, like ummms and aaaaws.
  • Lack of eye contact (reading isn’t presenting) and presence.
  • Body language issues and distractions.
  • Moments when you’re confused by your own material.
  • Energy level (do you seem to care about what you’re saying?).
  • Personality – are you indistinguishable from a presentation robot?

Watch yourself and take notes. After you’ve caught things like above that distract you as a viewer, videotape yourself again – on the same material – with the goal of doing less of the above, and more or the things you did well. As you repeat the material with these things in mind, more and more of your material will come through. Still think you suck? Do it again and again and I promise you will get better nearly every time.

With the video, you can ask friends to review and give feedback – but pick your presentation minded, critical friends, not the ones who, like your Mom, will just tell you how great you were.

This requires no training, no special Powerpoint voodoo, just your willingness to swallow your pride for an hour or more. Believe me – your audience will appreciate it.

Why conferences have bad speakers

Most of the time, at most conferences, most speakers won’t be very good. Public speaking is hard, but the low quality of speakers is strange given how most conferences focus on their agenda of speakers. It’s not like they market their event primarily on free beer or tasty food – they pitch the potential for learning from experts as the primary reason to buy tickets. The speakers are the fundamental premise for attending and often it’s a broken one.

Here’s why:

  • Organizers have 3 tough criteria: 1) find experts on a topic 2) who are good public speakers 3) and who are available and affordable. It’s hard enough to nail 2 of the criteria, but 3 can be impossible – organizing is a tough job. That said, organizers are typically rewarded for #1 and #3, and only hear about #2 when the conference is over. If attendance is good, concerns on #2 are easy to ignore. (See An open letter to conference organizers)
  • Speakers are chosen based on expertise, not performance. Most speakers are invited based on books, blogs or experience, rather than their ability to communicate or teach an audience. Public speaking is a kind of performance, yet it’s rare for organizers to have seen their speakers speak before the event. The biggest gamblers are academic conferences, like CHI, where people are invited to speak solely because they had a paper accepted. What does writing a paper have to do with being a good public speaker? Almost nothing.
  • Confusion between entertainment and value. Some speakers gain reputations for being funny or charismatic, but that’s not the same thing as teaching. Even speakers who are known as “good speakers” earn that reputation for charisma, not for the value of the lessons they teach or the quality of their ideas themselves.

What can be done:

  • Train speakers for the event. Serve speakers and the audience by providing voluntary coaching. Give them a checklist to guide their preparations. Most presentation mistakes even by expert/guru types are basic and I wrote Confessions of a Public Speaker to teach solutions to these problems. There are dozens of other books and resources it’s just up to organizers to use them. [Update: I am the speaker coach for Ignite Seattle and you can see how I coach speakers here].
  • Evaluate video samples of them speaking. It’s rare I’m asked for this, despite how easy it is to provide in the youtube era. Conference organizers should sample what they’re hiring for, instead of reviewing slides, proposals or other trivia. And why not put the samples on the conference website? Then attendees can sample the speakers, instead of guessing blindly from the descriptions at who will be good.
  • Give speakers their real feedback . Most conferences do some kind of audience survey for the event, but rarely does the feedback make it back to the speaker. And sometimes when it does, it’s filtered – all the rants and complaints are filtered out. Who but the conference organizers can point out to speakers that there is a problem or room for improvement? Human nature dictates that most of the informal feedback speakers will get will be polite and positive, not balanced or constructively critical. Someone has to fill in the feedback gap and only organizers can play that role.
  • Performance based pay. Speakers should earn part of their fees (if they are paid at all) based on feedback from the audience. This forces them to pay more attention to the value they’re providing and places greater power in the audience to recommend future speakers. UIE 12 is the only conference I’ve ever been paid performance based pay as a speaker and I wish more would follow their lead. If I suck, I want to be paid less. And if I do a great job, I want to be paid more. Even an audience favorite prize, where the winner by vote gets a $1k bonus is easy to do and in the right spirit. This audience shouldn’t be the singular arbiter of evaluation, but certainly should be a primary one.

See also:

What else can conferences do to improve the quality of conference speakers?

[Note: minor edits and updates 2/21/2014]

Does Google 2008 = Microsoft 1998?

MSFT vs. GOOGThis is a question I’ve thought about often (See Google’s ten rules compared to Microsoft). Before I give my answer, if you’re in Seattle you should go listen to Lawrence Lessig give his talk on the subject Friday Nov 2nd at Kane Hall, at the University of Washington.

The short answer is No. In 1998 Microsoft was suffering from the shaky Windows 98 release, was facing a new DOJ lawsuit, and will still engaged in the browser-war with Netscape. I was in my 4th year at MSFT in ’98, and it was the roughest year for the company I’d seen. The browser war was emotionally brutal, and on the Internet Explorer team we were trying to recover from IE4 (a release few of us were proud of). To outsiders, 1998 was a year of comeuppance for Microsoft.

Looking to next year I don’t see Google headed for seas quite so rocky. Yes, there are threats of major lawsuits with YouTube and search privacy, but those threaten future revenue sources more than current ones. However, like Microsoft in the 90s, the competitive landscape isn’t impressive. Yahoo and Microsoft have are still trailing players in tech-sector mind share.

Most important comparison: By 1998 Microsoft, the 23 year old company, had managed to piss off just about everyone at least once: at least it felt that way when I spoke at conferences. Google, only 8 years old, has a much higher standing in the industry, among competitors and partners, than Microsoft did. But then again, it’s 15 years younger :)

On culture and attitude: Life inside Google feels much like at Microsoft in the mid 1990s. I’ve been to Google several times (Chapter 1 of the Myths of Innovation recounts one visit) and know folks working there. The vibe feels incredibly familiar to my mid-90s MSFT memories: happy, smart, independent people who feel they are empowered to change the world, and who work in a special place, with special rules. And as best I can tell, it’s true. They deserve to feel that way. So in that respect, rock-on Googlers.

But the rub is that in the mid-1990s Microsofties felt the same way about their place in the industry, and their ability to change the world, as the folks at Google seem to today: We have the ball and we are running away with it. I suspect the folks at Atari in 1977 (year of the 2600), Apple in 1985 (and perhaps again now), Netscape in 1994 (year of Mosaic) and dozens of other companies that were once at the top of the world. And they were all prone to the same kinds of self-destructive hubris.

Common mistakes employees of dominant companies make:

  1. Believing no one has been at the center of the tech-universe before.
  2. Inability to take a non self-centric view of the world.
  3. Depending on power and intimidation, more than intelligence and wisdom.
  4. Failing to find ways to stay humble & hungry while being dominant.
  5. Focusing more on beating rivals than satisfying customers.
  6. Underestimating how decisions will be received by the rest of the world.

When I was at Microsoft (’94-’03), I always felt the company made things so much harder for itself in how employees, executives included, presented themselves to the world. I can’t tell you how many times I saw Microsoft employees embarrassing themselves at conferences, e-mail lists or on newsgroups. And it wasn’t entirely their fault: they were expressing the internal culture to the outside world and the result was predictably disastrous.

The perception of Google today, and in 2008, is at a tipping point. They are quickly rounding out their positions of dominance and the Microsoft comparisons will only get sharper. If they can learn the best lessons from Microsoft’s 1998, it’s about handling pressure with grace, and the wisdom to pay more than token attention to the mistakes above.

World usability day: Free usability review

Next thursday Nov 8th is World usability day, and there are events all over the world.

For you folks online, just like year’s past I’m offering the first 10 people who leave a comment a free expert usability review of the website they post (it doesn’t have to be their own website).

How to get a free expert usability review:

  1. Leave a comment, include your e-mail address and a URL.
  2. If you’ve got a specific problem or user scenario you’re worried about, mention it.
  3. If you’re in the top 10, I’ll post your review online.
  4. If you’re after #10, be creative. If you make me laugh you might get yours too.

Bonus: If you work on stuff for cell phones or mobile devices, Sender11, a mobile design expert, is offering free usability reviews for you.