Archive for the ‘Team Dynamics’ Category

The boy that cried technical theory

{Thursday, July 22nd, 2004}

I’ve been pondering the content of this blog for some-time now. As always, just like my code, if I’d have written this a month ago it would be entirely different. Here goes….

In my relatively short time in IT consulting and contracting, I’ve been fortunate enough to work on teams with members having strong technical opinions. I’ve also been unfortunate enough to work on teams where members are relatively without opinion – they are usually more focused on delivering business value. I find that one usually trades itself for the other.

It’s extremely rare to encounter a team member that has heaps of technical opinions. From my experience, both cherish and be wary of them. It’s difficult to judge the point at which serial ‘opinionators’ have more distracted the team from delivering functionality than benefited them by passing on words of wisdom. Like the boy that cried wolf, these people can initially appear important but later prove more of a distraction. Then again, if there opinion leads to an increase in efficiency, there contribution can pay for itself – so it’s tough to gauge if the pain will be worth it.

For those of you out there that are opinionators (I should mention that I’m only considering people with a RELEVANT & VALUABLE opinion) I’m not suggesting you’ve got problems, nor should you reign in your expressiveness. Far from it, I love seeing you all do what comes naturally and promote healthy discussion. I will suggest one thing though – that your colleagues need to know how to contain you. Closure communication patterns, such as ‘Digression’, ‘Offline Discussion’, ‘Email it to Me’ or perhaps even ‘Write a Book’ can effectively circumvent seemingly perpetual conversation, although I try to avoid ‘Talk to the Hand’ at the risk of burning bridges. Sustained communication patterns, such as ‘Yes, However’, ‘So that Means’ and ‘What do You Mean’ should be occasionally used with caution, especially when a team member is on the ‘really’ critical path.

All jokes aside, establishing team protocol to the circumvent less than pressing discussion can help make everyone feel productive, especially in meetings with many attendees.

A final point, for those of you like me that tend to reserve their opinion. A wise lad once told me, regardless of your environment, being honest in expressing and arguing your opinion can only help you re-enforce, grow or question your own opinion through debate. It also helps those around you further understand you and possibly learn. It’s a situation that benefits everyone.

Happy communicating!

Banter

{Thursday, May 13th, 2004}

Thanks to Pam’s generosity, this site has come into existence. It’s just celebrated its one month anniversary – but it’s missing one important feature – entries!

The author’s excuse; imminent relocation from Australia to the Netherlands. But that’s the topic of another blog.

I’ll devote my first entry to setting a precedence for the site - thrusting into the melee of technical opinion can wait for future entries.

Firstly, some notes on my writing style. My intention is not to be offensive. Occasionally, I’ll sound obtuse - the reason; I’m a big fan of direct, honest communication. Honest communication can lead to efficiencies and improvements, both personally and professionally. Granted, direct honesty usually focuses on negative aspects of a ‘thing’, and this negativity can overshadow the positivity the honesty is intended for.

I’m hoping that if the audience is aware of a ‘launch’ in advance, they will be less susceptible to being critical and defensive and more susceptible to it’s positivity. The proof will be in the pudding.

So – why the title for this blog entry – Banter?

It’s a combination of two things describing this site. It’s a blog. Expect plenty of ranting herein.

Rants are the product of people with strong opinions. As a colleague of mine once commented, people with strong opinions keep life interesting. It’s those that don’t form opinions that float around the opinions of others.

The subject of my next blog entry will be on a bi-product of honest communication – brevity. As I hope you’ll learn to appreciate, members who enjoy the sound of there own voice are dangerously effective at distracting teams.