29 June 2008

Thought of the Day - Ready, Fire, Aim

Sometimes a theory or and idea keeps coming up over and over again and in those situations it is hard to ignore. Recently i kept reading about the benefits of the "Ready, Fire, Aim" approach, it was in books, on websites and in podcasts and it made sense.

Most people use the "Ready, Aim, Fire" approach. Only it normally turns into "Ready, Aim, Aim, Aim ... maybe Fire", too much planning and not enough action. On the other hand "Read, Fire, Aim" relies on action straight away, the results of which can be used to improve your accuracy. It is like firing a gun for the first time, you don't know whether the sights are set correctly or if the barrel is straight, therefore until you fire the aiming might not matter at all.


Something i have been meaning to take action on for a long time (like since 2004) is updating my WebCV into the modern age. It was originally built like a site from 1996; a pain to update, not very modern looking and rubbish for search engine optimisation, frankly it was an embarrassment. At various times since then i have bought and read books about web design, i have felt guilty for not updating it and once or twice i have even started to put something together. But it never quite got done, i spent too long planning and worrying about how difficult it would be and how long it would take to get it perfect. Even the most recent time i made a start in March i had a big elaborate plan, it was gantt charted out over 3 or 4 months but of course after a week i lost interest and nothing ever came of it.

On Friday evening i was listening to a podcast from SXSW where various entrepreneurs who were renowned for being 'fast' were speaking on the topic. These were people who had built the likes of Twitter, Blogger etc which are rather complicated pieces of software and the timescales they were talking about from picking a concept to first release were ridiculously short, months if not weeks. At this stage i began to feel rather embarrassed, my WebCV really isn't that complicated, i have most of the skills to update it, so how come they can launch huge brands in a few months and i can't even build a website?

The answer is simple; they set a short timescale to get something out there, it may not be complete, it may not be perfect, but it is something that they can then build on going forward. Programmers call this "release early, release often". It is better to get something out and get real customer feedback about what needs changed than it is to spend years building what you think customers want only to find
it isn't actually what they want or the opportunity has passed.


With this in mind i decided that 12 hours was a reasonable amount of time to build a website. I set key tasks that had to be done and decided if something was taking too long that i would accept something that was ok, rather than taking longer and getting something that was perfect. It was difficult, first off it is the weekend so it was hard to avoid distractions and secondly i had forgotten most of the CSS i used to know. But after 11 hours of work i updated my WebCV and uploaded to the site.

I would be grateful if anyone who reads this could go and have a look at my WebCV and provide any feedback they can think of through the contact link. So far my list of things to do includes:

  • Validate the xHTML and CSS against the W3C standards
  • Improve consistency across browsers (IE7 and Firefox 3 are ok but i suspect it needs work on IE6, Firefox 2 and IE8)
  • Sort out the padding and margins to get the spacing between the headings and text right
  • Make a better header (the current one will do but its not great)
  • Make the navigation tabs a bit less bland and angular
  • Think of some ways to make it more visually appealing without being tacky

At least i have something out there, a base to build on. It is a much less daunting task to make lots of small improvements than it is to come up with something brand new and perfect first time. So remember; if you are procrastinating, if a project seems to big to know where to start, set a tight timescale and "Ready, Fire, Aim".



Idea from: http://www.fourhourworkweek.com/blog/2008/05/29/the-art-of-speed-conversations-with-monster-makers/#more-362

No comments:

Post a Comment