The F.A.V.E. Framework
A methodology for what
happens after the appointment.
Applying instructional design and systems thinking to healthcare implementation. Translating clinical guidance into systems patients can realistically execute and sustain.
Origin
Why F.A.V.E. exists.
When a patient leaves a clinical encounter with a care plan, they carry that plan back into a life that may include food deserts, transportation barriers, caregiver responsibilities, variable income, cultural obligations, and environments that were never designed to support their health goals.
Between the appointment and the outcome is an implementation gap: the conditions that influence whether a recommendation can realistically become part of everyday life.
"Healthcare recommendations do not end at the appointment. The conditions that determine whether they become part of everyday life come afterward."
TALIA DRAYTON · FOUNDER
Implementation Philosophy
The body provides data.
The patient provides lived context.
Healthcare often assumes that if a recommendation is clinically sound, successful implementation should naturally follow.
F.A.V.E. begins from a different assumption: clinical recommendations do not enter a vacuum. They enter real lives shaped by schedules, resources, geography, culture, family systems, and changing circumstances.
The body provides biological feedback.
The patient provides lived context.
The clinician provides clinical expertise.
The implementation system accounts for all three.
F.A.V.E. treats implementation as a design challenge rather than a compliance challenge.
Rather than asking patients to perfectly execute static instructions, F.A.V.E. helps transform recommendations into adaptive systems that evolve alongside changing environments, feedback, capacity, and lived reality.
Interconnected, Not Hierarchical
The Instructional Design Perspective
Traditional healthcare asks:
"Did the patient follow the recommendation?"
F.A.V.E. asks:
"How should the recommendation be redesigned so the patient can successfully implement it?"
This shift changes implementation from a compliance problem into a design problem.
Why This Matters
Many healthcare frameworks are designed to produce recommendations.
F.A.V.E. is designed to produce implementation.
It applies instructional design principles so recommendations can function inside real lives, not only clinical environments.
Health Happens Somewhere
Health outcomes emerge from environments.
Recommendations do not operate in a vacuum. They enter environments, relationships, schedules, infrastructures, cultures, and constraints. F.A.V.E. maps those realities before implementation begins.
The recommendation was medically sound.
The transportation system was not.
When distance separates the patient from the recommendation's requirements, follow-through becomes structurally impossible. The gap between the care plan and the patient's geography is not a motivational failure. It is an implementation variable that was never mapped.
OBSERVED REALITY
The recommendation assumed proximity to care. The environment determined whether that assumption was true.
IMPLEMENTATION VARIABLES
"Health does not happen in clinics alone. It happens in homes, families, neighborhoods, workplaces, transportation systems, and communities."
"The question is not whether the recommendation was correct.
The question is whether it could realistically succeed in the environment where it was deployed."
Recommendations are hypotheses
Implementation occurs in environments
Environments generate constraints
Outcomes generate data
Systems must adapt
Data Over Dogma
The body is dynamic.
The data is continuous.
F.A.V.E. optimizes for learning rather than compliance with ideology.
Average recommendations are built from population-level patterns. Real people live in specific environments, cultures, schedules, physiologies, resource constraints, and life circumstances.
The question is not whether a recommendation is theoretically correct, but whether it works for this person.
Every recommendation can be treated as a hypothesis.
Every implementation attempt becomes an experiment.
Every outcome provides feedback for the next iteration.
"Your body's data matters more than average recommendations."
Recommendation
Hypothesis
Implementation
Experiment
Outcome
Feedback
Adaptation
Progress
Implementation creates information.
F.A.V.E. is designed to learn from it, refining recommendations alongside real life.
Personalized Implementation
Personalized medicine changes the recommendation.
Personalized implementation changes the outcome.
Healthcare has spent decades improving diagnostic precision.
F.A.V.E. focuses on implementation precision.
Two patients can receive the same recommendation and experience completely different outcomes because they live in different environments, cultures, schedules, support systems, physiologies, and constraints.
The recommendation matters.
But the implementation system determines whether that recommendation can survive contact with reality.
Body Data
Patient
Physician
Environment
Feedback
The body provides data.
The patient provides lived context.
The clinician provides clinical expertise.
F.A.V.E. helps all three interact.
Instructional Design Lens
Body
Provides Data
Generates biological feedback about what is and is not working.
Patient
Lived Context
Carries the daily realities and constraints the recommendation must fit within.
Physician
Clinical Expertise
Provides diagnosis, evidence-based guidance, and professional judgment.
F.A.V.E.
Translation Layer
Connects recommendations to sustainable execution through iterative design and feedback.
F.A.V.E. does not ask:
"Did the patient follow the plan?"
F.A.V.E. asks:
"What can we learn from what actually happened?"
The Four Dimensions
What F.A.V.E. stands for.
DIMENSION 1 OF 4
Functional
Aligns recommendations with daily function, capacity, and real-world routines. What does the patient actually do every day, and where does the recommendation fit? F.A.V.E. maps the functional landscape before building any implementation plan.
IMPLEMENTATION QUESTIONS
- 01
How does this recommendation fit into the patient's actual daily schedule rather than an idealized one?
- 02
Where does realistic capacity exist to insert new behaviors?
- 03
What environmental constraints limit routine changes?
Systems View
F.A.V.E. as a connected system.
Health outcomes emerge from interactions, not isolated interventions.
Each dimension influences and is influenced by the others. F.A.V.E. functions as a living system of feedback, adaptation, context, and continuous refinement rather than a linear sequence of steps.
Systems Thinking
Traditional care models often evaluate recommendations one variable at a time.
Real life does not operate that way.
Capacity, culture, environment, behavior, physiology, resources, and feedback continuously interact to shape outcomes.
The dimensions are not separate.
Functional capacity influences implementation.
Cultural context influences adherence.
Pathway flexibility influences sustainability.
System design influences whether improvement can be maintained.
Change in one dimension creates change throughout the system.
F.A.V.E. is a framework for understanding the relationships between variables that shape implementation.
The Instructional Design Principle
Learning systems succeed when they continuously adapt to feedback.
Health implementation is no different.
F.A.V.E. applies this principle by treating outcomes as information rather than judgment, allowing recommendations to evolve alongside the realities of a person's life.
Implementation creates information.
What works, what becomes difficult, and what needs adaptation all provide feedback for the next iteration.
Progress emerges from adaptation, not from perfection.
Positioning
F.A.V.E. is precise
about what it is and is not.
F.A.V.E. IS NOT
- —A diagnostic tool or clinical decision support
- —A treatment protocol or care pathway
- —A replacement for clinical judgment
- —A generic coaching or wellness program
- —A patient education handout or curriculum
- —An EHR or care management software
- —A one-size-fits-all behavioral intervention
F.A.V.E. IS
- →A patient implementation methodology
- →A care-plan translation layer
- →A clinic workflow support framework
- →A structure for improving between-visit execution
- →A system for mapping and reducing implementation barriers
Next Step
Where is implementation becoming harder in your care environment?
Start with the F.A.V.E. diagnostic to identify where implementation may deserve a closer look and give Drayton Health Systems context about your care environment.