Speculative design asks us to imagine products and systems that don't yet exist, not as science fiction exercises, but as vehicles for critical inquiry. During my master's research, I explored this methodology through two projects: a self-health monitoring patch and a noise awareness device. Both were designed to provoke discussion about near-future interactions between humans and emerging technology.

Why Speculative Design Matters for Health Tech

Health technology is advancing faster than our ethical and design frameworks can keep up. Wearable biosensors, AI diagnostics, and ambient health monitoring are technically feasible today — but how should they behave? What data should they collect? Who should they report to?

Speculative design creates a safe space to wrestle with these questions before the technology is deployed. By building provocative prototypes and presenting them to users, we can surface concerns, preferences, and values that traditional user research might not capture.

The Framework

From my two speculative design projects and a review of existing literature, I've distilled a lightweight framework:

The goal isn't to predict the future — it's to use the future as a tool for thinking about the present.

Lessons from the Self-Health Monitoring Patch

The patch project imagined a thin, skin-adhesive device that continuously monitors vital signs and sends alerts to both the wearer and their healthcare provider. During provocation sessions, participants raised concerns I hadn't anticipated: data ownership ("Who sees my heart rate data at 3am?"), social stigma ("Will people know I'm wearing a health monitor?"), and dependency ("What if I can't trust my own body without the device?").

These insights directly shaped my recommendations for future wearable health devices — particularly around user control and transparency.

Applying This to Your Own Work

You don't need a research lab to practice speculative design. Start with a question: "What happens when [emerging technology] is applied to [everyday context]?" Build a low-fidelity prototype — even a storyboard works — and show it to five people. The conversations that follow will be more valuable than any feature spec.