Project tracks

Project tracks are planned in a way that reflects our Agile delivery approach, an example of a plan we expect to follow and looks something like this:

Master Document

Task

Method

Scheduled duration

Project Brief

  • Initial meetings

Kick-off workshop

Week 1

Statement of work

  • Project objectives

  • High-level scope

  • Agreed KPIs

  • Team roles and responsibilities

  • Client RACI (stakeholder) matrix

  • Milestones and timetable

  • Sign-off processes

  • Risk factors and mitigation

  • Escalation points

Workshop 01

  • Warranty

  • Budget, costing

  • payment schedules

Workshop 02

Experience design approach

  • Project hypothesis

  • Usability review

  • Data Analysis

    • Web Analytics

    • Expert Interviews

    • Surveys

  • Behavioural analytics

  • Task Analysis (Jobs to be done)

Heuristic analysis

Week 2-3

  • Content Audits

Desk research

Week 4

  • Information Architecture

Card sorting

Week 5

  • User Testing Plans

Report writing

Week 6

UX assets

  • User Flows

  • Content Flow

  • Cross-channel user management

  • Data analysis

  • Task analysis

  • Jobs to be done

Week 7

  • Wireframes (template definition)

  • User Flows

  • Content Flow

Week 10

  • Pattern library

  • Component functionality

  • Basic functional prototype

  • Wireframes

  • Jobs to be done

Week 12

Design system

  • Component UI design

  • Pattern library

  • Component functionality

  • Basic functional prototype

Week 13-18

  • Tone of voice documentation

  • Basic functional prototype

  • Solution architecture document

Week 16

  • Interaction documentation and visuals

  • Digital guidelines

  • Basic functional prototype

  • Solution architecture document

Week 17

  • High-fidelity functional prototype

  • Basic functional prototype

  • Solution architecture document

  • Component UI design

Week 18

Solution architecture document

  • Solution Overview

  • Feature Backlog

  • Technical Solution

    • Logical architecture Diagram

    • Architecture Principles

    • Physical Architecture

    • Environment development

    • Legacy system management

  • Software selection

    • CMS Solution and Platform Choice

  • Integration

  • Technical Risks

  • Interaction documentation and visuals

  • Digital guidelines

Week 12-18

QA Strategy

QA document

  • Solution architecture document

Week 18

Post-launch Optimisation

Once we deliver the final build, we don't just wash our hands of the project. What we suggest to most of our clients is our site monitoring and optimisation package so we can support you going forward. Our packages usually include:

Site Monitoring - we create quarterly reports that are tracked against business goals (KPIs). The purpose of these reports is to provide actionable data and insights to help the business make key changes and adjustments.

Search Engine Optimisation (SEO) - with access to your Google Analytics platform we can monitor performance and action insights. Our goal is to optimise content and increase site traffic.

Behavioural Tagging - based on an agreed set of KPIs we can tag your digital channels to track user behaviour. This will help us Identify barriers to completion and journey pain points. The goal is to see what we can do to improve visitor retention rate and favourable user sentiment.

A/B and Multi-variant testing - with data and insights gained from the business and our Site Monitoring, we can suggest content approaches and test against multiple hypotheses. The goal would be to determine which layouts, call-to-actions and design elements are most compelling to different user groups.

Content Strategy - using a combination of social listening, industry trend knowledge and SEO, we will be able to provide recommendations on how messaging and content could be improved and see whether the topics you're talking about are resonating with your audience.

Data gathering

Suggested software

A/B testing

Social listening & Market analysis

On domain/device tracking

Expert interviews

Zoom, Face-to-face

Diary studies

User Testing

Questionnaires

Last updated