8.5 Establishing teamdecoder as Role Database

If you introduce teamdecoder gradually, consistently document every workshop result there, get people used to reports and feedback, and hold the Campfire meeting regularly, an understanding will slowly establish itself that teamdecoder is NOW THE database for all roles and activities.

The team begins to discuss all changes in the Campfire and insists that these changes be recorded in teamdecoder. A shared understanding spreads that what is in the td is “set,” and if it’s not there, it’s not “official.” This is good for us — because it means the team has gotten used to operationalizing changes with td.

Still, it often remains our responsibility in daily work to remind people to document this or that now in teamdecoder. This then encourages discussion and fosters a shared understanding.

It is our role as consultants to help the team establish td as the roles database, where everything related to the work and way of working is recorded.