Waking up from the dream of UX An Article by Peter Merholz www.petermerholz.com In no objective sense were things better for UX [in 2010]. Most companies didn’t know it existed. Most who did, drastically underinvested in it. Those who were willing to invest in it were savvy enough to listen to thought leaders, but that was a paltry percentage of the real work to be done. What’s happened by 2021 is that UX is not interesting in and of itself anymore. UX is a given. As Joe Lamantia said in a mailing list I’m on, “it’s furniture.” And the challenges and frustrations people are expressing are largely due to this maturation. We’re moving from “the dream of UX” to “the reality of UX.” Why I'm losing faith in UXUndoing the Toxic Dogmatism of Digital Design ux
Design Leadership Truisms An Article by Peter Merholz www.petermerholz.com PEOPLE ARE NOT THEIR JOB TITLES. TEAM MEMBERS ARE NOT “RESOURCES”. PEOPLE WORK BEST WHEN THEY CAN BE THEIR FULL SELVES. YOU CANNOT CALCULATE AN ROI FOR DESIGN. FRAMING THE PROBLEM IS MORE IMPORTANT THAN SOLVING THE PROBLEM. (DESIGN) LEADERSHIP IS MORE TALKING THAN DOING. YOU’LL DO A BETTER JOB IF YOU LIGHTEN UP IF YOU HAVEN’T PISSED SOMEONE OFF, YOU’RE NOT DOING YOUR JOB RIGHT. NO ONE OUTSIDE YOUR TEAM UNDERSTANDS WHAT IT TAKES TO DO GOOD WORK. THE OUTCOMES ARE BETTER WHEN EVERYONE IS A DESIGNER. AGILE TRANSFORMATIONS ARE HOSTILE TO GOOD DESIGN. WHAT A DESIGN TEAM NEEDS MOST IS A CLEAR SENSE OF PURPOSE. YOU ARE ON THE FRONT LINE OF A GLOBAL WAR FOR TALENT. EVERYONE APPLYING FOR A ROLE HAS AN INFLATED TITLE. INTERVIEWS ARE A POOR WAY OF ASSESSING CANDIDATES. DESIGN EXERCISES ARE A BAD INTERVIEWING PRACTICE. YOU WILL NEVER HAVE ENOUGH DESIGNERS. YOU WILL NEVER HAVE ENOUGH TIME. THE SKILLS THAT GOT YOU HERE ARE NOT THE SKILLS THAT WILL CARRY YOU FORWARD. Truisms designleadershipteamwork
Product vs. Feature Teams An Article by Marty Cagan svpg.com This article is certain to upset many people. Empowered product teamsViability, usablity, feasibilityWhat went wrong? featuressoftwareagile
Empowered product teams When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. What went wrong? teamwork
What went wrong? If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong. Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question. And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question. Viability, usablity, feasibility