Westminster website project

1
Westminster website project

• Merlin Sinclair
• Westminster City Council

2

• A bit about myself

3

• 1. The first thing I learned
• Technophiles should make the site. Technophobes
  should test it.

4
The second thing I learned
The second thing I learned Follow the
footsteps.
5
(No Transcript)
6
3. People come to the council to do stuff. Make
it easy for them

• Task optimisation
• 13 of people visit parking
• 17 jobs and vacancies
• Just making two tasks simple will make 30 of all
  visitors happy.

7
4. Ask first what can you do

• Split it out
• Each page needs an owner
• Check links, content, tagging
• Get the most visited pages cross-checked
• No use getting supplier to mend site if you
  havent got the governance in place to maintain
  it

8
5. Use hothouses

• Get departments together

9

• Get departments together
• Close door

10

• Get departments together
• Close door
• Lock door

11

• Get people from all of the departments together
• Close the door
• Lock the door
• Wait until cooked

12
6. Once the project starts, work out EXACTLY what
you want

• Whats your website for?
• In plain English, what are you going to get?

13
(No Transcript)
14
Our definition for our website
Tell people what to do The site must help
people when interacting with government and guide
them through the procedure for common and
critical requests Tell people about the area
The site should tell people about the City of
Westminster and where to find council services.
It should also steer them to sites that deal with
other local requests i.e TFL or Time Out Help
people carry out transactions Whether paying,
applying, reporting or simply trying to find a
document, the website should provide a simple way
for them to do it.
15
The more specific you are, the less
misunderstanding there can be