Business and project objectives
Every project must have a set of objectives, and it’s our job to understand how they fit in with your organisation’s overall objectives. We’ll ask questions about your marketing strategy, about your goals for the next twelve months and how the project will help achieve them.
If it’s a new website, we’ll ask about your audience and your target market so that we gain a deeper understanding of what the project means to you. We do this because we care, and we care that the project will deliver the value you’re anticipating.
For us, it’s important that everyone working on the project has an understanding of what is trying to be achieved.
Design and functional requirements
We’ll start getting deeper into the requirements by asking about your brand, your design preferences, your competitors and your industry. We’ll find out what matters to you, and your users.
We’ll help you map out the functional requirements of the website by thinking about ‘user stories’ which are a creative and understandable way of determining what your users want to achieve and how we’ll go about providing them with the tools to do that.
Typically we’ll develop ten to twenty user stories and these all follow a simple sentence structure but are hugely effective in communicating requirements to you, your stakeholders and our team.
Content management systems
During our discussion, we’ll talk about how you’ll manage the content of the website (or web application). We’ll discuss the available options to you and give you our recommendation.
Typically if this is a content-orientated project (e.g. a website with the aim of educating and informing users about you or your product) then we’ll recommend WordPress.
If it’s a functionality-orientated project (e.g. you want users to be able to login and do something like make a booking, subscribe to a membership or something more bespoke) then we’ll recommend Laravel.
At the end of the discovery phase, we’ll deliver the following to you:
A detailed document which outlines the precise requirements of the project and all the supporting information that we have gathered during the discovery phase. This includes a sitemap of the proposed structure of the new website.
Wireframes of each key page will be created by our designer and uploaded into a system called Overflow.io which is a web-based tool that allows us to share the wireframes with you, and demonstrate how users will navigate through the website or application.
A statement of work is a document which outlines how 10 Degrees will meet all of the requirements listed in the project specification document. It goes into further detail about the way in which we’ll complete the project (including contractual terms).
We required WordPress best practice for database structure, workflow management and multilingual, which Jonny at 10 Degrees provided through a number of days of on-site consultancy. 10 Degrees’ expert advice was invaluable in helping us make strategic decisions on the configuration of our enterprise CMS.