akanoodles
Back
Services
5 min read

Getting a digital solution off the ground

  • Nural Choudhury
    Author Nural Choudhury
  • Published 27 December 2020

Getting a digital solution off the ground is a multi-step process that involves active collaboration between various teams. This document aims to provide an overview of the tasks involved and details of what goes into developing a solution.



During the engagement, we will end up accumulating (and delivering) the following documents and assets:

This is what
 we’ll deliver 
in detail...
PROJECT BRIEF – created from our initial meetings, conversations to help design the initial SOW.

STATEMENT OF WORK
 – This document becomes our contract and describes the rules of our engagement. It is intended to be enforceable by law and lists all the details of what is being built as well as:
  • Project objectives
  • High-level scope
  • Agreed KPIs
  • Team roles and responsibilities
  • Client RACI (stakeholder) matrix
  • Milestones and timetable
  • Risk factors and mitigation
  • Escalation points
  • Warranty
  • Sign-off processes
  • Budget, costing and payment schedules
EXPERIENCE DESIGN APPROACH – This document is a narration of our product strategy and formalises the project vision. Detailing the research and theory of why we’re building what we’re building. A project of any scale should not begin without the right level of planning and strategy. This document makes sure our approach is understood, and nothing is lost in translation.

  • Project hypothesis
  • Usability review
  • Data Analysis
  • Web Analytics
  • Expert Interviews
  • Surveys
  • Behavioural analytics
  • Task Analysis (Jobs to be done)
  • Content Audits
  • Information Architecture
  • User Testing Plans
and this...
UX ASSETS – When we talk about UX assets, we mean elements that define how the product should function. The data we collect provides the foundation for behavioural archetypes, experience maps and depending on the size of the project:

  • User Flows
  • Content Flow
  • Wireframes (template definition)
  • Cross-channel user management
  • Pattern library
  • Component functionality
  • Basic functional prototype
DESIGN SYSTEM – When we talk about a Design system we talk about UI assets, we mean elements of how the product should look, feel and interact. Depending on the size of the project the following items are usually created:
  • Component UI design
  • Interaction documentation and visuals
  • Tone of voice documentation
  • Digital guidelines
  • High-fidelity functional prototype
and finally 
this...
SOLUTION ARCHITECTURE DOCUMENT – This is a technical requirements document that defines the platform, its architecture and the functionality of what is to be built. It serves an essential role in communicating with stakeholders, engineers and ensuring successful outcomes. Documentation requirements differ based on the technology and methodology used to complete the project:
  • 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
WE’RE NOT DONE

To help us during this process, we would need the following client stakeholders available during the project.

The next few tables detail what they’ll be doing and why we need them…

WHAT ABOUT US!

Our deployment and engagement methodology differs from project to project. But usually comprised of members from the Client Services, Project Management, Design, User Experience, Business Analysis, Data Science, Software Development, Content Management and Quality Assurance teams.

The next few tables will detail the people assigned to this project and what they’ll be doing…

WAIT A MINUTE
This seems all fine and well, but when will you get to see things, right? Well, it all depends on the scale of the project, but our 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:
Post-launch
Once we deliver the final build, we don’t just wash our hands of the project. What I suggest to most of my clients is a site monitoring and optimisation package so we can support you going forward. You can read more about it on my next article.
Conversion rate optimisation plan

For more information about conversion rate optimisation plans have a look at the package here.

Read more

Got a project?
Get in touch

Request a callback
Monday to Friday
10:00 to 19:00 GMT
Book here

Call me
Phone: (+44) 020 8123 8482
Skype Chat: aka_noodles

Location
Based in London, UK.





    This website stores cookies on your computer. Cookie Policy