Site Planning: Tips and Resources for Planning Your Site

Categories:

I cannot emphasize enough, the importance of PLANNING OUT YOUR WEBSITE. Before you can even start thinking about what the colors will be, you need to have a few things in place. 3 i can readily think of are:

  • A Site Plan
  • A Site Map Diagram
  • A User Experience

Sustainability plays a large part in the success of the technology chosen and implemented. In fact, it shouldn't even be 'a part' of, it should be INTRINSIC to your site throughout it's development.

Web maintenance is a pretty big one - for instance, what happens if you've coordinated a bright, fresh and dynamic team to help out on your site, but one of them gets hired off someplace else? What if your graphic designer (for banners, buttons, etc.) is having more difficulty than originally anticipated or they simpy can't finish the work? These instances are particularly taxing if your team is a group of VOLUNTEERS. Volunteers can be notorious (through no fault of their own) at 'dropping off' a project. Will you, as the sole coordinator have the strategy, skills and time in place to 'fill in'? This can often happen (as I've been taken to task to many a time). Nothing is more taxing then if a website or listserv goes down RIGHT before a critical fundraising campaign (which will happen). Have a plan for this. Have back up documentation of what they were doing, and when? How far a long were they? What did the develop/what did they NOT develop?

A key thing that can help off set these things (and empower YOU as a web team coordinator) is to have a Site Plan - any designer should be able to have this on hand and have it transparent and viewable by ALL interested parties - executive board, support staff, consultants (if you're not fortunate enough to have in-house web staff), funder$...

I'm currently developing the site for NAMAC, but it is a HUGE undertaking with A LOT of planning that's going into it - discussion, visioning, functionality, user roles, modules needed, interaction workflow, meeting with each staff member individually, pre-launch steps, live launch monitoring, sustainability and optimization - and we haven't even gotten to the design aesthetics yet.

Without further ado and blathering, here's a few notes on some things that I think are pretty basic and key to web development. This is by no mean exhaustive, but you can certainly search for other web development tips on our site...



A Site Plan:
http://docs.google.com/View?docid=dw5pg78_5cmp6ts

This is my General Plan for the current site. I've made sure to have it public so interested parties (org directors, staff, consultants) can see it and comment on it. I asked each person what they'd like to see, asked them how and if they would interact with a particular functionality and then composed a report with all of their input in it. I am in CONSTANT communication with them about how the new site will function, how the planning is going, what purpose the site/functionality will serve, and IF a certain functionality they'll want is doable and/or necessary - this part is huge - the more functionality, the more troubleshooting down the road.

A general rule of thumb when developing is the 3 T's of Site Building (or any other tech project for that matter).

  • Tell them what you are planning on doing (when you're planning it)
  • Tell them you are doing it (when you are doing it)
  • Tell them that you did (when you are done)

That way there's no 'What? I didn't okay this!' from a frustrated laissez-faire client/director or 'But we had talked about it before' from an equall frustrated and head-strong developer. I'd add that keeping up an online document that EVERYONE can see will also make sure that everyone is on the same page - as well as help YOU as a designer/planner be able to refer back to and track your work.

***NOTE: as a VISTA, an online accessible/public document gives your directors/supervisors a way to reference the great work that you, as a VISTA are doing - mine are sending the link above to funders to show them what we are up to***



A Site Map Diagram:
http://www.michelinag.com/agx/en-US/images/sitemap/sitemap.gif
An example of a site map diagram.

http://www.gliffy.com/
You can draw out a diagram map of your site with this tool (NOT to be confused with an XML SITEMAP by the way). This is GREAT for working with distributed teams.


A User Experience Workflow
:
http://www.jjg.net/elements/pdf/elements.pdf
The above provides a great visual of the user design experience process.

http://farm2.static.flickr.com/1254/899914294_ab6745ac73_o.jpg
This (i like this one even better) provides another view of the design process).

Anyway, I hope this helps some of you VISTAs out there. Like i said, this is by no means an exhaustive resource of planning tips, but hopefully it's enough to get you started on your way to website planning nirvana.



peace,
m

AttachmentSize
Elements of User Experience.pdf16.55 KB