Starting out creating an interactive experience, of any sort really, can be rather daunting. In this tutorial, we’ll run through the basic components of a game, so we can get a handle on what the next steps are when you make the jump from the training tutorials to your own projects.

So when your boss, client, teacher or mentor drops a project on your lap and asks you to "add social to it," where do you start? I'm thinking you start with the information architecture and in particular your conceptual models.

Cities + Software

The other day I was looking at a proposal for a project I finished a few months ago. The result, by my measure and by the client's, was successful. But guess what? The process I so reassuringly put forward at the outset had almost nothing to do with the way the project actually went. What would happen, I wonder, if I actually told the truth about what happens in a design process?

A 17-minute presentation from John Gruber (Daring Fireball) on the application of Auteur theory to software design.

At OOPSLA, I'm planning to talk about NeoVictorian Computing. It's a big talk, with lots of side paths and a few surprises. I'm going to talk about why we in computing seem unhappy, and how we might fix it.

"The best basis around for user-centered interaction design, both as a primer for students as an introduction to the field, and as a resource for research practitioners to fall back on. It should be labelled 'start here'."

game, game, and again, game is a digital poem/game/net artwork hybrid of sorts. There are 13 curious levels filled with poetics, hand drawn creatures, scribbles, backgrounds and other poorly made bigts. The theme (cringe) hovers around our many failed/err

If you’ve ever sat through a requirements workshop thinking it was wasted time, maybe you’re ready to take on some new tools to get what people really need out of their heads, and into the world. One tool that I started to use in 2002 is design games: