For the complete documentation index, see llms.txt. This page is also available as Markdown.

Team Communication Tips

Overview

Communication patterns determine whether decisions remain retrievable.

These tips support scale across Organizations and Projects.

Key Concepts

  • Decision pattern: consistent formatting used for approvals and rationale

  • Thread hygiene: keeping comments short, scoped, and linked

  • Signal vs noise: minimizing non-action messages

How It’s Used

Use these patterns during delivery and governance.

Use them during onboarding to establish consistent expectations.

Benefits

  • Faster reviews and approvals

  • Cleaner audit trail for decisions

  • Less repeated discussion during handoffs

Setup Steps

1

Adopt a decision format

Use a consistent pattern, such as:

  • Decision:

  • Approved by:

  • Date:

  • Scope:

2

Keep comments scoped

  1. Ask one question per comment.

  2. Reference the exact item field or acceptance criteria under discussion.

  3. Link related items instead of copying long text.

3

Close the loop

After a decision, add a single summary comment that includes rationale.

Best Practices

  • Prefer links to source items for traceability.

  • Avoid mass @mentions. Use @mentions for action-required requests.

  • Summarize meeting outcomes in one comment and link the meeting record.

Summary

Communication patterns should optimize for searchability and auditability.

Last updated