[Research Planning] Data Reporting Research

[reitermb]

Description: Delivers a research plan for a roadmap gap area identified after enabling Yun with data access. Validates our understanding of OFA data workflow, "reporting" related touchpoints along it with STTs, and ideates on report and product requirements

AC:

• [ ] Research is scoped
• [ ] Open questions answerable by research plan are clear
• [ ] Path forward has been discussed in UX Sync

Tasks:

• [ ] Refine mural/roadmap epic gap area into a holistic research plan
• [ ] Refine Service Blue Print Map with respective meetings

Notes:

Following on from UX sync: To speak to your point about reporting @laurenfrohlich, I think we have a fair bit of existing insight when it comes to many of the existing high priority reports. 2909 dug into the reports DIGIT saw a prime opportunity for automating (and we have a lot of that discussion captured here)

Some of what we were seeing in our preliminary analysis of the provided SAS files suggested to us that some of what's happening there might have relevance to some of those reports. Whether or not that's accurate, I think one of the core open questions standing in the way of automating some of these reports is a holistic view of what cleansing / preparation / calculation is needed to get the data into a suitable state for reporting, which is where a lot of the utility of the SAS files comes in for dev.

Supporting Documentation:

• Working Mural
• FIGMA blueprint

[victoriaatraft]

Initial planning document here for New Data Requirements FRA found here and relative items to the next TDP UX sync added to the agenda.

[victoriaatraft]

@ADPennington transferring a ping from MM to schedule time to work on the service mapping workflow. :) Happy to send you time on your next availability. Maybe 45 minutes to start?

[ADPennington]

@lfrohlich this ticket. we're meeting on wednesday.

[victoriaatraft]

repurposing this post service mapping exercise wed 10/16

[lfrohlich]

Distillation of thoughts I mentioned/ some steering of the research: @victoriaatraft @reitermb @vlasse86 DIGIT team + Raft should continue to build out the blueprint/workflow but we know where we want to go first Focus research on Feedback Reports that OFA wants to offload

• Specifically, start with feedback reports related to submission history aka missing data reports (what data we should have vs. submission history)
• Include some triggers/flags when things are off (Sample states: at least 250 cases)
• Primary audience: OFA CO & RO; new audience: direct to state
• Aggregated submission history (across quarters), highlighting what is missing as of date generated
• We have the workbook with the data needed for the mockup
• Need to better understand what questions are answered by these feedback reports, who are the recipients, how frequently do they need the reports, what is the best way to produce them

[victoriaatraft]

Thanks @lfrohlich, we have another internal ux sync today we can take a look further into. prior to this comment, I started to put together a github draftof a report based off of the previous tdp ux sync. I'll work to get the above acknowledged and incorporated. I'll reach out for further questions/clarification.

[victoriaatraft]

Updates from UX Sync 11/12/23

Action Items:

• [x] Additional conversation with OFA to create a dev follow on to get design specs. Time on calendar this week follow up on UX channel
• [x] UX review TDP Submission History and follow up with questions next week
• [x] Comments left on OFA Regional Staff UI Epic

Meeting Notes

• https://github.com/raft-tech/TANF-app/issues/3249 is a low lift ticket to get Regional Staff Access. We'll focus on this ticket and giving current access to the information on TDP right now. Ticket contains information to inform design work to get access and so artifacts captured in this ticket. Requires follow up conversation
• Engaging in more in depth research is not feasible at this time. A separate ticket will be created to track work
• Missing Data Report / Submission History Report piece/recap: We will be sequencing the following:
  1. The additional conversation above because the first thing is to get Regional Staff access to submission history
  2. Morgan/Lauren/Andrew triage/to meet on Regional tickets in backlog/close out tickets
  3. If there is no history and you can't see anything that means it wasn't submitted. Figuring out how we want to track that is a future conversation. UX to review TDP Submission History to start.