How Traditional Design Principles Apply to Software Design

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. Read more on How Traditional Design Principles Apply to Software Design…

The Macro Impact of Microinteractions – Making Users Happy

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. Read more on The Macro Impact of Microinteractions – Making Users Happy…

6 Benefits of Pair Design for Software Designers

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? Read more on 6 Benefits of Pair Design for Software Designers…

How to Make a Customer Journey Map for Experience Design

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. Read more on How to Make a Customer Journey Map for Experience Design…

A Tale of Two Approaches to Innovation – IxD vs. Proto/Test

“So you can’t go out and ask people, you know, ‘What’s the next big thing?’ There’s a great quote by Henry Ford, right? He said, ‘If I’d have asked my customers what they wanted, they would have told me ‘A faster horse.’” – Steve Jobs, 2008

This quote from Steve Jobs was very much on my mind this summer when Alan Cooper sent out a series of tweets about differences between interaction design (IxD) and the prototype/test/learn (proto/test) approach to product development.
Read more on A Tale of Two Approaches to Innovation – IxD vs. Proto/Test…

Design Thinking and Atomic Project Leadership

IDEO sees design thinking as three lenses through which we can view design: desirability (human), viability (business), and feasibility (technical). Atomic’s project leadership roles (Design, Delivery, Development) share a significant alignment with these dimensions. That alignment strengthens our long-held belief that everyone on the team has a place in the design conversation.
Read more on Design Thinking and Atomic Project Leadership…

Should UX/UI Designers Code? Finding a Balance Between Yes and No

“Should software designers code?” I have heard this question asked over and over again within the design community. There’s not a definitive answer, but if we extrapolate the question and ask it in a few different ways, I think we can better understand the role a designer plays in writing code for projects. Read more on Should UX/UI Designers Code? Finding a Balance Between Yes and No…

“Most Advanced, Yet Acceptable” Software Design

Ever had a refreshing ice-cold Mexican Coca-Cola in that sweet glass bottle? The bottle just looks and feels right. Now close your eyes. Imagine the Shell Oil logo. It became so iconic that the company dropped its name from the displays at their filling stations. What about the fuselage of Air Force One? It pops instantly into mind, right? Anyone who has ever been to Johnson Space Center in Houston will also remember the interiors of Skylab and the Apollo moon mission capsules. All these objects are the work of one man: Raymond Loewy. Read more on “Most Advanced, Yet Acceptable” Software Design…