User research & feedback strategy for PW work within portfolio of existing products

[rachel-kauff]

Description

(Note: Used to be a CMS issue, PW took it over in 2023) User story

AS A PO/PM I WANT to formulate a strategy for incorporating Veteran research and feedback into portfolio maintenance decisions SO THAT we can direct future PW's run-and-maintain work where it will most impact Veterans. Background / Engineering notes

Resources:

[PW portfolio excel](https://dvagov-my.sharepoint.com/:x:/r/personal/wesley_rowe_va_gov/Documents/PW%20portfolio.xlsx?d=w2c8c26b2b1f0446ca786971396f14eb8&csf=1&web=1&e=EdpTCK) - documents high-level current understanding of product portfolio along with KPIs, status of research, etc

Acceptance criteria

[ ]

[EWashb]

@davidmpickett I feel like you've completed this with your runbook. Thoughts? Personally, I think this is ok to close

[davidmpickett]

I think it's safe to close. There may still be other opportunities to look at research strategy, but so much has changed since this was written, it might be easier to write something fresh later.

[EWashb]

The original intent of this ticket was aimed at editorial research, not Veteran research. Editorial research governance is being led and actively worked on with the CMS Team as we transition into Platform.

@wesrowe @jilladams are you using this epic for PW Veteran-facing research? Do you mind editing this ticket description for Veteran-facing research, adding your appropriate labels, and moving it out of the CMS backlog or moving your associated tickets out of this epic? I'm closing duplicative and old tickets for my teams now, and this is one of them.

[wesrowe]

@EWashb, it looks like we took this thing over without reading the epic. I'll take credit. The title was good.

I'll take it over to PW and revise.