AI Practice (Wenger Reading)

In The You On AI Field Guide

The prescription runs counter to the logic of the tools themselves. AI is optimized for efficiency; the spaces required for participatory meaning-making are, by efficiency standards, wasteful. Conversations that meander, debates that do not resolve cleanly, reflections that do not produce actionable output — these are the soil in which community grows, and they are the first things eliminated under productivity pressure.

Protecting AI Practice requires institutional commitment because the pressure to fill every hour with productive activity is constant and structurally reinforced. The organization that builds AI Practice into its workflows must resist the quarterly pressure to eliminate it — the pressure that says every hour not spent producing is an hour wasted. The resistance requires understanding that production and learning are not the same thing.

Concrete implementations observed in 2024-2025 include: reserved times when AI tools are not used, even when available; protected architectural discussions conducted without AI consultation; code review sessions that explicitly examine not just correctness but community standards; sustained mentoring relationships that preserve legitimate peripheral participation; cross-community forums where practitioners from different domains encounter each other's perspectives directly.

The framework connects to the beaver's dam metaphor that anchors the You On AI Cycle. AI Practice is, in Wenger's language, the cultivation of the participatory spaces that AI-mediated work does not automatically produce. It is not withdrawal from AI but structured engagement with it that preserves what community requires.

Origin

The original AI Practice framework was proposed by researchers at UC Berkeley's Center for Information Technology Research in the Interest of Society (CITRIS) in 2024, examining patterns of AI adoption in software development organizations. The researchers observed that teams that maintained certain traditional practices — regular stand-ups, protected design time, human-only code reviews — outperformed teams that fully embraced AI-mediated workflows on measures of long-term learning and retention.

The Wenger simulation extends the framework by providing its theoretical grounding: the practices work because they preserve the participatory space required for community practice to maintain itself. The original researchers' empirical observation finds its theoretical justification in Wenger's three-decade framework.

Key Ideas

Pauses are not respites. They are the participatory spaces in which communal knowledge is generated.

Runs against efficiency pressure. The required spaces look wasteful by productivity metrics.

Requires institutional commitment. The quarterly pressure to eliminate them is constant and structural.

Enables participation to complement reification. Without them, AI reifications accumulate without the participation that would evaluate them.

Preserves the dam structure. In Orange Pill Cycle terms, AI Practice is the beaver's ongoing maintenance work applied at organizational scale.