I have worked with many developers and designers on both front-end websites and back-end applications. Working through the user experience of an interface is one of the most important elements in any of these projects, and in the last couple of years, I have been fortunate enough to have worked with project managers and developers who know and utilize lean or agile product development techniques. Typically, I have worked within a two-week “sprint” – an iterative process that involves being able to release feature/functionality every two weeks.
I recently came across this article in CIO Magazine that articulates “How ‘Lean UX’ Can Improve Application Development“. I recently joked to a co-worker that I try so hard to help developers visualize what I need them to build, that even when designers are too tied up with other projects to prototype something, I will mock it up myself in Photoshop or Paint (yes, even in Paint).
The article outlines Four Fundamental Elements of Lean UX. My favorite is number 4, since I’ve seen that developers really appreciate having that visual to work with so that they have a clear idea of what they are to build.
- Finding the core features that matter most to customers—no more, no less—and find them at the cheapest possible cost.
- Moving as quickly as possible through the “build-measure-learn” loop. This is also referred to in UX circles as the “think-make-check” loop.
- Exposing the product directly to target users early and often.
- Developing “minimum viable products.” Moving through the loop often does not require building an actual product. Clickable prototypes, presentations, screen mockups, and other low-fidelity techniques often work well.
