Managing a complex program's decision registry

[Tiffany Scolnic]

Hi everyone! Tiffany here and I'm a program manager at Atlassian. I would love to learn more about how you effectively manage your decision registries, especially for those of you working on complex programs with multiple workstreams. 

For example, within your decision registry: 
1. What level of decisions do you track (in other words, the altitude of the decision)

2. What information do you track within your register? 

3. How do you organize your decisions? I love the Confluence decision report but it's just one big list with no context! 

Any other best practices to share? 

[Rachael Scott]

Hi Tiffany, I was lucky to work on the original decision playbook at Atlassian when I worked there a long time ago. It's evolved since then https://www.atlassian.com/team-playbook/plays/daci of course :) but to answer your questions ... 

1. Level of information - I tracked decisions that were cross-org (especially product decisions where more than one org. or team were working), high risk or decisions that had hard deadlines.   

2. Info - I still use the play above but I adapt it for the team I'm working with so it meets their needs.  

3. I use the details from the play in a Google docs. 

Cheers, Rachael