# Day 1 - Sharing

The first day is all about sharing information and onboarding all participants to the problem space. It's important to establish a common understanding for what's going to be worked on. This makes it possible to work on this together in the first place.

## Overview

<table data-header-hidden><thead><tr><th width="174"></th><th></th></tr></thead><tbody><tr><td>Ownership</td><td><ul><li>facilitator</li></ul></td></tr><tr><td>Goals</td><td><ul><li>share research findings and existing deliverables</li><li>present as-is-journey</li><li>share legal analysis</li><li>share technical analysis</li><li>gain insights from civil servant our public representative expert</li><li>conduct to-be-journey workshop </li></ul></td></tr><tr><td>Participants</td><td><ul><li>Designer</li><li>Manager</li><li>Legal</li><li>Business Analyst</li><li>Technical consultant</li><li>Civil Servant</li></ul></td></tr></tbody></table>

The facilitator is responsible to set up the sessions and guide the group through the day.&#x20;

## How to get started

Journey mapping is a powerful visualization tool that outlines the steps a person takes to reach a goal, offering invaluable insights in transforming eGovernment services. The video provides an overview of the journey mapping and explains how to use [the template](https://www.figma.com/file/lGv2zUy9Er4ni4283Ds7aO/Journey-Template?type=whiteboard\&t=qaKo7elhGbSHKbSn-0).&#x20;

{% embed url="<https://www.youtube.com/watch?v=sKnTfcUm2z4>" %}
Journey Mapping with GovStack
{% endembed %}

It's recommendable to start by sharing findings from the different areas after introducing to the existing as-is-journey. These findings should be used to expand the as-is-journey and to enrich it with user centered information. For this, especially the inclusion of a civil servant or other government official concerned with the matter can make a big difference.

These information will help for the second part of the day, where the collaborative effort to set up the to-be-journey is the primary and shared goal.

Finally, the team finishes Monday, when a to-be-journey is in place, including all possible pain points from user perspectives and insights collected upfront.&#x20;