Effective teams need a charter to understand who they are and what they do. Without this, they increase the risk that they thrash around trying to do all things

Effective teams need a charter to understand who they are and what they do. Without this, they increase the risk that they thrash around trying to do all things for all people, or fail to take advantage of their unique talents and opportunities. This post gives the AWS Rust team's perspective about their charter, which is not at all vacuous. They are sharing with the community to seek earnest validation and feedback.