At this stage, it’s also good to speak to the key process owners and collectively develop a list of requirements that can be used to help a procurement process.
Content doesn’t just appear by itself, so thinking about who will audit the existing content, add it to the website once it is live, and whether they will need any additional training is also important.
Now, here comes the science! If you have an internal web resource – or a supplier – then chances are you will have access to usage data. This can be useful to understand the volume of traffic and the effectiveness of tasks users undertake on your website.
Usage data is also key, as one of the main challenges with any website project is deciding how to transfer or remove content. Its usefulness can only be answered by data and its ability to aid in meeting those goals.
It’s now time to talk servers and tech stacks. Your IT team may have a specific tech stack (typically either .net or PHP) in mind and this may be due to other technologies and systems (for example, a CRM system or Learning Management System) that are in place and may require integration with the website.
They will also be instrumental in advising on the base level of security requirements, and how and where the website should be hosted. They may also have a view on uptime. This information will help build out the non-functional requirements.