JobProtocol All articles
Treasury

Five Signers, No Manager: How DAOs Hand Out Promotions Without an HR Department

JobProtocol

At a normal company, the annual review is a meeting. Someone with a title sits across from you, reads a document you're not allowed to see, and tells you what you're worth. In a lot of decentralized organizations, that meeting has been replaced by a forum post, a rubric nobody remembers writing, and a transaction that either clears or doesn't.

It works better than you'd expect. It also fails in ways that a conventional HR department would have caught.

The review that arrives as a Snapshot proposal

Picture the rhythm inside a mid-sized protocol with roughly forty regular contributors and no CEO. Once a quarter, the ops multisig publishes a compensation review. Contributor councils — usually three to seven people elected or grandfathered into the role — submit written evaluations for everyone in their workstream. Below a certain threshold, say a $15,000 annual increase, the change executes from the ops multisig on a 3-of-5 signature. Above it, the increase gets bundled into a budget proposal and goes to token holders.

For the individual contributor, this looks uncannily like a normal process: a form, a self-assessment, a decision, a number. The difference is that no single person is accountable for the outcome, and the reasoning may only exist as a paragraph in a public thread.

Three architectures, three failure modes

The mechanics vary, and the variation matters more than people admit.

The delegated council. A small group holds review authority for a workstream. Fast, coherent, and dependent on whether that group likes you. Councils drift toward insularity because the people who join them are the people who were already visible.

The multisig signers. Review authority sits with whoever controls the treasury keys. This is efficient and quietly concentrates power: the same five people who approve wire transfers now approve your raise.

The token vote. The broadest and least personal option. It's also the one where a contributor's compensation becomes a proxy fight between delegates who have never read your work.

When your reviewer is also your competitor

Here's the structural problem with decentralized review. The people evaluating your work are frequently bidding for the same quarterly budget you're bidding for. A council member who runs a competing workstream has a direct financial interest in your request looking expensive.

Good DAOs handle this with recusal rules — a reviewer with a conflicting workstream abstains, and the abstention is recorded. Most don't. If your review process has no recusal mechanism, assume conflicts are being resolved informally, which means they're being resolved in favor of whoever is more embedded.

Token-weighted feedback adds a second distortion. Where reputation scores or attestation counts feed into compensation decisions, popularity becomes a currency. Loud contributors accumulate attestations; quiet ones who ship the unglamorous infrastructure don't. That's not corruption, exactly. It's just the same halo effect you'd find in any office, running on a public ledger where it can never be forgotten and never be corrected.

Documenting impact when nobody owns your career

Since no manager is tracking your trajectory, you have to be your own institutional memory. A few practices that consistently pay off:

Keep an impact ledger. Not a resume — a running file with links. Merged PRs, shipped features, incidents you resolved, proposals you drafted, onboarding docs you wrote. Date everything. Six months from now, when a reviewer who joined last month is deciding your raise, that file is your entire case.

Publish weekly, publicly. A short weekly update in your workstream channel does double duty: it's coordination, and it's an audit trail that any future reviewer can search.

Ask for attestations in writing. If a peer or a protocol lead says your work was valuable, ask them to put it somewhere permanent — a forum reply, an on-chain attestation, a signed note. Verbal praise evaporates when a review cycle starts.

Get your scope in writing at the start of each quarter. The most common review dispute isn't 'you did badly.' It's 'that wasn't your job.' Written scope settles it before it starts.

Learn who signs. Find out whether your compensation decision goes through a multisig, a council vote, or a token proposal — and then talk to the people in that channel, not to a manager who doesn't exist.

What a healthy decentralized review looks like

You can tell a functional process from a dysfunctional one by a handful of signals: a published rubric with actual criteria, a fixed cadence so reviews aren't triggered by personal annoyance, a written rationale when a request is denied, an appeal path that doesn't require knowing the right person, and a conflict-of-interest disclosure requirement that's enforced.

None of that is exotic. It's just HR, rebuilt in public, without the department. The organizations that get it right tend to be the ones that admit something uncomfortable: decentralized doesn't mean structureless. It means the structure is visible — including to you.

All Articles

Related Articles

Read the Multisig, Not the Manifesto: A Treasury Due Diligence Checklist

Read the Multisig, Not the Manifesto: A Treasury Due Diligence Checklist

Foundations, DUNAs, and Cayman Wrappers: Who Actually Signs Your Offer in Web3?

Foundations, DUNAs, and Cayman Wrappers: Who Actually Signs Your Offer in Web3?

Audition, Don't Interview: The Rise of Paid Trial Bounties in Web3 Hiring

Audition, Don't Interview: The Rise of Paid Trial Bounties in Web3 Hiring