Archive for the 'Design Strategy' topic

How Are You Getting Your Team on the Same Page?

While developing the topics and workshop leaders for this year’s User Interface 20 Conference in Boston, November 2–4, I realized that a general theme was emerging—getting everyone on the same page about your designs. Here’s how each workshop at UI20 contributes to this theme: Marc Stickdorn’s workshop on Service Design: Creating Delightful Cross-Channel Experiences is about […]

Aligning Your Team with Design Systems and Style Guides

Nathan Curtis, co-founder of EightShapes, has worked with component libraries and style guides for years. He says that when you’re thinking about all the platforms that comprise the totality of an experience, these patterns (such as a sign-in form, or elements like buttons) need to be more broadly applicable. It’s one thing to create the […]

Using Journey Maps to Visualize the Path a Customer Takes

Communication is at the heart of service design and Marc Stickdorn knows the core of it is getting everyone on the same page. He says that the importance of this lies in the fact that customer experiences sometimes aren’t tangible—a user or customer could be experiencing an internal event. It’s important to understand how different […]

Help Designers and Developers Learn to Understand Each Other

The notion of being a “designer who can code” has been a prevalent topic in recent years. One of the greatest benefits of using CSS is speaking the same language as your developers. Having this common language aids in creating a more collaborative feel to conversations with developers versus dictating to them what to do. Being […]

Erika Hall – Cultivating Shared Understanding from Collaborative User Research

Traditionally, user research has taken on more of a scientific identity. You would do usability testing and research, take a ton of notes, and then compile all of your findings into a report. The effectiveness of that research depended on whether anyone read the report, and then if they could do anything actionable with that data.

Nathan Curtis – Building Scalable Design Systems and Style Guides

The expansion of the web past a desktop-based world into more of a multi-device ecosystem has caused organizations to re-evaluate almost everything they do. Style guides have had to grow to accommodate this new reality of multiple screens sizes and resolutions. When you start incorporating the multitude of products across devices and all the people working on them, organizations are forced to think more “systematically.”

UIE Newsletter: Preparing Organizations to Become Design-Infused

In this week’s UIE newsletter, I define a design-infused organization as one where every decision is made with design at the forefront. Here’s an excerpt from the article: It takes a long time to become a design-infused organization. Many have yet to make the transition. Some organizations are approaching it. These organizations value design enough […]

Kim Goodwin – Using Scenarios to Solve Problems

Understanding is what user experience as a field hinges upon. After all if you don’t understand how users are interacting with your product or service, you don’t know what to design for. But how, as a team, do you come to that understanding? Telling the story of a user’s journey highlights areas where you’re right on point and where you’re missing the mark.

Marc Stickdorn – Service Design: Creating Delightful Cross-Channel Experiences

Service design seems to go by an increasing array of names: Customer Experience, Cross-Channel UX, or even just “design thinking.” In most cases, these terms describe a holistic approach to your users’ and customers’ needs, no matter where or when they’re interacting with your product or service. In traditionally siloed organizations, it can be no small task to ensure that you are providing the best possible service.

A UX Advantage Podcast with Karen McGrane: Shifting To Continuous Deployment

The speed of Agile delivery fundamentally changes the work process and puts new demands on the design cycle. What happens when the notion of deadline dates is replaced with a continual stream of experience enhancements by everyone in the organization?