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
Labels:

Comments

Post a Comment

Popular posts from this blog

Continuous (Self) Improvement

“Everyone thinks of changing the world, but no one thinks of changing himself.” - Leo Tolstoy Introduction: Most people talk a great game about continuous improvement.  And as a group, most of us truly agree with and see the benefits of, the concept as applied to our projects and teams. Sprint Retrospectives, Post Implementation Reviews, 5S, DMAIC, PDSA (not the dog people) and so on. But... Do you practice it personally ?  I don't mean training courses, formal development plans and all the other bureaucracy that people step through stoically every year in a bid to get a pay rise.  I'm referring to the small (but meaningful) improvements we can make every day. Or to work in an Agile principle: "At regular intervals, the team (of one in this case) reflects on how  to become more effective, then tunes and adjusts  its behavior accordingly." Step 1: Feedback (aka input to the CI process): Of course, all improvements need to be identified i...
Post a Comment
Read more

"We are Agile!"

A phrase Project Managers hear a lot, and one that occasionally proves to be at least partly true. As it's most often spoken rather than written, it is hard to know whether the speaker means 'agile' or 'Agile'.  I find that asking the question ('big A' Agile or 'small a' agile?) can reveal a lot about that person's knowledge of the 'Agile' world.  If you find yourself asking the people around you this question and you receive blank faces or confused responses you can be fairly certain you haven't landed in a particularly Agile organisation, rather you're somewhere that has rolled out a buzzword in the hope of improving speed of delivery. Organisations tend to fall into one of the following categories: - Comfortably Waterfall - Fine . This organisation knows how it wants to work and perhaps has reasons why they prefer to keep projects waterfall. - Waterfall but concerned they need to get on the Agile bandwagon - Confused ....
Post a Comment
Read more

Definition of Done - An example

Done? To call a story 'Done-Done' we should refer to two things: the acceptance criteria for each story the team’s Definition of Done The DoD is defined by the team and should be updated whenever it seems appropriate e.g if there's a big change in the team or the work; or the team simply sees the need for a change. If you have project based teams, it's something to agree before timebox 1 kicks off. If you're more product based and continuously working through an ever growing backlog, slot it into a timebox kick-off, a retro (if that's where it was discussed) or just grab 10 minutes after the daily stand-up. An Example: Here's a basic example created by a team I was working with: ---------------------------------------------------------- A. Dev done ---- Code review done ---- Unit Tests written and passing ---- Integration tests written and passing B. Test complete ---- Manual Testing complete – Acceptance Met ---- Automation Tests written and ...
Post a Comment
Read more