Urban Plan-AR

Using a design sprint to create a mobile app that uses AR technology to
foster citizen participation in urban planning.

PROBLEM

Including citizen input in the urban planning process provides undeniable advantages; because they live in these spaces, they can provide observations and knowledge that are different from those of the experts. But it can be challenging to garner citizens’ interest and participation.

SOLUTION

As a group project, a team and I designed a product that uses augmented reality (AR) to help foster public participation in the urban planning process.

We used Google Ventures’ design sprint methodology, which is typically a 5-day process where stakeholders are brought together to use design, prototyping, and user testing to answer business questions.

However, you won’t see images of designers crowded around a whiteboard of Post-its because:

The team members were located around the world (Canada (me), South Africa, Lebanon, and Brazil), and,
Our design “sprint” was spread out over 3 months (for the purpose of the class).

Watch the video of the prototype below. You can also navigate through it yourself; to begin, click on the “cloud” download icon.

Overview

PROBLEM STATEMENT

How might we use augmented reality (AR) to help citizens visualize the end result of urban planning projects to motivate them to participate in the process?

MY ROLE

I was the facilitator and the other group members took on the roles of decider, designer, and developer.

As the facilitator, I managed the overall project, including setting the agendas and scheduling, facilitating the online meetings, and synthesizing the results of our discussions.

METHODS & TOOLS

Google Venture’s Design Sprint methodology, Miro, Google Suite, Google Hangouts, Adobe Illustrator, Articulate Storyline, Veer, Sketchfab

TIMELINE

3 months

Setting the stage

Even though we were spread out around the world, we connected synchronously every week using the following tools to communicate and collaborate:

Miro online whiteboard for collaboration
Gantt chart to track progress
Google Drive for sharing documentation created in Docs, Sheets, Slides
Google Hangouts for both synchronous and asynchronous communication

Phase 1: Map

Expert Input (interviews)

To get a deeper understanding of the problem, we interviewed a city planner, professor of architecture, and municipal special projects coordinator. The following themes emerged:

Issues with current system

Not all stakeholders are included in the process/not involved early enough
Citizens don’t have a sense of ownership over decisions being made

Potential and current barriers

Lack of means to participate
Digital divide and exclusion from the process
Lack of education or trust in the system

Current methods used

Rely largely on social media and physical meetings

“In order to have meaningful public participation, citizens need to feel that they are part of the decision-making process (or the design process) from the very beginning – to feel ownership.”

N.C., professor of architecture

Idea/Concept

We focused on designing a mobile app that uses AR/VR (virtual reality) to present urban planning projects to citizens and encourage direct feedback to urban planners and communication with other citizens.

We also considered how to include citizens who don’t own AR-enabled devices and leverage existing networks and platforms (social media) to expand the reach to more citizens.

Phase 2: Sketch

We took a couple of days to research and collect inspiring ideas and solutions, then uploaded our findings onto our Miro board to share with each other.

We then met synchronously to review our inspirational ideas. Most of us found inspiration in apps like those offered by Ikea; a number of builders also use AR for visualization. With respect to tackling the digital divide, I was especially inspired by tower viewers, those coin-operated binoculars you typically see at vantage points.

After completing a rapid ideation exercise called Crazy 8’s (where we drew out 8 sketches in 8 minutes), we parted ways to asynchronously finalize our solution sketches to upload to Miro for the next phase.

Phase 3: Decide

Heat Maps

In the next phase, we used the functionality within Miro to vote on the frames of the solution sketches that we liked best. The resulting heat maps served as a guide for selecting the functions to include in the app. In the design sprint process, the Decider gets final say, so they used their Supervote powers to select those ideas which were a must-have.

We chose a name (Urban PlanAR) and agreed on the following functionality to include in the app:

Visual map view similar to Google Maps
Bottom navigation menu for alerts
Voting capability to see how other citizens feel about projects
Interactive top menu (add comments/pins, take images) and social media elements (sharing, upvoting, downvoting)
Ability for citizens to “view” the finished project

Storyboard

With the sketches completed, we now had to pull everything together into a storyboard.

When this exercise is done face-to-face, new sketches are drawn for each frame, as guided by team members. I adjusted the process slightly by separating each solution sketch into individual panes so they could be easily moved around and placed into the storyboard frames.

Since our sketches reflected different parts of the user journey, the storyboard came together nicely. In fact, once the panes were in place, we only had to create one sketch of the opening scene.

I recognize that approaching the activity in this way may not always work out, but given our greatly disparate locations and time constraints, it was the best strategy to adopt.

Phase 4: Prototype

We went back and forth on the appropriate tools to use to design the prototype, exploring UXPin, proto.io, and Adobe XD, among others. We had the following constraints: At the time of this project, these tools were either too costly for multiple users, didn’t offer the ability to prototype our app’s requirements, or didn’t allow for true collaboration.

We ultimately decided to use the following tools:

Adobe Illustrator for the user interface design
Veer for the embedded VR and AR links
Sketchfab for the 3D model
Articulate Storyline for the interactive prototype
Github for publishing and hosting

Though unorthodox for prototyping, we used Articulate because it allowed us to include the more advanced functionality we wanted (for example, upvoting, downvoting, commenting). I reviewed drafts of the prototype during this phase to ensure consistency in the design (navigation, intuitive flow, and functioning links).

Then came the testing!

Phase 5: Test

Usability Testing

We conducted usability testing with one individual each (4 in total) and our participants represented a range of ages and occupations of citizens one could potentially find within a neighborhood. Our sessions were recorded (using ScreenCam).

Age	Gender	Occupation
50	Male	Educational researcher
59	Female	Retired
28	Female	Pharmacy technician
27	Female	Project manager

For the usability test, participants were asked to:

Navigate to the Bridge Restoration planning project
Select each of the available views of the project (AR/VR/3D)
Add a comment to the project
Vote on the project, or on an existing comment

Video Analysis

We uploaded our respective videos to our shared Google Drive for review.

After watching the videos individually, taking notes on insights along the way, we categorized our notes as positive (green), negative (red) or neutral (white), then clustered them according to the tasks from the usability testing to identify any commonalities.

Testing Results

Overall, participant feedback was positive. The concept seemed viable and they thought the app could help to increase public participation in urban planning.

However, the following insights were identified:

1. The onboarding experience could be enhanced. Several users couldn’t navigate to the main screen from the “app” store.

2. Icons and terminology need to be more clear. The participants misidentified the terms VR/AR and the icons on the tab bar, and had issues navigating the map pins.

3. Users had unclear expectations of the AR and VR views. One user expected the AR view to show the completed project and the 3D view to show its current state, while another expected the opposite.

4. Familiar icons and platform design patterns were well received. Most users recognized the icons and functionality of the thumbs up/thumbs and comments bubble, comparing them to Facebook.

5. The older participants needed more details on the project. They wanted to be better informed about the project(s) before adding their comments.

Next steps

Based on the testing results, we identified next steps to improve the user experience.

The Designer changed the interface, adding color and including onboarding screens to help explain the app’s purpose. We also improved the navigation by:

Labeling the tab bar icons
Opening up one of the pins in map view by default to identify that each pin represents a project.

Additional steps to take and concerns to address included:

Add text descriptions to the AR, VR and 3D screens to describe the scene (e.g. “This is a 3D mockup of the proposed bridge renovation”)
Include links to detailed information about each project
Countering the digital divide by offering an alternative version of the app at public facilities, such as libraries.
Government buy-in to help market and promote the application.

Lessons Learned

Connecting once or twice a week wasn’t frequent enough, so we ramped up communication between formal meetings by chatting informally on Google Hangouts.
Because several team members were underprepared for the first meeting, I began the practice of sending detailed task lists of what everyone had to complete before each subsequent meeting to keep everyone on track.

Accordingly, working with a globally distributed team wasn’t the greatest challenge; it was keeping people on track between meetings, which was helped by the asynchronous chats.