Skip to content

IXD 106 / Website redesign

Granville
Island.

More to discover.
A clearer place to start.

How can a destination website help visitors move from an idea for a day out to the details they need to make it happen?

I completed the information architecture independently, conducted three user-testing interviews, made wireframes, and collaborated with Sara and Avery on the layout.

Open the Figma prototype
My contribution
Independent IA, testing,
wireframes, shared layout
Design team
Ian Johnstone,
Sara and Avery
Timeline
February–April 2026
Context
Coursework / Figma concept
Final desktop prototype
Final group concept / Desktop homepage excerpt

The brief and the direction

Help visitors see
more possibilities.

The course brief asked us to rethink Granville Island’s website as a place for discovery and planning. The challenge was to help people explore beyond familiar attractions while keeping practical visitor information easy to reach.

We were designing for first-time visitors and people who already knew the island. Someone looking for a new experience needs a different starting point from someone checking a particular vendor’s hours.

Discover something

Surface current events and offer ways to browse food, arts and activities.

Decide whether it fits

Show the details that help someone judge a place or experience before committing.

Prepare for a visit

Connect discovery to hours, location, directions and planning support.

The early strategy work included personas, journey maps and a companion-app proposal. The journeys considered discovery, planning, preparation, visiting and returning, connecting an online choice to the information someone might need on the island.

These were planning tools developed from supplied course material, rather than additional interview participants. They helped frame structured planning and more spontaneous exploration.

This was an academic concept using an imagined client brief. The finished deliverable was a desktop Figma prototype, with broader mobile, map and itinerary ideas explored in wireframes.

My independent contribution

Give the content
a usable structure.

I completed the information hierarchy independently. I worked from a supplied historical content inventory whose URLs were inactive, using page titles and descriptions to infer content types and relationships.

The structural problem was broader than the menu. Recurring content needed a consistent model, and visitor tasks needed a clearer place alongside tenant, media and administrative resources.

Information hierarchyIndependent proposal
Visit, Explore and Public Market, excerpted from my original sitemap. My proposal used six primary sections. The later group header combined Market & Events, so this diagram represents the independent IA stage.

Three structural decisions

Keep leaf content inside a useful parent
I grouped individual recipes beneath a recipe index and treated the “Top Ten” pages as content within a guide. Both decisions kept individual entries from becoming competing navigation choices.
Separate visitor and specialist tasks
I moved leasing, permits, tenant resources and media materials to secondary access points. They remained available without carrying the same navigation weight as planning, events or finding a vendor.
Make shared utilities global
I proposed search and an English/French toggle as site-wide elements. This offered direct access to utilities and avoided duplicating the navigation for language content.

These were proposed structural decisions. The IA was inferred from the supplied inventory and was not validated through a separate card sort or tree test.

The content model behind the pages

Define what each
entry needs to contain.

I separated recurring content into types such as events, vendor listings, recipes and listing indexes. Specifying their fields was intended to make information more consistent for visitors and easier to maintain.

Condensed from my original content model
Content typeSelected fieldsPurpose
EventDate, time, location, cost, audience, accessibility notesCompare experiences and judge whether an event fits a visit.
VendorCategory, location, hours, contact details, accessibilityAnswer practical questions consistently across businesses.
RecipeIngredients, instructions, preparation time, related vendor, tagsKeep repeatable market content connected and structured.

Source: information hierarchy, pages 3 and 5–10. This table is a condensed presentation of that work.

Exploring the structure on screen

Make room for
different kinds of visits.

I created wireframes and worked with the team on the layout. The working file includes planning, directory, vendor, About and map explorations, along with early mobile layouts.

The planning direction broke a broad request, “plan my visit,” into interests, available time and accessibility preferences. Those inputs made the intended planning logic visible in the wireframe.

Planning inputsEarly desktop wireframe
An excerpt from the working file. Interests, duration and accessibility preferences divide the task into manageable choices.
Early mobile exploration
The same planning concepts explored at a narrow width. This is an early wireframe, with placeholder content.

The map exploration paired a search and filter area with a results list and a map region. The goal was to connect discovering a place with understanding where it was. The map content remained a placeholder, and itinerary generation, saving and routing were not demonstrated as complete functions.

View the three wireframes in Figma.

What we tested and what it changed

Follow how visitors
look for a day out.

I conducted three of the team’s five user-testing interviews. We used think-aloud, scenario-based tasks across the homepage, events, recommendations and vendor details, then recorded observations in a shared workbook.

The tasks followed a realistic sequence: find something to do this weekend, read an event’s details, explore quick food options, then find information about a specific vendor.

Finding a route

People used different entry points.

Some used the top navigation to reach events. Two tried the filter control before finding category browsing. A single route would not explain how everyone expected to move through the site.

Support browsing and direct access

The final concept offers top navigation, category cards and contextual links. Categories such as Quick Bites and Rainy Day Plans provide starting points around the kind of visit someone has in mind. Filter controls are visible concepts; their complete behaviour remains to be developed.

Workbook: interview rows 19, 23, 32 and 36–37.

Choosing a vendor

Finding hours did not answer every question.

Participants could locate hours and contact details. Requests for a menu showed that a person could still lack the information needed to decide where to eat.

Keep practical details visible and add menu access

We kept hours and location on recommendations, before opening a vendor profile, and added a View Menu action to the vendor page. The action is visible in the final design, while its destination remains incomplete in the sampled prototype.

Workbook: interview rows 26–31. Final vendor design: 377:566.

Knowing whether a place fits

Some needs required more specific content.

One participant wanted clearer dietary information. Another wanted to filter reviews. These requests exposed gaps beyond the basic address and opening hours.

Separate a visible revision from an unresolved need

The final vendor layout includes a review count and filter control. Dietary information still needs a clearer treatment. The displayed ratings and reviews are sample prototype content, and review filtering was not verified as a complete interaction.

Workbook: interview rows 30–31. Final presentation: pages 24 and 39.

The connected final concept / Shared team work

From a weekend idea
to a place to visit.

The final concept connects broad discovery to a specific vendor. Current events introduce possibilities, categories narrow the type of experience, and recommendations lead to practical details.

Use the screen controls to inspect that route through the original designs. These are faithful screen excerpts. The linked Figma prototype provides the original click-through experience.

Home / Discover possibilities

A broad starting point.

The homepage combines current experiences with direct routes into planning, events, the map and the directory. It supports visitors arriving with different levels of familiarity.

Continue the route

Market & Events opens the events page.

Open this screen in Figma
Final group homepage / Top-of-page excerptClick artwork for the full screen

Designed route: Home → Market & Events → Categories → Quick Bites → Blue Parrot Coffee.

Event listings, vendor details, ratings and reviews are sample content. Complete menu, filter and itinerary behaviour is outside the demonstrated route.

A closer look at the decision

Give someone enough
to choose a place.

The recommendation page shows hours and location before a visitor opens the profile. The vendor page then brings the name, hours, location and menu action together near the top.

This separates two jobs: scanning possible places and investigating one in more detail. It also responds to the menu request without making every recommendation card carry all of a vendor’s content.

The next question to test

Can someone with a dietary requirement decide whether this vendor is suitable, including reaching a complete menu? That task still needs a finished destination and another round of testing.

Final group vendor profile / Excerpt. Vendor details and reviews are sample content. The menu action is a design response, with its destination still incomplete.

Connecting the screens

Carry the island’s
character through the UI.

The team’s visual direction used bright colour, photography and activity-led language to present Granville Island as a varied, welcoming place. Repeated headers, blue headings, cards and icon treatments connected the pages.

The icon set distinguished entertainment, location, visitor and activity types. Labels carried the meaning alongside the colour. The study also showed a trade-off: strong colour could draw attention away from the content we wanted visitors to notice first.

Original icon and button sample from the final team presentation, page 41. Shared team design.

What we delivered and what comes next

A connected concept.
A clearer next test.

The project brought together content structure, wireframes, a five-session study and a shared desktop concept. My contribution was the independent IA, three interviews, wireframe work and collaboration on the layout.

Looking back, I would distinguish content findability, prototype completeness and usability outcomes more explicitly. A person finding a printed location does not establish that a map works, and a favourable reaction does not establish a change in real visits.

Delivered
Content types and fields, an independent hierarchy proposal, early desktop and mobile wireframes, research records, and the shared final desktop screens.
Explored
Map search, planning inputs, itinerary ideas and mobile layouts. These extend the direction, with important interactions and final states still unresolved.
Next validation
Finish one vendor-selection task, including menu and dietary information, then test it alongside event discovery on desktop and a matched mobile layout.

No post-revision study, production launch or measured impact on visits or vendor engagement is verified.

Project sources and disclosure

Supporting records reviewed: the Phase 1 strategy presentation; “GI - Informtion Hiearchy.pdf,” pages 3 and 5–10; the research plan and workbook; and “GI Final pres.pdf,” including the annotated wireframes on pages 35–40 and component sample on page 41. Findings here are paraphrased from the recorded notes. Participant names and private session details are not reproduced.

The personas and journey maps are planning and synthesis tools, with details that are not all traceable to the five prototype sessions. They are not presented as additional participant evidence. The independent IA and later team navigation represent related stages whose structures differ.

Project records disclose AI assistance with writing, structural exploration and some imagery, including sample review content. This expanded case study was also prepared with AI assistance. Original interface artwork is reproduced with selected crops and optimized image encoding. No additional participant research or new project-interface design was conducted for this presentation.

Project artwork