Every month in this column, our Ask UXmatters experts answer our readers’ questions about user experience matters. To get answers to your questions about UX strategy, design, or user research in an upcoming edition of Ask UXmatters, please send your questions to us at [email protected].
Pitching is one of the most important skills for any UX designer to have. Your ability to pitch clients well naturally permeates your UX design outcomes. Knowing what makes a perfect pitch is something that undoubtedly comes with practice, but your pitches can be effective if you prepare them meticulously. Whether you’re working for a multinational design agency or are an independent UX designer, your design solutions are only as good as they appear to your clients. Therefore, a good design that you pitch poorly has very little impact.
Throughout all my years pitching designs to clients, there have been highlights and lowlights. Over the years, I’ve isolated what has worked well from what hasn’t. I’ve picked up the best ideas from how others pitch and formulated and refined my own approach to pitching. You can do the same. In this column, I’ll share my specific approach to pitching, including five strategies that have helped me impress my clients. Whether you’re a rookie UX designer or seasoned veteran, incorporating some or all of these pitching strategies can elevate your pitching skills to the next level. Read More
So, you’ve wrapped up your customer research, completed your personas, and have even written a few scenarios that show how users would want to interact with your brand new product. What’s next? What happens to the personas and scenarios once you’re ready to start requirements definition and design. Are you sure you’ve adequately communicated the type of system your users need to the Business Analyst and Interaction Designer on your team?
If you’re like me, you’ve always felt something was missing once you finished creating your personas and scenarios. They communicate the heart and goals of the user, but miss out on a lot of details. And while it’s the intent of both documents to do just that, neither personas nor scenarios succinctly communicates to your business what features a product or service should have and why it should have them. Read More