Heirloom LogoHeirloom

Choose Together, Build Together: How Heirloom’s Shared-Ownership Cycle Works

A practical guide to our governance loop (Proposal → Vote → Tasks → Rewards) and how it turns ideas into shipped work without slowing teams down.

Brandon R.By Brandon Reid
Flow diagram showing Proposal → Vote → Tasks → Rewards

Great teams don’t just divide the upside, they decide the path together. At Heirloom, we use a simple loop to turn community ideas into shipped work while keeping incentives and voice aligned: Proposal → Vote → Tasks → Rewards. Under the hood, it blends lessons from employee-ownership research (shared upside improves engagement and resilience), high-involvement management findings (participation raises performance), and commons governance (clear rules, transparent monitoring) for the messy early stage where roles and information change fast.

Companion read: Curious why we take this approach? See Build Together, Own Together: Why Heirloom Uses Dynamic Equity.

Why a decision cycle at all?

Without a shared process, early projects drift into loudest-voice wins, founders over-centralize, and contributors disengage. A light, repeatable cycle gives contributors voice (anyone can surface opportunities), visibility (preferences and tradeoffs are clear), and value (decisions become tasks; tasks earn rewards). The pattern matches the research base on employee ownership: broad-based participation and upside are associated with stronger performance and resilience.

1) Proposal: frame the decision, not just the idea

A good proposal sets the table for a high-quality vote: the problem and context, options with tradeoffs (including “do nothing”), budget and timeline, success criteria, and dependencies. We prefer small, testable proposals - momentum stays high and outcomes are legible. This echoes commons best practices inspired by Elinor Ostrom’s principles: clear boundaries, locally fitted rules, and transparent monitoring.

2) Vote: pick the rule that fits the decision

Not every decision deserves the same vote. We support several patterns:

  • One-person-one-vote for culture and people matters, so “wealth ≠ voice.”
  • Stake-weighted when tradeoffs track contribution or budget, with quorum and pass-rate guardrails.
  • Delegation for speed - lend your vote to someone you trust, revoke anytime.
  • Cooling-off & transparency windows so big changes aren’t rushed.

(Analogs in modern tooling: Snapshot and Aragon.)

3) Tasks: turn “yes” into shipped work

A passed vote auto-generates a work package: tasks with acceptance criteria, clear owners and due dates, and traceability back to the proposal. Lightweight check-ins keep the loop warm without micromanagement. This is where trust compounds and decisions lead to visible progress.

4) Rewards: close the loop with value

Delivered and accepted tasks earn dynamic-equity points. Points are weighted by role, complexity, and outcomes, then convert to formal equity at predefined “hardening” events (incorporation, revenue milestones, funding). Guardrails - minimum/maximum allocations, cliffs/vesting, buy-back/off-ramps, public ledgers - keep flexibility compatible with trust. This mirrors findings summarized in Shared Capitalism at Work and the NCEO’s research findings.

Why this speeds you up (not down)

Small proposals, short voting windows, and automatic tasking keep velocity high. Because preferences are visible, you spend less time politicking and more time building. The DAO world learned this at scale - see frameworks like Snapshot and Aragon - and we’ve tailored those mechanics for product teams that don’t need (or want) crypto overhead.

Practicing what we preach: community proposals

We run Heirloom Community Proposals for our own roadmap. Community members can suggest features and policy tweaks and vote on what they’d like to see on Heirloom. When a proposal passes, we scope it, ship it, and acknowledge contributors in our changelog (with rewards when appropriate). For a broader industry push on broad-based ownership in mature companies, see Ownership Works’ 2024 Impact Report.

When to split decisions - and when not to

Keep proposals tight (one theme per vote). If a question bundles multiple tradeoffs, split it so voters can express real preferences. Tightly coupled changes, however, should move together to avoid misaligned fragments.

The culture this creates

Over time the cycle normalizes three habits: clarity beats charisma (evidence over vibes), participation is power (show up, shape outcomes), and accountability compounds (public decisions with visible follow-through build a reputation flywheel). These patterns are consistent with the employee-ownership literature.

Heirloom provides collaborative tools and templates to help teams organize decisions, track work, and capture credit. Nothing on this page is legal advice. If you choose to incorporate or adopt specific ownership plans, consult counsel; we provide exports that make formalization easier.

Sources & Further Reading

Keywords: governance, proposals, voting, shared ownership, dynamic equity, employee ownership.
Author

Written by Brandon Reid

Making the first step feel a little easier.

More to explore

Keep reading to go deeper on shared ownership and collaborative building.

Collaborate with brilliant builders.
Own what you ship.

Dynamic equity makes collaboration fair by default. Apply to the next batch

Applications close in
09Days
13Hrs
07Min
37Sec