Guideline: Providing Asset Feedback
This guideline provides a detailed list of things to be considered when feedback is provided for an asset.
Relationships
Related Elements
Main Description

The Asset Repository may provide automated feedback mechanisms. This means the Asset Repository would notify the Asset Consumer shortly after retrieving the asset, requesting feedback and surveys to be taken.

If the Asset Repository does not provide automated feedback mechanisms, then the Administrators should solicit feedback from the Asset Consumer.

When sending a survey to the Asset Consumer, there are some sample questions to consider, such as:

  • How long did it take to use the asset?
  • What amount of time was saved by using the asset?
  • What did not go well with using the asset?
  • On what asset discussion forums have you participated?
  • On average, how much time do you spend searching for each asset?
  • Can you estimate what percentage of searches result in not finding what you want?
  • What assets do you need in the repository, but you cannot find?
  • What kinds of assets do you not need?
  • When you have submitted defects, have you received a timely response on the defect?
  • How do you generally search for assets, keywords, search filters, custom tags, combination?
  • Have you subscribed to any assets or searches? If so, have you received notification of events?

Keep track of the number of survey responses that are sent back.

Another key form of feedback is user success stories. The Asset Owner and Administrators should actively pursue collecting these and then promoting the successes. There are several forms of promoting these stories including sending newsletters via email to stakeholders.

Another way of communicating successes is to update the metadata structure on assets in the repository and include this information. This benefits potential Asset Consumer(s) as they evaluate assets. The Administrator can also create an Asset Type in the Asset Repository called Asset Success Story, and can store asset success stories in the repository and create relationships to the assets involved in the success story. This becomes a simple approach to finding the success stories and then navigating to the assets involved.