The Friction Audit: Why Telehealth Adoption Depends on Subtle Workflow Gaps

Telehealth adoption rarely fails because of a single dramatic breakdown. More often, it erodes slowly—a patient who can't find the login link, a clinician who spends extra minutes toggling between systems, a follow-up that never gets scheduled because the workflow doesn't prompt it. These are friction points: small, cumulative gaps that drain momentum. This guide shows you how to run a friction audit, a structured method to find and fix those gaps before they undermine your telehealth program.

Who Needs a Friction Audit and What Goes Wrong Without It

Any organization offering telehealth services can benefit from a friction audit, but it is especially critical for clinics that have seen adoption plateau or decline after an initial rollout. Without such an audit, teams often blame low usage on patient reluctance or poor technology, when the real culprit is a clunky workflow that frustrates both patients and staff.

Consider a typical scenario: a primary care practice launched video visits during the pandemic. Initially, usage was high because patients had limited options. Over time, in-person visits resumed, and telehealth utilization dropped to 20% of what it was. The practice assumed patients preferred face-to-face care. But a friction audit revealed that the scheduling process required patients to download a separate app, create an account, and then wait for a confirmation email that often landed in spam. The audit also uncovered that clinicians had to manually copy visit notes from the telehealth platform into the EHR—a step that added 3–5 minutes per visit. These small inefficiencies compounded, making telehealth feel like more work than it was worth.

Without an audit, teams might invest in a new platform or marketing campaign, only to see the same adoption ceiling. The friction audit shifts the focus from technology to process, uncovering the invisible barriers that quantitative dashboards miss. It is a diagnostic tool for workflow health, not a one-time fix.

Who Should Lead the Audit

The audit works best when led by someone who understands both clinical workflows and patient experience. This could be a practice manager, a telehealth coordinator, or a quality improvement specialist. The key is to have a neutral perspective—someone who can observe without assuming they already know where the friction lives.

Signs You Need an Audit

Look for these indicators: high no-show rates for telehealth visits, frequent patient complaints about login or connectivity, staff reports that telehealth visits take longer than in-person ones, or a growing backlog of unscheduled follow-ups. Any of these suggests that friction is present and growing.

Prerequisites: What to Settle Before You Start

A friction audit requires preparation. Jumping in without a clear scope or baseline data can lead to inconclusive results. Here are the prerequisites you should address first.

Define the Patient Journey Stages

Map out the complete telehealth journey from the patient's perspective: awareness, scheduling, pre-visit preparation, the visit itself, and post-visit follow-up. For each stage, list the steps the patient must take and the tools they interact with. This map becomes your audit checklist. Without it, you may miss critical touchpoints.

Gather Baseline Metrics

Collect data on current adoption rates, no-show percentages, average visit duration, and patient satisfaction scores. You need these numbers to compare against post-audit improvements. Do not rely on anecdotal impressions alone. For example, if you think the scheduling process is smooth but data shows a 30% abandonment rate at that step, you have a clear target.

Secure Stakeholder Buy-In

Clinicians, front desk staff, and IT support all play a role in telehealth workflows. Without their cooperation, you may miss friction points they experience daily. Schedule brief interviews or shadow sessions with each role. Explain that the goal is to make their work easier, not to assign blame. This builds trust and encourages honest feedback.

Choose an Audit Window

Pick a period of 2–4 weeks for the audit. Avoid major holidays or system upgrades, as those introduce noise. During this window, you will observe, measure, and document every step of the patient journey. Consistency in timing helps ensure that what you find is typical, not anomalous.

Core Workflow: How to Conduct a Friction Audit

The friction audit follows a structured sequence of observation, measurement, and prioritization. Here are the steps.

Step 1: Map the Current State

Start by documenting the actual workflow, not the intended one. Walk through each stage of the patient journey as if you were a new patient. Note every click, every form, every waiting period. Use a process mapping tool or even a whiteboard. The goal is to see the process as it truly is, with all its detours and redundancies.

Step 2: Identify Friction Points

For each step, ask: Does this step add value? Could it be removed, simplified, or automated? Common friction points include multiple logins, redundant data entry, unclear instructions, and long wait times for confirmation. Mark each friction point with a severity rating (low, medium, high) based on how often it occurs and how much time or frustration it causes.

Step 3: Measure Impact

Quantify the cost of each friction point. For example, if patients spend 3 minutes searching for the visit link, and you have 200 visits per week, that is 10 hours of patient frustration weekly. If clinicians spend 2 minutes per visit toggling between systems, that is nearly 7 hours of lost clinical time per week. These numbers make the case for change.

Step 4: Prioritize Fixes

Not all friction points are equally important. Use a simple matrix: impact vs. effort. High-impact, low-effort fixes should be done immediately. High-impact, high-effort fixes need a project plan. Low-impact items can be deferred. Focus on the top three to five friction points that, if resolved, would create the most noticeable improvement.

Step 5: Implement Changes and Monitor

Make the changes, then track the same baseline metrics over the next 4–6 weeks. Compare no-show rates, visit duration, and patient feedback. A friction audit is not a one-time event; it is a continuous improvement cycle. Schedule a follow-up audit in 6 months to catch new friction that may have emerged.

Tools, Setup, and Environment Realities

The tools you use for the audit and the environment in which telehealth operates can either amplify or reduce friction. Here is what to consider.

Process Mapping Tools

You do not need expensive software. A shared spreadsheet or a free diagramming tool like draw.io works well. The key is to create a visual representation that everyone on the team can review and edit. Avoid overly complex notation; simple flowcharts with decision points are sufficient.

Data Collection Methods

Combine quantitative data from your EHR and telehealth platform with qualitative data from patient surveys and staff interviews. Automated session logs can show drop-off points, while a short post-visit survey can capture patient frustration in their own words. Use a mix to get a complete picture.

Environment Factors

Consider the physical and digital environment. Are patients using smartphones or desktops? Do they have reliable internet? Is the telehealth platform mobile-responsive? If your patient population is older, small fonts and complex navigation create friction. Similarly, if clinicians work in a noisy environment, audio-only visits may be more practical than video. Tailor your solutions to your specific context.

Integration Realities

Friction often stems from poor integration between systems. If your telehealth platform does not sync with your EHR, every visit requires manual data entry. This is a high-impact friction point. Evaluate whether your current tools can be integrated via APIs or if you need a middleware solution. Sometimes the fix is not a new tool but better configuration of existing ones.

Variations for Different Constraints

Not every clinic has the same resources or patient demographics. Here are variations of the friction audit for different settings.

Small Independent Practices

With limited staff and budget, focus on the highest-impact friction points. You may not have the capacity for a full month-long audit. Instead, pick one patient journey stage per week. Start with scheduling, as that is often the first point of friction. Use free tools and involve the whole team in brainstorming solutions. A small practice can often move faster because fewer approvals are needed.

Large Health Systems

In a large system, friction points may vary across departments. Conduct separate audits for different specialties or clinics, then look for common patterns. Centralize the data collection using a standardized template. The challenge here is scale: changes that affect one department may require IT and administrative approval. Prioritize fixes that have the broadest impact, such as standardizing patient instructions across all departments.

Rural or Low-Bandwidth Settings

If your patient population has limited internet access, friction points around connectivity are critical. The audit should include a step where you test the platform under low-bandwidth conditions. Consider offering telephone-only visits as an alternative. Simplify the patient instructions to minimize steps. In these settings, the goal is to reduce the number of digital interactions required, not to add more features.

Pediatric or Geriatric Populations

These groups often need caregiver involvement. Map the journey for the caregiver, not just the patient. Friction may occur when the caregiver has to create a separate account or when instructions are not clear for non-native speakers. Include proxy users in your audit observations. Adjust the communication channels—text reminders may work better than email for younger caregivers, while phone calls may be necessary for older patients.

Pitfalls, Debugging, and What to Check When It Fails

Even with a careful audit, some fixes may not produce the expected results. Here are common pitfalls and how to debug them.

Pitfall: Fixing Symptoms, Not Root Causes

You might reduce the number of steps in scheduling, but if the underlying problem is that patients do not know telehealth is an option, the fix will not move the needle. Always trace a friction point back to its root cause. For example, if patients are not showing up, is it because they forgot, or because they could not find the link? A reminder system helps with forgetting, but a clearer link placement helps more if the link is buried.

Pitfall: Ignoring Staff Workflow

Patient-facing friction is often mirrored by staff-facing friction. If clinicians have to manually enter data, they may start avoiding telehealth altogether. Include staff workflow in your audit. Ask them to keep a log of every extra step they take during a telehealth visit. That log is a goldmine of friction points.

Pitfall: Overengineering Solutions

Sometimes the simplest fix is the best. A practice once spent weeks developing a custom patient portal integration, only to discover that most patients preferred a simple text message with the visit link. Start with low-tech solutions and test them before investing in complex automation. A/B testing a new reminder format can be done in a day.

What to Check When Adoption Still Lags

If you have addressed the identified friction points but adoption does not improve, revisit your assumptions. Is the telehealth service actually meeting a patient need? Perhaps patients prefer in-person visits for certain conditions, and that is not friction but preference. Also check if the fixes were implemented consistently. A new scheduling process that is only used by half the staff will not show results. Finally, consider external factors: changes in insurance coverage, competing priorities, or seasonal patterns can mask improvements.

FAQ: Common Questions About Friction Audits

This section addresses frequent questions that arise when teams start conducting friction audits.

How often should we run a friction audit?

At least once a year, or whenever you introduce a major change to your telehealth platform or workflow. Some clinics run a mini-audit quarterly, focusing on one stage of the journey each time. The key is to make it a habit, not a one-off project.

Do we need a dedicated person for this?

Not necessarily. A practice manager can allocate a few hours per week during the audit period. For larger systems, a designated quality improvement role may be justified. The important thing is that someone owns the process and follows through on fixes.

What if we find too many friction points?

That is common. Do not try to fix everything at once. Use the impact-effort matrix to select the top three. Fix those, measure results, then move to the next set. Trying to solve everything simultaneously leads to burnout and incomplete fixes.

Can we automate the audit?

Partially. Session logs and analytics can automatically identify drop-off points. But qualitative insights from staff and patients require human interaction. A fully automated audit misses the context behind the numbers. Use automation for data collection, but keep human judgment for interpretation.

How do we get patients to participate in the audit?

Keep it simple. A short post-visit survey (3–5 questions) can capture friction without burdening patients. Offer a small incentive, like entry into a gift card drawing. Explain that the feedback will help improve the service. Most patients are willing to help if they see it leads to better care.

After you complete your first friction audit, you will likely find that the biggest barriers are not technical but procedural. The audit gives you a roadmap to remove those barriers, one step at a time. Start with one patient journey stage this week, and build from there. Your telehealth adoption numbers will follow.