Stop Proposal: Stop maintaining the PPS data on the "Features by Theme" page
Start pointing to the Post purchase survey (PPS) Dashboard
We currently update the pps_*
values in features.yml
in order to populate the Features by Theme page.
We should discontinue maintaining those values and instead direct the audience to the PPS Dashboard.
What was the initial objective?
!66574 (merged) created features/by-theme
in order to create:
a page that represents the key features by capability and cleanups some of the listed features for those capabilities. The cleanup mostly involved removing features that seemed duplicative when listed alongside others in the same capability.
!84577 (merged) added the PPS data to the page ...
But there isn't any additional context on the intent in the MR.
Are we achieving the objective?
I'm not sure, but updating the pps values to populate that page is an inefficient, time-consuming process.
Now that all of the PPS data is available in Sisense we should utilize it as the primary destination for this type of data.
If grouping the results by pricing theme is valuable to team members, we could explore a way to provide that visualization in Sisense.
Proposal
- Remove the PPS values from the table and return the page to its initial design:
Wayback machine
-
Add a link to the page pointing visitors to the PPS Dashboard if they are looking for PPS data for a given feature.
-
Optionally, delete the page entirely if "Features by Theme" is no longer used by team members in strategic decision making.
Traffic
Is there an audience for this page?
The page had 711 visits in calendar year 2022. 509 if you remove that strange spike at the end of August.
The vast majority are from Google, but I'm not sure what to make of that.
It's an internal-facing page, so the low traffic may not be particularly instructive.