The Kestrel Echo*

Adopt unified digital communication
In the course of #24theweb I lost count of how different applications, on-line services and means of communication we used. Tasks such as transferring designs, collectively tracking progress, maintaining the codebase, swapping solutions, asking questions and the list goes on.

To do this we ended up using a hotchpotch of email, twitter, flickr, ftp, subversion ¹, passpack, a USB key and doubtless several others I wasn’t aware of. Needless to relate this wasn’t ideal but it worked. It was less than efficient, especially towards the end when time was short and brains were running on less than empty.

I don’t have a ‘go to’ option – one that I know can be dropped in anywhere and it would be more of a help than a hindrance. Options like Basecamp or Google Wave come to mind. Unfortunately I really don’t like Basecamp and the Google Wave has fallen flat under the almighty burden of its own features. This leaves me without an answer, but I clearly have a question, a question I am open to suggestions on.

Creativity and Team work are key
I have heard stories of wonderfully talented people being put together, yet nothing meaningful is produced. There are countless other stories of projects which have had massive amounts of resources thrown at them producing only failed results. These muted results can sometimes be attributed to overbearing managers, shifting requirements, in-fighting, the list goes on.

In the case of the #24theweb challenge we had several key factors in our favour. The time line was set. The goal was set. The client was entirely on our side, and us theirs. The real challenge was in the co-ordination of the resources we had available to us, ourselves. With the firm aspects of the project immovable it really seemed to be the catalyst for creativity, that and the fact that it was the weekend. In any event this was of course constantly balanced by the time left on the clock.

But we found a way around all problems. Improvising when necessary. Individually committed to filling our specific roles. Worked together when stuck. We all knew we had a job to do, we were open to suggestion, mutually supportive and it worked.

Generating energy
As the hours wore on of course energy levels dropped, and kept dropping. With reduced energy levels, increasing tiredness and impending deadline there was little any of us could do other than to get on with it. But that is just it, it is all about the little things that you can do.

When a milestone was achieved, take a second to spread the word – share the feel good factor of definite progress. When stuck on a problem, ask someone a question from which a solution may arise – a problem shared is a problem halved. When you absolutely need a break, make a cuppa and offer to get one for others – a simple supportive gesture.

Very much in the same vein as the last lesson, team work was what got me through. And what got the project completed. I feel good team spirit helped us all keep our energy levels up and it was the little things that made the big difference.

Always strive to be better
It is all to easy to find yourself in a position where complacency occurs. As likely as not this will be driven by the rate that projects come through such that you rely on the same solutions too often. No matter how much you know or how much experience you have there is always a new challenge around the corner.

Even if I was the best at any one role or skill set it is a very short distance from there before I become a mediocre something else. One more step over and I have likely become a plainly awful something else. By this I am saying that it is always important to remain humble, don’t be afraid to ask questions, be happy to answer other peoples questions, and to never get to comfortable with any single technology platform or workflow pattern.

Trust your team
On several occasions during the earlier stages of #24theweb I couldn’t help but feel that other team members could be doing certain tasks better. On reflection I am not surprised these thoughts crossed my mind for several reasons:-

1. Being part of a team of so many experts was a new experience. Subsequently I was feeling unusually separated from aspects of the build process I would normally be closely involved in.
2. I hadn’t worked with anyone on my team before so I was concerned about being able to achieve our collective goal.
3. I’m a programmer ².

Thankfully I chose to keep my mouth shut and get on with my own tasks. In time, as our work progressed and the team came together, any doubt I had was answered. All manner of surprising, elegant and hard fought goals were achieved. In the words of General Patton

Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity ³

Alternatively this snappy talk given by John Wood on What business can learn from the German Army covers the same concept.

Sleep and Downtime is vitally important
Everyone who was involved in #24theweb doesn’t need to be reminded how important sleep is. If I am honest it was several days later before I got over the coding jetlag. My brain was just tired, tired of thinking, tired of being at a computer, wholly disengaged.

In the context of #24theweb the need for sleep is was highly pronounced. But all too often that same brain fatigue creeps into my normal working week. The only genuine remedy is time off-line and good sleep.