Event Design is how it works

Design is how it works“Design is how it works” is the favorite thing Apple software engineer Ken Kocienda heard Steve Jobs say.

Here’s Steve:

“Most people make the mistake of thinking design is what it [a product] looks like. People think it’s this veneer—that the designers are headed this box and told, “Make it look good!” That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works.
—Steve Jobs, The Guts of a New Machine, 2003 New York Times interview

If only we applied Steve’s insight to event design.

Read the rest of this entry »

How to help meeting design clients figure out what they really want and need

Great — a client who doesn’t know what they want!
Recently, a client asked for help designing a new conference. Thirty minutes of discussion with three stakeholders revealed they hadn’t yet settled on the event’s specific purpose, scope, and format.

From my perspective this is actually a great problem to have.

Why? Because most clients engage me after they are committed to programs and logistics that are not optimum for what they’re trying to accomplish!

The needs assessment trap
Conference design clients who “know what they want” have already decided on their “why?” and “who?“, have often fixed their “when?” and “where?“, and typically bring me in to consult at the “how?” stage. I understand their perspective, because I also feel the temptation to pin down specifics — number of participants, duration, venue, budget, etc. I hope that in the process the event’s purpose and desired outcomes will become clearer.

It’s true that focusing on these details can help uncover what the client wants, and whether it’s realistic. {“Hmm, I think we’d need a lot more than $10K to bring together 200 scientists to plan how to eradicate malaria in Southern Africa.“} But this is a roundabout way of avoiding the all-important question that is rarely fully and productively explored:

Read the rest of this entry »