Decide the environments first
Agree what environments exist — commonly production, staging and development — and what each is allowed to contain. Making this explicit prevents the slow drift in which test resources quietly become load-bearing.
Name things on purpose
A naming and tagging convention agreed at the start costs nothing and makes every later question answerable: what this resource is for, who owns it, which environment it belongs to, and whether it can be deleted.
Plan for failure and for growth
Write down what happens when a component fails and what you would do if traffic doubled. Both answers influence the shape of the design, and both are much cheaper to address on paper than after the fact.


