Design Reports for your Users

When you create reports, design them for the end-user in mind, especially if it's not you. For example, if you want to roll up a report to the executive team, you want to invoke modules that pertain to high-level analytics and trends.

An actual department head might want to know more specifics. For example, an individual in shipping may want to know all the negative reviews with the 'Shipping' tag.

Example 1 - The Analyst

This day-to-day user of the platform is not actively replying back or engaging with customers but trying to understand trends in reporting, identify issues before they start, and generally understand the influx of information.

Recipes for the Analyst

Review Acquisition - This shows you collection effectiveness for each acquisition method alongside a summary of star rating breakdown for the period.

Instant Surveys - This gives you insight into what people are thinking immediately after purchasing a product from your store.

Example 2 - The Executive

The executive wants to know high-level trends to make decisions. Where are there supply line issues? What's happening with shipping due to slowdowns in a particular factory? What are people saying about all of this? What are the collection rates and how effective are the review collection programs?

Did this answer your question?