Talk it through with Mura
Library›Mura›The problem
Mura · Creativity
Knowledge + Guidance

Are we losing something because all our work happens on screens?

You watch your team open a document, and within seconds a draft appears. No one touches paper. No one holds anything. The work is fast, and everyone says fast is good, but someone always asks, quietly, whether the fastness is hiding something. What is hidden is not talent. It is friction — the small delay where a hand hesitates over a shape, where someone else leans in to look, where a mistake becomes visible before it is deleted. On screens, mistakes vanish before anyone sees them. So does the moment where two people notice the same flaw at the same time. This is not a case against screens. It is a case for noticing what a group loses when every step is frictionless — and choosing, sometimes, to slow down together on purpose.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with MuraWith others (a Pod)
Some one-to-one
Practise with peers
The group needs a clear reframe of what's actually at stake (not screens vs. purity, but friction and shared noticing), then mostly needs a structured push to practice it together.
How the two dials adapt to you →
What’s really going on

Something is lost — not the ideas, but the pause between them. A screen lets a group move from thought to output with no resistance in between. That resistance is where hands notice what eyes skip, and where real disagreement surfaces. Add friction back on purpose; you don't need to leave the screen forever.

🔒 What you’ll build togetherUnlock by starting
A movePick one stage of your process — sketching, drafting, planning — and do it on paper or with objects for one full session, together, in the same room.
A moveAfter that session, ask each person to name one thing they noticed about someone else's work that they wouldn't have caught on a shared screen.
A moveKeep the physical draft visible during the digital phase that follows it — don't file it away.
A moveBuild in one deliberate delay per project: a full day between making something and finalizing it, with no editing allowed during that gap.
A moveRotate who leads the physical session, so the practice doesn't quietly become one person's ritual instead of the group's.
PractiseThe Slow Pass · a Pod of 4 · 30 min

What changes unlock by starting

  • The team can name specifically what physical work adds, instead of feeling a vague guilt about screens
  • At least one shared discovery emerges from watching each other work by hand
  • The group builds a repeatable habit of slowing down at one stage, not all stages
  • Digital work afterward shows evidence of the physical pass — not replaced by it, but changed by it

Related problems

The same struggle, seen by other coaches
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Mura’s live plan for your version of it.