Select a result to preview

Tiered Technical Scaffolding Model

The most common failure mode in community technology education is teaching to the middle and losing everyone else.

When a workshop assumes too much, less confident participants fall behind, nod politely, and revert to old habits the moment they're on their own. When it assumes too little, the technically confident get bored and check out — then quietly do things their own way anyway. Both outcomes leave the community more fragmented than before.

A tiered model solves this by being honest about the fact that people in any group have genuinely different starting points, different goals, and different amounts of time and motivation to invest.

The Three Tiers

Core Champions — Deep Investment

These people who go all the way in. They learn the infrastructure: encryption concepts, server administration, how to troubleshoot, how to train others, how to participate in the governance decisions that keep the systems running.

These are not necessarily the most technically experienced people in the group — they're the most motivated and trusted. They become the internal experts that others can turn to when something breaks or when a new person needs orientation.

The depth investment here matters. A community with one or two people who genuinely understand its digital infrastructure is significantly more resilient than a community where everyone knows just enough to use the apps but no one knows what's underneath.

Power Users — Functional Depth

These people who understand enough to customize, troubleshoot common problems, and support others. They don't need to run the infrastructure, but they can hold the knowledge network together.

Power users are the connective tissue. When someone in the general population has a problem, they don't need to reach a Core Champion — they reach a Power User who can probably solve it, and escalates only when necessary. This distributes the support load and prevents the burnout that comes from a small number of people holding everything.

General Users — Confident Participation

Everyone else. The goal here isn't technical mastery — it's comfort and agency. People should be able to use the tools, understand at a conceptual level why certain choices were made, and feel confident enough to ask questions and explore independently.

General Users who feel confused or excluded don't stay neutral — they create pressure to go back to familiar platforms, even ones the community has good reasons to leave.

Why This Works

It matches investment to role. Not everyone needs to know how the server works. But someone needs to. The tiered model makes that explicit and ensures the depth goes where it's needed.

It distributes the support load. Concentrated expertise creates bottlenecks and burnout. Distributed capacity — where many people can handle many problems — creates resilience.

It gives people a path. A General User who becomes curious has somewhere to go. Power Users can become Core Champions. The tiers aren't fixed — they're a scaffold, not a ceiling.

It prevents the confidence gap from becoming a power gap. In communities that don't scaffold deliberately, the technically confident end up making most of the decisions about shared digital infrastructure — not because that's what anyone chose, but because the knowledge wasn't distributed. Intentional tiering is a democratic practice.

Implementation Notes

The tier sizes are guidelines, not rules. A small organization might have one Core Champion and five Power Users. A large network might have ten Champions and fifty Power Users. The principle — match depth to role, distribute broadly — holds regardless of scale.

Tiers should be revisited as the community evolves. People move between them as interest grows or as life circumstances change the time they can invest. The model needs to be live, not a one-time designation.

Connections