I am never anything less than completely honored when someone considers or chooses me as a speaker, because with that choice comes risk. The success of any event rests on the quality of the presenters and speakers – and whether or not they engage their audiences and deliver valuable insight. So I take the responsibility of making the event a success every bit as seriously as you do.
Finding the right speaker is always a challenge, so I’ve put this overview together in order to help you make an informed decision. For starters, here’s what I look like in action:
I spend a great deal of time talking specifically about the principles and practices of good UX. But there are a number of hot-button topics that audiences, students and clients wrestle with, and I find myself returning to them quite often. Here are a few of the most popular topics from my speaking engagements and training workshops:
Since UX has become a buzzword, developers and programmers have been feeling the pressure to get better at the visual part – and quickly. The common cry is often “but I’m not a UI designer!” I get letters every week from developers who are extremely worried about the fact that their employers and clients expect them to be as equally skilled in visual UI design as they are in the realm of technical complexity. But I have good news: they may never be UI designers – and it doesn’t matter.
In this session, I show developers and programmers how it’s possible to design great user experiences without a shred of visual design talent. They learn how changing the way they think about features, functions and implementations makes a massive, positive difference in the quality and value of the user experience.
Clients and stakeholders will always have a voluminous laundry list of features and functions, all of which they will insist are equally important. But these folks all share something very important in common: they’re all human beings. And we human beings all have a fundamental flaw: we often make very confident – but equally false – predictions about our future behavior. So the requirements that will actually be most useful and most valuable – the ones that will increase user adoption or sales; the ones that will make or save money – are almost never surfaced in traditional requirements sessions.
In this workshop, I show attendees how to change that, along with how to tell the difference between what people say they need and what they actually need. And finally, I show then how to uncover the things people don’t know they need (but absolutely do).
The prescriptive interpretation of this axiom has guided the work of engineers, programmers, developers – and even designers – for a very long time. The result of this has been sites, software and systems that exhibit poor usability, frustrating user experiences and a marked failure to deliver expected business results. Throw a stone and you’ll hit a legacy system that proves this point. “Form follows function” has essentially encouraged an approach that prioritizes functionality over all other design considerations, including usability, ergonomics and aesthetics.
In this session, I explain why pure function is rarely the single or most important component of success. I demonstrate how every force at play in any project is what really evolves form (and dictates function). Finally, I show attendees how balancing considerations of form and function produces feature specs and appropriate design decisions that create great UX.
If you’d like to see if I’m available for your event, or would like to ask some questions before moving forward, please fill out this short form. Someone on my staff wil respond within 24 hours.
Do you wish you could get stakeholders to agree to UX work at the start of the project, instead of at the end, when it’s too late? Shouldn‘t you play a role in creatingrequirements, instead of receiving them like written law?
If you answered YES to either question, I have no doubt you’ll find this video extremely valuable
There's only one way to get it — by subscribing to my free email newsletter.