UIE.fm Master Feed

Traditional marketing and communications often take the form of a one-way conversation. Things are put out into the market and it generally ends there. With the emergence of social media, a two-way conversation has also emerged. It leads to the opportunity for companies to sense what is happening in the market and respond to it. Jeff Gothelf and Josh Seiden previously co-authored the book Lean UX and in their latest, Sense & Respond, they investigate how companies can foster that two-way conversation. In particular, convincing companies that, no matter what industry they're in, they're software companies. In this podcast, Jeff and Josh share some of the highlights from the book and their research. Our hosts, Adam Churchill and Jared Spool dig into those highlights.

Art versus Science is the quintessential Left Brain/Right Brain cage match. But in reality, math factors into great works of art as much as developing a treatment plan for a patient could be considered the doctor's design. Andrew Shipe is a developer at MEDITECH, a company that makes Health Records software. Through his research he found that medicine can sometimes be as much art as science, a fact that was getting lost in the cold, analytical research data. He discovered that telling stories helped to span that divide in understanding. Kim Goodwin, Author of Designing for the Digital Age, joins us on this podcast to share her thoughts on Andrew's approach of using stories and how that is the first step down the road of scenario based research. Kim will also be teaching one of the full day workshops at UI22 this November 13-15 in Boston. For more information visit uiconf.com.

You can draw a direct line in the UX family tree from User Experience Design back to Human Computer Interaction. What if we could make the “computer” aspect of that interaction, feel less like a machine, and more like a human? Robert Sens, the Lead Product Designer of the restaurant reservation app, Reserve, sought to create a conversational user interface to help users get seated at restaurants. They settled on implementing a chatbot to simulate the interaction of speaking to a reservationist. Steph Hay, VP of Design for AI Experiences at Capital One joins us on this podcast to share her experiences in crafting conversational UIs and her insights into Reserve’s approach. Steph will also be teaching a full day workshop at UI22, November 13-15 in Boston on designing conversational UIs.

According to Heraclitus, the only thing that remains constant is change. The internet itself has evolved exponentially over a relatively short amount of time. Few relics from the early days of the web remain, and those that have, have been forced to change. Adam McClean is the SVP of Product at Dotdash. Dotdash was once About.com. The very same About.com that has been around for 21 years. Adam and his team were increasingly aware that the landscape around them was changing, and that they needed to evolve. They made the switch to a new brand, Dotdash, and a new process, to keep up with technological and market changes. Dan Mall, who runs SuperFriendly out of Philadelphia, joins the podcast to share his views on the evolution of dotDash’s process in support of their new brand. Dan will also be teaching one of the daylong workshops at UI22 this November 13-15 in Boston, MA. He’ll show how to develop workflows for the multi-device world we live in.

Project management encompasses an important set of skills, such as communication, planning, and forecasting. But does someone need the title of project manager to actually do the work? In Brett Harned’s book Project Management for Humans, he makes the argument that project management is always needed on projects but the role itself is less important. You should focus on the skills in order to manage projects well. In this podcast, Brett shares some of the highlights from his book. Our hosts, Adam Churchill and Jared Spool dig into those highlights, in particular, whether designers already possess the skills that project managers have.

Design systems can organize and clarify a team’s design practice. Made of patterns and component libraries, they add a level of cohesion across designs. This, of course, can only occur once you have a design system in place. So how do you build one in the first place? Nick Stamas, the Creative Lead on the Business Products Team at WeWork, set out to do just that. He surveyed WeWork’s existing designs, noting inconsistencies, and pitched the idea of a design system to help streamline the work being done. His challenge was building this all out while WeWork continued to grow. Nathan Curtis, author of Modular Web Design, has identified stages that occur when implementing a design system. He shares his insights into Nick’s story and how you go from building the system to working as a systems team. He will be joining us in Boston, November 13-15 to teach one of the daylong workshops at the UI22 conference. For more information, visit uiconf.com.

Storytelling is an essential form of human communication. You likely have a favorite story, something really memorable. The more that story is told and retold, the further it travels and the more influence it gains. A good story can be infectious. Stories can also come from unexpected places. LaiYee Ho is the Head of Research at Wink and joins us for this episode. Early in Wink’s research practice one story in particular resonated with the team that was uncovered during an in-home visit, the story of Dominic and Donna. That story spread throughout the organization and fundamentally changed the way Wink approached their products. Also on the podcast is Whitney Quesenbery, the author of Storytelling for User Experience. She shares her insights about Wink’s discovery and how storytelling can be one of the most powerful research tools. Use the power of storytelling as a UX strategy during our Creating A UX Strategy Playbook workshop.

There’s a stigma surrounding meetings. They’re often seen as unproductive wastes of time. But in Kevin Hoffman’s view, meetings are actually a design problem. In his upcoming book, Meeting Design for Managers, Makers, and Everyone, Kevin lays out strategies to make meetings better for all those involved, making them gateways to success. In this podcast, Adam Churchill and Jared Spool discuss some of the highlights from Kevin’s book.

Empathy. It’s an unavoidable word in the world of user experience design. Too often it is applied to designs in too narrow a fashion. Your empathy should come from the problem your design is solving, not measured in the level of frustration or delight experienced with your design. Ariel Kennan is the Director of Design and Product at the New York City Mayor's Office for Economic Opportunity. She has been working on the HOME-STAT initiative which is an effort of the City of New York to properly provide services to the city’s homeless population. In this episode, Ariel shares her story and is joined by Marc Stickdorn who offers his insights on how service design can be done on such a massive scale. Marc is the CEO and co-founder of More Than Metrics and author of the book Service Design Thinking. He will also be teaching a daylong workshop at the UI22 conference in Boston this November 13-15. To find out more about his workshop, visit uiconf.com.

We often talk in terms of silos in organizations, where information isn’t readily shared and communication leaves something to be desired. Another way to think of a team who is heads-down working on the overall journey is to imagine swim lanes. Each department is so focused on their own part of the experience that they might not be fully aware of each step a user has to go through to complete the journey. In this episode, Conor Ward, Head of UX and Design at Centrica & British Gas, tells a story of how mapping out the journey to acquiring a quote for boiler insurance revealed some unexpected insights. Jim Kalbach, author of Mapping Experiences, also joins the podcast to share his expertise on the subject of journey mapping.

Sometimes, the world of user experience design requires creative solutions. There are numerous methodologies and an even greater number of myths about where and when they are supposed to be used. Lean UX is one such process that is associated mostly with startups and very early stage projects. But what if you were to apply Lean UX to an existing site? And what if that site was a multinational industry-leader with millions of users? In this episode of the UIE Podcast, Austin Knight, Senior UX Designer at Hubspot, discusses how the Hubspot team employed Lean UX to tackle their website’s redesign. Jeff Gothelf, the co-authour of Lean UX and Sense & Respond, joins us to offer his insights on Austin’s efforts.

Much like superstition, something that is believed to be an important metric may not apply to the reality of your product or service’s experience. Understanding the behavior of your users, introducing some science, is what leads to greater context and insight. In this episode of the UIE Podcast, Chris Callaghan of McCann UK talks about his experience of joining a team and seeing the superstition first hand: A roomful of folks attempting to derive meaning from numbers, but having the same conversations over and over. Straying from superstition and introducing science started with the simple question: “do we know if anyone outside of this room can use this?” Kate Rutter joins us to help dispel some of the myths surrounding analytics and offers insight on how to come to true meaning.

If we keep adding functionality, we start to clutter our enterprise application’s design. That clutter can create a substantial burden on the user while obscuring the functionality we want them to use. In this episode of the UIE Podcast, Amanda Linden talks about her challenge of fighting back clutter in Asana’s design. Hagan Rivers talks about her techniques for helping enterprise app teams deal with the issue of clutter.

When we’re training teams on our design methods, what we perceive as ‘proper’ may in fact become a hindrance. Our dogmatic approach to our processes may prevent people from ever employing the techniques. Is it better to do it the right way, or to teach a wrong way that will get the job done?

You’ve got a groundbreakingly innovative product idea, and you’ve assembled a crack team of designers. You know exactly what you want to do, but you’re unsure of how to do it. Without a framework to drive your product development, it’s Game Over.

Mobile, ambient technology, and connected devices are about mediating people’s behavior in their environments. Uncovering the whys and hows that drive behavior takes empathy, hours of observation, and masterful prototyping skills. You’ll succeed when you make, test, iterate, and learn.

Design leaders are unsung revolutionaries. They’re often at the forefront of culture change, advocating for a new conversation about creativity and quality. The old one involved meetings, presentations, and top-down mandates, and little to no input from customers.

Creativity isn’t just about expressing yourself. It’s also about solving problems by putting disparate pieces together to form a new, unique whole. Practical Creativity fuels the everyday work and once-in-a-lifetime breakthroughs of designers, engineers, and scientists.

The only job of application navigation is to get users to the right screen. Ideally, all of your users should find what they need in 10 seconds or less, and with only a few clicks. But many enterprise app navigation systems fall short. If you’re facing a much-needed nav overhaul and don’t know where to start, it can be overwhelming.

For the longest time, making a great experience for the user was a business-strategy luxury item. A great product only had to work and ship. A great experience was a nice-to-have, not a requirement. Times have changed. The cost of delivering a product is no longer a barrier to entry. Quality is no longer a differentiator. What’s left? The user’s experience.

Products and service designers deal with complex design problems in equally complex markets. It’s hard to know which solutions are winners and which ones will fail. Fortunately, you can use simple design insights from biology to eliminate doubt and risk, and prepare you for whatever comes your way.

Corporate life expects us to be experts, to know the answer to every question. We make “requirements”, which turn out to really be assumptions, but because we never call them assumptions, we never go about testing them. This is as much a social political issue as anything. The higher you are in the organization, the more you’re expected to just know the answer. In this episode, Jared and Richard Banfield explore the role of design sprints in cultivating an environment where it is ok to say “I don’t know”. Allowing yourself to admit this, and allowing your teammates to as well, leads to greater collaboration as you explore the answers together.

Storytelling is a powerful way to measure our understanding of our users and their experiences. But unfortunately, we don't always get the story right. User experience rests more on listening to what the users want to tell us rather than the stories research teams and designers tell themselves within the confines of their organizations. Perhaps it’s time to first try story listening before recanting the tales. In this episode, we hear a story from Mike Monteiro about design going wrong. Jared Spool then talks to Marc Rettig about how the team could employ a technique, the Collective Story Harvest, to take apart the problem and come to new insights. All by listening to a story.

The challenges we have ahead require top talent to execute. Design leaders, who could lead our organizations to new heights, are a rare gem to find and recruit. A designed approach to hiring will change the caliber of your team. From first contact through the candidate’s start date, the hiring process needs to be thoughtfully designed. You’ll see a performance-based talent system that replaces the talent repelling old-school HR processes.

Creating a culture of design is a special case of “organizational becoming,” touching teams, processes, and the delicate and difficult areas of culture and identity. Few of us feel equipped for such work. But “social technologies” are appearing to help us manage cultural emergence. Weaving theories of change with the nitty-gritty of daily life, Marc uses stories from organizations large and small to describe the ways and wisdoms of becoming an organization that embraces design.

Adam Cutler explains how his team has built up the IBM Design organization, delivered a new design system, and created studios all over the world to tackle the world’s toughest enterprise user experience challenges.

Dana Chisnell and Dean Logan discuss the unique challenges of bringing UX into the government sector and how some things they learned can benefit the private sector.

When your user gets value from your design, they’ll likely make using it into a habit. They’ll keep coming back, forming more habits as they continue to get results. When we add new features, we often force them to break the habits they’ve carefully formed. That’s what makes our users upset when we change the design unexpectedly. Their old habits no longer deliver the value they once did, and now they have to form new ones. In this episode, Jared learns from Amy Jo Kim how game designers approach the problem of introducing new levels, weapons, and other features. Amy Jo shows how the way game designers think can be easily applied to your designs.

Karen Pascoe provides an example of what sweeping corporate change can look like when a company like MasterCard puts creativity, innovation, and its users at the top of its priority list.

Gina Villavicencio and James Nixon discuss Marriott’s efforts in ensuring their brand isn’t lost across cultures, and how the organization is shifting to a more global perspective and locale-specific user research.

There’s a saying that you can’t know where you are going unless you know where you come from. Designing navigation for enterprise applications is a journey unto itself. One that UX Immersion speaker, Hagan Rivers is quite familiar with. In this podcast, listen as Jared Spool discusses the importance of clear navigation systems in enterprise applications with special guest Hagan Rivers. They explore techniques for tackling complex navigation, how screen codes are perfect for those with in-depth experience, and how a balance with ease-of-learning is critical. When you’re sitting face to face with the wilderness that is an enterprise application, a map and compass would serve you well. Unless you’re a tracker, know which side moss grows on a tree, or can follow the stars, you’re likely not going to be able to navigate through on your own, much less find shortcuts and become proficient.

Bill Scott examines what it took to win buy-in from executives, bolster communication, and push boundaries as he led a remarkable transformation in Paypal’s corporate structure.

Enterprise applications are massive, often unwieldy pieces of software. You get a sense they were never truly improved or updated, they just had a continuous string of features tacked on until it got to the point where they are almost impossible to use. And they’re old. This focus on features let design fall to the wayside, making it less important than the application’s perceived capabilities. Now, you’re forced to stare at a screen straight out of 1995. You’ve become a time traveler, whether you were aware of it or not. We’ve come across other time travelers in our journey. You aren’t alone. One such person is Hagan Rivers, who has worked tirelessly to bring these enterprise applications into modern time, if not the future. In this podcast, listen to Jared Spool weave a tale of time travel with special guests Hagan Rivers and Dana Chisnell.

Organizations need to approach every problem and decision from a design viewpoint. Jared connects the UX Advantage themes together to form a framework for how we tackle the amazing challenges ahead of us. Using his entertaining storytelling style, Jared weaves together the threads of what was heard throughout the conference. We’ll look at how to rethink the way we structure our teams, how they collaborate, and the implicit and explicit rewards that drive their achievements. Organizations need to approach every problem and decision from a design viewpoint. Jared connects the UX Advantage themes together to form a framework for how we tackle the amazing challenges ahead of us.

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.

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.”

The notion of being a “designer who can code” has been a prevalent topic in recent years. Delivering static PDFs and working in photoshop is seen as inefficient in some circles. Being able to create a clickable or even responsive mockup to present to developers and stakeholders can be a better way to show your intent. It’s also much easier to iterate by changing a few lines of code.

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.

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.

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?

There are always burning questions about how to get organizations to be more design-centric and what better way to learn than from someone who has done it. Marc Rettig has been helping organizations make the transition for 30 years. In this podcast, Karen McGrane shares why he was chosen as one of the keynote speakers for UX Advantage.

The belief of public failure or marketplace irrelevance can drive an organization to change. How does a UX leader exploit this corporate fear? What transforms the momentum from fear into positive change within the organization?

Usability in products and websites is what most organizations strive for. The more usable the product, the more likely that people will use it. Through research and testing, you can root out many issues with clunky interactions that hinder the experience. What isn’t as immediately clear is if some perceived usability issues are actually understandability problems. Your content could be the culprit.

When some people hear the term Lean UX, they dismiss it as simply a nouveau buzzword. There can be some confusion as to its relationship to Agile, both the methodology and the adjective. Some of the biggest resistance came from the idea that Lean UX was shortcutting and lazily undoing much of the groundwork to get organizations to buy into the value of UX. But as waterfall development increasingly becomes “the old way” of doing things, teams are operating in more agile, or Lean, ways.

Product Managers are responsible for the success of a product. As we’ve seen, UX is not misaligned with business goals, in fact it helps achieve those goals. If UX has become a necessity in terms of a driver of business, product managers need to adapt to it. Those who have a respect and understanding for the value of UX, and incorporate it into their product strategies, can better serve their users and customers, as well as the business.

Traditional organizational silos are the nemesis of delivering great experiences. How do you scale multidisciplinary teams to enterprise size? Does a culture of design require a fundamental structural shift in how the organization operates?

Organizational change must be top down and bottom up. How do UX and design leaders influence the way executives make product and technology decisions? What defines true support as opposed to just lip service to a great experience?

Does moving to a design-infused culture mean that outside agency support is no longer valuable? What need does an outside viewpoint fill for design-led organizations? Or are agencies shifting to being an acqui-hire talent pool?

Global organizations can no longer project their corporate views of a customer experience upon a multitude of cultures. How do you embed the nuances and subtleties of each culture into a familiar experience regardless of where you are in the world?

It’s no secret that the content on your site needs to adapt to a variety of viewing environments. Responsive and Adaptive Design have been wonderful for ensuring your design flows and displays appropriately for the multitude of devices out there. But what about your content? How can you be sure your content is in the right place, or even makes sense in these different contexts?

What does it take to create a culture of design? How does putting user experience first change the way organizations work? Those are the questions being addressed at the UX Advantage conference. Jared Spool and Karen McGrane will be your hosts as they delve into a series of topics with top design executives. In this podcast, Jared tackles two of those topics, Inventing the Yes Lawyer and Restructuring Incentives and Rewards.