CRAFTING TRUST

How digital craft communities negotiate trust in everyday technology

BACKGROUND & QUESTION

Across roughly eighteen months of research for Styling the Self, I read and analyzed how people describe their relationship to hobbies, self-care routines, and everyday devices in explicitly ethical or identity-laden terms: menswear and heritage-object collectors, home baristas and fermenters, amateur woodworkers and repair enthusiasts, and members of online "slow tech" and digital minimalism communities, as they discuss these relationships across forums, YouTube channels and their comment sections, and community message boards. The animating question, reframed for a product context: when does technology feel like it supports someone's sense of craft, care, and control — and when does it feel like it is quietly taking those things away?

METHOD

  • Close reading and discourse analysis of forum threads, YouTube videos and comment sections, and subreddit discussions across three community types — menswear/heritage-object collectors, home craft and fermentation communities, and "slow tech"/digital minimalism communities — conducted over roughly nine months.

  • Comparative reading of community-authored material (FAQs, wikis, recurring threads) alongside press coverage of these communities, tracking how members articulated trust, skill, and value in their own language rather than in response to researcher-posed questions.

  • Thematic coding in NVivo or even Notion, developed iteratively against the discourse data, then triangulated across the three communities to test which themes were genuinely shared rather than niche.

  • Reading conducted against Richard Sennett's sociology of craft and Etienne Wenger's concept of "communities of practice."

THREE THEMES

  1. Visible effort is a value signal, not friction to design away

    People repeatedly distinguished between tools that let them see and feel their own skill accumulating (a cast-iron pan seasoning over years, a woodworking joint learned through failure) and tools that quietly performed the task for them. The former were described with pride and attachment; the latter, even when more "efficient," were often described as faintly deskilling. For technology in the home, this suggests real tension between automation framed as convenience and automation experienced as erasure of competence.

  2. Trust is built through legibility, not reassurance copy

    Expressions of trust in a device tracked closely with how legible its behavior was — could a person build an accurate mental model of what it was doing and why — rather than with explicit privacy or safety messaging. Devices that behaved predictably, even when limited, were described more positively than more "capable" devices whose behavior felt opaque or occasionally surprising.

  3. Ritual repurposes technology to mark boundaries, not just to perform tasks

    People described adopting ordinary devices — a kitchen timer, a smart speaker, a basic fitness tracker — into small daily rituals that had little to do with the device's advertised function: marking the start or end of a workday, creating a pause before a meal, signaling to family members that focus time had begun. These informal repurposings were a recurring, almost invisible source of attachment in the discourse, and a design implication that runs somewhat against feature-maximization logic.

TWO PERSONAS

*The following composites are built from clusters of forum posts, comments, and video discussion that shared overlapping attitudes; they are not individual real people, and are presented here as an example of how I would package this kind of reading into designer-facing artifacts.

“The Custodian” — Priya, 34, London

Values competence and continuity over convenience

RELATIONSHIP TO TECH Owns capable devices but deliberately uses them at a fraction of their functionality — she wants a timer, not a platform.

Distrusts features she didn't ask for.

WHAT EARNS TRUST Predictability and reversibility. She wants to be able to explain, to herself, what a device just did and why.

DESIGN PROVOCATION Where could a device make its default behavior narratable in one sentence, rather than impressive in a spec sheet?

“The Ritualist” — Danny, 41, Manchester

Repurposes ordinary tools into markers of everyday meaning

RELATIONSHIP TO TECH Uses mainstream, unremarkable devices, but has built small personal rituals around them (a specific speaker command to end the workday, a fitness tracker check-in as a wind-down cue).

WHAT EARNS TRUST Consistency over time — a ritual breaks if the device's behavior drifts or gets "improved" without warning.

DESIGN PROVOCATION How might a product protect a user's informal rituals across software updates, rather than optimizing them away?

WHAT THIS COULD MEAN FOR A DEVICES & FUTURES TEAM

  1. Treat legibility as a design metric alongside capability — can a user articulate what the device just did and why, in their own words?

  2. Audit new automation features for deskilling risk, not just for time saved: does this remove a moment of visible competence that users valued?

  3. Look for the informal rituals users have already built around existing devices before shipping updates, and protect continuity of behavior as a design constraint, not an afterthought.

  4. Consider a research stream that treats "restraint" — deliberately limited or narrowed device use — as a legitimate user segment worth designing for, not a failure to adopt full functionality.