The purpose of a User Experience (UX) Architect is to develop the structure and flow of a digital solution (website, app, software, mobile, etc.). The Architect conducts research, interviews, and surveys, and then translates that information into sitemaps, wireframes, and prototypes. The Architect sets up the system and process that will be used to design the final product. The job title UX Architect is often used interchangeably with UX Developer and UX Designer (although some UX specialists insist that each role is unique).
What does a UX Architect do, typically?
Focuses on structure and flow
A UX Architect partners with various business teams in an organization to understand how the end user will interact with the platform, and then develops the structure and flow to make that possible.
Answers the question, “can we do that?”
A UX Architect has a solid grasp of user research, information architecture, interaction design, and content strategy, and is able to clearly communicate to teams and clients how those factors will influence the design processes and outcomes.
Uses UX principles & techniques
A UX Architect is familiar with usability principles and techniques and is skilled using UX tools for the various stages of development—wireframing and prototyping, user research and testing, organizing information, and analytics and metrics.
UX Architects are not UI Designers
User Interface (UI) Designers: There is a lot of discussion about the differences between UX and UI, and between architects and designers. Check out this site to find out how a plate of brownies can help explain the difference. More information here.
Important metrics for a UX Architect
UX Architects use various metrics to see whether their UX vision and strategy are working over time. Some of these metrics include task success rate, perceived success, time on task, ease of use rating (SUS), error rate, and back-button usage.
