UX CASE STUDY

THE KICK OFF MEETING

The kick off meeting is made up of business people, product people and anyone else that has an accountability to the project.

1.

SETTING GOALS

The meeting helps to externalize information that's important for everyone to know and understand; set business goals, product goals and explore the user or customer goals.

2.

PEOPLE INVOLVED

Anyone who is involved in your project should meet in this meeting before everyone starts doing work. These include the stakeholders, the teams; everyone needs to be on the same page.

3.

RISKS & MITIGATIONS

You’ll want to know what makes a project successful but just as important, you want to know what will make a project unsuccessful. This is where we call out any risky assumptions and how to face them.

THE BUSINESS GOALS

You’ll want to know key performance indicators (KPI’s) that inform business analytics, this could be something along the lines of: "lower the number of support calls."

We want to understand the business goals and how they map to milestones that our design will need to achieve. This also helps in connecting user needs and goals, to the business needs and goals. You want to know how well your design decisions informed the business goals in small and large stages.

Developing customer empathy (research) and experimenting with solutions will de-risk business unknowns and help to ensure product success.

THE PRODUCT GOALS

It's important to understand that you as the business owner thinks of the possible product goals. These are not fine details but overall “what is needed to achieve business goals” within a piece of software or service or product. These goals can be changed, depending on the research and solution testing outcomes.

THE USERS AND THEIR GOALS

This is where we apply user-centered design. Create personas and really get to know them; what do they need or desire? What are their pain points and problems? What motivates them? Also, discuss how to turn un-validated personas into validated ones.

tHE STAKEHOLDERS

Involving all relevant stakeholders in the process like “Design Sprints” or "user interviews" or ''user-testing" help everyone align and share ownership of information, decisions and ideas.

THE RISKS AND MITIGATIONS

A risk is anything that can block, disrupt or fail a project or software. A risk can be turned into a question, and that can point you into the right direction when answering that question.

You’ll want to know what makes a project successful but just as important, you want to know what will make a project unsuccessful. After you learned about the project context everyone should have time to call out and prioritize risks so that the teams can start focusing on activities that will intend to mitigate or solve the most important RISKY ASSUMPTIONS.

Design your uI with oDi7

We validate the User Experience then we dig in to the details, meticulously designing beautiful, intuitive interfaces that are easy-to-understand and even easier to use.