Whole Product Thinking: Expanding beyond problem and solution space thinking (Videoconference)

Join us for this session with Sean McKay, Founder, Product Strategy & Design Consultant at Whole Product Thinking.

Why is it so hard to align everyone so we can deliver products that our customers love? It’s a question that will steal your soul (and your job) if you let it. I believe it’s more important now than ever that we transcend the nagging industry debates, power struggles, and process wars that are blocking us all from doing our best work for our customers. In this session, I’ll share a new “Whole Product Thinking” framework I’ve been developing. It’s intended to help structure conversations and align teams around the fundamental concepts needed to deliver human-centered products that are meaningful to users and effective for business. My approach centers on the ‘what’ and ‘why,’ deliberately separating the ‘how’ to allow organizations the freedom to choose approaches and methods that align with their unique contexts, development philosophies, and company culture.

Design Systems To-Go: Indigo.Design Overview and Exploring the Developer Workflow (Part 3)

A Design system is not only about standardizing the UI or accelerating design. In the big picture, it can streamline collaboration between design and development. With this goal in mind, an effective Design system is available to both designers and developers in a format that is native to each discipline. However, getting to this point takes time. But what if we can skip ahead with a starter Design system containing both design and coded components that are ready for use?

Join our activity sessions to see how you can transform your pixel-perfect designs into pixel-perfect code for modern web applications with Indigo.Design. We will also revisit the typical developer handoff by introducing a re-imagined workflow that minimizes rework. In the end, this approach can free up our focus to run Design-Ops better and deliver value sooner.

Part 1 (Thursday): Introducing a starter Design system, and Indigo.Design overview
Part 2 (Friday): Reimagining developer handoff, and introducing App builder
? Part 3 (Friday): Indigo.Design overview and exploring the developer workflow

C’mon Get Happy

Team happiness is an important and oft-mentioned DesignOps metric, but we need to reframe how we think about it. No human* can “”make”” their team happy, and it’s folly to measure ourselves by that impossible standard. But what we _can_ do is create opportunities for our teams—opportunities to get weird, share freely, give feedback, encourage each other, and create their own team culture. And they get to choose whether and how they take advantage of those opportunities.

*If you are a literal kitten, you may indeed be able to *make* people happy just by existing.

Design Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)

Part 1 (Thursday): Introducing a starter Design system, and Indigo.Design overview
? Part 2 (Friday): Reimagining developer handoff, and introducing App builder
Part 3 (Friday): Indigo.Design overview and exploring the developer workflow

Design Systems To-Go: Introducing a Starter Design System, and Indigo.Design Overview (Part 1)

? Part 1 (Thursday): Introducing a starter Design system, and Indigo.Design overview
Part 2 (Friday): Reimagining developer handoff, and introducing App builder
Part 3 (Friday): Indigo.Design overview and exploring the developer workflow

How Your Organization’s Generative Workshops Are Probably Going Wrong and How to Get Them Right

Generative workshops are a critical generative component of any product development process. But in my 20+ years conducting product user research, I have seen more product harm come from so-called “workshops” or “design sprints” than good. In this tutorial, I will share more about my experience and what I’ve found are critical components of generative workshops — whether they last five hours or five days.

Contrary to popular belief, a design sprint is a highly structured and carefully designed series of exercises, not a brainstorm, design jam or free-for-all. The whole point is to drive a cross-functional team to the right outcome, and this requires a set of structured exercises which weave the thread of user needs, behaviors and attitudes throughout. This involves more than reviewing the research at the start and then moving on to create without that research in context.

A true design sprint takes us from user insights — even broad user insights — to user-evaluated concepts or designs. The generative phase of a product is deeply impactful, and design sprints are a fantastic tool for driving this needed impact. However, many are practicing brainstorms or design jams rather than true design sprints. One can make a mismatched concept extremely usable throughout the product development process, but that will not remedy the fact that it is not the right concept.
Researchers are ideal design sprint organizers and facilitators, but researchers are sometimes not even considered a critical component of the sprint. It’s important for knowledgeable researchers to drive design sprint impact.

People, not Petri Dishes: Stories from a Research Recruiter (Videoconference)

Less than a year ago, we opened an in-house participant recruitment service at Atlassian, a 3,000+ employees tech company, for anyone who wanted to do research. During that year, the Research Recruitment team grew to two people and serviced over 150 people who do research. In this talk, I share what our main learnings were, the pitfalls of opening a free-for-all recruitment service, and some of my top participant recruitment tips.

Standardizing Product Merits for Leaders, Designers, and Everyone

There is nothing more frustrating than dedicating your blood, sweat, and tears to developing a product, only to see it shut down for no particular reason. We still lack standards for measuring potential opportunities and solutions—so leadership continues to base decisions on intuition, personal experience, and other factors that often barely correlate with success. Organizations large and small need agreed-upon measures of potential product-market fit for their concepts and solutions, ones that help establish unmet needs and lead to designs that users understand and want to use.

The DesignOps team at Athenahealth has solved this problem by creating a standardized measurement framework—including qualitative and quantitative instruments—that helps product teams measure their concepts and solutions early and often. These are measures that leaders can use to make informed investment decisions across the larger portfolio, and that free product teams to be awesome at what they do: designing, managing, and developing products that lead to better experiences for users.

The Trials and Tribulations of Directors of UX (Videoconference)

Directors of UX are navigating an overwhelming set of explicit and implicit expectations in their work, leading to frustration, anxiety, burnout, and leaving the field altogether. In this freewheeling discussion with guest Peter Merholz, organizational consultant and leadership mentor, we’ll address how we got into this situation (layoffs requiring those who remain to manage more people; botched agile transformations requiring UXers to lean into product management; immature organizations not knowing how to value the work), and identify paths forward out of this mess.

Design Ops Metrics

This session will detail how we are capturing metrics on product development and resource allocation. We will discuss how we are capturing people’s time on task to get us to a standard set of recipes that we can use when planning and budgeting for new products. We will discuss how we captured and identified tasks that could be handled by a 3rd party offshore vendor to free up our in-house designer who needs to be focused on strategic and innovative work.