ryanwold.net - Civic Tech, Bitcoin, and Open Government Innovation

Show

An entry

Get it down. Make it good. Share it.

Title

Text

How to assess rhythmic balanced interchange (a'la Walter Russell) in an organizational context?

Analogy: Spin sets whether mass moves inward (centripetal) or outward (centrifugal). In social systems, “spin” maps to decision velocity, information flow, and incentive gradients.

## How Spin Affects Center vs. Edge
- **Low spin + high friction:** Decisions stay in the center; edges wait. Bureaucracy thickens as control accumulates.
- **Higher spin with aligned direction:** Energy moves outward—edges get more autonomy and resources because the center cannot hold everything stable.
- **Chaotic spin (many directions):** Energy dissipates; neither center nor edge stabilizes. Coordination costs spike.
- **Stable spin with lightweight governance:** Center provides coherence (standards, shared services), while edges execute rapidly with minimal approval loops.

## Organizational Levers to Reduce Center Clustering
- **Shorten feedback loops:** Edge units ship and measure locally; center only aggregates signals, not approvals.
- **Budget envelopes to edges:** Allocate “edge envelopes” with clear bounds; center monitors outcomes, not line items.
- **Standard interfaces, minimal approvals:** Publish APIs/checklists for legal, finance, security; if the edge meets standards, no extra approvals.
- **Rotating stewards:** Rotate center roles back to the edge on a cadence to prevent permanent mass in the middle.
- **Transparency of queues:** Make request backlogs and cycle times public; long queues create pressure to decentralize capacity.
- **Outcome-based incentives:** Reward edge outcomes (customers served, incidents resolved) rather than center proximity (meetings attended).
- **Temporal caps:** Time-limit committees and working groups; if they persist, they must re-charter with explicit value.
- **Edge data ownership:** Let edge teams own their metrics and publish summaries; center curates, not hoards.

## Signals of Centripetal Creep
- Approval chains lengthen; most work waits on the same few people.
- Middle layers grow faster than edge-facing roles.
- Budgets pool centrally with slow disbursement.
- Information symmetry declines; edge teams hear news last.

## Signals of Healthy Centrifugal Energy (With Cohesion)
- Edge teams launch experiments without bespoke approvals because standards are clear.
- Resource flows track to demand peaks at the edge (regions, product lines) within set guardrails.
- Middle roles are lean and time-bound, focused on enablement, not gatekeeping.
- Shared services act like platforms with SLAs, not checkpoints.

## Practical Moves to “Spin Out” Resources
- **Edge starter kits:** Pre-approved playbooks (contracts, risk checklists, messaging) that let edges act fast.
- **Micro-budgets:** Small, fast grants to edge teams for pilots; center funds follow-on only if metrics hit.
- **Delegated authority maps:** Explicitly list decisions the edge owns vs. center; review quarterly to push more outward.
- **Shadow cost display:** Show the hidden cost of approvals (time, staff hours) to motivate slimming the middle.
- **Edge rotations:** Require managers to spend rotations on edge teams to stay grounded in customer reality.
- **Public retros:** When center intervenes, publish why and how to avoid the same bottleneck next time.

## Cautions
- Pure centrifugal force can fragment strategy; keep a light, explicit charter and shared metrics.
- Pure centripetal force can suffocate edges; watch for growing queue times and shrinking edge experimentation.
- Tune “spin speed”: too slow and nothing moves; too fast without direction and you lose coherence. Aim for stable, intentional spin with minimal friction.

Status

Series