Skip to main content

Smash the echo chamber

Who doesn't enjoy the warm glow of validation that comes from having others strongly agree with their opinions?

It's a great feeling; it's encouraging,  and a gentle massage to our self-confidence.

Without this experience, all but the most arrogant of us would soon be wracked with self-doubt, so it's certainly not a bad thing.

But... everything in moderation!

At time-of-writing I'm in the position of having a team who are incredibly comfortable in voicing their opinion.  Whether they're just brutal or a little further along the spectrum than the average developer I can't be certain, but I do know I can rely on hearing their opinions.

Not a great environment if you're sensitive, but it does force me to challenge my views, thoughts, and actions on a regular basis.  And on the assumption that I'm not always correct, which my wife assures me is the case, that's a great thing!

Why?

Because living inside your comfort zone 24/7 can only result in maintaining the status quo.

To stay in that optimal spot between the comfort zone and a place that will cause you to panic you cannot stay in an echo chamber of carbon-copy opinions.

Not the bullseye, not the bullseye!!

"[A person] does well to encounter those of whom she has little knowledge orthoses by whom she feels threatened or intimidated.  The benefits of this broadening of social experience go far beyond a simple increase in understanding of actual people and groups she meets.  In more general terms it tends to increase confidence and also humility, both of which facilitate the development of empathy."
- Mearns and Thorne*

Balance

And here comes my most commonly used word: BALANCE.

Though it's hard to tell if we're in the optimal zone it's safe to assume that if we experience no discomfort at all we might be a little too relaxed.  On the contrary, if we are always uncomfortably on-edge, then it's also worthy of review.

"You need to place one foot in what you have mastered and understood and the other in what you are currently exploring and mastering... That is where there is something new to master and some way that you can be improved. That is where meaning is to be found."
- Peterson **

Pick your battles

If you're a firefighter and climbing a ladder makes you tremble, you definitely have something to address.  But if you're a software developer it's less of a career-limiting factor.

You don't have to be comfortable with everything - no-one is.  Richard Branson has made it to the top of the entrepreneurial tree without having any level of comfort in basic mathematics (he's dyslexic, but has harnessed it to his own ends).  He has made sure over the years to push hard at challenges BUT not to spend time on unwinnable battles.  Instead, he poured his energy into creating businesses and left the numbers to his accountants.

So

- Get out of the echo chamber
- Start a debate
- Get proved wrong
- React well
- Learn from it
- Improve.
  
Whenever I start working with a new client or a new team, whatever else I forget or leave behind, I'll hopefully go there as a slightly improved iteration of myself.

References:

* - Person-centered counselling in action.
Dave Mearns and Brian Thorne
ISBN: 0 8039 8050 7
https://uk.sagepub.com/en-gb/eur/person-centred-counselling-in-action/book238837

** - 12 Rules for life
Jordan Peterson
ISBN: 978 0 241 35163 5

Comments

Popular posts from this blog

The case for Project Management in Agile?

OK, I know how most of the Agile community feels about Project Managers: Process over People Meetings Documentation Urrgh... But however you name the role (Agile Delivery, Scrum Master, Project Manager) and whoever does it  - someone needs to help the team to: Plan Track Deliver Communicate Being a group of incredibly talented engineers does not give a team the right to ignore 3.5 of these. All too often, engineers want to dive in to designing and building great software, but see planning as a hassle, tracking as a waste of time (or an abuse of their rights), communication as an alien concept and delivery (the fun bit) as something that will be done when it's done. It may be popular to talk about being a 'self-organising team' and railing against any form of 'order' being imposed.  But why is that order being imposed?  Maybe it's to deal with the chaos that your s-o-t has failed to deal with so far. As organisations scale and the senior leadership gets further a...

Agile Armchair Generals

If you're an Agile practitioner of any sort you will understand what I mean by Armchair Generals (if not, it may be an idea to check if you are one..). Apropos of nothing an email arrives that questions the management of your project in terms of whether it is properly 'Agile'. Feedback is, of course, a great tool.  But it must always be understood within the context of the person providing it. So when the email lands questioning the type of contingency you've built into your project or the depth of analysis performed on your requirements set, ask yourself: 1. Has the questioner spotted something you and the team have missed? It happens.  That's why independent reviews can be helpful. 2. Has the questioner misunderstood something about your project?  If so, maybe your communications weren't quite clear enough or they've missed something - it happens, we're all busy. If the questioner has understood the topic correctly and is simply disagreeing ...

Project Team morale and how it is affected by YOUR leadership style.

If I asked what qualifies someone to lead an IT Project you might immediately think of literal qualifications; a degree, a PRINCE2 practitioner certificate, DSDM certification. You might think of the practical skills needed to achieve Project Management tasks; the ability to plan, management of RAID/CARDI items, stakeholder communication. All of these things are vital to managing a project, but as we're often reminded: Management ≠ Leadership And projects need leaders.   Why?  Because people need leaders.  Humans are pack orientated creatures and we are most comfortable within a structure that supports and guides us.  Within a project the same is true.  The 'doers' usually thrive within a supporting structure that takes care of their (professional) needs and protects them from attack.  Without Developers and Testers the rest of the project team is just a lot of expensive * flesh. In a mature and capable project team there is a certain joy to be ...