Austin Govella's writing on Lean, Agile, and
Balanced user experience

Hacking UX Zombies

Just in time for Halloween, the UX Zombie survival guide, how to hack UX zombies down to size, a shorter introduction to hacking UX for agile, lean, and waterfall teams.

Agile+UX: A Tale of Three Teams

For any project involving any amount of user experience, the team needs three models: one for the user, one for the interaction, and another for the interface. These models can exist in any fidelity, in any medium, transmitted in any form, but the team needs all three.

Rewriting the agile manifesto

When we remove the kittens from the Agile Manifesto, we reveal the conflict between “the real” and “models of the real”. We reveal the primary tension between development and design, between disciplines of making and disciplines of modeling.

Most people make the mistake of thinking design is what it looks like. People think it’s this veneer — that the designers are handed 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

Agile+UX: Your process should be healthy, not lean

Lean UX isn’t about a skinny process. Formal deliverables are often the cookbooks your team needs to whip up some tasty UX.

Agile+UX - remembering what a team's sposed to be

Agile + UX: (un)Synchronizing UX and development

User experience can help agile teams create better experiences, but agile isn’t designed to manage user experience.

Agile + UX: six strategies for more agile user experience

Six ways to be more agile and better integrate user experience and information architecture into agile development teams.

Agile + User Experience = Parallel work streams

In an agile process with a rolling series of sprints, UX requires two, parallel work streams, clear expectations, and constant status reports.