2022-01-12 Team Management Concept

Overview

Create a method for teams, eg: programming teams, to self organize in a way that:

1. rewards those that perform well by allowing them to take on additional responsibilities
2. gives opportunity to all participants to take on more responsibility
3. allows team members to move around tasks to keep their positions interesting
4. a management team (or individual) sets task remuneration according to what they see as important for the progress of the project

Distribute remuneration according to:

1. How long a team member has been working on the project
   • base salary increases periodically by a standard amount
2. The responsibilities they currently hold
   • during the period they take on that task their salary will increase by a set amount
3. The responsibilities they have taken in the past can extend into future earnings
   • after the task period ends there a fraction of the salary increase remains and tapers off over time

Concepts

management token

Each team member receives an allocation of tokens periodically, some team members may receive more that others depending on factors such as if they are the owner or top level management, or how long a member has been part of the project

Tokens are spent voting on the performance of other team members

task re-organization

Break assignment of tasks into time period blocks, eg 1 month, each task has it's own period, so some tasks might be locked in for 3 months or 6 months.

There might be a cross over time where old team member brings the new member up to speed.

assigning tokens

At any time a member can assign their tokens to either support or oppose another team member's position, once assigned those tokens are locked.

anonymity

Token balances and assignment are anonymous. Amount of tokens distributed to each member can be public.

related tasks

Tasks can link to other tasks with a weight of how similar the task is, similarity could be type (eg managing a team) or specialized knowledge (eg graph database management) or any other reason why support for those other tasks would pass on to this task.

taking on a task

Any member can request to take any number of positions.

allocation of tasks

At a set time before the task is due to be taken over assignments are calculated, then an allocation period where members must confirm they will take on tasks allocated to them. This allows members to choose which tasks to not take on if they are assigned too many.

A member must lock in each task by the end of the allocation period or it passes down to the next member.

assigning tasks

Consider:

• how long a member has been requesting to take on the task
• the amount of tokens assigned to support/oppose that member for the task, this would weigh in for persistent tasks
• the amount of tokens assigned to support/oppose that member for related tasks