# Next steps
<a name="next-steps"></a>

This guide explains the differences between three common Git branching strategies: GitHub Flow, Gitflow, and Trunk. It describes their workflows in detail and also provides the advantages and disadvantages of each. The next steps are to choose one of these standard workflows for your organization. To implement one of these branching strategies, see the following:
+ [Implement a Trunk branching strategy for multi-account DevOps environments](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/implement-a-trunk-branching-strategy-for-multi-account-devops-environments.html)
+ [Implement a GitHub Flow branching strategy for multi-account DevOps environments](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/implement-a-github-flow-branching-strategy-for-multi-account-devops-environments.html)
+ [Implement a Gitflow branching strategy for multi-account DevOps environments](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/implement-a-gitflow-branching-strategy-for-multi-account-devops-environments.html)

If you are unsure where to start your team's journey to using Git and DevOps processes, we recommend picking a standard solution and testing it. Using a standard branching convention helps the team build upon existing documentation and learn what works best for them.

Don't be afraid to change your strategy if it isn't working for your organization or development teams. The needs and requirements of development teams can change over time, and there is no single, perfect solution.