Identify from a UX lens, what fields we need from registration that affect reporting

[suhafa]

Describe the task

Going off #28, we want to identify which fields from registration affect reporting and on a system design perspective, how will reporting live in the app?

For this we will need to plan collaboration with team Moose to understand their scope for registration part 2 and have a few touch points in place for future collaboration

Acceptance Criteria

• [x] Add POs to OBPS Design syncs
• [ ] Book design collaboration session with Nan for outstanding design decisions to be made
• [ ] what does the landing page look like after the user comes back for reporting
• [x] Have a wireframe party to confirm our assumption
• [x] Document design decision from wireframe party

Additional context

• Add any other context about the task here.
• Or here

[patriciarussellCAS]

@suhafa - I have booked a "wireframe part 2" party (Jan 9) with Developers to help discuss this ticket.

[suhafa]

@nanyangpro Hi Nan! We hope to have a system in place for Moose and Giraffe to sync up and be aware of changes and important updates. Tagging you on here for visibility and if you have any more ideas for team collaboration + design collaboration work we hope to do together!

[rdromey]

Combined with #166