Contents

Intent

Insert here

The DRI for this discovery activity is [Person]

Discovery Plan

0️⃣ Kick off

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

1️⃣ Discover

Opportunity/problem ticket

IREQ-285 - Getting issue details... 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

2️⃣ Define

Opportunity/problem consolidation documentation

[Insert here Confluence page on opportunity findings consolidation]

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

3️⃣ 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]

Potential Solutions

To avoid the user from closing the payment process, we explore different options:

New loading page informs the user about the processing payment and prevents them to take any action that can interfere with the process.

2- Alert the user about the importance of keeping on the page until the payment is complete. If the user wants to go back/ leave the process, a modal is displayed as doble check.

3- Disabled all the actionable items in the page, including the arrow to go back.

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

4️⃣ 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

Figma Link (still WIP): https://www.figma.com/design/wEeYkRHLwLdMJHKvQJOdd0/%5BIBFEC-1795%5D-Remove-Pre-filled-Name-On-Card-field?node-id=7913-1549

To avoid the user from closing the payment process, we explore different options and finally decided that the most convenient is to add a new loading page (option 1) because:

· We prevent the user from interrupting the process and therefore having errors in the future regarding erroneously charged or duplicate orders.

· The user has the feeling they are progressing because they are not stuck in the same page, they “have moved” forward to another one.

· The message displayed informs the user about what’s going on and we think that can prevent the user from leaving the process or going back.

To check all of them up, visit: https://www.figma.com/design/wEeYkRHLwLdMJHKvQJOdd0/%5BIBFEC-1795%5D-Remove-Pre-filled-Name-On-Card-field?node-id=7913-1549

Alternative Payments User Case

Important: There is a user case regarding alternative payments in which we must ensure the user finds a way to go back to the Checkout, because if we remove the “X” the user will be stuck in a “loading loop”.

Current PayPal User Case in App:

The only way the user has access to select a new payment method is pressing the ”X”. When closing this page, the user comes back to the Checkout because the platform needs to generate a new Transaction ID for the order before selecting a new Payment option.

Current PayPal User Case in Desktop:

DoD

In Whitelabel-app (WIP):

· Ensure the final solution works for all payments methods: Card, Cash, Card on Delivery, Online Mobile Payment Apps.

· Ensure the final solution works for Pick Up and Delivery service modes. In Pick Up mode, have in consideration both Store Confirmation after and before payment.

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.

[Discovery Plan] Block user from closing window