UX Trends
Your job is to come up with the perfect solution that users will love while taking into account the needs and constraints of sales, marketing, support, design, development, QA, IT, and every other part of the business that has a stake in the product. Oddly enough, getting to the right solution requires proving that you’re NOT a know-it-all.
One of the toughest conversations to have with a product manager or UX designer is pointing out that they’re losing the respect of the developers. It’s tough because frequently it comes as a surprise. With that said, there are actions you can take to foster a harmonious relationship with the developers on your team.
Have you ever worked on a project that seemed to shrink at every turn? There are any number of reasons stakeholders and managers cut the scope of projects. Sometimes these things are out of our hands, but other times, connecting the dots between the proposed solution and the business objectives can save the project… and your sanity.
Top 5 UX Articles Rolling into Fall
Whenever we came across an article that we thought could help you hone your UX skills, stay on top of the latest prototyping trends, or help you pitch your projects to your stakeholders, we did our best to share them across our social media channels. Based on the shares, comments, and clicks from this summer, we bring you the 5 most popular UX articles and why they stand out to us. Cheers and happy reading!
Accessibility and Prototyping: Axure in Conversation with Jennifer Sutton
Jennifer Sutton of JSutton Media dives into Accessibility and Prototyping. She answers questions such as: What a well-meaning UI designer can do if a project's stakeholders truly have "no accessibility aspirations" and are maybe even hostile to the notion.
Developing the Subscription Update to the Axure Customer Portal
We’ve been refining how we build software here at Axure since 2002, and by this point, the process is pretty streamlined. But we don’t adhere to any particular espoused philosophy of process management; we aren’t a strict Scrum Agile shop, and we don’t make use of a Kanban board. Our approach is informal by design, which makes it hard to encapsulate in a pithy five-point list or what have you. But what I can do instead is describe it by example.