Research with other teams

Research script

Before showing prototype

Has there been an instance where you needed to track if someone changed something to your product?
- Where? What usecase?
- Who did so?
Are you currently adding information / changes to a part of the tool? What is that workflow?
- Who is doing so?
Which changes would you like to keep track of? What are the usecases you can envision for your product?
- What granularity is needed in seeing changes made? Should this be on top level (for instance organisation name)? Or on a deeper part of the product (specific page/feature)?
Are there different roles & responsibilities in making changes?
- Are there usecases where you can envision reviewing changes prior to making them would be useful?
- Are there usecases where you'd want to be alerted when certain changes are made?
Would you need to see changes in the product or in a back-end?

With showing prototype

Product page:
- Is there a usecase for seeing the changes on the page (vs in a back-end) would you want to see changes on this page as well?
back-end page
- (export function) Can you tell us ore about a use where you would want to analyse the changes outside of the environment?
- (watch functionality) What do you think this button does?
- Would you want a summary of the changes made to a product entity or feature?
Person who made changes page
- Is there a usecase where you'd want to get in touch with a person that made changes?
- (reporting functionality) Should people be able to report faulty data? Who would do so? What is the context?
- Would you want a summary of who creates changes and where?
Revision page
- Is there a need for someone to revize data that changed (like a super editor)?

Can you rank these features from most to least important?

if we allow anyone to build on this super admin, would you do so?

Last updated 1 year ago