Practical guide
Create a shared team news digest
Define the team, decisions, and delivery owner first. Use shared primary sources plus a few role-specific sections, merge overlap across functions, and assign action only where responsibility is clear.[1][2]
Why this gets difficult
A shared team digest often fails because it serves no defined owner: every function adds sources, the result grows, and generic takeaways do not connect to a team decision.[1][2]
A practical way through
- List the team's shared decisions, monitored risks, customers, competitors, and deadlines.[1][2]
- Choose a core reading list and separate optional role-specific additions.[1][2]
- Group shared stories once and state which function or owner is affected.[1][2]
- Review readership, missed events, and unused sections before adding more sources.[1][2]
An example
The situation: Product, sales, and marketing contribute separate sources about one competitor launch and receive three disconnected summaries.[1][2]
What changes: The launch becomes one shared item, with distinct product, customer, and message implications assigned to the relevant owners.[1][2]
What you get: The team sees one event and three bounded consequences instead of three news queues.[1][2]
What to watch for
Sources worth keeping
How Scottie helps
Scottie is currently centered on reader-specific briefs. A team can begin with shared priorities, but Scottie does not yet promise a full collaborative workspace.[3]