Institut for [X]

Brainstorming, layout sketching, mind-maps, research, team meetings, field work, client and user interviews, research, content creation, web development—these are just a few of the tasks my team completed in the race to make a prototype in five days.

I had an opportunity to participate in a GV Design Sprint and practice rapid prototyping for Aarhus-based Institut for [X]. How might we answer critical business questions through design, prototyping, and testing ideas with end-users? 

View Project
The Challenge

Aarhus K is an ephemeral village spanning the former railway area of Aarhus, Denmark. Run by Institut for [X], its mandate is to provide a safe, creative citizen space as an independent culture, business, and education platform. Since launching in 2009 the project has flourished, however it faces the challenge of inviting more active participation from citizens. Our aim: create a prototype promoting the businesses within Aarhus K which welcomes anyone to participate in the space.

My Role

This project

This is what our process looked like:

Monday

we agreed on a long-term goals, set an ambitious yet realistic target, and learned about potential users from Juul Wendell, a project manager at Institut for [X].

Tuesday

we remixed existing ideas, drew on inspirations, and each of us set out to sketch a solution.

Wednesday

we agreed on a long-term goals, set an ambitious yet realistic target, and learned about potential users from Juul Wendell, a project manager at Institut for [X].

Thursday

we prototyped.

Friday

we tested the prototype and learned by watching users interact with our solution.

Understand

Decide

Prototype

Understand
Decide
Prototype
Understanding

A major challenge at the start of a Sprint is understanding what user-needs our solution should fulfill. Where is the perfect meeting between how our client wants to be represented and what the users want to know?

Sorting, mapping, and clustering our data in different ways helped us link ideas and find patterns.

Understanding

A major challenge at the start of a Sprint is understanding what user-needs our solution should fulfill. Where is the perfect meeting between how our client wants to be represented and what the users want to know?

Sorting, mapping, and clustering our data in different ways helped us link ideas and find patterns.

Defining guiding goals and reframing problems into opportunities helps us narrow our focus.

What
(is Aarhus K?)

How
(will our solution turn this info into a call-to-action?)

Deciding

Making decisions as a team is not always easy, but our product can only be improved by giving every member a voice.

Following structured processes helps us move through quick, good decisions.

1

The Sticky Decision

Each team member reviews sketches in silence and adds sticky notes to the solutions.

2

Structured Critique

Each member weighs in on elements they think should be implemented in the prototype.

3

The Final Call

A nominated decider considers everything that has been said and makes the final call.

Prototyping

It’s intimidating to put a prototype in front of a user- rarely does it ever feel complete before it’s time to be tested. This fifth day of the Design Sprint was a great way to overcome this fear. Why? Because the prototype can only be improved through putting the product in front of customers.

Privacy Settings
We use cookies to enhance your experience while using our website. If you are using our Services via a browser you can restrict, block or remove cookies through your web browser settings. We also use content and scripts from third parties that may use tracking technologies. You can selectively provide your consent below to allow such third party embeds. For complete information about the cookies we use, data we collect and how we process them, please check our Privacy Policy
Youtube
Consent to display content from Youtube
Vimeo
Consent to display content from Vimeo
Google Maps
Consent to display content from Google