Rethinking Users as Ecosystems: My take

Rethinking Users as Ecosystems: My take

A driver holds a phone to their ear while navigating traffic, despite the car having Bluetooth audio, steering wheel controls, and a speakerphone. The technology to keep hands free already exists. Why doesn’t the ecosystem use it?

Mike Youngblood and Ben Chesluk’s framework challenges the assumption that a user is a single, coherent agent with unified goals. Instead, they propose treating the user as an ecosystem: a dynamic network of competing roles, contexts, habits, social pressures, and devices that interact in real time.

This reframing is especially illuminating in the driving-while-calling scenario, where the user is simultaneously a driver, a conversational participant, a social being, and an operator of multiple overlapping technologies, each making competing demands on attention and behavior.

🧠
Cognitive Agent
The Attentive Driver
Tap to expand
🗣️
Social Agent
The Caller
Tap to expand
📱
Tool Node
The Handheld Phone
Tap to expand
🔊
Infrastructure Node
Car Bluetooth / Speaker
Tap to expand
🎛️
Interface Node
Steering Wheel Controls
Tap to expand
⚖️
Regulatory Node
Law & Social Norms
Tap to expand
Ecosystem Tensions

Embodied Habit vs. Designed Alternatives

Phone-to-ear is a deeply trained motor habit. The body knows what to do when a call arrives.
Bluetooth and wheel controls require conscious re-routing of that habit through unfamiliar inputs.

Youngblood and Chesluk would note that ecosystems favour low-friction paths, and habit is the lowest friction of all. Design must work with the body’s memory, not against it.

Social Presence vs. Physical Safety

Holding the phone enacts a posture of relational presence. I am here, with you.
Speaker mode or Bluetooth routes the voice to the car, but the caller's voice becomes environmental, less intimate.

The ecosystem is performing a social relationship through a physical gesture, even at the cost of safety. The design question becomes: how do you preserve the social quality without the dangerous posture?

Device Autonomy vs. Contextual Awareness

The phone does not know it is in a moving vehicle. It just rings and waits to be answered.
The car's system may detect motion and prompt routing, but these systems are often siloed, not integrated.

The ecosystem’s nodes do not communicate. A connected ecosystem would share context: the phone knows it is paired, the car knows it is moving, and together they could redirect the call automatically.

User Agency vs. Protective Friction

I know what I am doing. Drivers resist systems that feel paternalistic or override their choice.
Automatic rerouting to speaker or Bluetooth could be lifesaving, but users may disable it, defeating the design.

An ecosystem-aware design must calibrate between preserving user agency and providing guardrails, nudging rather than forcing, and making the safe path feel like the natural one.

Ecosystem-Aware Design Opportunities

Contextual Auto-Routing

When the phone detects pairing with a moving vehicle’s Bluetooth, incoming calls automatically route to car audio with a brief haptic confirmation. The path of least resistance becomes the safe path.

Safety

Steering Wheel Onboarding Ritual

On first Bluetooth pairing, the car’s display walks the driver through wheel controls with a 30-second simulation, building the motor memory before the first real call. The node is activated through rehearsal, not just availability.

UX

Social Presence Signalling Without Holding

A small in-car camera or presence indicator could signal attentiveness to the caller without requiring the physical phone posture. The social signal becomes decoupled from the dangerous gesture.

UX

Graceful Decline with Auto-Reply

If a call comes in and no hands-free mode is active, the ecosystem offers a one-tap driving, will call back message, with a reminder to call back on arrival. This reduces the temptation to reach for the phone entirely.

Agency

Cross-Node Ecosystem Pairing

Phone, car, and wearable share a unified context layer. The watch knows the car is moving, nudges the wrist, and gives a subtle route to car prompt on the face. One tap confirms. The ecosystem nodes finally talk to each other.

Safety
"
The user is not a single point of interaction. They are a living system, shaped by context, habit, social role, and competing devices. Design that ignores this complexity does not serve users. It simply adds one more node to an already overwhelmed ecosystem.
Paraphrase of Youngblood and Chesluk · Rethinking Users as Ecosystems


More in this category