Software development methodologies often lack the details of how UX fits into projects. Some suggest that a Product Manager describing features is enough for developers, UX should train others to do their specialized jobs, or excluding UX experts solves them being “too siloed” and “not collaborative.” This happens with no (other) role in software dev; it’s hurting culture, efficiency, and productivity, and creating poor products for customers.

Your customer only sees your UX, not 1000 developers or if you were Agile or Lean. Companies are figuring out that UX specialists and the User-Centered Design process are good investments that more than pay for themselves. Recent highly-publicized UX failures remind us that skimping on the UX process can alienate customers, create negative media attention, and burn millions of dollars.

Saying "UX" is like saying "Engineering." There are multiple phases, tasks, and roles within both, and an endless amount of complexity. It’s time for more Agile coaches, fans, and engineers to better understand UX so that we can improve process, product, and culture.

Learn how the UX process fits into Lean and Agile; augments software dev goals; increases customer satisfaction; and saves time, money, and sanity before developers write a line of code.