Here’s a problem we all face every now and then.<\/p>\n\n\n\n
It’s when a customer lets us know that an employee was somehow inappropriate.<\/p>\n\n\n\n
Maybe it was something that the customer just overheard – an inappropriate remark to another employee perhaps.<\/p>\n\n\n\n
Or maybe, some rudeness to themselves or someone else.<\/p>\n\n\n\n
Either way, we didn’t see or hear it, and we couldn\u2019t substantiate it.<\/p>\n\n\n\n
Often this reporting is as far as it goes, and nothing is done.<\/p>\n\n\n\n
This disconnect is what I want to urge us not to do.<\/p>\n\n\n\n
This situation needs to be addressed.<\/p>\n\n\n\n
With a bit of delicacy, we need to check in with them (privately, one on one) and let them know that a concern was raised about their behavior.<\/p>\n\n\n\n
This is where the delicacy comes in. We are in no way accusing them or even acting in a mode of suspicion. <\/p>\n\n\n\n
This is a check-in to simply inform them of this situation. <\/p>\n\n\n\n
We’re neutral and see what they say.<\/p>\n\n\n\n
If they confirm, well, depending on the negative impact we may be on to a coaching memo or more. More likely though will be ambiguity, denial or some other lack of clarity about what actually occurred. When this happens simply re-visit expectations and then document the conversation in our log. <\/p>\n\n\n\n
Whichever way things go, our goal is reached. That is to shine light on their actions. <\/p>\n\n\n\n
To demonstrate that managing is taking place. That follow-through is happening.<\/p>\n\n\n\n
And, that limits, guidelines, and expectations will be tended to.<\/p>\n\n\n\n
It shows you’re present.<\/p>\n\n\n\n
After a while these small check-ins will reap big rewards in not letting small problems become big problems.<\/p>\n\n\n\n
And that’s where we want to go.<\/p>\n[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]","protected":false},"excerpt":{"rendered":"
Here’s a problem we all face every now and then. It’s when a customer lets us know that an employee was somehow inappropriate. Maybe it was something that the customer just overheard – an inappropriate remark to another employee perhaps. Or maybe, some rudeness to themselves or someone else. Either way, we didn’t see or hear it, and we couldn\u2019t substantiate it. Often this reporting is as far […]<\/p>\n","protected":false},"author":1,"featured_media":2309,"comment_status":"open","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"\n
Here's a problem we all face every now and then.<\/p>\n\n\n\n
It's when a customer lets us know that an employee was somehow inappropriate.<\/p>\n\n\n\n
Maybe it was something that the customer just overheard - an inappropriate remark to another employee perhaps.<\/p>\n\n\n\n
Or maybe, some rudeness to themselves or someone else.<\/p>\n\n\n\n
Either way, we didn't see or hear it, and we couldn\u2019t substantiate it.<\/p>\n\n\n\n
Often this reporting is as far as it goes, and nothing is done.<\/p>\n\n\n\n
This disconnect is what I want to urge us not to do.<\/p>\n\n\n\n
This situation needs to be addressed.<\/p>\n\n\n\n
With a bit of delicacy, we need to check in with them (privately, one on one) and let them know that a concern was raised about their behavior.<\/p>\n\n\n\n
This is where the delicacy comes in. We are in no way accusing them or even acting in a mode of suspicion. <\/p>\n\n\n\n
This is a check-in to simply inform them of this situation. <\/p>\n\n\n\n
We're neutral and see what they say.<\/p>\n\n\n\n
If they confirm, well, depending on the negative impact we may be on to a coaching memo or more. More likely though will be ambiguity, denial or some other lack of clarity about what actually occurred. When this happens simply re-visit expectations and then document the conversation in our log. <\/p>\n\n\n\n
Whichever way things go, our goal is reached. That is to shine light on their actions. <\/p>\n\n\n\n
To demonstrate that managing is taking place. That follow-through is happening.<\/p>\n\n\n\n
And, that limits, guidelines, and expectations will be tended to.<\/p>\n\n\n\n
It shows you're present.<\/p>\n\n\n\n
After a while these small check-ins will reap big rewards in not letting small problems become big problems.<\/p>\n\n\n\n
And that's where we want to go.<\/p>\n","_et_gb_content_width":"1080","footnotes":""},"project_category":[3],"project_tag":[],"class_list":["post-2310","project","type-project","status-publish","has-post-thumbnail","hentry","project_category-m2m"],"_links":{"self":[{"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/project\/2310","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/project"}],"about":[{"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/types\/project"}],"author":[{"embeddable":true,"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/comments?post=2310"}],"version-history":[{"count":4,"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/project\/2310\/revisions"}],"predecessor-version":[{"id":2315,"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/project\/2310\/revisions\/2315"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/media\/2309"}],"wp:attachment":[{"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/media?parent=2310"}],"wp:term":[{"taxonomy":"project_category","embeddable":true,"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/project_category?post=2310"},{"taxonomy":"project_tag","embeddable":true,"href":"http:\/\/merrimanmanagementsupport.com\/index.php\/wp-json\/wp\/v2\/project_tag?post=2310"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}