Skip to content

Instantly share code, notes, and snippets.

@FdelMazo
Last active July 1, 2020 17:27
Show Gist options
  • Save FdelMazo/12d039f76e97945163f666b1d2b4e278 to your computer and use it in GitHub Desktop.
Save FdelMazo/12d039f76e97945163f666b1d2b4e278 to your computer and use it in GitHub Desktop.
A Scope Canvas in markdown

☑ User Needs

Our users need or want:

The needs of our users They are the next most basic and important step for a successful UX project. What problems or unmet opportunities have the potential to meet ?

At this point it´s where the team will spend more time in the field, researching, talking to users, analyzing data and getting in touch with pains, needs and unmet opportunities.

❤ Purpose

The world needs this because:

The purpose is at the heart of any project and defines the motivation of your team to venture in the proyect. What makes this worth it for you? What moves and motivates you?

The purpose is always a balance between your goals as an organization and your user needs. It´s added value for everyone.

֎ Objectives

Our goals for this project are:

Now it´s time to get back to the inside of the organization. Ask yourselves what you want to accomplish with this project. What is the reason why you are investing money, time and energy in this? What is the priority for the business?

Objectives can be specific improvements (reducing the time of completing a task, increase conversions) or overall consumer satisfaction. The important is that they must satisfy a concrete need of the organization, and at the same time be measurable.

⚡ Actions

We expect our users to

What specific user actions mean conversion to us? How do we know that users are having their needs met? Both questions need to be answered at the same time: if you only focus on conversion and leave aside user needs, they will abandon your product over time.

The actions are objectively observable, as if you were looking at them through a video camera. They translate into a concrete and direct action executed on the product or service.

📊 Metrics

We'll know if we're doing well by measuring

What will we measure to know if we are doing fine? Metrics allows us to quantify the return on investment of the UX project for the business.

Metrics can be quantitative or qualitative. Not everything is Analytics and hard data; satisfaction surveys or usability measurement tools such as the SUS can also help. If no existing metric suits your needs, create one.

Focus on measuring the specific success of the UX project, user satisfaction and customer loyalty. Frustrating as it may be, keep your attention on what the project actually is capable of changing. Stay away from Vanity Metrics: those that look good but reflect nothing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment