GPM First

Practical

24 essential website project analysis questions

Before you even start any new website project, there are 24 questions you must answer, says Bert Heymans of Journeyman PM.

This article is about starting out a website project and asking the most effective questions. When you’re doing anything online these days, there are a lot of online channels to consider (websites, apps, social platforms, newsletters and so on), however the website still remains one of the central ingredients for doing anything online.

I’m going to try to be as complete as possible with a few questions (a maximum of four per topic) and work my way up from basic IT, to content and purpose of the website.

It’s easy to cover a lot of ground like this in a short time. These questions are directed at whoever has the senior user role in the project. In many cases that role can be filled by the business.

Before we start … let’s say that you already have some of the PM stuff covered. You have a list of people and know who’s going to review, who’s going to sponsor and who’s going to execute the work. You also already have your high-level budget and planning indications. It’s clear that the business case requires a website and there’s a general idea of how big the website will be in terms of content.

Technology and IT:

  • Does the website need to be integrated with an existing technology, website or system (hosting, domains)?
  • What kinds of technologies will the website be developed in and hosted on (server specifications, programming languages, network or firewall restrictions)?
  • To what level is email used in support of website functionality (no mails, only functional mails, mass mailing)?
  • Is there a testing or acceptance environment, or do we need to provide one?

Design and branding:

  • Which features are essential for the website design to work (the form follows function principle)?
  • Are there any brand guidelines or standard (proprietary) digital assets and how do we get them?
  • Are there any examples you’re looking at, any inspiration you’re thinking of (look at competition, similar concept websites … and so on)?
  • Is there a need for a specific mobile website design (mobile, tablet etc.)?

Content:

  • How much content in how many languages will the website support and, if multilingual, where do translations come from?
  • Are there cultural and geographical constraints, will different content be shown based on this (for example, different prices by country)?
  • Who will provide copy, translations and digital assets (texts, photography, video)?
  • How much content will be generated by visitors/users and will there be moderation?

Maintenance and metrics:

  • Who will maintain the content and what is their level of technical knowledge?
  • Who will do the technical maintenance? Do they have specific needs?
  • Are you using tracking services (Omniture, Google Analytics, Clicky)?
  • Are there special reporting needs the website has to provide (e.g. easy database exports, dashboard)?

Website launch or marketing (say marketing strategy isn’t part of your deliverable):

  • How will the website be launched (phased launch, big bang, public beta)?
  • Are there associated offline media campaigns (TV, radio, print) and what kind of visitor impact is there to expect?
  • Are there online marketing campaigns (activity on social networks, bannering, email marketing)?
  • How optimized does the content need to be for search engines (if SEO is important, which keywords)?

Purpose and usability:

  • What’s the main audience of the website?
  • Which information should be on the website, how will people navigate the content (information architecture, content prioritization)?
  • Are there specific accessibility needs (visitors with visual or cognitive difficulties and so on)?
  • How will the website be visited most? Is a mobile or tablet version a priority?

Expert tip: Start your questions on the topic you feel is unlikely to change when you’re doing your interview and work your way up from there. I’ve put the checklists in a rather bottom-up, technology-first order but there’s no particular reason to follow that order in your interview.

When you have a sufficient level of detail, you can start discussing milestones and working on planning and resource allocation.

Never forget that one of the first things you should find out from a client as a PM is ‘Why are you doing this project?’ If you don’t know that, you can’t do your work.

 

Submit your own content for publication

Submit content