conditions
System
Applications, integrations, policies, and constraints create the conditions.
DeVon McWhite - Human-Centered Systems Technologist
I shape systems by understanding people — then prove the impact with data.
I work where technical systems, human behavior, workflows, analytics, and real-world outcomes meet. My background is healthcare and enterprise systems. My direction is human-centered systems work: make the system usable, measurable, and better.
How I See Systems
A system does not succeed because it exists. It succeeds when people adopt it, use it correctly, and produce a better outcome through it.
01
Adoption is architecture.
If people route around the system, the system has already failed in the real world.
02
Behavior drives outcomes.
The interface, workflow, incentives, and friction shape what people actually do.
03
Workflows beat features.
Features matter only when they improve the movement of work through the system.
04
Measurement is non-negotiable.
Without data, improvement is just a confident opinion.
Capability Stack
Systems
/ systemsEnterprise applications, integrations, data flow, infrastructure awareness, operational reliability.
application ecosystemsinterfaces and handoffstechnical constraints
Behavior
/ behaviorUser workflows, adoption, friction, incentives, decision paths, and real-world usage patterns.
workflow observationfriction mappingadoption loops
Analytics
/ analyticsMeasurement, dashboards, outcome tracking, optimization loops, and evidence-based decisions.
Power BI / reportingbaseline → intervention → resultoperational KPIs
Execution
/ executionWeb systems, automation, implementation, documentation, stakeholder translation, and practical delivery.
static/web systemsautomationimplementation discipline
Case Study Thinking
Define the system. Locate the human friction. Intervene. Measure the result.
Analytics
Analytics Outcome Loop
Connecting interventions to efficiency, throughput, safety, and real-world outcomes.
Problem → Friction → Intervention → Outcome
Enterprise systems
ERP / EHR Adoption Loop
Evaluating whether system changes are changing behavior or merely adding features.
Problem → Friction → Intervention → Outcome
Healthcare systems
Healthcare Workflow Friction Map
Mapping where technical steps, user behavior, and operational delays create measurable friction.
Problem → Friction → Intervention → Outcome
What I’m Building
A public lab for systems, behavior, and measurable impact.
mcwhite.dev
A base for field notes, case studies, analytics experiments, and systems thinking.
A base for field notes, case studies, analytics experiments, and systems thinking.
Current projects
Digital presence, analytics, workflow improvement, UX/HCI thinking, and operational systems notes.
Digital presence, analytics, workflow improvement, UX/HCI thinking, and operational systems notes.
Experiments
Baseline → intervention → measurement loops for real systems and human behavior.
Baseline → intervention → measurement loops for real systems and human behavior.
Direction
The trajectory is HCI-informed, analytics-driven, and grounded in operational reality.
The next phase is not about collecting labels. It is about building a clear body of work around systems people actually use, behavior that can be shaped, and outcomes that can be measured.