/
Best Practices
Write updates that inform, engage, and build a culture of transparency. These guidelines will help your team get the most out of Project Feed.
Writing effective updates
Lead with the most important information
Put the key takeaway in your title and first sentence. Busy teammates should understand the gist without reading the full post.
✓ “Launched dark mode — available to all users today”
✗ “After many weeks of work, I wanted to share something...”
Be specific about outcomes
Include concrete details like numbers, dates, and next steps. Vague updates create confusion and don't give readers a clear picture of impact.
✓ “Reduced page load time by 40% (3.2s → 1.9s)”
✗ “Made some performance improvements”
Use clear, scannable structure
Break up long posts with headers, bullet points, and short paragraphs. Walls of text get skipped. Bold your key points so readers can skim effectively.
Visual communication
Add screenshots and visuals
A picture is worth a thousand words. Show, don't just tell — especially for UI changes and data. Annotated screenshots with arrows pointing to changes are far more effective than text descriptions.
Use before/after comparisons
When showing improvements, include the previous state for context. Side-by-side comparison images highlight the impact of your work much better than only showing the new version.
Record quick videos for complex changes
For flows or interactions, a 30-second screen recording explains better than paragraphs of text. Project Feed supports embedded video playback — just drag your recording into the editor.
Timing and frequency
Post updates as work completes
Don't wait until the end of a project to share. Frequent small updates are more valuable than rare comprehensive ones. Share progress weekly or when milestones are reached.
Batch related micro-updates
If you have several tiny updates, combine them into one post. Too many small posts create noise. A single “This week: fixed 3 bugs and improved search” is better than three separate posts about minor fixes.
Consider your audience's timezone
Post during work hours when your team is active. Important announcements deserve prime visibility — avoid posting late at night or on weekends.
Engagement and culture
Acknowledge others' work
React to and comment on teammates' posts. Building a culture of recognition starts with you. A quick reaction goes a long way.
Ask for feedback explicitly
If you want input, ask directly. People are more likely to respond when invited. End your post with a specific question like “Looking for feedback on the copy — what do you think?”
Credit collaborators
Mention teammates who contributed using @mentions. It builds goodwill, gives credit where due, and helps others understand who worked on what.
Common mistakes to avoid
- Jargon overload — Using acronyms and technical terms without explanation excludes teammates
- No context — Assuming everyone knows the background. New team members will be lost
- Ghost posting— Posting but never engaging with others. It's a conversation, not a broadcast
- Overcommunicating— Posting every tiny detail. Some things don't need an announcement