Role
Research Manager
Discipline
Research Leadership · Research Operations
Focus
Research operations and experience mapping
Approach
Research strategy, mixed-method research and knowledge systems
I led research across Nando’s digital design team, helping projects decide what they needed to learn and how best to learn it.
Product and development set the longer-term direction; design had a clearer view of the work likely to arrive over the next one or two quarters.

The work was visible before the research demand was.
The roadmap made the scale of the challenge clear. As Research Manager, I was the point through which a growing range of studies had to be understood, prioritised, and supported. The problem was not simply how to complete more research, but how to decide which work needed a researcher at all.

Waiting to Be Seated
I created a Research Operations function to turn scattered research demand into a managed programme—defining the support each project needed, prioritising it against capacity, and tracking it through delivery.
ResOps did not exist as a separate function. I built it around the Research Manager role, beginning with three ways research could be supported.
Self-service
Designers conducted the research themselves, using shared guidance with oversight from ResOps.
Self-service with support
Designers led the research, while a researcher took on a defined delivery role when the project needed additional capacity.
Bespoke research
A researcher led work that was complex, consequential, or required specialist methods.
The routes changed who performed the work—not the standard it had to meet. Each entered the same flow, from an emerging request to a completed study.

Each stage made the request’s maturity and current status visible—from first submission to completed research.
Translated into Jira, the timeline made future demand and available capacity visible; the board showed the status of each request and active study.


The House Standard
ResOps standardised how research moved through the programme. The House Standard did the same for CX insight—connecting evidence across journeys so recurring needs, pain points, and problems could be recognised and reused.
CX Maps are already a well-established design tool. I defined how experience maps, journey maps, and lifecycle stages could contribute to a shared evidence base and a wider understanding of the customer experience.

This was not one map template. It showed how individual maps could build shared UXD intelligence.
A guided Miro framework turned the model into a repeatable workshop process. Teams moved from defining scope and gathering evidence to analysing the journey and producing a completed map.

A shared method made evidence comparable without forcing every journey into the same shape.
Structured Miro content could be exported as CSV and taken into Excel for analysis. Scores, comparisons, and visualisations could then be returned to the map without separating them from the evidence behind them.

The map remained collaborative; its underlying data remained portable.
Example
Order and Pay at Table
Order and Pay at Table allowed guests to scan a QR code, order through the mobile experience, and pay from their table. It provided a live journey through which to apply the shared approach.


The completed map combined the familiar account of the journey with gap analysis, opportunity and confidence scores, prioritisation data, and a view of the emotional forces shaping adoption.

The emotional layer adapted Alan Klement’s forces-of-progress model for CX and UX. It showed where emotional forces were helping or hindering adoption, making them available as inputs to design.

Emotion became an actionable design input—not simply a research observation.
Ready for Service
The operating model gave research work a clearer way to enter, move through, and contribute to the programme.
ResOps organised different forms of evidence around a common activity structure. It allowed research to vary without leaving every project with an entirely different kind of output.
Better prioritisation
Research capacity could be directed towards the work that needed it most.
Clearer support
Designers could distinguish self-service work from research requiring specialist involvement.
Visible capacity
Upcoming demand could be considered alongside the team’s ability to deliver it.
Consistent knowledge
Different studies could produce outputs that were easier to understand and connect.
Greater continuity
Research became less dependent on individual researchers, isolated documents, and organisational memory.
The result was not a production line for identical studies. It was a research practice structured enough to support variety without losing quality.