Context Cards

Gepubliceerd op 05 sep, 2019

If you work with different clients you probably have experienced the complexity of collaboration on projects. Different experts with various fields of expertise, with very different ideas, all of them involved in a project where nobody has a common vision, and where nobody is used to work with each other... sounds familiar?

We experience these issues often and we are trying to make this process smoother and more efficient.

Context Cards

The context cards are a set of visual cards that we created to deal with this complexity. By providing graphic elements to support the communication, it's easier for all the parties involved to share valuable insights and make more informed decisions. The set contains different categories (people, objects, mobility/places and communication) that help us establishing a common language with our clients, users and stakeholders.

Why use the Context Cards?

The cards are very versatile and can be used with different goals:

Why context cards

How and when we use them varies from project to project. Some examples:

  • We mapped out the whole process of study allowances with AHOVOKS.
  • We designed the ideal user journey with Neo Scores.
  • We visualised the service blueprint of Edutube, a project with VDAB.
  • We've also used them as a prototyping tool during workshops and hackathons (GovJam, Service Jam, Hack the Future, ...).

The possibilities are endless, but to make things easier we have put together some concrete exercises:

Stakeholder map
Organigram
User journey

Example: Stakeholder Map

Let's have a closer look into one of these examples. Here are some steps we follow and some insider tips about our workflow. These are meant to inspire you, but please feel free to explore other methods and use the cards any way you like.

The purpose of a Stakeholder Map is to get an overview of the different stakeholders involved in a project.

Step1
Step2
Step3
Step4
Step5