In my previous blog post on how training and the run/ swim disciplines in a Triathlon compare to web project management. In this final instalment I look at the run and all important transitions.
4) Run
I’m a hopeless runner, and it’s definitely the hardest left to last in my opinion. The run up to the launch of a web project (see what I did there) is where the race can be lost or won, and, without proper planning it can be the most painful part.
You can have the best designed, most richly featured web project, but if it doesn’t work, has a content drought or if no one knows about it then it will not likely make become a career personal best.
Content creation and population takes longer than you think, and, in my experience, is typically twice the job you thought it was. Also preparation is key (Just as most people could swim and do the cycle without any training, few could run more than a few hundred meters), content must be planned, audited, reviewed, shaped, prepared and honed well before the project goes live.
The moment you cross the line is only when the real journey begins. You have to position the web project in part of a wider digital strategy, users need to be able to find it and you want to keep bringing them back. I’m yet to meet someone who stops after just doing the one Triathalon. Similarly your web project needs to become a continual process of development and evolution whilst you think about all the other stuff that goes one in your organisation.
If you keep at it you will see how things can improve and change and you’ll capture feedback, tips and opinions from other ‘competitors’ to fee in to your thinking on how you can trim just a few second off here and there.
Finally you will find yourself endlessly analysing the numbers and statistics - thinking about how you can improve further, and before you know it you’ve a list of tweaks, optimisations, enhancements that will improve performance yet further.
5) Transition
The fourth discipline as Triathletes describe it cannot be overlooked. In the web world the handover between teams, individuals or phases of the project is one of the biggest risks a project can face.
Until telepathy becomes a reality, knowledge capture, documentation and transfer is tricky. Typically the only way to manage that risk, and make sure nothing falls between the gaps is to use documentation to make the next person in the chain have to read what you want them to think/ do. Valuable (and to be honest relatively easy) seconds can be made up in a Triathlon for having a well organised and planned handover between disciplines.
In a web project we use simple concepts such as project teams, who, if possible, physically sit together to work on a project. We also sometimes use ‘scrum’ meetings to bring together all the different disciplines together to share their progress and announce focus for the coming day.
In conclusion I think the web world really pushes the envelope, as you’re reliant on the very different disciplines of Business Creative and Technical being pulled together in perfect harmony, and that preparation is key – rushing the groundwork or skimping on the training is unlikely to give you the result you’re hoping for.