Objectives

A website with a clear CTA to an online booking system and an updated information architecture that have clear entrances.

Design process

Research

Stakeholder conversation

Stakeholders were representative clients from IAM. We conducted bi-weekly meetings.

Stakeholder painpoints

• No up and running website today. "lost information", remnant memories
• Needs a booking solution, website needs a clear entrance to it
• Old website had unclear navigation, easy to get lost
• A lot of phone calls asking about adress and location
• Needs a place to host research projects

Feature analysis of CMS

We looked at our own CMS to map out how we could resolve some of IAMs need functionality.

Key findings we're aiming for

• Where's the CTA placed for bookings?
• How are preparations for certification conveyed?
• Where do other aviation medicine institute place their research articles — strategic or based on user tasks

Development

Sitemap

We made a sitemap from their old website. Due to time constraints, we made changes to entrances based on what we assumed would be users priorities from the competitor analysis. We invited the stakeholders to discuss the sitemap and make changes accordingly.

Wireframe prototype

With the project objectives and sitemap in mind, I set up wireframes as sketches to map out user journeys. I presented variations on the landing page and under pages, with what we could assume be top tasks for users. Some changes were made inline with the clients goals.

Delivery

The delivered website consisted of an updated information architecture. Expected top tasks were placed at the top, with entrances descending in importance.

Reflections

It would be interesting to see how the website perform once it goes live. The website would benefit from getting insight both from a user of the websites perspective as well as IAMs usage from the CMS.

‍