Help CenterA big part of using teamdecoder as a team is what working with teamdecoder does to the team. The fact that a team regularly discusses HOW they want to work, additionally to the otherwise common talks about the WHAT, improves transparency and trust.
And to encourage this and make it a routine, we recommend the follwing governance setup:
- Usually there is 1 team member who functions as "Governance Moderator" (GM). We recommend this to be the team leader.
- This role (which is also a pre-created generic role inside teamdecoder) is the only person who has the teamdecoder login and who can make changes.
- And this role organizes a "Governance Meeting" aka "Campfire Meeting" where all team members can come and request changes inside teamdecoder. When no one vetoes, the change can be made and is law from then on until the next change request.
- We recommend to start a "Governance list" somewhere (e.g. Intranet, Microsoft Teams a Google Doc, Jira, etc.) where everyone has access, where people can list their change requests. In the meeting the GM would then lead throught topics on this list - we are working on a feedback function that will allow users to send messaged to the GM.
- Sometimes it makes sense to also give the teamdecoder login to circle and project leads so they can work on the admin part of the circles and projects themselves. That is usually nothing the whole team needs to agree on. We are also working on a feature where different teams can have different admins.
You can find many articles on how rolebased work improves team health in our blog.