Skip to content
Snippets Groups Projects

User Journey for Fab City OS and Glossary

    • Closed Issue created by Raphael Haus @haus

    Value Statement:

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

    • User Journeys
    • and defining wordings (aka Glossary)

    These two things go hand in hand. Please start with the User Journey mapping. Obviously along the journey the wordings for the journey waypoints need to be solved as well.

    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.

    Ressources:

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

    Term Definiton
    Product Design Platform Platform aiming to Designers, Engineers and Inventors to upload, co-create and share OSH Products
    Fab City Platform Platform aiming to Cities becoming a Fab City and getting support in setting up their FC Organisation
    Manufacturing Platform Companies manage their orders, materials, & manufacturing (also for repair, recycle, and modification)
    https://gitlab.fabcity.hamburg/community/wiki/vereinsinterne/-/wikis/Global-Glossary

    Fediverse was an expression that was introduced and had no final agreement till now.

    The Fab City OS Fediverse is an ensemble of interconnected, independent digital services that provide the core digital infrastructure for the OS. It stores and connects informations, cryptographically secures them, ensures interoperability, and provides an API for the network. by raphael

    other approaches where: FC OS + Reflow OS = Fab City Stack?

    Acceptance Criteria:

    • Document the outcome of the User Journey Mapping. This should address reasonable usecases, show the identified usecases for each product platforms.
    • Document a comprehensive Glossary in the Wiki's Global Glossary
    • Also technical wordings should be adressed and documented
    • Definitions of wordings should be evaluated with relevant team members in advance to ensure consistency and quality
    0 of 4 checklist items completed · Edited

    Designs

      Child items ...

      2. Activity

      Please register or sign in to reply