Helping prospective franchisees explore Dodo Brands

Helping prospective franchisees explore Dodo Brands

I redesigned Dodobrands.io around three questions: who is behind the business, what does each brand offer, and how do its stores perform?

I redesigned Dodobrands.io around three questions: who is behind the business, what does each brand offer, and how do its stores perform?

Product

Corporate, franchise and live-sales website

Scale

2 brands across 28 markets

Role

End-to-end product design, prototyping, information architecture, content requirements

Team

C-Level stakeholders,
1 back-end, 2 front-end devs

From the group overview to store performance

Different audiences needed different depths of information without feeling like they had entered separate websites.

Different audiences needed different depths of information without feeling like they had entered separate websites.

Evidence

Visitors needed to understand the group, evaluate individual franchise propositions and inspect actual store performance. Each task required a different level of detail.

Decision

Connected the group overview, brand propositions and live sales data, giving visitors clear routes from exploration to enquiry.

Trade-off

Kept brand and sales journeys distinct, with shared navigation so visitors could move between them without losing context.

Shared structure, distinct brands
Kept the group coherent without flattening Dodo Pizza and Drinkit into one expression.
Desktop case study image
Making the menu easier to scan
Kept the group coherent without flattening Dodo Pizza and Drinkit into one expression.
Desktop case study image

Evidence

Both brands needed to communicate comparable franchise information, but their products, identities and emotional propositions were different.

Decision

Shared the page structure and interactions; used colour, photography and expressive details to give each brand its own voice.

Trade-off

Standardised comparable franchise information while leaving room for each brand’s identity.

From exhaustive reporting to focused comparison
Working prototypes moved the decision from stakeholder preference to evidence from franchisees.
Desktop case study image
Making the menu easier to scan
Working prototypes moved the decision from stakeholder preference to evidence from franchisees.
Desktop case study image

Evidence

The first prototype prioritised reporting depth. In testing, franchisees struggled to get a clear overview of the most important metrics because the interface was too crowded with secondary details of little value to them.

Process

Tested 4 working prototypes with 18 active franchisees to identify essential metrics and confusing controls.

Decision

Kept the most-used comparison metrics in the overview, moved secondary data into store details, and let users narrow the list by country, town, and store.

Resulting experience

In the next round, franchisees noted the lowered cognitive load and simplified experience. That gave stakeholders confidence to simplify the overview and keep detailed reporting one step away.

Making the menu easier to scan

Comparison first

Kept only the information needed to compare store performance.

Detail on demand

Moved secondary metrics into the individual store view.

Clear active context

Preserved the selected brand, market, reporting period and currency while users narrowed the dataset.

Responsive prioritisation

On smaller screens, users compare stores through one selected metric rather than a compressed desktop table.

Evidence replaced preference

Evidence replaced preference

Testing gave us a clear basis for deciding what belonged in the overview and what could sit one level deeper.

Testing gave us a clear basis for deciding what belonged in the overview and what could sit one level deeper.