User Journey for Fab City OS

Value Statement:

To develop the Fab City OS Vision further, we want to focus on User Journeys

1. Start with the user’s first step or entry point into your product experience
2. Add each step in the journey until the user’s goal has been reached
3. Include descriptions for each step and highlight pain points along the journey

If you’re doing a Design Sprint for a new product and/or you are in the early stages of the product cycle, you may want to explore a certain use case for your product and start your journey map with the user’s initial entry point into that use case.

Resources:

Andrea proposed more here: https://pad.dyne.org/code/#/2/code/edit/1BCohPUxvz+rlhTlOGda4ow-/

• User Journey Mapping Method https://designsprintkit.withgoogle.com/methodology/phase1-understand/user-journey-mapping.
• you might find some team input in element. E.G. search for fediverse in REACT Channel.
• You might also use Graphics for better understanding
• There is a Visual Concept Brainstorming in Miro going on which will be found here: https://miro.com/app/board/o9J_l6ZbxLI=/?moveToWidget=3074457366567459325&cot=14

Acceptance Criteria:

• Document the outcome of the User Journey Mapping. This should address reasonable usecases, show the identified usecases for each product platforms.

This started as a copy/redux of #47 (closed) and might need more refinement.

changed milestone to %backlog

mentioned in issue #47 (closed)

added Requirements label

for some more user stories see https://gitlab.fabcity.hamburg/software/reflowos/3.1-requirements/-/blob/main/Basic_User_Stories.md

removed Requirements label

added Governance Meeting label

assigned to @alex

Assigned Alex to decided on relevance of the links going forward.