The Consultant's Desk

The Consultant's Desk
Poring over the details on your behalf
Showing posts with label respect. Show all posts
Showing posts with label respect. Show all posts

Thursday, October 26, 2017

More Workplace Abuse Resources

It's with great dismay that a particular page needs to be closed. The reason for the reluctance is because the content is so useful (and I need the laptop resources). The site is called "When An Abuser Goes to Work" and is authored by Patricia G. Barnes, J.D. Patricia also focuses on age discrimination at Age Discrimination in Employment. Unlike Chai Feldblum, Patricia has not been an EEOC Commissioner. But she has been a judge and is a lawyer. Their advocacy is Title VII related but on specific aspects of enforcement of rights for particular constituents.

When you visit her LinkedIn profile, you'll notice that Chai has a strong leaning toward supporting gay and lesbian rights. She is a contributor to a book title on religion and same-sex marriage. She also keeps her followers up to date on the outcome of EEOC age discrimination cases (that were not under her purview).

Patricia has written on a wide swath of Title VII issues, in addition to workplace abuses. Yes, it is entirely possible to visit her blog to learn what she's published. But I'd like to preserve at least some of those titles here (until I can move them to my website's Library) where we'll have a quick reference to her insights on the subjects.

Pat Barnes' list of aggressive behaviors in the workplace is not only enlightening, it's what's been considered offensive and abusive over time. Failing to respond to phone calls and messages is the classic. Recruiters (both retained and staffing industry) use the excuse that they're too busy. Too busy to get someone (a motivated worker) employed? No one comes up with a spoken excuse for interrupting. However, the underlying message is what the person has to say isn't important. The other unspoken message is the one doing the interrupting is entitled to do so; they are privileged.

There are times when an interruption is a kind gesture. The train of thought is meandering or drifting into whining. The speaker needs to get refocused. Sometimes they may be exhibiting distress and needs to regather their thoughts. Many times, unfortunately, none of those reasons are the case. There was no kindness intended. The one doing the interrupting is simply showing they have very little regard for the one who was speaking.

There are a lot of behaviors that demonstrate abuse in the workplace. Perhaps taking in what these two authors have to say on the subject will help make us more aware and more inclined to discourage the behavior.

Resources:
Sponsored Links:

Thursday, November 24, 2016

OD Cautionary Lessons

There are times when teachable moments happen in a spontaneous way. You're not looking for them but they sort of leap in front of you as though challenging you to see whether you'll speak up or let them continue to fester. There are many risks when these situations arise.
  • The company brand suffers
  • Customers become annoyed and abandon the store or even the entire company
  • Customers take their business to the competition
  • Lack of training becomes obvious, causing further deterioration in credibility
  • Your business looks ridiculous
In an effort to avert these and other consequences of poor development initiatives and poor hiring strategies, here are a few cautionary lessons.

Cautionary lesson 1: Assign personnel to areas where they are most effective and then train them to learn and take on gradually increasing duties.

Cautionary lesson 2: Make certain a customer is treated with respect at every phase of contact. If they do not receive immediate attention because of high traffic, let them know that they are part of a queue and will be attended within the next [insert reasonable number] minutes.

Cautionary lesson 3: Don't put the customer through a chain of referrals that exceeds 2 unless it is absolutely mandatory. If the referrals are necessary, provide some reasonable explanation.















Cautionary lesson 4: Don't allow the wait time between referrals to amount to more than 2 minutes if at all possible. If the wait is longer, provide a reasonable expectation of when service will be provided.

Cautionary lesson 5: The customer will not be impressed when attending to their needs is put off by allowing the associate tell the customer they cannot be served because the associate is too busy doing something else that's more important. Don't be surprised if the customer responds that they have something else to do as well.

Cautionary lesson 6: When the employee is falling down on customer service, back office reprimands don't help rebuild brand. Asking the employee in the presence of the customer if the employee has knowledge about the service that was supposed to be delivered helps in the understanding on both sides of the equation. Immediately begin serving the customer while the employee watches and learns.

Cautionary lesson 7: Sometimes the customer who's being put on hold and referred around the store to all the personnel until they're back to the original is actually some type of expert who could be a consultant for your office. Refer to Cautionary lesson 2. Consider the image of the company that begins to form in the customer's mind as these types of scenarios evolve.

Chaos is one way to describe it. Is that what was intended?

Sponsored Links:



Monday, June 29, 2015

Maslow and Retention Strategies

Abraham Maslow introduced his hierarchy of needs circa 1940s. The validity of his theory took hold and has grown in the scope of dynamics it covers. The chart can be found in quite a number of places on the Web.

Tim Vandevall's printable version comes in both color and black and white. Some of you may be interested in something that's a little more straightforward in presentation. In that case, consider one of these versions.

The theory is explained in more detail on other sites. However, one thing becomes very apparent as each level is examined: the principles can be applied to essentially any type of organization or social unit.

What characteristics does a person who is self actualized exhibit? You know, the more I read and re-read McLeod's discussion of those 15 traits, the more I realize there are many people who have them. Unfortunately, they tend to be free spirits in relation to where they go and the people with whom they associate and interact. Many are labelled as crazy or odd while others are simply called fun. The label that's applied has many aspects for its interpretation. And many times the insecurity of the one doing the labeling plays into that. If the one doing the labeling carries some amount of authority, others will do little to make their own, independent evaluation and will simply rely on the faulty characterization.

Wikipedia traces even more of the theory, its challenges, and its expansion to seven tiers. In the 1960s and '70s, an eighth tier was added wherein a person who has reached a certain level of their own actualization turns to others in order to help them in their growth and fulfillment. It's a bit like paying it forward by becoming the teacher or mentor.

Still, the level at which we approach self actualization is what workers strive to achieve when they become employed for an organization. They want to be respected; they want to feel as though they are genuinely growing in their knowledge and abilities. They want to feel their talents are growing and they are serving the needs of customers and colleagues. It's like engagement but it's also more than mere engagement. It begins to pay in value because of loyalty - customer and employee - and referrals. It becomes expansive because the reach grows as the organization's reputation does so. It's a healthy place to be.

So I ask you who are managers, governing executives, HR professionals: What are you doing to create an environment that feeds the eight levels of needs? What are you doing to retain your valued workforce? As you map your designs for growth, you want to find yourself providing more than the basics and survival needs. It would be good to supersede the belonging level and start banging your head at versions past esteem. Perhaps qualifying for that growth entails having your people outline not only their plans for self actualization but also how to achieve it economically and so that the costs can be recouped in some way.

And now I turn to those who are employees or job seekers. As you do your research about a company, are you keeping Maslow's hierarchy in mind when it comes to finding an employer who can fulfill at least most of your needs and desires?

Resources:
Sponsored Links:

Tuesday, May 29, 2012

Thoughts on Enterprise Social Media Protocols, Pt. 2

Star status is important to some and not to others. Knowledge that they've been part of the end product sometimes carries its own limelight. To cut the negative side of competitiveness, it's important to acknowledge the more significant contributions of certain members of the team. However, the leader also needs to recognize how the rest of the team contributed to reaching that plateau.

Secretiveness among members needs to be discouraged. If there's an offsite meeting or finding, the results need to be shared with those who could not be present. It's such bad form to have suspicion coloring what's done. It leads to mistrust and eventual exits that create delays in the project while the replacements are hired. And the project will then have to absorb at least some of the replacement costs of search, intake, training, and returning to the point where the team was before the loss of manpower.

Make certain systems work. If there's a malfunction, the basis for it needs to be discovered and disclosed so that it won't happen again and so that successors don't have to deal with it. The basis for the malfunction, once discovered, needs to be revealed so it can be avoided and personnel can feel as though their efforts are subject to being thwarted (i.e., a major waste of time).

If someone on the team is promised feedback, more information, asked to attend a meeting, they need to receive what they've committed to. Make it on time, or as close to on time as possible. They may be sitting on something that requires that bit of information; delay causes their part to either not be delivered or delivered late. Coming back to the team member for a meeting that's before the appointed time is the same as telling them their schedule has no value and that you feel they're simply sitting around with nothing to do and waiting for your precious presence. Don't come off as smug and self important.

Additionally, the team member may have quite a bit on their plate. Putting the meeting (whether in person, by phone or Skype, or some other mode) on their calendar and clearing out a point when they can give you their undivided attention allows them to keep their workflow moving and timely. A spontaneous change because one has jumped the gun or suddenly has an open slot in the day is quite simply selfish. Other priorities then get shifted to a different situation. Progress is thrown off to the point of having to be rescheduled to another day or may even be lost because there simply is no longer any time for the exercise. Keep appointments. If it can't be done and you realize it, reschedule for another time that is mutually convenient.

Now that we're in the 21st Century, people seem to forget some of the Web 1.0 netiquette we used to practice. There used to be these cute little abbreviations and initials that gave us clues, initials such as "afk" which stood for "away from keyboard" (a tactful way of saying I need to get something, put out the fire, go to the bathroom, etc.) and "brb" which stood for "be right back." Both of those let us know that the person on the other end was no longer available for a short duration.

Unfortunately, we've lost touch with those practices. Now people will walk away from the computer and have a meal, go visit with someone in another building, have a conversation with someone else in person for 30 - 60 minutes. Respect your team mates and their time. Let them know when you're stepping away. Let them know when the absence will be protracted. You're more apt to get their future cooperation when they're shown that they and their time are valued.

Sunday, May 27, 2012

Thoughts on Enterprise Social Media Protocols, Pt. 1


Enterprise Social Media relates to shared information from one department manager to the rest of their personnel as well as from one department to another (or several), and then from the CxO office to the rest of the enterprise. That means reaching out to all of the teams, whether in the 2-3 person business as well as the global enterprise with thousands of employees.

Because the reach is so vast, and the message can be distributed so quickly, great care needs to be taken that people who are hired appreciate and respect the sensitivity of information that is shared. Team members need to keep project details and findings within their team until they are told it is ready for distribution. Even then, their leader needs to define the breadth of the distribution.

Corporate culture with regard to feedback and results of work can be playful on occasion just to keep things fresh and not oppressive (or boring and tedious). However, the jocular moments need to be defined as such because a text message or email doesn't contain voice inflections (unless they're composed on a voice synthesizer) and not everyone from the same country, let alone the same region, understands some things that are humor. But I digress.

Team members need to respect one another in every way. Likewise they need to be imbued with the power to build the results of what they do by being able to offer a different perspective or even object to something that's been put on the table. But they also need to take responsibility for those positions by offering the basis for the position. When points of differences are defined, it's easier to understand where the idea won't work in a particular situation but may be one of the potential solutions in another setting. And understanding the reasoning behind the support or rejection helps to shed light on the project side of it and not allow it to be construed as a matter of personality.

There's no room for gossip (unfounded information about others or things); there's no room for needless distractions that tend to cause panic or discomfort. Constructive criticism should be encouraged for the sake of growth and learning. Learning should be encouraged. Good communication skills through open, tactful speech should be encouraged. Tact is paramount followed by exchanges between parties for the sake of transmission of information as well as building alliances. And exchanges of information mean confirming that the correct message was heard by the correct party(ies). Confusion about terms and terminology should be cleared up quickly so everyone is on the same page.

Nor should there be any space in any way for threats of punishment, suggestions of coercion, destruction of input to work or research or work, withholding of privileges for lack of consent. Abusive and retaliatory consequences simply do not belong in your corporate culture much less on any of your teams. Isolation, being ostracized, personality differences, failure to recognize the advantages of diversity of culture, ethnicity, abilities, and even age make being in your enterprise not a healthy place to be. Get rid of all of it and don't let it slide under the door.

Star status is important to some and not to others. Knowledge that they've been part of the end product sometimes carries its own limelight. To cut the negative side of competitiveness, it's important to acknowledge the more significant contributions of certain members of the team. However, the leader also needs to recognize how the rest of the team contributed to reaching that plateau.