Comments on: Leaders Want Input. Employees Won’t Share It. What Can We Do? https://cruciallearning.com/blog/leaders-want-input-employees-wont-share-it-what-can-we-do/ VitalSmarts is now Crucial Learning Thu, 06 May 2021 14:59:34 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Jason F. https://cruciallearning.com/blog/leaders-want-input-employees-wont-share-it-what-can-we-do/#comment-7700 Thu, 06 May 2021 14:59:34 +0000 https://www.vitalsmarts.com/crucialskills/?p=9214#comment-7700 After asking for and receiving ideas and input, one of the worst actions a manager can do is take the input and make it sound like it was their (the manager’s) idea. This is demoralizing to the individual and team and causes even further shut-down in communication. People will shift back to work in silos and ‘protect’ their thoughts and ideas because of fear that others will take the credit for them. If someone has a good idea, bring the individual(s) in and let them lead the implementation of it; don’t try to implement other’s ideas. This builds confidence and makes people feel valued, heard, and part of the larger team.

There is a saying that ‘good leaders always give credit to others when there is success and take blame when things go wrong’ — in other words, give credit where credit is due and take blame when there is a problem. In this case, the management team should be more vulnerable; be open and willing to take blame for poor communication within the team/company, not take credit for anything good, and give credit to individuals and the team for making changes that benefit the team, company, customers, other stakeholders, and maybe even the bottom line.

And lastly, and maybe most importantly, make sure your words match your actions – if you lose this integrity, shut-down in communication will inevitably repeat itself.

]]>
By: Heather B. https://cruciallearning.com/blog/leaders-want-input-employees-wont-share-it-what-can-we-do/#comment-7699 Wed, 05 May 2021 18:18:37 +0000 https://www.vitalsmarts.com/crucialskills/?p=9214#comment-7699 It may also be helpful to share a detailed agenda in advance and let staff know that the group will be discussing ideas/feedback/etc. This gives people time to consider what they would want to share, rather than potentially being put on the spot in the moment.

]]>
By: Mary Parker https://cruciallearning.com/blog/leaders-want-input-employees-wont-share-it-what-can-we-do/#comment-7698 Wed, 05 May 2021 17:09:25 +0000 https://www.vitalsmarts.com/crucialskills/?p=9214#comment-7698 It’s incredibly important to also plan for how you will handle any input. If people are brave and provide feedback, but are then attacked or disparaged for doing this, communication will be completely shut down. Sometimes, the best we can do is offer thanks for their insights. But, if you’re not willing to do something with the comments, then it is best to not even ask as that will destroy any credibility.

]]>
By: Joy Exstein https://cruciallearning.com/blog/leaders-want-input-employees-wont-share-it-what-can-we-do/#comment-7697 Wed, 05 May 2021 16:44:08 +0000 https://www.vitalsmarts.com/crucialskills/?p=9214#comment-7697 Why not comment? Very simple – while some welcome comments, there can be repercussions, leadership gossip about what was said.

]]>
By: ir. K.E. (Karel) van Zanten https://cruciallearning.com/blog/leaders-want-input-employees-wont-share-it-what-can-we-do/#comment-7696 Wed, 05 May 2021 15:29:04 +0000 https://www.vitalsmarts.com/crucialskills/?p=9214#comment-7696 As an IT ‘test coordinator’ I tried to get the best plans, procedures etc. for the testers and the organization. So I composed a draft and we did a ‘quality review’ as described in the project management method PRINCE2. More specifically: we met with a group of 2 to 6 people, I read the draft aloud and every comment was noted. Then I processed the collected comments in a second draft. This underwent the same procedure.
The result was that the participants saw and recognized that their comments were taken seriously. The second draft usually needed only minor modifications and then was fit for purpose. The document became the participants’ own document and commitment to what was in it was self evident.
This approach worked with ‘underlings’ and with ‘higher ups’ (program manager, head of IT, head of software development, project manager, me and a scribe).

Caveat: I work in The Netherlands. Dutch culture is different from US culture, or should I say NY, TX or CA culture.

]]>
By: Rick Paradis https://cruciallearning.com/blog/leaders-want-input-employees-wont-share-it-what-can-we-do/#comment-7695 Wed, 05 May 2021 15:19:14 +0000 https://www.vitalsmarts.com/crucialskills/?p=9214#comment-7695 It may also be worth considering alternatives to large group sharing and discussion. Perhaps have people discuss in trios or small groups first. Provide options for sharing the results of these small group discussions – for example, if you’re working online, ask groups to type in their highlights into a common whiteboard, add check marks to ideas they see and agree with. Make it about the ideas more than who raises them.

]]>
By: George R Wilhelmsen https://cruciallearning.com/blog/leaders-want-input-employees-wont-share-it-what-can-we-do/#comment-7694 Wed, 05 May 2021 14:48:57 +0000 https://www.vitalsmarts.com/crucialskills/?p=9214#comment-7694 There are a lot of good points here.

However, they may miss the elephant in the room – that leaders can be dismissive of such feedback, which is what kills the flow in the first place.

To break down this erected barrier (and make no mistake about it – it’s a strong barrier), the leader has to admit fault – “In the past, I have asked for input, and then didn’t listen effectively. I pledge to you that I am going to change, and I need your help to do it. Hold me accountable if I do anything other than take the input and write it down. Feel free to tell me if I don’t meet this commitment I’m making to you.”

Then ask the question and go quiet. Uncomfortably quiet. Have an easel with a pen in your hand. Write the problem on the top of the easel.

And then wait.

The suggestions will come.

Now the important part: All the leader does is write down what is said. Paraphrasing is okay, but it is critical to capture the statement. Then ask “Did I capture that correctly?” If they say no, ask for feedback and fix it. Then wait for more statements.

Don’t offer your opinions of “We tried that, it didn’t work” or anything similar, whether true or your perception. Allow the team to freely offer ideas, and write them all down. If you get more than a page, KEEP WRITING.

When everyone is done, now is the time to discuss those ideas. Let the TEAM analyze / vette / discuss the concepts.

All ideas are good, but let the TEAM run with this. Allow them to vote. Everyone gets 3 dots. You can put them on one or three solutions you think work best. All the dots are the same color.

Then come back and recap: Here are the 3 (or whatever number) solutions we are going to pursue. We’ll need people to look at these – would anyone like to volunteer to take on or join each of these teams?

Again, you wait. People will step up. It will help if you say “We’ll give each team a week to review the proposal and let us know why it is the best option, or after your analysis, why it isn’t the best option. This isn’t going to be piled on to your existing work – we’ll move deadlines so you can work on this with the right focus.” Then take those actions.

I’ve done this, and it is very effective. And the Leader speaks last, and ONLY in support of the great ideas presented.

So if you think you’re done, you are wrong. To repeat this, you’ll need to follow the same approach every time. If you slip once back to what caused their silence, you will have convinced them you have fallen back, and they’ll go back to the silence your management style engendered in the first place!

Good luck.

]]>