What this guide covers
What you’ll be able to do
- Audit understanding and functionality together
- Separate a symptom from its likely cause
- Record and recheck one completed repair
Applied psychology asks whether the message helps a person understand and act. Applied economics asks whether the effort and investment produce useful progression. Audit both by following one connected journey.
Skip to a section
Chapter 01
Choose one journey with a clear purpose
Begin with an actual introduction: an ad, search result, social post or shared resource. Write the question it opens and the next step it promises. Then follow that route as someone unfamiliar with the practice would.
- 01
Choose a real entrance
Start with an actual ad, search result or shared link. Record what it invites the person to understand or do before following the destination.
- 02
Follow the same question
Keep the original expectation in view as you move through the page. Notice where the subject changes or the person must supply missing context.
- 03
Record the first hesitation
Write what caused confusion before proposing a fix. A useful audit preserves observation separately from the team’s preferred explanation.
In this fictional workshop, the team follows Maya from Dr. Casey’s post to a first-visit page. The post invites her to learn what an appointment involves. The page should answer that question before asking her to act. That simple continuity is the starting test.
See it in action
Follow one real patient journey.
Read the campaign as a person discovering your practice.
Follow the link and find where things become unclear.
Look at what happens when someone actually gets in touch.
Sample creative. Fictional practices; no client results implied.
Examples & steps
Audit the same journey from three different entrances
Once the basic route is inspected, test whether it stays coherent when the person enters somewhere other than the campaign’s first page. A visitor may arrive from a search result, a shared article or the practice’s social profile. The page should still make sense without requiring knowledge of an advertisement they never saw.
Advanced case: the useful article with no way forward
A first-visit article answers the process well, but its only next link returns to a general resource index. A person who is ready to contact the practice has to search for the phone number. The repair is a clear, relevant next step near the answer, while preserving the article’s value for readers who are still learning. The diagnosis is a missing connection, not insufficient persuasion.
Use a three-entrance inspection
- Campaign entrance: open the actual creative’s destination and check the promise.
- Information entrance: open the useful article directly and check whether the practice, subject and next step are clear.
- Ready-to-contact entrance: open the contact or booking route directly and check the essential facts and action state.
Record where the experience depends on information the person may not have. A headline such as “You’re in the right place” says little to someone arriving without context. A concise description of the page’s purpose is more useful.
Test the interruption between visits
Imagine someone reads the page today and returns later from a saved link. Can they identify the practice and find the relevant action? Does the page still display current facts? This simple scenario can expose a route that only works when a person remembers the whole campaign.
Chapter 02
Bring the people who see different parts
The doctor knows the care explanation. The front desk hears the practical uncertainties. The marketing person understands the message and destination. Ask each to describe what the person is likely to know at the moment they receive the conversation.
- 01
Hear each operating view
Ask the doctor, front desk and marketing lead what this person needs to know. Keep their answers separate long enough to notice contradictions or missing responsibilities.
- 02
Let a newcomer try
Give someone unfamiliar with the page a practical task and observe without coaching. Their uncertainty can reveal a gap the team no longer notices.
- 03
Agree the actual standard
Resolve the process facts together. The page should represent the visit the practice delivers, not the version that makes the neatest marketing story.
Let someone unfamiliar with the page try it before the team explains it. Ask them to find the location, describe the first visit and say what they expect the main button to do. Their hesitation often identifies a missing connection more clearly than a debate about design preferences.
Examples & steps
Use disagreement to find different kinds of evidence
The marketer, front desk and clinician may interpret the same problem differently. The marketer sees engagement, the front desk sees unanswered questions and the clinician sees the expectations people bring into the appointment. Treat those views as different evidence sources rather than competing opinions.
| Statement in the meeting | Evidence to request | Question it can answer |
|---|---|---|
| “People like the campaign.” | The actual engagement and inquiries, with context. | What kind of attention did it earn? |
| “Everyone asks the same thing.” | A defined de-identified question sample. | Which answer is missing or difficult to find? |
| “They arrive with the wrong idea.” | The exact expectation and the message that may create it. | Where does the campaign imply something inaccurate? |
| “The form works.” | An authorized test showing confirmation and receipt. | Does the action complete the intended handoff? |
Separate preference from a defect
“I prefer a larger photograph” is a design preference. “The text inside the photograph cannot be read on a phone” is an observable usability issue. “I would use a different headline” is an alternative. “The headline promises a confirmed appointment but the form only requests contact” is a meaning mismatch. Label the type of finding so the team can choose the right repair.
Preference still matters, especially for a brand-led practice. It simply should not be presented as measured conversion evidence. A clear audit can respect the owner’s design judgment while documenting technical and meaning problems separately.
Ask a neutral task
Instead of “Can you find our easy booking button?”, ask “Show me how you would arrange a first visit.” The first question tells the tester what to look for and implies the answer should be easy. The second lets you observe the route they actually choose.
Chapter 03
Follow the action beyond the button
Check whether the next step reaches somebody who can help. A request is not a confirmed appointment. A confirmation should explain what has happened, what remains to be arranged and how the person can ask a question.
- 01
Check the destination
Confirm that the primary button reaches the promised page, form or booking route. Test on the devices people actually use, including a narrow phone.
- 02
Inspect the receiving side
With appropriate authorisation, use clearly fictional test details and check what the receiving team sees. A success screen alone does not establish a complete handoff.
- 03
Verify the next instruction
Read the confirmation and identify what has actually happened, what remains open and how the person can ask or change something.
Use fictional information for a planned test and observe the receiving side where available. If the team cannot see a part of the journey, record the gap. The point is to understand the experience, not to declare that everything works because the page looks polished.
See it in action
Find where the connection breaks.
Make sure the page delivers what brought them there.
Name the problem, the owner and the check.
Examples & steps
Inspect the difference between a visible success and a completed handoff
A confirmation message can appear even when the receiving process is incomplete. The page may say the request was sent, but the team may not know who receives it, how it is assigned or what happens next. Conversely, a backend record may exist while the public confirmation leaves the person confused.
Use an authorized test environment or a clearly approved test procedure. Avoid creating unplanned real appointments or sending messages to actual patients while auditing. Record the exact test state and the systems you inspected so “tested” does not become an overbroad claim.
Advanced case: the duplicate request
A person presses the button twice because the page gives no clear feedback. Two records appear. The audit should inspect the public waiting and confirmation states, the receiving duplication behavior and the team’s handling rule. Merely disabling the button visually may not address the full issue. The repair needs to match the actual implementation.
Advanced case: the right record, wrong owner
The request arrives in the system, but it is assigned to a person who is away. The page works technically; the service handoff does not. The repair is ownership and backup coverage, plus a way to see unresolved work. A new landing-page design will not solve that gap.
Record four states
- What the person sees: loading, success, error and next-step wording.
- What is recorded: the correct request or appointment state in the appropriate system.
- Who receives it: the assigned role and backup.
- What happens next: the verified response or task, with an appropriate exception route.
Keep the evidence limited to what was actually checked. A local form test does not establish delivery to a live CRM. A visible record does not establish that a real person responded. Precision makes the audit useful for the next operator.
Chapter 04
Separate the symptom from the cause
A low booking rate may reflect unclear value, an unanswered question, unsuitable appointment times or a broken route. Do not leap straight from the number to a new headline. Read the actual questions and inspect what the person encountered.
- 01
Name the symptom precisely
Replace “the form does not convert” with the observed behaviour, such as abandonment before unnecessary questions or repeated uncertainty about whether a time is reserved.
- 02
Compare plausible causes
Inspect message clarity, practical availability, field requirements and technical behaviour. Use the evidence to narrow the cause before choosing a familiar cosmetic repair.
- 03
Choose a bounded repair
Change the part most directly connected to the observed problem and preserve useful surrounding work. This makes completion easier to verify and later results easier to interpret.
For Maya, the visible problem might be abandoning a long form. The useful repair could be explaining the first visit earlier, reducing unnecessary questions or offering a clear way to discuss availability. Choose the cause supported by the observation rather than changing everything at once.
Examples & steps
Compare competing explanations before choosing a repair
The same symptom can have different causes. A weak booking rate might reflect unclear information, limited appointment times, delayed responses, an unsuitable invitation or an incomplete observation window. Choosing the first explanation that fits your preference can lead to an expensive repair of the wrong problem.
| Symptom | Possible explanation | Discriminating observation |
|---|---|---|
| People inquire but do not book. | They cannot find suitable times. | Review actual time requests and available options. |
| People inquire but do not book. | The appointment is poorly explained. | Inspect repeated questions and uncoached understanding. |
| People inquire but do not book. | Replies are delayed or unowned. | Check the receiving process and pending work. |
| People inquire but do not book. | The group has not had enough time to progress. | Check cohort dates and pending appointment decisions. |
Use a small evidence test
Choose an observation that helps distinguish the explanations. If the suspicion is availability, inspect scheduling questions. If it is message clarity, ask a newcomer to explain the offer. If it is delivery, trace an authorized test request. The best first test often requires less production than the proposed redesign.
Keep multiple causes possible
A route can have more than one problem. Correct a confirmed defect while continuing to investigate the larger pattern. Do not make a technical fix carry a promise that it will solve every business outcome. A repaired form can make inquiries arrive reliably; it cannot guarantee appointment fit or a care decision.
Write the hypothesis in plain language: “We think [specific obstacle] contributes to [observed behavior] because [evidence]. We will check it by [bounded task]. If the observation does not support it, we will examine [alternative].” This makes the audit a learning process rather than a debate won by confidence.
Chapter 05
Leave with one repair and a follow-up
Prioritise a problem that interrupts understanding or action. Write what happened, why it matters, the change to make and who will make it. Preserve the pieces that already help the journey; an audit is not an automatic invitation to redesign.
- 01
Write the repair contract
Record the observed problem, the change, the owner and the task that must work afterward. Include the important surrounding behaviour that should remain intact.
- 02
Repeat the original task
After the change, follow the same route on the same relevant device. Compare the result with the original observation before calling the defect fixed.
- 03
Review the later outcome
Once enough real use has occurred, check recurring questions, progression or workload. Keep that outcome review distinct from verifying the immediate functional repair.
Then repeat the same task after the change. Observe the surrounding step too: a clearer button is helpful only if it still leads to the promised action. Review later whether recurring questions or progression changed, keeping that outcome review separate from confirming the repair itself.
See it in action
Leave with one repair to make.
Go from the first image to a useful practice conversation.
Examples & steps
Prioritize repairs by consequence and confidence
A long audit list can overwhelm the team. Sort findings by the consequence of leaving them unresolved, the confidence in the evidence and the effort to repair them. A broken action or inaccurate promise often belongs ahead of a cosmetic preference. A large redesign based on a weak hypothesis may need a smaller test first.
- Correct a verified defect: a broken destination, missing required information or inaccurate action state.
- Resolve a material uncertainty: an unverified receiving route, unclear ownership or a disputed practice fact.
- Improve a demonstrated friction point: a repeated misunderstanding or difficult task observed in use.
- Develop a design opportunity: a stronger creative treatment or presentation that supports the page’s job.
These categories help sequence work without dismissing design quality. Once the route is accurate and functioning, strong visual communication can make its value easier to see. The key is knowing which kind of improvement you are making and what evidence would verify it.
Define acceptance in the same terms as the finding
If the finding is “a newcomer cannot tell whether a time is confirmed,” the acceptance check is whether an uncoached newcomer can explain the appointment state after the revision. If the finding is “the request does not reach the assigned owner,” the check is the authorized delivery trace. Do not substitute a screenshot of the new button for either test.
Close the repair with a durable note
Record the old behavior, the change, the exact verification and the remaining limitation. Link to the working asset. This prevents the next person from repeating the audit or reintroducing the problem through an unrelated edit.
POWERSURGE / PRACTICE WORKSHOP
Make the next step easier to take
A PowerSURGE working kit for practice owners, front-desk leads and marketing teams
Help more interested visitors understand your practice and reach the right next step. This workshop follows one journey from a public invitation to the receiving team, then turns the first supported problem into a repair someone can finish. Use it when your team has plenty of opinions about the website but needs a clear decision.
A common example: the first-visit page explains the practice well, but “Book my visit” opens a callback form. The visitor wonders which time they selected, while the front desk thinks it received a request. You can fix the words and the handoff without rebuilding the website. The completed example below shows how.
It extends Run a practical marketing audit with your team. The Booking & Follow-Up Check is a useful starting check. This workshop goes further by separating what a visitor understands, what the technology does and what the receiving team can carry forward.
THE WORK / MADE VISIBLE
Follow the work, not your assumptions.
A contained inspection with evidence and a retest.
- 01 / OBSERVE
Give a neutral task.
Use the exact route and device. Record what happened before discussing why.
- 02 / LOCATE
Name the kind of break.
Meaning: unclear. Function: not working. Ownership: nobody receives it.
- 03 / REPAIR
Choose the smallest useful fix.
Record the change, responsible role and expected result.
- 04 / RETEST
Repeat the same task.
Keep the evidence beside the decision. A change is not a verified repair.
Set up a contained workshop
Plan a focused 45-minute working session. Bring a practice decision-maker, someone who receives enquiries and whoever owns the website or campaign. Invite a colleague unfamiliar with the specific page to attempt the task.
Choose one entrance: a real public post, search listing, ad or shared link. Choose one task: understand the first-visit process, find the correct office or request a time. “Audit our marketing” is too broad to observe.
Start with public pages and the team's response templates. For any live test, agree who will receive it and where to stop. Record the receiving side separately from the success screen: they answer different questions.
The agenda
| Minutes | Activity | Output |
|---|---|---|
| 0–5 | Agree the task and what can be tested | One task statement and test boundary |
| 5–15 | Observe the newcomer without coaching | Exact words, actions and hesitations |
| 15–25 | Compare public promise with actual process | Confirmed facts and unanswered questions |
| 25–35 | Inspect the receiving handoff or its current template | Separate front-end and receiving-side evidence |
| 35–45 | Choose one repair and assign verification | Named owner, reviewer and recheck |
If the problem needs longer investigation, leave with an investigation owner and the missing evidence. Do not manufacture a repair just to finish the agenda.
1. Give the newcomer a neutral task
Read this aloud:
“Imagine you are considering a first visit to this practice. Starting from this link, find what happens at the first visit and how you would arrange a time. Please describe what you are looking for and what you think each step means. You can stop whenever you would normally stop. Stop before submitting the form so we can review what you expect next.”
Do not say “Click the green booking button.” That tests obedience to instructions rather than whether the page explains itself. If the person asks for help, record the question before answering. A useful observation might be “They asked whether sending the form reserves a time,” rather than “They didn't like the design.”
Observe successful moments too. An accurate location card or clear practitioner introduction should survive the repair.
2. Record evidence before explanations
Use one row per observed event. Keep hypotheses in their own column.
| Step / public URL | Task or question | Exact observation | Possible explanation | Evidence still needed | Status |
|---|---|---|---|---|---|
Status choices: Clear / Needs work / Not checked. “Needs work” means you observed a specific problem. “Not checked” means you do not yet know. Neither is a diagnosis of the whole practice.
Examples of useful evidence:
- The exact button says “Confirm booking,” but the practice describes it as a callback request.
- The map opens the other office's address.
- On the tested phone, the keyboard covers the next control and the tester cannot reach it.
- The first-visit explanation is found and accurately understood without assistance.
- The form displays success; the receiving record has not been inspected.
Use exact public wording and team roles in the observation sheet. That gives the repair owner enough detail to reproduce the issue.
3. Inspect three different kinds of continuity
Meaning: does the person understand the next step?
Ask the newcomer to explain the practice, location, first-visit process and action in their own words. Compare with the real operating facts. A page can be attractive and technically functional while communicating the wrong expectation.
Function: does the action work in the observed conditions?
Record device, browser and date. Follow the exact link. Check the chosen task with touch and, where practical, keyboard navigation. Look for legible labels, clear focus, recoverable errors and a truthful success message. These are useful checks, not a claim of complete accessibility testing. W3C guidance explains form labels and clear submission feedback for your implementer.
Ownership: can the team continue the conversation?
Check whether the intended queue receives the request, whether someone owns it and whether a backup exists. Preserve the campaign topic so the next person can continue the conversation. A technically delivered enquiry can still wait without an owner.
4. Choose the right kind of repair
| Observation | First investigation | Avoid jumping straight to |
|---|---|---|
| Visitor does not understand the first appointment | Missing or conflicting practice facts | A discount |
| Button does not work on the tested device | Reproduce the technical failure | A headline rewrite |
| Correct request reaches an unattended inbox | Routing, ownership and coverage | More advertising |
| Person expects an immediate confirmed time | Button, form and success wording | Blaming lead quality |
| Person cannot find suitable availability | Actual capacity and arrangement process | A stronger urgency message |
Prioritise a misleading fact or a blocked action. Next address an unowned handoff. Then remove unnecessary effort. Aesthetic improvements can follow when the decision and action are intact.
The front desk should verify operational statements. The practitioner or appropriate reviewer should approve clinical explanations. The website owner should verify the change behaves as intended. Together, those checks connect the page to the real visit.
5. Completed illustrative example
Fictional teaching example. This is not a real practice audit or a claim of campaign results.
Meadow Practice invites visitors to “See your first visit, step by step.” The fictional observer finds a clear introduction and accurate office directions. The action says “Book my visit.” After opening the form, the observer asks, “Which time have I chosen?” No appointment selection exists. The approved operating description says the front desk receives a request and contacts the person to arrange a time.
Observation: The action label creates an expectation the process does not fulfil.
Hypothesis: Clear request wording could reduce this specific uncertainty.
Evidence: Exact button text, observer question and verified administrative process.
Next question: Do fewer people ask whether a time is already reserved after the change?
The team chooses a bounded repair: change the action to “Request an appointment”; add “Our team will contact you to arrange a time”; align the success message. Keep the clear introduction, directions and approved clinical copy intact.
Completed ownership map
| Work | Responsible role | Evidence needed |
|---|---|---|
| Confirm actual process | Front-desk lead | Written agreement that this is a request |
| Edit three affected messages | Website editor | Changed button, form introduction and success template |
| Recheck understanding | Workshop facilitator | New uncoached reading correctly distinguishes request from confirmed appointment |
| Check receiving side | Front-desk lead | Labelled fictional request visible in correct queue with owner |
| Remove test artefacts | System owner | Test record and queued messages handled under agreed plan |
The repair is complete when those checks pass. The team can then review whether the same practical question continues to recur.
6. Reusable repair contract
Journey: __________
Visitor's task: __________
Observed problem, quoted precisely: __________
Evidence location and date: __________
Confirmed operating facts: __________
Unresolved questions: __________
Smallest proposed change: __________
What must remain intact: __________
Owner / reviewer / backup: __________
Test / stop point: __________
Pass condition: __________
Recheck date: __________
Result: Passed / Failed / Not checked
Next investigation, if any: __________
Verification script
“Starting at [exact entrance] on [device/browser], attempt [original task]. Read [changed wording]. Explain what happens next without coaching. For the agreed submission test, use [fictional test reference] and stop before [boundary]. Confirm [expected receiving evidence]. Check that [preserved behaviour] still works. Record actual result and cleanup.”
Team handoff note template
“We observed [specific issue] while attempting [task]. The agreed correction is [bounded change]. [Owner] will complete it; [reviewer] will verify the operating facts. We will repeat [exact test] on [date]. Preserve [working elements]. Until the receiving-side check is complete, its status remains Not checked.”
Keep the workshop grounded
- Use public copy, team roles and fictional test details. Keep patient information in the practice's appropriate systems.
- Confirm prices, appointment status and operating promises with the team; have clinical explanations reviewed by the appropriate practitioner.
- Before a live submission, agree the receiving owner, stopping point and cleanup so the test does not create an unintended appointment or send messages to someone else.
Leave with a decision, not a score
At the next team meeting, ask: Did we make the repair? Did the same task work? Did it cause a new problem nearby? What evidence remains missing? Review recurring questions or aggregate journey progression separately when there is enough relevant activity to learn from. Record the period, any changes to traffic or staffing and unknown outcomes.
If implementation needs a connected marketing starting point, bring the repair contract to The Defibrillator. You will arrive with something more useful than “we need a better website”: a real task, a supported observation and a clear next move.
YOUR TURN / A WORKING COPY
Your journey inspection record
Draft here, then download your notes. This exercise does not submit anything to PowerSURGE or your CRM. Notes are not saved automatically; keep patient details out.
Put it to work
Run the advanced audit: three cases, three different repairs
Use realistic edge cases to separate message problems, delivery problems and operating constraints.
Case 1: a beautiful campaign, an unclear commitment
The creative and page look strong. The button says “Book now,” but the confirmation says the office will call to arrange a time. The receiving team reports that some people believe they already have an appointment.
Diagnosis: the central action implies a different commitment from the implemented process. Repair: accurately label the request and confirmation, or deliberately implement a real booking route if that is the approved practice choice. Verification: an uncoached newcomer can explain what happened and what remains to be arranged. Later observation: review whether the same misunderstanding continues.
Case 2: a working form, an unowned conversation
The form creates the correct record, but the assigned person is absent and there is no backup. The team later finds unanswered inquiries. A report describes the campaign as underperforming.
Diagnosis: the receiving process is incomplete. Repair: define ownership, coverage and a visible unresolved-work check. Verification: an authorized fictional inquiry reaches the appropriate role under both normal and absence conditions. Later observation: inspect the defined inquiry group and the actual response experience. Do not attribute all downstream change to the form itself.
Case 3: relevant inquiries, unsuitable availability
The campaign produces questions from people who understand the practice, but many ask for times the clinic cannot currently offer. The proposed response is to rewrite the ads to be more persuasive.
Diagnosis: the evidence points first to a capacity or access mismatch. Repair: verify the appointment options, make practical information clear and align demand with what the practice can serve. Verification: the public invitation and receiving answers reflect real availability. Later observation: review the kinds of requests and whether the remaining route fits the practice’s capacity.
Use the case pattern on your own finding
Observed behavior: [what happened]. Evidence: [where and when]. Competing explanations: [plausible causes]. First check: [bounded task]. Confirmed repair: [specific change]. Owner: [role]. Acceptance: [repeatable test]. Later outcome review: [defined group, period and observation]. Remaining uncertainty: [what the check does not prove].
Bring one current finding to the team and complete the record together. Keep the first repair small enough to verify. If the evidence calls for broader work, the record gives that work a clear reason and a concrete starting point.
The audit is complete when a useful decision has been implemented and checked, not when every page has accumulated comments. Preserve the learning and move to the next limiting connection.
Notes aren't saved automatically. Download them before leaving. Don't include patient details.
06 / Put it to work
Finish one repair and verify the same task
The best audit ends with a clearer patient journey and a specific improvement the team can finish.
What is preventing a useful audit decision?
Your next move
The team is debating preferences
Choose a real entrance and ask a newcomer to complete a specific task. Record where they hesitate before discussing solutions. A shared observation makes the audit more useful than another round of opinions about colours or headlines.
- Name the visitor’s task.
- Observe without coaching.
- Record the first supported point of confusion.
Put your plan in motion
Your first campaign. Our compliments.
The Defibrillator connects 12 custom social posts, 3 articles, a landing page, a lead form and 3 follow-up emails. Built for your practice.
Request your kit with your name, practice, email and website. No call. No purchase.
Explore my free campaignThe method behind the work.
Continue with the original guides and the source material behind this lesson. Worked examples are teaching illustrations unless explicitly attributed.
Internet Playbook ↗Open the complete original guide.The Internet Playbook for Chiropractors ↗Current 18-page V13. Pages 4–11. The eight moves connect marketing, conversion, patient experience and advocacy.The R.O.I. Method for Chiropractors ↗Original R.O.I. framework; PDF pages 7–12. Relevancy, Omnipresence and Intimacy describe communication responsibilities, not a financial return calculation.Sources and context
Dr. Stacey on attribution and refinementHistorical rationale for linking observation to management decisions; the audit cases are illustrative.
W3C: form labelsVisible descriptive labels and programmatic association support understandable form controls.
W3C: form instructionsInstructions should remain available; placeholders do not replace labels.
