Likewise if the user journeys are not sufficiently thought out (in our case we use Wireframes to thrash these out) then it is unlikely the user journey through the final site are going to be simple and efficient.

The basic rule is the more time and effort put into the scoping stage then the development/implementation process will be more efficient (and therefore quicker) and the result better. So this is where client time and effort is needed the most.

The problem is scoping is just not fun! It requires one not just to think of the requirements of the new site but also how these requirements could met effectively, which sometimes involves compromise because one goal/requirement of the new site conflicts with another. One has to put one’s self in the shoes of the target audiences, conceptualise, extrapolate, visualise, spend time explaining how the organisation works and ensuring that the document output captures the requirements adequately and the outlined solution meets those needs. This is probably on top of one’s normal day-to-day job, it’s a tough order!

However, in some ways building a new web site is like building a new house, if the plans are not good then the more decisions will have to made during the build when options will be more limited, solutions less elegant, they will probably take longer to implement, could ultimately cost more and the finished product may not be as slick. You just have to watch Grand Designs to see the results!

So although it can be tough going and you may be frustrated that it takes longer than expected and be under pressure from senior management for the design and build to begin – skimp on scoping at your peril.

Think of your new site like your Grand Design, put in that extra effort during scoping and I assure you, you will be happy with the result!