Skip to main content

Compensation Model

Purpose (Why)

So far, Samara only dealt with a single type of compensation, called contribution:

  • historical contributions (recorded in Google sheets)
  • personal contributions (work done on the side)
  • external contributions (financial or knowledge transfers)
  • quest-based contributions (Hypha quests)

In addition, Samara has developed an interim compensation model:

  • define HUSD need in advance (based on fiat needs)
  • propose commitment (%)
  • do the Co-Ev process
  • update commitment
  • use 3 salary bands related with contribution (%): 70k for 1%- 49% contribution, 90k for 50%-79% contribution, 110k for >80% contribution
  • HUSD amount pay and the rest in Samara tokens with 1.8 multiplier

The purpose of this policy is (1) to simplify and improve the above interim model, (2) to anchor the compensation model on the approach outlined in The Chronicles of Samara  and (3) to better integrate 4 key components of compensation:

  1. Mindshare (how much of your life you give to Samara)
  2. Complexity (the anticipated intensity or difficulty of the work you do for Samara)
  3. Value (the actual value your contribution brings to the organization)
  4. Bonus (the go-above-and-beyond recognition as a generic multiplier added on top)

To simplify the above interim model, we need to reconsider:

  • pay out HUSD per collective schedule, not per individual need
  • uncouple commitment from contribution and salary bands

To integrate the 4 key components, we need to revisit the compensation model and start at the bottom:

  1. Dividing mindshare into quests, contributions and roles
  2. Encoding complexity a priori through the allocation of the funding, expenses and salaries
  3. Decoding value a posteriori through the contribution level, proof of work and role archetypes (+OKRs)
  4. Adding a bonus through the membership level and badge archetypes

Note that complexity is tied to a role-assignment within the context of a circle (e.g. a senior front-end developer for the DHO sub-circle in Hypha) and the value is decoded and voted on in an organizational context. 

Implementation (How)

Let's try to spell out a possible new approach for Samara:

Goals (TBD)

  • try to move the salary discussions off the table so that they are no longer front-and-center (this is a major source of contention in any organization)
  • try to stay away from any competitive measures (that lead to comparisons, e.g. my experience vs yours, my commitment vs. yours, my needs vs yours etc)
  • find a compensation model that is (1) fair and equitable for members, (2) allows for a personal growth pattern, and (3) aligns with the goals of the organization

ModelKey principles (TBD)

  • everyone has the freedom to choose their distribution of mindshare
    • the overall distribution across all activities cannot exceed 100%
    • you are encouraged to adjust your commitment levels accordingly
    • there is no connection between level of commitment and complexity
  • the circle (pod) decides what the level of complexity is for a given task/quest/role ("job")
    • intense or difficult tasks/quests/roles are rewarded higher
    • simple or repetitive tasks/quests/roles are rewarded lower
    • alternatively, all tasks/quests/roles are rewarded equally
  • the organization decides if the task/quest/role has contributed value to Samara or not
    • tasks are proposed and voted on by each member 
    • quests are co-evaluated for each milestone and member
    • roles (assignments) are evaluated and re-confirmed every 3 months 
  • the salary is based on a compound token model
    • any work activity will earn 2x SVOICE in USD equivalent terms (investment activity is 1x)1 
    • long-term contributors are expected to earn proportionally more SAMARA tokens ("deferring", "having skin in the game") Irina: Not clear what refers to
    • incentives for SAMARESAMARA tokens include a 1.8 multiplier that degrades over time

Bands

Universal, Consistent & committed ‘Work/Play-Pay’ (B1) 
  • $70k annual salary 
  • Relatively Low Complexity - focused on doing - minimal time sensing and on calls - maximum time DOING!
  • 60/20/20 - Doing / Sensing / Learning (within one circle)
Mid Complexity Pay (B2):
  • $90k
  • Requires much more headspace and managing overlapping topics, issues, information etc. Supporting multiple individuals. 
  • 40/40/20 - Doing / Cultivating (Sensing & Coordinating) with multiple individuals & circles / Learning 
Max Complexity/Intensity Pay (B3):
  • 110k
  • Supporting and serving multiple circles, individuals, and the movement effectively. 
  • 20/60/20 - Doing / Cultivating (Sensing & Coordinating) with multiple circles & organizations / Learning

Compensation models for Samara 

1.  Standard abundance compensation, a model that benefits of the abundance of the Samara token to compensate for the work done within Samara, permanently available for Samara members.

  • 100% Samara tokens, adding the multiplier in place

2. Diverse compensation, a model that includes other available tokens in the compensation when these tokens are available (like for example HUSD, Liquid Seeds etc.). This model is available whenever Samara has a diversity of tokens and Samara members decide to use those tokens as part of compensating member's contributions.

This model will be updated at the beginning of each quest period or whenever necessary, reflecting the available tokens.

  • Contributors can choose a HUSD component up to 30% of their total contribution
  • Contributors can choose LSeeds component within a total of HUSD + Seeds being up to 50% of their total contribution
  • The balance to 100% is made by Samara tokens, adding the multiplier in place

3. Default model for in between Hypha quests. The purpose of this model is to continue supporting the long term Samara contributors with the fiat needed to cover life expenses while being able to continue to contribute to Samara. Applicable to members with at least 3 months of past contributions at a commitment higher than 70%, based on initial request of covering the HUSD needs in periods between quests.

Note: For the period between quests starting with April 20, 2021 (not having a long history of past contributions behind) this model is applicable for past contributions higher than 50% in the 2 previous distinct evaluated periods (March 1 - March 12 and March 13 - April 19).

  • define HUSD need in advance (based on fiat needs)
  • propose commitment (%)
  • do the Co-Ev process
  • update commitment
  • use 3 salary bands related with contribution (%): 70k for 1%- 49% contribution, 90k for 50%-79% contribution, 110k for >80% contribution
  • HUSD amount pay and the rest in Samara tokens with the multiplier in place

Examples (What)

  1. Jeff joins Samara as a new member and goes on an onboarding quest
  2. After completion, he earns an Apprentice badge, some SVOICE and is looking for a long-term engagement
  3. The XYZ circle has a new job posting at complexity level "B3" and archetype "building"
  4. Jeff applies and is accepted into the new role and starts his new assignment
  5. Each week month he claims to pre-defined tokens for the B3-Builder rolerole 
  6. At the end of each quarter (or 3 months period) he documents progress in OKRs

 

1 This differs from the book, I believe Samara investors want to have a voice in decisions, that's why they invest, but that voice is lower than that for existing members enacting roles

Irina: I have some concerns of giving voice to investors. LEt'Let's discuss.

 

 

Back to top