Our Approach · Floor First, Commercially Measured

Understand the real work. Build the smallest useful solution.

A practical implementation method for retail, operations and customer experience improvement.

Mayne & Loh works with the people doing the job, identifies where time, customers or control are being lost, then builds and embeds a solution that can survive contact with the frontline.

The goal is a working operating improvement—not a report that depends on another project to become real.
Richard leads the diagnosis and strategic work Measures are agreed before the build Ownership is transferred to the client team
25+ yearsRetail and multi-site operating leadership
CCXPCertified customer experience methodology
Floor firstWork is understood with the people doing it
Capability transferTools, access and ownership stay with the client
Four Operating Principles

The method is designed to make implementation more likely

These principles replace generic consulting theatre with a clearer operating discipline.

01 · SEE THE REAL WORK

The process on paper is rarely the process in practice

Diagnosis includes the people completing the work, the workarounds they use, the information they wait for and the customer consequences they see first.

02 · MEASURE BEFORE RECOMMENDING

A useful proposal starts with a baseline

Time, delay, conversion, customer loss, risk or rework must be visible enough to determine whether the improvement is worth pursuing.

03 · BUILD SMALL ENOUGH TO TEST

The first build should prove value, not attempt to solve everything

A focused workflow, dashboard, app or frontline standard can be tested faster, corrected earlier and adopted more successfully than a large transformation programme.

04 · LEAVE CAPABILITY BEHIND

The client should not depend on the consultant to operate the solution

Ownership, access, measures, documentation and coaching are transferred so the client team can continue operating and improving the system.

The Four-Stage Method

Diagnose. Prioritise. Build. Embed.

Each stage produces a concrete output and a decision about whether the work should proceed.

01 · Diagnose

Understand where the operation is actually breaking

Evidence

Richard works with leadership, managers and frontline teams to understand the current workflow, systems, handoffs, workarounds and customer impact. The purpose is to separate symptoms from the underlying operating problem.

What happens

Interviews, process observation, branch or workflow review, available data analysis and examination of existing tools.

What is produced

A friction map, current-state workflow, baseline and a clear statement of the problem worth solving.

Decision

Is the leakage material, measurable and practical enough to justify further work?

02 · Prioritise

Choose the smallest change capable of producing a meaningful return

Commercial Choice

Opportunities are ranked by likely value, implementation effort, adoption difficulty, operating risk and dependency on existing systems. The objective is not the most impressive solution. It is the most useful first move.

What happens

Potential workflows, dashboards, operational apps and frontline changes are compared against the agreed baseline.

What is produced

A prioritised recommendation, measurement plan, build scope, owner, timing and known dependencies.

Decision

Which change offers enough value to build now, and what should be deliberately left for later?

03 · Build

Put a working solution into the real operating process

Implementation

The solution is configured around the people, systems and decisions already present in the operation. It is tested with real users and real work before broader rollout.

What happens

Prototype, workflow connection, user testing, manager review, correction and staged implementation.

What is produced

A functioning workflow, dashboard, app or frontline operating system with agreed access and measures.

Decision

Does the solution work reliably enough in the live environment to expand and embed?

04 · Embed

Transfer ownership and make the new operating rhythm visible

Sustained Use

The final stage establishes who owns the process, how managers coach it, how exceptions are handled and which numbers remain visible after launch.

What happens

Training, documentation, ownership assignment, access handover, performance review and follow-up adjustment.

What is produced

A client-owned operating process, trained users, visible measures and a defined review rhythm.

Decision

Can the client team operate, measure and improve the solution without day-to-day dependence on Mayne & Loh?

The Paid Diagnostic

One to two weeks to determine what is worth building

The diagnostic is a fixed-scope piece of work agreed before it begins. It is designed to create a reliable basis for investment—not to manufacture a reason for a larger project.

01
Current-state friction mapThe real workflow, handoffs, workarounds, systems and points where delay or inconsistency enters.
02
Commercial or operational baselineThe current time, delay, rework, conversion, customer loss, risk or cost used to judge improvement.
03
Prioritised opportunity listPotential interventions ranked by payback, feasibility, adoption difficulty, risk and dependency.
04
Defined build recommendationThe smallest useful solution, owner, timeframe, required access, expected outputs and measurement plan.
05
Clear decisionA recommendation to build, defer, solve internally or stop—without an automatic obligation to continue.
How Opportunities Are Ranked

Payback matters, but so do feasibility and adoption

A high-value idea that cannot be adopted, governed or supported is not yet a good first project.

Value

What improves?

Hours, conversion, retention, response speed, cost, risk, compliance or customer outcome.

Feasibility

Can it be built reliably?

Available data, system access, process stability, technical dependencies and internal capacity.

Adoption

Will people use it?

Ease of use, manager ownership, training requirement, frontline relevance and change load.

Risk

What must be controlled?

Security, privacy, customer impact, business continuity, decision authority and auditability.

The preferred first build is not necessarily the largest opportunity. It is the opportunity that combines meaningful value with a realistic path to implementation and adoption.
Governance and Collaboration

Practical implementation should respect the systems and controls already in place

Mayne & Loh can work alongside internal IT, data, operations, CX and regional teams. Governance is designed into the work rather than added after the build.

Data, access and security

The required information and access should be limited to what the agreed work actually needs.

  • Use client-controlled accounts and environments where practical
  • Define data fields, access roles and retention requirements before build
  • Avoid requesting sensitive customer or employee data unless clearly necessary
  • Confirm privacy, confidentiality and Singapore PDPA requirements before access

Internal IT and operating ownership

The solution should complement internal capability rather than bypass or duplicate it.

  • Identify technical and operating owners early
  • Document dependencies on existing systems and vendors
  • Agree who supports the solution after handover
  • Make subscriptions, licences and ongoing costs visible before implementation

Frontline participation

The people using the process are involved before the design is finalised.

  • Observe real work rather than relying only on policy documents
  • Test language, steps and interfaces with actual users
  • Capture workarounds and exception cases early
  • Use manager coaching to reinforce the operating standard

Ownership and handover

The client should know exactly what it owns and how the system continues to operate.

  • Transfer access, documentation and operating instructions
  • Assign an internal owner for measures and exceptions
  • Establish a review rhythm after launch
  • Define any optional support separately from the core build
Supporting Customer Experience Discipline

CCXP methodology strengthens the operating work

Formal customer experience practice supports the method, but it does not replace operational judgement. The purpose is to connect customer insight, frontline behaviour and commercial outcomes.

Customer Insight

Understand the experience

Use customer feedback, behaviour and frontline observation to identify what is actually happening.

Strategy

Connect CX to business priorities

Focus on the customer moments that influence retention, conversion, trust, cost or operational performance.

Design

Translate intent into a usable standard

Define the journey, language, process, ownership and tools required for consistent execution.

Measurement

Link experience to outcomes

Track customer and operating measures together rather than treating CX as a purely soft indicator.

Culture

Make it part of daily management

Use manager coaching, visible standards and regular review to sustain the expected behaviour.

Operator Judgement

Adapt the framework to the real environment

Balance formal methodology with practical constraints, local market context and frontline reality.

Common Questions

What clients usually want clarified

Why start with a paid diagnostic?

The diagnostic creates the evidence needed to decide what is worth building. It reduces the risk of investing in a technically attractive solution that does not address the real operating problem.

Can we stop after the diagnostic?

Yes. The diagnostic is a defined piece of work. Its conclusion may be to build with Mayne & Loh, solve the issue internally, defer the work or not proceed.

How involved do our managers and frontline teams need to be?

They need to participate enough to explain the real workflow, test the proposed change and support adoption. The time requirement is agreed in advance and should be proportionate to the scope.

Can Mayne & Loh work within our IT and security requirements?

Yes, provided the relevant controls and decision-makers are identified. The design should reflect approved systems, access rules, privacy requirements, data retention and internal ownership.

What happens after the four-to-six-week build?

The client receives the working tools, access, documentation, training, assigned ownership and agreed measures. Optional support can be scoped separately, but the core model is not intended to create operational dependency.

A Clear First Step

Request a free working session with Richard

Bring one operational problem. Clarify what is happening, what it may be costing and whether a one-to-two-week diagnostic would be worthwhile.

Request a Free Working Session

No obligation. Scope, deliverables and pricing are confirmed before any paid work begins.

The conversation will cover:

  • The process or customer moment causing the greatest friction.
  • What evidence is already available.
  • The number that would prove an improvement succeeded.
  • Whether the problem is practical and valuable enough to diagnose.
The team is online. Questions about AI, dashboards, or training? Or take Harvey's free five question diagnostic.
M&L
Mayne & Loh
The team is online
AI Team
Who would you like to talk to?
Real expertise, available now. Richard handles every strategic conversation personally.
Our AI team is part of what we build for clients. Talking to them is the product demo. Everything important reaches Richard.
AI team member · Powered by Mayne & Loh