FUNDAMENTALS · EMBODIED & POETIC INTERACTIONS
Most technology is designed to disappear. The best interface, the common wisdom goes, is the one you don't notice — the one that gets out of the way so you can focus on the task. This section starts from a different premise: that the body noticing, hesitating, and interpreting is not a failure of design. It can be the point.
This page is a primer. It doesn't replace the Manifesto or the Frameworks page — it exists to prepare you for them, gathering the core ideas in one place before you go deeper into either the argument or the analytical tools.
For a long time, cognitive science treated the mind like software running on the brain's hardware — thinking happened "in there," and the body was just an input/output device that carried commands to and from the world. Embodied cognition rejects that picture. It argues that how we think is shaped by having the particular body we have — its size, its senses, its capacity to move, reach, and manipulate.
You don't just use your hands to execute decisions your brain already made. Reaching, gripping, and gesturing are part of how you figure things out. Architects sketch to think, not just to record a finished thought. Dancers rehearse a phrase to understand a piece of music their ears alone couldn't parse. The body is not downstream of cognition — it's inside the loop.
Embodied cognition says thinking is not confined to the skull. It happens through the body's movement, through the tools we use, and through the environment we're embedded in. Interaction designers who take this seriously stop asking only "what should the screen say?" and start asking "what should the body do?"
This platform organizes the idea into four overlapping dimensions — Embodied, Embedded, Enactive, Extended, known as the 4E framework. Rather than repeat that material here, this page assumes you'll read the full breakdown, with design questions for each dimension, on the Frameworks page. What matters for now is the shift in posture: cognition is not a private event behind the eyes. It is something bodies do, in places, with things, over time.
"Poetic" here doesn't mean pretty, whimsical, or covered in metaphorical flourishes. It names a specific design commitment: leave room for the person using this to make their own meaning out of it.
Think about how a poem works compared to an instruction manual. A manual tries to eliminate ambiguity — one meaning, one correct reading, no room for confusion. A poem does the opposite. It compresses meaning, leaves gaps, and trusts the reader to bring something of themselves to fill them in. Two people can read the same poem and walk away with different, equally valid, understandings. That's not the poem failing. That's the poem working.
Poetic interaction design borrows this posture for technology. Instead of a product that tells you exactly what to do and precisely what it means, a poetic object or interface opens a space — for interpretation, for personal appropriation, for the user to discover meaning rather than receive it pre-packaged.
This isn't a rejection of clarity everywhere, all the time — a fire alarm should not be ambiguous. It's a claim that most everyday technology has been designed with a manual's certainty when it could have been designed with a poem's openness, and that something valuable — surprise, ownership, personal meaning — gets lost in that overcorrection toward clarity.
The Manifesto closes with seven principles for poetic interaction. They're worth previewing here because they'll recur throughout this section, especially in the Activities:
It helps to lay the two postures side by side. Neither is universally "better" — a pacemaker should be relentlessly functional; a museum installation probably shouldn't be. But most consumer technology defaults to the functional column without ever asking whether it should, and this platform exists to make that a conscious choice rather than an unexamined habit.
Notice that these two columns aren't a hierarchy of quality — they're a hierarchy of intent. A well-designed to-do list app belongs firmly in the functional column, and that's correct: you want it fast, predictable, and forgettable. A meditative object, a game controller, or an artwork that lives on a gallery wall has a much stronger claim to the second column. Part of the designer's job, in this framing, is simply deciding — deliberately — which column a given piece of work belongs in, rather than defaulting to "functional" because that's what the tools and templates assume.
Consider a kitchen timer. The functional version is a countdown on a phone screen: a number ticking toward zero, an alarm at the end. It works. It is also completely interchangeable with every other countdown timer that has ever existed — nothing about using it is particular to you.
Now consider an hourglass. It tells you less — no precise digit, just a diminishing pile of sand. But it also tells you more: you can see time passing, not just read a number representing it. You can feel the weight of "almost done" in a way a countdown number doesn't convey. It leaves room to notice, to watch, to be present with the passage of time rather than simply waiting for a number to hit zero. Neither is "better" for every situation — but the hourglass is doing something the digital countdown structurally cannot, and that difference is the entire subject of this section of the site.
This page has stayed intentionally broad. The rest of the Embodied & Poetic Interactions section builds on these two ideas — embodied cognition and poetic openness — in different directions: rigorous analysis, hands-on practice, critical theory, and tools for making things yourself.
Nothing here asks you to reject clarity, usability, or good functional design outright. It asks you to notice that "make it frictionless" is a choice, not a law of nature — and to consider what becomes possible when you choose otherwise, on purpose, for the right project.