Wayfinding Web App
Ongoing feature development of the Pam Wayfinding “SWS” service
Current implementation can be seen here: http://wayfinding.uts.edu.au/
The SWS service was designed about 9 months before I began work on it, with the goal of exposing signage data from the core Pam Wayfinding service to a client’s users in a manner to facilitate personal way-finding.
The service allows users to browse a list of destinations within a client’s physical site, based off signage data. From a given destination, users are able to access information to help them navigate through a campus in concert with the existing physical signage.
My work began before the service had been fully released, with my primary task being to bring the service online with the help of the development team, assist the clients with data curation and develop new functionality based on the needs of the business and end-user.
During this project, I ran a user-workshop for around 20 participants, from which the concepts for version 2 of the service were developed.
First year University Students
- Age 18-mid 40s
- Assumed limited technical experience, likely familiar with smart-phone apps though
- Brand new on campus and doesn’t know where anything is
- A little anxious because it’s their first day
- Some language barrier assumed for international students
Returning Students & Staff
- Age 20 – 65
- Mild technical experience, likely familiar with smart-phone apps though
- Spent a fair amount of time on campus, knows where their common destinations are already
- Probably looking for the nearest coffee/bathroom/study space
- Assess the current status of the project mid-development
- Define a concise list of requirements and review with product leader
- Abstract requirements into clear, actionable items
- Sketch / mockup new functionality to be added
- Create wireframes based off mockups. Test with team using Invision & paper prototypes
- Through feedback from wireframe test, refine wireframes.
- Create high fidelity designs of the refined UI
- Create developer hand-off documentation for developers to build from
- Test & review developed functionality
- Consult with client regarding new functionality (and repeat above process)
- Run post-launch workshops to assess user acceptance of new functionality
- Create refined prototypes to begin planning version 2