2023-03-01 Steve & Sandbox UX #1

Owned by Jonas Bergmeier, created
Last updated: May 17, 2023 by Artun Gürkan
2 min read

 Date

Mar 1, 2023

 Participants

  • @Martha Vasquez

  • @Steve Conrad

  • @Jonas Bergmeier

 Goals

  1. Define scope and goals of upcoming sessions

  2. Review index of information

  3. Test run over at least one wireframe to review BB involvement

 Discussion topics

Time

Item

Notes

Comments

Time

Item

Notes

Comments

10min

Define scope and goals of upcoming sessions

  • clarify terminology and “product tracks”

  • take a look on our roadmap for bigger picture

  • goals of upcoming sessions

    • generally to reduce the amount of insecure assumptions

    • build shared understanding of which sources are relevant from technical perspective for our work ahead

    • map superficial BB involvement to wireframes and actions

    • identify risks

 

10min

Review index of information



Index of technical information sources

 

20min

Test run

https://www.figma.com/file/tq8VOr1v9LabYEbAZxVbvs/GovStack-Sandbox?node-id=1752%3A102138

wasn’t done in first session

 Action items

@Steve Conrad GDPR and Data privacy → review current state Mar 17, 2023
@Artun Gürkan @Martha Vasquez @Jonas Bergmeier : try to identify workflow patterns (“capabilities”) for our USCT and share results with @Steve Conrad / @Wes Brown Mar 17, 2023
@Jonas Bergmeier create ticket for this and share with others Mar 3, 2023
add Gitbook links to BB in Index of technical information sources @Jonas Bergmeier Mar 3, 2023

 Decisions

  1. Follow-Up arranged for Mar 6, 2023 , primary goal: Identify explicit UI and action-based BB involvement in USCT Simulation

 

Follow-Up on Mar 6, 2023

@Martha Vasquez @Steve Conrad @Artun Gürkan @Jonas Bergmeier

Goals

  • Test run over at least one wireframe to review BB involvement: Identify explicit UI and action-based BB involvement in USCT Simulation

  • Check in regarding capabilities: If, when and could we contribute and feedback?

Notes and Action Items

Steves Feedback on Wireframes

  • Payment - adding Voucher payment options, currently only bank options visible

  • Wireframes Feedback - Create more versions of different states (e.g. Civil Servant view, more possible outcomes, validation pages)

  • Data storage - where is it stored right now? Additional data, registration, digital registry not sufficient enough

  • Localisation - multi language options should be considered

Goals - Test run Notes

  • ID Buildingblock - Authentication; Information Mediators, workflow building block

    • Would we store a list of civil servants and their roles on a digital registry?
      Where would we store the list?
      Not defined by the current building blocks

    • Rolebased management is part of the security but not defined yet.

    • Registry topic - clarification necessary for the MVP

    • Is there a separate database that will store information about civil servants (including their roles/permissions)

    • What BBs manage the login process? The ID BB is just for foundational ID, so how is login managed?

  • https://docs.google.com/document/d/1yyuzxfAQndrxkNaya5kcSbhc9hFqQ2vZtUF4aDPdvaI/edit related BB

  • identify the high level BBs for the next steps

  • Digital registry database stores who is registered and enrolled

  • Workflow BB - which information (Programs) does the civil servant has access to?

  • https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/PzBEEsm2haAbBj2uBAKN/consent

 

Action Item

Registry / identification BB details should be clarified for the MVP @Steve Conrad
Rework package description and additional information, wireframe, so that the context is clear; info depends on the user @Artun Gürkan @Martha Vasquez
identify parts of the USCT journey which could be transferred into other use cases @Jonas Bergmeier @Artun Gürkan @Martha Vasquez