Team Trap #5: Withholding Information

This content is syndicated from Insights You Can Use by Esther Derby. To view the original post in full, click here.

I’m not talking about information related to the task and context, here, though that can damage a team. Withholding that sort of information is unacceptable, and probably pathological. I’m talking about a different sort of information: information about your internal state .

Let me tell you a story about a team I coached. They’d asked me to observe them solving a problem, help them see their process and offer advice.  Ten minutes into the task things started to go awry.

The team was standing around a  whiteboard, and had generated a list of possible solutions to the problem. They’d started filtering the options, testing them against the requirements of the assignment, adding notes as they went.  As they eliminated options the guy with the marker, Jon, crossed off the options.  Until he got to Harry’s idea.  The board was getting crowded and when Harry’s idea didn’t pass the tests,  Jon erased it.

Harry tilted his chin down.   Then he crossed his arms over his chest, and took two steps back from the group. Everyone else was focused on the white board and didn’t notice as Harry withdrew.

When he didn’t rejoin the group within a few minutes, I approached him, touched his elbow and asked “What’s happening for you?”

“They rejected my idea,” he said. “Wiped it right off the board, like I’m nothing.”

(Notice that he equated rejecting his idea with rejecting him. Easy for us to say that’s not the case; you have to start where people are, not where you think they should be.)

“You have to tell the team,” I said.

He shook his head.  ”No one is even notices that I’m not participating anymore.”

“All the more reason to let them know. They’re engrossed in the task, and they’re missing some important information about what’s happening to the team.”

Harry gave me a blank stare.  “You are withholding information that the team needs to function well,” I explained. “They need to know that one of their members has just checked out.  Will you tell them?”

He nodded, got the attention of the group, said his piece.

He was right, no one had noticed that he’d checked out, and that surprised everyone.  Jon was surprised that his erasure had affected Harry so. But he didn’t try to talk Harry out of his feeling or get defensive.  ”Gosh, Harry, ” he said, “I didn’t mean it that way.”

Harry rejoined the group.

This sort of thing happens all the time.  One member of the team feels like he’s not being heard, or isn’t valued and withdraws. The rest of the group goes on, discusses, makes decisions, starts to act. The team is missing out on the intelligence, creativity and participation of that member.  They won’t  have his buy-in for decisions, and won’t have his full-hearted support for action.  When situations like this aren’t handled, relationship fracture and drains away.  When you’re part of team, you need to be willing to say what’s going on for you, so that the team stays healthy and connected.

I anticipate that at least one reader will judge Harry as thin skinned. Someone will assert that people need to “man up” and stop being so sensitive.

What I’ve noticed is that some people talk that way until they feel rejected ….and they they act pretty much the way Harry did (though sometime less grown up).

Post to Twitter

© derby for Insights You Can Use, 2011. | Permalink | 3 comments | Add to
Post tags: , , ,

Feed enhanced by Better Feed from Ozh

Leave a Reply

Your email address will not be published. Required fields are marked *

seven + 4 =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch