Reviewing your business is a smart step to take if you’re about to start doing something new and maybe something that makes you a little nervous. It’s about taking a critical eye to products, processes, or programs before they are implemented. If done correctly, you’ll save time and money by revealing problems.
The reviews should be inspired by the kind of comments you find on websites like Amazon.com or Yelp.com. While these reviews can be painfully honest, they can expose hidden issues.
Often, when something new is being developed at a business, it’s created in an environment that doesn’t include criticism. An executive team may be asked, “Do you like it or not?”
This question only considers two answers: a “yes” or a “no.” Some successful and unsuccessful ideas exist in the space in between those two responses. It’s better to have your team write reviews of the new thing from different perspectives.
Scenario One
Imagine a company switched to an online computer system designed to track productivity.
Someone who was reviewing the program from the perspective of the employee in the field, might realize not everyone has easy access to a computer or works in a place with no Wi-Fi or cellular reception.
The review might read, “Great program but I can’t use it on a regular basis.”
As a result, the business could then decide whether to continue to pursue the program on a limited basis, make accommodations to allow better access, or scrap it entirely.
Scenario Two
Another scenario could see a business changing its hours of operation. Imagine if a grocery store considered switching to banker’s hours. While employees might be thrilled with the change, the general public could hate the idea.
A review written from the perspective of a shopper might say, “This place is never open when I need it. I’m going elsewhere.”
By writing a review, you allow your team to cast a critical eye at something without them feeling like they’re directly challenging it.
Try reviewing your business from different perspectives. It’s better to discover potentially negative feedback, while you can still make changes, rather than after the problem is created.
