Is your office layout keeping you from being effective?

I work in an open plan office..

Noise carries.

I like to listen to podcasts while i work, I also occasionally like to listen to music. The colleagues that I share the space with hate any kind of noise - to the point where any time they're around I'm forced into headphones, which doesn't work - the sound is too intense, too "right there", it forces me to concentrate on the sound instead of the work. Counter intuitively, background music actually makes me more effective by giving me something to block out.

The point is, I'm sitting with two other people who's working style is completely incompatible with mine. Downstairs there are at least 3 other people who work in a similar way to me - but they're from our engineering team (I'm in the sales team).

15 years ago it would have made sense that our office was organized by function - most things relied on paper, communications infrastructure was pretty average and everyone had an assistant of some kind (because admin work inevitably involved something cumbersome and inefficient).

These are the days of hot desks, remote working, video conferencing, collaboration tools and speed of thought communication. Concern for work life balance has lead us to build gyms and enforce responsible working hours and productivity concerns have us painting our walls green and running classes on emotional intelligence. After the walls have been painted and classes run, we send the same people back to their desks to work with the same person who's working habits have been distracting them and annoying them for years and wonder why their effectiveness doesn't increase greatly.

Next time you get a chance to move desks, try it. Sit with someone in an unrelated function who likes to work in the same environment you do, might surprise you just how much more you get done.

How to know you're doing the right things

I had a couple of good friends of mine have some outstanding results in their respective sports over the weekend, for both of them it was the result of well executed long term training program and was a continuation of a long term top 5 trend for both of them. They both have larger goals and it put me in mind of some advice that my old rowing coach used to give out on a regular basis that relates pretty well to my sales career.

"You don' have to be winning to know you're on track, you just have to make the final every week, eventually your number will come up"

Every week we would train and every weekend we would race, for him the truth wasn't in the winning of the finals - generally if we won he worked us harder because the only race he wanted us to win was the last one of the season - the national championships. Not making that final also provided an important feedback mechanism - either he had worked us too hard or something was just flat out wrong - and needed to change.

I think about it regularly when I'm selling now.

Am i consistently making the top 3? In the situations where I am, I know I'm on track - once you're in that top couple the outcome is generally fixed and will be decided based on things that you cant really control.

In situations where I didn't make the top 3, why? Sometimes it's a lack of time spent - (not enough training), or too much spent on other things (too much training), these things are fairly easy to tweak, what is more worrying is when I miss the mark completely - generally this is an indication of unfitness for competition, either because of things I didn't know or because I just missed the mark. If I'm consistently not in the top 3, that's a serious problem.

The top 3 test is a good litmus test, if you're regularly making the top 3 there's probably not a lot you need to change - a tweak here and there and some luck and your number will come up, if you're not regularly making the top 3, you've got a serious problem and need to seriously change something you're doing to get the results that you want.

Unfortunately sales rewards the winner and no one else, but not winning this time doesn't make you a loser. If you're in that top 3 every time and you're putting yourself out there on a regular basis, your number will come up eventually.

The limiting power of jargon and the importance of understanding why

Next time you use a piece of jargon, have a think about what you’re actually saying, do you know why the jargon describes what you think you’re saying?

Jargon is a great tool, it can provide a quick, simple way of describing a complex concept when among people of compatible technical knowledge - concepts like Standard Operating Procedure (SOP), describes in 2 seconds what could take hours to explain.

The problem with jargon is that we generally understand what we’re describing but often forget why it is described or done that way. We can end up either make changes to what the jargon describes without understanding their impact or limit ourselves within the confines of the jargon, preventing us from reaching our objectives.

This week I heard a piece of jargon used to describe a particular sporting team training time and method. The crux of the problem was the inability of a team member to make the time, what was lacking was an understanding of why the training time was as it was, a detailed understanding could have lead to an adjustment of the schedule to produce the same result, instead the term became a road block and the desired result wasn't achieved because the Jargon limited the capacity of the team members to think differently.

Next time you use a piece of Jargon to describe a way of doing things, make sure you understand why, and if you dont, use plain english - sometimes it can take longer to use less time.

Training, pain and failing forward.

How much of your working life causes you pain?

I ran the city to surf this year, more accurately, I made the city to surf my annual jog - and paid for it in the same way most things get paid for when you're unfit - in pain.

I was out of my depth. I didn't train. I turned up on the day and did the best I could with what i had and got what I deserved - 90 minutes of pain that are sure to be followed by a week of reminders.

It made me think back to my first couple of IT sales engagements. I walked off a building site literally weeks before them and was clearly out of my depth in every way. Clients regularly poked holes in my knowledge and sent me packing. It left me feeling pretty worthless and raised all kinds of questions. Mostly it made me wonder just what the hell I was thinking when I agreed to this job.

Two and a half years on, it's a different story. I'm well read, well studied and I know enough that when I admit I don't know something it's a small thing.

A large number of the things that have caused me pain in my working life came down to things that I didn't know, hadn't done before or misinterpreted when I got there. These were almost all avoidable - and I cant see myself making the same mistakes again because I've experienced the pain that goes with the failure.

Avoiding the second failure is mostly a matter of experience. The reason most senior executives are 40+ years of age is simply because at that age they've failed often enough that they will read most situations correctly because they've either had the failure themselves and made it through, or seen someone else make the same mistake.

Seeing someone else make the mistake can also be a matter of education. It's no coincidence that case studies are a major focus for some of the best business schools. If you've read many good management you've probably noticed that they generally follow a simple formula - they back every principle with a case demonstrating a situation in which it was effective.

The case study is a form of failure - it's helping you fail forward so that when you reach a point where the principles involved become relevant, you will recognize it and act accordingly. It's not as effective as having the failure yourself, but it's the next best thing - and far less soul destroying.

Next year I'm going to train for the run, I'm going to spend at least 3 months training specifically for the event - failing forward with the specific aim of enjoying the event. I'm not waiting around for it though, training is a habit that you build on every day. It's the same in every part of life and there's a chance that if it's not going well, you haven't trained.

Next time you fail, face a painful situation or get forced to really put in a super hero level of effort, ask yourself a few questions - Did you train? Are you failing forward effectively? Or are you just turning up on race day, hoping you can tough it out?

Business relevant IT - a performance metric supported approach

A simple management tenet from the late great Peter Drucker is (slightly paraphrased) "if it isn't measured, it cant be managed", yet in IT, measurement and benchmarking seem to be a long way from the conversation that is being had at most organizations.

How much time are you taking to measure the effects of your strategy?

Who are you benchmarking against and on what metrics? Are they internal IT or business relevant metrics?

According to George Westerman and Richard Hunter in their great book "The Real Business of IT", the companies who value their IT division as a strategic partner have one principal thing in common - the performance of IT is benchmarked regularly and communicated to the rest of the organization in terms relevant to them.

I'm about 50% of the way through their book and I've arrived at the conclusion that I need to modify my framework for IT projects, I've come up with the following as a framework to make sure that I always deliver value and to allow me to begin screening out those projects that either have a low probability of success or are going to be seen as the typical IT black hole that doesn't deliver value.

1 - Benchmark the current performance using relevant metrics.

2 - Understand the metrics that you are trying to influence.

3 - Formulate a technology strategy that will influence those metrics.

4 - Execute.

5 - Benchmark and compare your outcome with your target outcome.

Tell me what you think - I'll be testing it out over the coming months and will do a follow up post once I understand where the gaps are.