Skip to main content

Lean UX for Startups (Book Review)


I recently received a review copy of another book in Eric Reis's Lean series, UX for Lean Startups: Faster, Smarter User Experience Research and Design. In this book, with a lively, if somewhat irreverent, tone, Laura Klein guides you through the process of using UX as a gateway into finding a market and eventually, success. This book has pragmatic advice on what to do and how to do it now, and more importantly, what not to spend time on. Not just a concept book, this book discusses tools and detailed approaches. Klein addresses many of the concerns people might have about "skipping steps" in order to be lean, and explains the both the challenges and benefits of a lean approach to UX design. The author discusses how UX fits into an agile startup environment.

This book shares some of the irreverant tone of another book geared to people starting a business: The Pumpkin Plan: A Simple Strategy to Grow a Remarkable Business in Any Field. The author's tone takes a bit of getting used to, but the advice is good, and actionable, and the style of the writing emphasizes the "just do it" theme of the book.

UX For Lean Startups has a slightly different audience than the earlier, similarly titled book Lean UX: Applying Lean Principles to Improve User Experience. Looking at the books, it's a bit unclear which one to read. As it happens, Lean UX: Applying Lean Principles to Improve User Experience is more about how to apply Lean Principles to UX design, with an eye toward migrating from a non-iterative UX process to a more iterative, lean, agile process. That book seemed to be geared more towards UX professionals, though anyone who touches UX could benefit from it. Lean UX for Startups addresses the needs of entrepreneurs and members of a startup who want to have a good UX, but can't waste a lot of time and effors on it. I'd reccommend that either individual get both books. But if you are building a startup, this one will give you the most actionable advice quickly.

You can benefit from reading both books. If you want to read one on UX, you might get more out of the Lean UX book. And Maybe read Lean Startup or perhaps the Pumpkin Plan. This book will add information so it is worth a read. The 4 books I mentioned would be a good addition to the library of anyone who is starting a business and wants to deliver value quickly.

Comments

Popular posts from this blog

Continuous Integration of Python Code with Unit Tests and Maven

My main development language is Java, but I also some work in Python for deployment and related tools. Being a big fan of unit testing I write unit tests in Python using PyUnit. Being a big fan of Maven and Continuous Integration, I really want the  Python unit tests to run as part of the build. I wanted to have a solution that met the following criteria:
Used commonly available pluginsKeep the maven structure of test and src files in the appropriate directories.Have the tests run in the test phase and fail the build when the tests fail.
The simplest approach I came up with to do this was to use the Exec Maven Plugin by adding the following configuration to your (python) project's POM.

<plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <executions> <execution> <configuration> <executable>python</executable> <workingDirectory>src/test/python</workingDirect…

Displaying Build Numbers in Grails Apps

Being a fan of Continuous Delivery, identifiable builds, and Continuous Integration: I like to deploy web apps with a visible build number, or some other way of identifying the version. For example, having the build number on the login screen for example. In the Maven/Java world, this is straightforward. Or at least I know the idioms. I struggled with this a bit while working on a Grails app,  and wanted to share my solution. There may be other, better, solutions, but the ones I found approaches that didn't quite work they way that I'd hoped.

My requirements were:
To display a build number from my CI tool, where the number was passed in on the command line. In Bamboo, for example you might configure a grails build as
-Dbuild.number=${bamboo.buildNumber} warTo only change build artifacts and not any source files.To not misuse the app version, or change the names of any artifacts.To be simple and idiomatic.I realized that that Grails itself changes the application metadata (appl…

Motivation Visibility, and Unit Testing

I've always been interested in organizational patterns (such as those in Organizational Patterns of Agile Software Development). I've recently found myself thinking a lot about motivation. I'm now reading Drive: The Surprising Truth About What Motivates Us and just finished Rob Austin's book on performance measurement. Being the parent of a three year old, I'm finding more and more that "because I said so, and I'm right" isn't too effective at home. My interests in motivation are closely related to my interest in writing software effectively. Writing software is partially a technical problem about frameworks, coding, and the like, but the harder (and perhaps more interesting) problem is how to get a group of people working together towards a common goal. Agile practices, both technical and organizational, build a framework which makes having the right amount of collaboration and feedback possible. But there's a bootstrapping process: How do yo…