Guidance for shared judgment and best practice.
Guidance is where teams share judgment, best practices, and workflow notes that are useful but not enforced. The boundary between guidance and rules stays obvious.
The page is useful when a team wants shared wisdom without turning it into a policy engine.
Guidance is the place for judgment, not enforcement.
It lets teams share how they prefer work to be done without turning every preference into a hard rule.
A recommendation that helps people move faster with less friction.
Lessons learned from one team that can help another.
A note that is meaningful in one workspace but not everywhere.
Useful advice keeps tasks moving forward.
Keep guidance close to the work and separate from policy.
Keep the boundary between 'recommended' and 'required' clear.
Start with the one thing that tends to go wrong repeatedly.
Let teams publish useful advice across scopes without over-authorizing it.
Project guidance can override global habits when needed.
Guidance can be curated without following a strict approval workflow.