UX – scoping and planning

Process:
A process for having a correct scoped project relies on the input and the understanding (insights) about what the challenge is and how the problem can be solved. Big data can be used, but what we can relate and connect to, is the human/person. We are part of the co-creation, shaping each other’s experiences and supporting each other evolve.

When having conversations based upon change management project, or a project regarding several parties, or a journey, a transition from different states (A-B), a common language and a common ground can be helpful in order to touch base. It helps define and zero in the problem, what you want to solve, the product you want to sell or the conversation you would like to engage or ignite. As a helping hand, there are initial points, which can help us align the expectations and obtain the common, collective goal.

The point below is merely an illustration of the tasks/jobstobedone, or more outcome based results, when you “want a website, which does XXX for the users, who wants to XXXX..”.

Problem/challenge:
Is the problem well stated? If the problem is only vaguely described, there a risk of ending up with a half-solved solution.
DESIRABLE (wanted and enjoyable)
USEABLE (understandable)
USEFUL (needed)

Think beyond the product:
What is the feeling/the empowerment you want to enable at the end-user?

Functionality:
Are there any requirements regarding functionality or integrations?
Existing back-end, maintenance, front end, integrations with CRM/Salesforce etc.

Criterias:
What the criteria of succes?
Are they are Key success factors or KPIs,
SMART goals?
When is the project considered “done”?
How do you measure it?

Scalability:
is the solution scalable? Is it built to handle peak moments? (black friday, concerts etc.)
Does it have a work overhead? is it scalable to life events?

Design and architecture:
Is there a sitemap, flow diagram, with designated task/functions?
User journeys and KPIs/conversions?

Code:
– can it be scaled and build upon?
is it clean code with a minimum lines of code? Does it align with global standards such as W3C, accessibility (fx.: public domains), GDPR, e- privacy?

Maintenance:
Who is in the charge of maintaining the site? cloud, hardware, handles security/hacking, updating the site (plugins and content)?

Empathy / problem/challenge
TASK

DELIVERABLES

Understand the problem Idea/form/layout

Align expectations Plan and methods

Correct scoping Financial frame
Concept / brief


Facts and analysis Insights and facts

POC Overall concept/strategy

KPI/KSF /OKR/KEIs Overall estimate
UX & Design


User experiences + journeys + flows Prototype + specs

Visuals/colour/type Visual identity

User test/feedback Detail estimates 
Development

frontend- & backend /development Production and deadline Live launch/beta
automation DemoDocumentation

Quality and finish Acceptance/approval
Support



Accessibility


Maintenance


Optimization