There is a point at which another article about digital change stops helping. You may agree that platform debt is expensive or that parts of the client experience are weaker than they should be. The practical question is what happens after you ask us to look.
Our first two weeks are designed to replace a broad concern with a usable view of the problem. We experience the service, assemble evidence, test our interpretation with the people who run it and agree what deserves attention first. The result should have value even if you decide to do the work internally or appoint somebody else.
This is what that process looks like in practice. The exact timetable changes with the size of the firm, the access available and the sensitivity of the systems involved. It is a working sequence, rather than a promise that every organisation can be understood on an identical fourteen-day clock.
Days one and two: experience the service
We begin where a prospective or existing client begins: the public website, an enquiry route, a service page or a client task. We look for answers a buyer needs, follow calls to action, use the mobile experience and trace what happens after an interaction.
That does not mean submitting live enquiries or entering a production portal without agreement. We define the journeys and permissions first. Where a portal or workflow needs testing, we use an approved test account or synthetic information. The aim is to encounter the service realistically without creating false leads, exposing client data or confusing operational teams.
This first-hand view matters because firms can be living with small points of friction that nobody inside the organisation now sees. A service described internally as simple may involve several hand-offs, a PDF that is difficult to complete on a phone and an acknowledgement email that tells the client very little. Nobody has been deceptive. Familiarity has hidden the effort.
By the end of day two, the useful output is a set of specific observations and questions. We arrive at the first leadership conversation with evidence to discuss. A brief mystery-shop is still only one evidence stream, rather than the truth about the whole firm.
Days three to five: build the evidence base
Next, we look at the information already available. That can include analytics, conversion data, search behaviour, CRM stages, support enquiries and structured client feedback. We review these sources together because a pattern that is invisible in one system may become obvious when several are compared.
Access is deliberately proportionate. We agree which questions the data needs to answer, request the minimum permissions required and avoid copying sensitive information into a separate working environment without a reason. A named owner on the client side usually helps us arrange access, explain what each dataset can and cannot show, and resolve differences in definitions.
Evidence comes before confident conclusions, but people are part of the evidence. The original version of this process placed stakeholder conversations after the data because people naturally steer discussion towards what they expect to be true. That risk is real. So is the opposite risk: treating incomplete analytics as objective while ignoring how a process actually operates.
We therefore use the data to sharpen interviews, not to disqualify them. A high exit rate may indicate a weak page, or it may mean visitors obtained the answer they needed. A slow CRM stage may reflect a broken workflow, an inconsistent field definition or a deliberately long buying cycle. The people who own the work help us distinguish among those explanations.
Competitor review also has a defined purpose. It can show how peers explain a complex service, structure an enquiry or support a client task. It cannot establish a universal benchmark on its own. We compare relevant journeys and capabilities, then explain why a difference may matter commercially instead of scoring the firm for being unlike a competitor.
Days five to seven: share the emerging diagnosis
We then bring the initial findings together. The session covers what appears to work, where the experience and evidence conflict, which conclusions remain tentative and what we still need to learn.
The important word is emerging. Two useful days of analysis do not justify theatre about knowing the business better than the people who run it. Equally, a desire to preserve harmony should not turn the session into a recital of facts everybody already accepts. We show the evidence behind each significant judgement and separate observations from interpretations.
We also share the material in advance. That practice came from experience. Presenting a surprising finding as a dramatic reveal can make a senior stakeholder feel ambushed and leave the meeting focused on defensiveness rather than the problem. Giving people time to inspect the evidence produces a more demanding conversation and usually a better diagnosis.
Commercial implications are expressed with similar care. If a form fails, a service is hard to understand or an internal hand-off creates delay, we describe the plausible effect and identify what would be needed to quantify it. We do not turn an industry conversion rate or a competitor's apparent speed into a precise forecast of deals the firm has lost.
Days eight to ten: improve something useful
An assessment should not become an excuse to postpone an obvious, low-risk fix. At this point we identify a short list of improvements that are valuable, feasible and unlikely to pre-empt a larger decision.
Candidates might include correcting out-of-date team information, repairing an agreed form, improving an accessibility defect or making the next step on a service page clearer. We begin one only with the relevant owner's approval, an understood release route and a way to reverse the change. Production changes remain subject to the firm's normal security, compliance and change controls.
That boundary is important. A visible quick win can build confidence, but speed is not proof of value. We will not alter regulated copy, customer data flows, tracking behaviour or core workflows simply to demonstrate activity by day ten. Where the right change needs more investigation, the useful result is a tested recommendation and a clear owner, rather than an unsafe deployment.
Days eleven to fourteen: decide what follows
Finally, we organise the work using our WHNN® framework. It gives the assessment four connected views:
- Now: the current position, supported by the strongest available evidence and explicit gaps.
- Next: a credible near-term state, shaped by the firm's commercial priorities and constraints.
- What: the few initiatives most likely to close that gap, ranked by value, feasibility and dependency.
- How: the ownership, sequencing, capability and delivery approach needed to move.
The output is a focused findings document, not a large audit designed to prove how much analysis occurred. It records the important evidence, what we think it means, where confidence is limited, the decisions required and a recommended starting point. It should be intelligible to the executive sponsor and useful to the operational or technology leaders who would act on it.
We also make dependencies visible. A website issue may actually begin in proposition design, content ownership, CRM configuration or a slow approval route. Recommending a new interface without dealing with that cause would produce a cleaner surface and leave the service unchanged.
What we need from your firm
The assessment needs an executive sponsor who can clarify the decision it must support, a day-to-day contact who can coordinate access, and time with the people closest to the relevant journeys. We agree the exact requests before starting. They may include read-only access to selected systems, approved test accounts, existing research, process documentation and stakeholder interviews.
Current pricing, duration and client effort depend on scope, the digital estate and access requirements. Those details should be confirmed in a written assessment brief rather than inferred from an old article. The brief should state the fee, assumptions, inputs, named outputs, security arrangements and what happens if access is delayed.
You are buying clarity, not an obligation
The findings remain useful if you do not commission a following phase from Distinction. You should be able to give them to an internal team, use them to brief another supplier or decide that the evidence does not justify further work yet.
That independence is a useful test of the engagement. If the assessment only makes sense when it leads to our preferred delivery project, it is closer to paid qualification than discovery.
If you want to explore whether this kind of two-week assessment fits the decision your firm is facing, book a conversation. We can define the question, the access required and the output before either side commits to the work.
