Skip to main content

Best Practices

Getting the Most from Samepage

Start with Your Morning Routine

The best way to think about your first Signals: what do you want to know with your first cup of coffee? Common starting points:

  • Competitive tracking (web Signal) — What are my competitors up to?

  • What shipped this week — What's been deployed without me having to ask?

  • Communication triage — What's the top 5 things in Slack and email I need to pay attention to?

  • Customer feedback trends — What are customers saying this week?

Signal Design Tips

Be specific with instructions. The more precise your instructions, the more useful the output. Instead of "tell me about customer feedback," try "surface the top recurring feature requests from Gong calls and Intercom conversations this week, grouped by theme, with links to the original sources."
​Combine data sources for insight. Single-source Signals are useful, but cross-source Signals are powerful. For example:

  • Gong + Jira: "What features are customers asking for that aren't in our backlog?"

  • Mixpanel + Linear: "How is our V2 feature performing, and what should we build next to improve it?"

  • Slack + GitHub + Linear: "What shipped, what's in progress, and what's blocked?"

Start narrow, then expand. Begin with a focused scope (one team, one channel, one project) and expand once you're confident the Signal is useful.
​Use appropriate schedules. Not everything needs to run daily. Competitive tracking might be weekly. Bug monitoring might be daily. Match the cadence to how often the information changes and how often you'd act on it.
​

For Product Leaders and VPs

Product leaders typically get the most value from broader, cross-functional Signals:

  • "Where am I needed across the organization?"

  • "What are the biggest risks across all active workstreams?"

  • "How is the business doing — pipeline, product usage, delivery?"

  • "What decisions were made this week that I should know about?"

For Individual PMs

Individual PMs tend to benefit from more tactical, focused Signals:

  • "What bugs are stuck in my product area?"

  • "What shipped in my sprint this week?"

  • "What are customers saying about my feature?"

  • "What specs or reviews are waiting on me?"

Sharing Insights

When a Signal surfaces something valuable, share it. Currently you can take screenshots or copy content. A native share feature is coming soon. Teams often adopt Samepage organically — one person starts using it, shares a useful insight, and others want in.
​

Building Habits

The users who get the most value treat Samepage like their morning briefing:

  1. Open your Daily Signal with your morning coffee

  2. Scan the summary card for anything that needs attention

  3. Drill into Signals that flag something important

  4. Use Copilot to dig deeper or draft a response

  5. Share relevant insights with your team

Did this answer your question?