By
Download on the App Store

episodes

  • Panel: The Secrets of Master UX Consultants
    Being a design, IA or UX consultant is hard. Most new consultants struggle just to stay busy. In this panel, expert practitioners will share their wisdom on what it takes to be a master consultant. Panelists with many years of consulting experience will share their insights on winning engagements, dealing with clients, and the different skills needed for internal and external consulting.
    If you’ve polished your UX skills extensively, but are struggling with clients or internal stakeholders, this session will provide insights into the consulting soft skills you need. We’ll share our secrets to help you become a more effective leader and a happier consultant.
    Session Takeaways
    Attendees will learn tips and trick for consulting from the multiple perspectives of each panelist. They may not always agree.
    Here are some examples:
    Consulting is about delivering – be clear about your deliverables – if you’re just offering “advice” clients will have a hard time seeing your value after you leave.
    Don’t do the hard work of writing a proposal until the client already knows your planned approach and has agreed to a ballpark budget. The work should be mostly sold before you write up what you’ve already talked about in the proposal.
    The roles of internal consultant, external contractor, and external consultant are all very different. Each of these roles requires different behaviors. For example, as an external consultant, you need to be able to effectively “project manage” your work and hold clients accountable for their action items, while as an internal consultant or contractor, you’re often part of a larger team managed by the client. If you’re not good at managing projects…take note. On the other hand, as an internal consultant, you must be great at navigating the political waters of the organization.
    External consultants need to HAVE A CLEAR RECOMMENDATION. Don’t be wishy-washy (saying “it depends…”) or give clients too many options. You need to be an expert. That’s what they hired you for. But that doesn’t mean you have all the answers.
    41 min
  • The Art and Science of the Pre-Attentive Variable
    It’s been used to explain everything from love to racism, but in actuality, the pre-attentive variable is a powerful concept that belongs in every information architect’s toolkit. Rooted in cognitive psychology, pre-attentive variables are elements that operate on a subconscious level, conveying information to users before they’re even aware of it. Pre-attentive variables can help users tell which articles are the newest, which videos are the highest rated, and which books are the most popular before they even start actively processing the information on the screen.
    This presentation will cover the basics of pre-attentive variables – what they are, why they work, and when to use them – and will provide an overview of some design patterns to use when creating them, including:
    Size
    Shape
    Color
    Texture
    Prominence
    Focus
    Orientation
    Density
    Participants will learn how to identify and analyze the effectiveness of these variables in existing interfaces, as well as how to design them for new experiences they create.
    Session Takeaways
    Pre-attentive variables are elements that subconsciously communicate information to users, before they have even started processing what’s on the screen
    Pre-attentive variables help IAs organize, prioritize and classify information for users in a meaningful way
    Some top design patterns for pre-attentive variables include size, shape, color, texture, prominence, focus, orientation and density
    Pre-attentive variables can be used for good, to influence positive user behavior, and for evil, to manipulate users against their will
    16 min
  • IA in a Complex Business Context
    How do you address user goals when your users seem to speak a language of their own? How do you stand up for users when developers dominate the process? How do you engage stakeholders to turn them into evangelists? How do you make sure everyone really understands and agrees on what you’re doing
    In this talk, you’ll see how we rescued a project that was about to go off the rails and in doing so, answered all these questions and more. It will leave you with specific, actionable advice, illustrated with examples from this project, about how to get to meaningful consensus in a project and develop, test, and socialize your IA deliverables.
    Session Takeaways
    How to plan user research to quickly master a complex business context and socialize the project before it’s even finished.
    The importance of designing and testing one thing at a time, and how to structure your deliverables to do it.
    Strategies to get to meaningful consensus that are about process, not personalities.
    20 min
  • Defining the Damn Data
    Building Consensus Around the Meaning of User Behavior
    Task maps. Customer journeys. Cognitive walk-throughs. All are artifacts of our process of seeking understanding about our users that we likely create on a regular basis. But how can we better connect that work to the process of web site data collection and analysis?
    In this talk I’ll show how we can adapt our existing process and artifacts to drive the definition of what user data we need to collect, as well as how to better analyze and validate what we do, including:
    Using existing site analytics to set a behavioral baseline.
    Defining what we want to measure based on task maps and other UX artifacts.
    The result? A shareable document that can be used to tell the evolving story about our users as we continue to learn more about them through data.
    Session Takeaways
    Defining data we need to collect to validate business goals/direction
    Using task maps and customer journeys as the blueprint for both in-page interaction patterns and site navigation paths we want to track and measure
    Applying behavioral data from a newly-launched product to those same task maps and customer journeys as a way of telling an updated story about our users
    21 min
  • Design Doing: Creating a Digital Practice
    This practical case study takes its lessons from how my company is transforming our service delivery and, incidentally, creating a fantastic way to work. In my session I’ll walk through the key conceptual and practical aspects of bringing “design doing” into a consultancy setting. Results so far include new processes, new and participatory types of client and team engagement (such as the project Hack Day and Innovation Mining), and wider adoption of tools for design thinking (like Journey Mapping, Business Origami, and Content Modeling). The point of the session is to deliver beautiful ideas, some familiar, some new, in a down-to-earth package that practitioners, managers, and business owners can adapt to fit their own situations.
    Session Takeaways
    * A framework for building a transformative way to work
    * Concepts and a kit of tools that can be applied, adapted, invented, and reinvented
    6 min
  • Learning from Users in their Natural Habitat
    One of the shortcomings of user interviews is the vast gulf between what people think they do versus what they actually do. Fortunately, a new generation of digital research tools are filling that gap by allowing users to provide quick feedback via their smartphone right after using a product. This allows rich details to be captured that might otherwise have been forgotten. These tools are breathing new life into a traditional research tool, the diary study.
    This talk shares best practices for creating a digital diary study that collects relevant and insightful data. It will be framed by examples from a recent digital diary study I conducted that explored how people use their fitness trackers (Fitbit, etc).
    Attendees will come away with not only an understanding of the kind of rich data that can be collected this way, but the basic knowledge needed to create their own digital diary studies.
    6 min
  • DesignOps Skunkworks: Shoes for the Cobbler’s Children
    We’ve all worked at places where there’s never enough time to make sure that things are operationally done the “right way”—bills need to get paid, client or product/project work needs to get done and takes priority, and hey, everyone deserves to have a life, too. There is light at the end of this tunnel! Several companies, including Atari, Ford, Microsoft and Google, have pulled off some great things by taking advantage of skunkworks teams and projects. I’ve been fortunate enough to see some successes with those teams and projects, as well, and will share them so you can see how to apply the approach(es) to your own practice.
    Way back in the 1940s, Kelly Johnson and his team of mighty skunks used their Skunkworks process to design—and build—a prototype jet fighter in 143 days. Kelly established 14 Rules and Practices for Skunkworks projects in order to help articulate the most effective way for his team to be successful in the projects that they worked on. Not only can we learn from Kelly’s rules and adapt them to our current methods of working, we can also create our own skunkworks teams and projects to ensure that the Cobbler’s kids—the operational areas of our design practices—get some shoes put on their feet. And the results might just smell pretty good, if you’re patient enough.
    Session Takeaways
    What is this Skunkworks thing you mentioned?
    What are Kelly Johnson’s Skunkworks Rules and how can I apply them to my design practice?
    What have other companies done that are considered skunkworks and how were they successful?
    How can skunkworks be used in our current work practices?
    How can skunkworks be used to help accomplish the ever-growing stack of non-priority (yet still very important) projects that are important to me and my team?
    18 min
  • The Politics of Navigation
    For years, REI.com’s global navigation existed in a relatively stable equilibrium. It balanced the need to sell products and services, provide access to educational content, and inform visitors about unique aspects of the company. But a recent agency-led redesign threatened to disrupt this stability. Suddenly, a whole host of assumptions around the proper role of site-wide navigation were exposed. As REI’s in-house IA, I had a front row seat to watch merchants, marketers, designers, and business managers wrangle over their competing expectations of REI’s global nav. My job was to influence opinion and try to restore a healthy balance in the navigation while still supporting a new design direction for the site.
    This talk will be a case study of the unexpected political struggles that were revealed during the design process. I’ll attempt to fairly portray the full range of perspectives on global navigation, from customers to business owners, from agency designers to in-house designers, from accepted practice to emerging trends. I’ll talk as candidly as I can about the discussions that took place throughout the redesign process, and where we landed on some fundamental questions about navigation: Who should we design for? Who should care about the global nav? And, particularly, what is IA’s role in the creative process? In short, when politics enter the design studio, who wins?
    38 min
  • Archaeology & IA: The Adventures of Information Jones
    During my previous career as an archeologist, I studied people I couldn’t talk to in order to learn how they interacted with the world around them. As a User Experience Analyst, I now study people I can talk to and learn first hand how they interact with their environments.
    In this presentation, I will bring my interdisciplinary perspective to life through a case study of the FCC.gov redesign, demonstrating how my experience as an archeologist made this daunting task doable.
    In 2014 we began the research process for redesigning the Federal Communication Commission (FCC) website. The project included intensive research and restructuring of the site. We dug through layers of data and content making fascinating discoveries along the way.
    The understanding and research that goes into information architecture is not unlike what goes into the study of an 18th century farmstead. Both disciplines use maps and collect artifacts to create a story of people and information. Using the right methods, you can get the job done with more ease than Indiana Jones.
    Every step during the FCC project can be reframed through the archaeological process. The parallels can help you prepare for IA research with the mindset of a historian or archaeologist, expanding your approach and enhancing your skill.
    Session Takeaways
    Be a historian: Gather historical materials relevant to the site and talk to the locals when you can
    Survey the area: Have a standard method to your research, this helps you determine when you need to go back and investigate an area further
    Dig deeper: Determine where you need to analyze more
    33 min
  • The Anatomy of a Content Model
    With the rise of responsive design, a content model and a CMS are necessities for any content-rich web presence. Once you’ve designed the front-end user experience, it’s important to consider the content structure that will support your design. Content models define:
    the underlying structure of each type of content
    the user experience for content authors and editors within the CMS
    Luckily, designing a content model is a natural extension of IA for a front-end user experience. In this talk, we’ll get into the details of HOW to content model. We’ll dissect the content model for a single content type for a nonprofit website. The goals for this content model were:
    to be adaptive and portable for any device or context
    to contain a lot of content, yet display it in a simple way
    a successful user experience for administrators creating and editing the content
    a delightful user experience for end users of the content
    In content modeling, there are often multiple approaches you could take so I’ll also cover the alternate models we explored and describe the process that led us to our end result.
    Session Takeaways
    Define a content model
    Evaluate a content item and create a content model based on that item
    Learn best practices for adaptive content models
    21 min