On June 23 I’ll be giving a presentation at UXPA Cleveland on the onboarding user experience. Talk title is “How Not To Suck At Onboarding: Patterns and Anti-Patterns Explored” and I’ll be, well, here’s the blurb from their event calendar:
What’s with the relative lack of love for user onboarding among UX practitioners? So many of us researchers and designers focus on creating great product and service experiences, yet we often give scant attention to one of the most important parts of the user experience: the critical phases between the time when someone first installs or signs up and when they’ve incorporated your offering into some aspect of their life.
Paul Sherman will provide you with ammunition you can use to sell the value of user onboarding design in your organization, as well as sharing some great, good, and not-so-good examples of user onboarding experience design from around the web and mobile.
If you’re near Cleveland on June 23, stop by!
A few months ago I updated and released a process guide for implementing a rapid contextual innovation program. Because I value open culture, I’ve released it under the Creative Commons Attribution-ShareAlike 4.0 International License.
The guide includes an overview of how organizations can conduct ongoing rapid innovation using UX methods and product management best practices. As you might expect, the process guide incorporates some concepts covered by Lean and Agile UX proponents.
Get it here: Rapid Contextual Innovation: How To Start And Run A Customer Value-Driven New Product Development Program
There’s currently 850+ answers on Quora to the question “What are some examples of bad design?”
Need bad design examples? This is the place to go.
Sarah Bloomer, founder of UX Managers Circle, just published my article on using UX research methods to set up and drive rapid contextual innovation programs.
This is basically a continuation and expansion of the topics I covered at the UX Strategies Summit in June. My main point, and I’m quoting myself here, is this:
UX techniques such as contextual inquiry can be adapted and expanded to become the basis for observation-based customer value discovery and innovation development.
Enjoy and feel free to reach out to me with comments.
Over the past few weeks I’ve been saving up some UX-related articles to read later.
On the theory that I’ll actually follow through if I publicly commit to it, here’s what I’m fixin’ to clear off my guilt pile this week:
While reconnecting with my colleague Jan Moorman, now a UX researcher at Walmart eCommerce, I found an article she and another practitioner wrote about personas. The main points definitely bear repeating:
- Half-baked and research-free personas can do more harm than good.
- To be truly useful, personas should be based on actual research and should focus on “goals, motivations, and expectations.”
- Ground your personas with (relevant) details from real users.
- Evangalize your personas.
Regarding points 2 and 3: I’ve always felt that personas containing extraneous personal detail (“Dale is a yoga practitioner who likes skeet shooting and extreme chess and dotes on his 3 bichon frise puppies”) can actually be off-putting instead of empathy-generating. And I’ve also strived to annotate my personas with user profiles to connect them to the raw data. So I was pleased to see them advocating for this as well.
As far as evangelizing personas…well, you’re reading the blog of a guy whose UX team at a former company laminated their user personas and distributed them to the executive team. So yeah.
Love, Hate, and Empathy: Why We Still Need Personas :: UXmag
I was fortunate to be asked to run a half-day workshop at the UX Strategies Summit this week. The goal of the workshop was to provide attendees with perspective and tools to take a strategic approach toward embedding user experience practices and processes more deeply into their organizations. Enjoy.
I just finished presenting at the 2015 UX Strategies Summit on how UX, product and development can work together to identify and prototype new product opportunities. Enjoy.
I’ve updated the UX Kit with some good stuff. What’s new? How about:
- Updated all the UX position descriptions.
- Added two new position descriptons – UX Strategist and Content Strategist / Information Designer.
- (At long last) Added a section discussing how UX and Agile processes can work together.
- Updated the salary info per the 2014 UXPA Salary Survey.
I also updated the Creative Commons license to Attribution-ShareAlike 4.0 International. Which means all this sweet sweet content is yours to use and modify as you see fit.
Please enjoy and share.
I’m excited to be speaking at the UX Strategies Summit, coming up June 9-11 in downtown San Francisco. I’ll be running a workshop and giving a talk. The workshop is almost full – 8 seats left – and I’d love to see you there.
Workshop: Embedding UX Processes Within Your Ideation, Design, Dev and Release Cycle
Description: The war is over, and UX has won. Thanks to the ubiquity of easy-to-use web applications and mobile apps, everyone from C-levels on down recognize that good user experience design is now just table stakes. It’s part of the cost of doing business.
However, as the saying goes, you can win the war but lose the peace. Even with the best of intentions, many organizations still don’t know how to effectively incorporate UX processes into their product life cycle activities. And they’re looking to you for leadership, UX practitioner, product owner, scrum master, or whoever you are!
In this workshop, we’ll work on:
- How to identify and cultivate UX champions
- How to leverage small tactical UX wins to drive toward a strategic UX approach
- How to get the right UX activities embedded into the right places in your organization’s product life cycle…without giving your stakeholders sticker-shock (or project plan conniption fits)
Talk: Decision Insurance: Iterative Prototyping To Reduce Business Risk
Description: As UX professionals, we appreciate the value of iterative design. After all, who doesn’t want user feedback on a new design or a redesign? It helps us understand where our designs hit the mark, and where we might’ve missed a key user need or misunderstood something about the users’ mental model.
But there’s a whole other level to iterative design: the reduction of business risk. One of my mentors, a VP of Product Management at a former company, asked me why he should let my team take two weeks out of the schedule to test and revise a design in prototype form. I told him our typical UX justifications. When I was done, he looked at me and said “I get it now. You’re my decision insurance. If we make a product decision, you can test it before release.”
In this session, you’ll learn how to position iterative design and testing as a risk mitigation strategy.