But wait, isn’t everything we do for users? Nope! I’m really beginning to hate the term “user.” It has become mainstream. Much as we say “google it” when we mean “search for something on a search engine,” “user” has become synonymous with anything we do in the design/development/product world.
I think it’s fair to say that, in general, designers prefer a blank canvas—a fresh start. But that’s not always the case. Sometimes we have to take over legacy projects or step into projects that are ongoing. There are a few ways to make sure the engagement is positive for the client and fulfilling for […]
You’ve probably heard of the Netflix show “Tidying Up,” where Marie Kondo works with families to help them organize and declutter their homes. While watching the show, I couldn’t help noticing the parallels with software design.
I just returned from traveling and wanted to highlight some good design I saw: the mobile ticket display for Chicago’s Metra (suburb commuter) trains.
There’s a perceived divide between “traditional” designers (who work in print and branding) and software designers. But the reality is, most of us received the same foundational education and follow the same design principles. The tools and outcomes are often different, but the ingredients have a lot in common.
On a recent project, we had enough time to do a small user test, which got me thinking about the optimal time to get feedback. We discussed two options: at the visual design stage with a clickable prototype, or with a rudimentary minimal viable product.
Most designers would agree that in our day-to-day work of creating the next big thing for our business, we try to make all the right decisions. But, for one reason or many, we often fall short. On the way to making a brilliant idea, we get to almost brilliant. Almost.
I’ll admit it. I’m that designer. I’m constantly sticking my phone in peoples’ faces and exclaiming, “Look how cool this is!” But I’m never talking about a specific product or trending meme. I’m always talking about a unique and delightful interaction within an application—the thing that gives me the “warm fuzzies”—the microinteractions.
There have been numerous articles, and even a Wikipedia page, written about the value of pair programming in the Agile process. As the adage goes, two heads are better than one. But does the same hold true for software designers?
At some point in every project, we are asked, “How does this product/service create value for our customers?” or better yet, “How might we create value for our customers?” Customer Journey Maps are well suited to answer these questions.