The document discusses how wireframes were initially developed based on business processes and data requirements rather than user needs, resulting in an unintuitive interface. It then describes how the team shifted to an agile, user-centered approach using tools like personas, scenarios and prototypes to understand users and design an interface that meets their needs and supports their work. This iterative process in close collaboration with users improved the design and increased buy-in.

1. Wireframes – from screen concept to user interaction Mia Horrigan IT Strategic Advisor and Architect

4. Information Architecture journey

10. Our problem …process & data driven wireframes and scenarios More reflective of the Physical Data Model vs. User Need 150 wireframes

11. Example Wireframes Tabs used to reflect change in state However when click on tab identical info repeated (not new info) Secondary navigation originally proposed to be hardcoded into each screen Screen reflected an electronic copy of the manual application form – little value add Sequencing was not in line with how the users would work through an application Screens developed as separate screen concepts without view of bigger picture usage scenario

13. What we should have considered Not just about the process … .or the technology Its about Users and how they work ..and the context of their work

20. Agile Approach – User Centered Prioritised feature sets Multidisciplinary team and Product owner working together Standards based ISO13407 Consult Tech Team regarding options and desired functionality

24. The result – ZenAgile Personas Wants Communication preferences Context Behaviour Motivations

25. User Segmentation – What they want Central office Key Stakeholders Want Map Really effective tool and point at which we started to see buy in from our end users

26. Want Maps to User Needs

35. Our Mapping of the User experience Understood user needs and wants Mapped business process Workshop processes and user requirements Developed usage scenarios – feature set (story cards) Iterated improvements to user interface in prototypes Validated prototype with users Translated user needs into features and benefits