[Design Plan] Fraudulent user blocking (Admin App x Whitelabel)

Owned by Hainzenreder, Diego
Last updated: Jun 05, 2024 by Pereira, Filipa (Deactivated)
1 min read

Contents

Intent

Insert here

The DRI for this discovery activity is [Person]

Discovery Plan

Kick off

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Problem defined

  • Opportunity template, sections Context, Problem Statements and Expected Outcomes

 

 

 

NOT STARTED IN PROGRESS

done

Stakeholders informed

  • Kick off meeting

 

 

 

 

Discover

Opportunity/problem ticket

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Stakeholders interviewed

  • List of stakeholder requirements

 

 

 

 

Franchisees interviewed

  • List of FZ requirements

 

 

 

 

Existing metrics understood

  • Report with current values for main KPI's (input to next milestone)

 

 

 

 

Success metrics defined

  • List of success metrics

  • Targets to aim for

  • Definition of how each metric will be measured

 

 

 

 

Run usability testing on existing solution

  • Proposed changes to the design

 

 

 

 

User interviews

 

 

 

 

 

Online surveys

 

 

 

 

 

Desk research

 

 

 

 

 

Competitor landscape

 

 

 

 

 

Persona mapping

 

 

 

 

 

User journey (use cases) mapping

 

 

 

 

 

Define

Opportunity/problem consolidation documentation

[Insert here Confluence page on opportunity findings consolidation]

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Problem consolidation

  • Opportunity template: insights section and any others that may be relevant

 

 

 

 

Approach review and stakeholder validation

 

 

 

 

 

Develop

Note: the term “Develop” refers specifically to the production of solution design artefacts. There will be no software development in this phase.

List of solutions & designs

[Insert here Confluence page on solutions tested or figma designs]

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Ideation & wireframing

  • High-level user flows

  • High or low fidelity wireframes

 

 

 

 

Design & prototype

  • Figma happy path screen flows

  • Figma prototype (if needed)

 

 

 

 

User testing

  • Report with findings and insights

  • Changes recommendations

 

 

 

 

Design review with stakeholders and franchisees

  • Approval for final happy path screen flows

 

 

 

 

Deliver

Note: the term “Deliver” refers specifically to the delivery of solution design artefacts. There will be no software development in this phase.

Solution Description

[Insert here the same solutions page if applicable]

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Milestone

Output

Owner

Approver(s)

Reviewer(s)

Status

Feature (MVP) agreement

 

 

 

 

NOT STARTED

Tech solutioning review

 

 

 

 

NOT STARTED

Development Handoff

 

 

 

 

NOT STARTED

Analytics tagging

 

 

 

 

NOT STARTED

User story breakdown

 

 

 

 

NOT STARTED

Documents

Ideally (not mandatory) we should use the same Opportunity and Solution templates that we use for Delivery.