When response rates across your team drop, it's usually one of three things:
They don't know what you're doing with the information they provide
Explain in your own words why you're using leep, and how this will benefit them. For example:
You don't have to wait for our 1:1. If something is blocking you on a Tuesday, tell me on Tuesday, rather than holding it for a fortnight until we next have time in the calendar.
You won't have to repeat yourself. What you share stays on the record, so you don't have to re-explain the same blocker every quarter or write the same QBR commentary twice.
Your answer carries the same weight as anyone else's. You can reply by voice or text, whenever suits you, so you're not competing for airtime in a packed stand-up or missing out because of different timezones.
Acknowledge your team's insights, even if you can't action their ideas today
Acknowledge your team's answers by responding to their Signals.
Responding to Signals
At the bottom of every Signal, you'll see the option to Ask a follow-up or to Respond. Ask a follow up will create a new leep question and will come pre-filled with context from the Signal, making it easier to drill-deeper across your team.
Respond allows you to acknowledge the Team member's thoughts with a quick pre-filled response, or you can write your own custom follow-up. Replies are sent immediately via email to your team member, and will also appear in their response summaries. Letting people know that they have been heard is the best way to continue receiving high quality responses from your team.
Review the question you've asked
The question you've asked might be too vague, or too pointed to answer honestly. Change what you're asking and watch whether the answers change. Learn more in our guide about what questions you can ask with leep.