Description
Record the team's decision and reason for every research recommendation, check later whether accepted items shipped, and roll results into a per-product scorecard.
Recommendations are often agreed in a readout and then forgotten. This method adds a status column to the recommendations table, captures a decision (accept, reject, investigate further) and a reason for each at a prioritisation meeting, asks teams to cite research as the source in requirements, and revisits after release to record what shipped. Results roll up into a scorecard showing which products received research support, how often, and how much was acted on. It answers complaints by showing whether earlier recommendations were implemented (for example 12 of 15 accepted but only 5 shipped) and gives executives an at-a-glance view of research impact.
Attributes
- Discipline
- Research Design & Rigor
- Loss type
- Latent
- Stage
- Post-launch
- Data
- Quantitative
- Effort
- Days
Steps
- Add a status and reason column to every study's recommendations table.
- At the prioritisation meeting, record a decision (accept, reject, investigate) and a reason for each recommendation.
- Ask the team to cite the research as the source when recommendations enter requirements or tickets.
- After each release, record which accepted recommendations actually shipped.
- Summarise per product in a scorecard (studies run, recommendations made, accepted, shipped) and review it periodically with leadership.
Sources
- Understanding Your Users (Baxter et al., 2015)
Also known as
- Recommendation status tracking and research scorecard
- Usability scorecard
- Recommendation tracking
- Research impact tracking
Categories
- Research Operations
- Research Design & Rigor