Echoes

Echoes is all about giving you the context you need, when you need it, on a regular schedule. Ask about anything going on at work, pick a delivery schedule, and Echoes pulls data from check-ins, goals, and your activity integrations to deliver fresh answers again and again. Echoes takes time-consuming, energy-sapping context assembly off of your plate so you can focus on the work that matters.

Using Echoes

To start using Echoes, select the waveform icon in the sidebar, or press e from anywhere in Steady.

1. Start an Echo by typing a question or prompt into the field, or by picking a question from the default set. You can use simple questions like “Who’s out next week on the product team?” or use more advanced prompts like “summarize the major progress that the Design and Dev teams made last week, and include any related pull requests”.
2. Once you submit your question, Echoes will generate a preview so you can make sure the output is what you want/expect. If it’s not, make changes and select Preview (or press Enter) to generate a new one.
3. Pick a daily/weekly/bi-weekly/monthly cadence and the day and time you want answers delivered, and optionally edit the “short name” (which is displayed on answers).
4. After you save your Echo, an initial answer will be delivered to your Digest. Future answers will be delivered to your Digest according to your schedule, and you’ll also get notified when that happens.
5. All answers for an Echo are viewable in one place. Just click on the Echo in question from the list on the main Echoes view. This is also where you can edit, pause, or delete an Echo (via the ••• menu at the top of the page).

Sharing an Echo with your team

Want your team to see what an Echo tells you? Share the Echo preset. Each person who saves it gets their own answer on the same schedule, delivered to their own Digest. Answers are scoped to what each person has access to in Steady, so a teammate with access to more or fewer teams, goals, and integrations gets an answer that is right for them — not a copy of yours. This is the way to get an Echo in front of a team.

1. Select the ••• menu on the Echo and “Share Echo preset”
2. Copy the link to send directly via email or Slack/Teams to the recipient(s), or select the team member(s) to share from the dropdown.
3. When an Echo is shared directly, the recipient will receive an action item to save the Echo in Steady.

Can Echoes post answers to a Slack or Teams channel automatically?

No. Echoes don’t post answers to Slack or Microsoft Teams channels, and that’s by design. An Echo answer is generated for one person, using only the data that person has access to. Posting it to a channel would share one person’s view with people who have different access, and they would get a worse answer than the one Echoes would generate for them directly. Share the Echo preset instead (above): each teammate gets their own answer, in their Digest, with notifications, reactions, comments, and links to the source material.

If you need Echo answers in another system, they are available through the MCP server, the CLI, and the API.

Best practices

• Echoes is all about automating context gathering for information you need weekly, bi-weekly, or monthly. For a question you have right now, use Asks.
• Keep Echoes specific. Instead of a single “tell me everything that’s going on across every team” catch-all Echo, create more specific Echoes like “give me a progress report for the Design and Engineering teams”.
• Start simple. Echoes is designed so that you don’t need to be a prompt engineer to get great results.
• You have complete control over the output style. “Give a high-level progress report for the Development team” and “Give me a detailed progress report for the Development team, making sure to include summaries of all merged PRs” are both valid. You can even give more abstract instruction, like “Give me a high-level summary of what the Development team has worked on in the past week that is understandable for non-technical leadership. Focus on the product changes, not individual contributions.”

Use cases

Put 1:1 prep on autopilot

If you’re a manager with direct reports, you know exactly how much of a time sink 1:1 prep can be. Echoes makes that number zero. Ask a question like “What did Jane work on last week?”, and set the delivery time for 15 minutes before your 1:1. Echoes will deliver a complete report of absolutely everything they did — including activity from all of your tools — week after week.

Get a bird’s eye view of what shipped

Let’s say you’re an engineering manager on a busy team, and you need to keep tabs on everything that’s going out the door. Use a simple prompt like “list all the Github pull requests that were merged in the last 2 weeks” and set the cadence for every other week. Echoes will deliver a complete list of everything that’s been shipped, and include a summary of the changes for each PR. No digging through Github, no having to ask for updates.

Get alerted when goals start to slip

No manager likes to learn that their team won’t hit a goal until it’s too late. Write a prompt like “list any goals that are slipping, and summarize why”, and Echoes will review all of the goals you have access to, find the the ones that are slipping, and analyze the updates to give you a summary. Set the delivery time for every Monday, and never be caught off guard again.

Break down cross-functional silos

Let’s say you work on the marketing team. You need to know at a high level what the product team is working on, but wading through Jira takes too much time. With Echoes you can write a prompt like “give me a high-level summary of what the Design and Development teams worked on last week", and Echoes will put all the pieces together for you.

Echoes feedback

Open the ••• menu on any answer in your Digest, pick “Echoes feedback”, and choose one of the options. You can also send us a support request in-app at any time with your questions or feedback.

Data use and privacy

• No training on your data: We use enterprise-grade vendors to generate answers for Echoes, with contractual agreements to never use your data for training purposes.
• No permission leaks: Echoes can only access the data that people already have access to in Steady. There’s no risk of people seeing content they shouldn’t.
• Human-sourced inputs: All inputs are human-generated, and therefore inherently more trustworthy than systems that encourage generative input.
• Auditable answers: Answers include links to the source material used to create them. You can always audit answers to verify that they’re correct and trustworthy.

Learn more about our approach to AI