What UX struggles would you love to end?Do you want to stop the endless cycle of rework to satisfy stakeholders moving targets?Would you like to play a role in creating requirements instead of having them handed to you like written law?Are you tired of delivering products with UX defects you know could have been avoided?Do you wish there was a way to get managers to agree to UX work at the start of the project, instead of tacking it on at the end, when its too late?If you answered YES to any of those questions, youre in the right place. I created this course specifically to end the vicious cycle too many developers and product teams are trapped in: vague requirements they had no hand in creating, constant rework and a never-ending stream of new (and changing) requirements. See, Ive been there myself. In nearly 30 years of working with organizations of all sizes in nearly every industry, I know that cycle all too well. I know what its like to try and roll the UX rock up that hill only to have your stakeholders or managers or clients roll it back down. No more debate about when UX work should happen.I know the pain of fighting to get UX included at the start of a project all too well. And I also know that its entirely possible to put an end to it. UX Requirements Made Simple will show you how to get a seat at the requirements table, open the minds and ears of your managers or clients, and see a massive change in both the quality of requirements and the success of the delivered product. Youll see how easy it is to quickly integrate strategic UX validation into an existing requirements process without the need for additional time, money or resources. Heres just some of what youll learn: Poor methods for requirements that rely on a broken engineering process and a better, simpler set of methods that get to clarity and value quickly. Why what users say they need isnt what they actually need (and how to tell the difference).Poor requirements tools that address task completion instead of success and a smarter set of tools that focus your work squarely on desired outcomes. How to get managers or clients (or your team) to ask the right questions, instead of solution jumping. How to create contextual use scenarios that tell the real story of the users journey from start to finish and extract relevant functional needs and elements that make up valuable requirements. Its simple, its straightforward, and it works. Not because I say it does but because the Enterprise teams Ive taught to use these methods have gotten the results Im talking about. It works because more than 140,000 students (yes, thats a real number) tell me that my courses have changed the work they do for the better. Why? Because I deal in software development reality instead of UX fantasy. Perfect situations where we can do these well-funded deep dives into UX research dont exist for a vast majority of development teams, and Im really tired of hearing everyone pretend otherwise. So everything I deliver is based in reality, in the less-than perfect world most of us live in.
