In my last post, I walked you at length through the creation of a pretty simple task flow. It was exhausting! This time, I’m going to walk you through an even simpler one, but this one has a few interesting twists.

In this flow,, we’re going to design the Create Playlist module I talked about previously. If you recall, the final flow looked like this:

Image for post
Image for post

You see that box with lines down the side? That’s a module, and as I mentioned in the previous post, it indicates that a whole bunch of things are going to happen there. …


This is part 1 of the series. When you’re done here, read part 2!

In our podcast, Kate Rutter and I talk a lot about task flows and how helpful they can be when designing a product interaction. The problem is, I’ve rarely met a designer or product manager who understands how to make them well, and I haven’t found a very good guide to building them online. So, I guess I’m writing one? You’re welcome.

Please note, this post is not about how great task flows are or why you would use them. I’ll probably write that up later…


An unintentionally long episode about time estimates that proves that time estimates are bullshit. Also, Kate talks about her favorite drink recipe.

Drink Pairing: Old Fashioned

Listen to all of the What is Wrong with UX podcasts here now!

A sketchnote of episode
A sketchnote of episode


A little while ago, I asked a lot of designers what product managers did that annoyed them the most. For the sake of fairness, I also asked PMs the same question about designers. I thought maybe I’d get a few responses and write up a quick blog post about some of the worst offenders. I’m going to be honest here. I dramatically underestimated the number of responses I’d get.

This is the second in a series of blog posts covering some of the biggest mistakes product teams are making when it comes to collaborating and a few suggestions of how…


Recently, there has a been a big shift in the focus of Product teams from outputs to outcomes. In other words, some companies are starting to care a little bit less about the fact that a feature got shipped and a little bit more about whether that feature had a positive impact on user behavior and metrics. This is a great development. Shoving out 10 new features, none of which improve anything, seems like a fairly big waste of everybody’s time and money.

Unfortunately, a lot of teams find it hard to understand whether what they’ve built improved anything important…


Image for post
Image for post

Understanding the Business

One of the biggest complaints was fascinating, because I heard it from both PMs and designers. Designers complained that PMs were bad at understanding and describing the business case for features they were requesting, while several PMs complained that designers didn’t understand the company’s business.

Whatever you think about splitting up roles within a product team, most people agree that understanding and explaining the business side of a product is more the PM’s job than the designer’s. If they don’t understand the business or if they’re not sharing it in a way that helps everyone know what is being built…


Originally published at www.usersknow.com on 5/23/2016.

I’ve been thinking a lot about building better products lately. After all, I’m writing a book called Build Better Products, and it’ll be out this autumn, so I haven’t been thinking about anything else, really.

The hard part about building better products is often knowing what better means. This is especially true when building MVPs or first versions or experiments or whatever you want to call that thing that you put out in the world in order to see if anybody might care about it.

It’s even harder, I think, for designers, since many…


September 12, 2016 by Laura Klein

Once upon a time, I worked with a designer who refused to use any tool except Illustrator. Everything got made in Illustrator, whether he was building a visual design mockup, a task flow, or a discussion guide for a user research session (seriously). All of his deliverables were gorgeous.

He was also the slowest designer in history. Every single thing he did took five times as long as it would have taken anybody else, and much of it wasn’t very usable or useful. Pretty, though.

While the visual interface, if your product has one…


Image for post
Image for post

October 09, 2018 by Laura Klein

In this episode, Kate and Laura barely conceal their terror that they could be replaced by people with no skills or abilities whatsoever at any time. For once, they’re not wrong.

Drink Pairing: Mudslide (in honor of our newest patreon!)

You want a drink pairing of your own? Patreon us!

October 09, 2018 /Laura Klein Subscribe to What is Wrong with UX

Originally published at www.usersknow.com.


Image for post
Image for post
What is Wrong with UX

October 23, 2018 by Laura Klein

What is Wrong with UX is a podcast from Laura Klein and Kate Rutter! Check it out and subscribe!

Detours from the Happy Path Podcast

In this episode, Kate and Laura get all metaphorical about basic task definition and flows. Also, they introduce a drinking game where you have to chug every time they say “task flow,” so you’re going to have to sign a release saying the podcast is not responsible for your inevitable alcohol poisoning.

Drink Pairing: Preferably something that won’t kill you when you drink a gallon of it

Originally published at www.usersknow.com on October 23, 2018.

Laura Klein

Principal at Users Know & Author of UX for Lean Startups. I blog about UX, Research, Product Management, and Lean Startup.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store