Q&A
Ask questions during a wave and get answers from leadership.
Last updated
Q&A is a per-wave channel for the team to ask questions and get answers from leadership. Each wave has its own Q&A board so questions stay scoped to the work in flight rather than getting buried in a generic firehose.
Who can do what
| Action | Who |
|---|---|
| Ask a question | Anyone in the wave (members, leads, managers, admins) |
| Answer a question | Admins and wave managers |
| Upvote a question | Anyone in the wave |
| Edit a question | The asker (until answered) |
| Delete their own unanswered question | The asker |
Questions must be at least 10 characters. There is no length cap, but concise questions get answered faster.
How it works
- Open a wave → Q&A tab.
- Type your question and submit. It appears in the Unanswered list immediately, attributed to you.
- Other people in the wave can upvote your question. Upvotes sort the unanswered list — the most-asked questions float to the top, so leadership can see what the team most wants addressed.
- An admin or wave manager opens the question and posts an answer. The question moves to the Answered list, ordered by
answered_at(most recent first). - Both the question and the answer are timestamped and attributed.
What it's good for
- "What's our position on X?" — strategic clarifications during a wave
- "Why did we pick this objective over Y?" — surfacing the why behind wave OKRs
- "Are we still hiring for the role we were going to fill this wave?" — staffing or scope clarifications
- "Can a team pivot if blocked?" — process questions
- Anything where the answer is useful for the whole team to see, not just the asker
Q&A is intentionally not anonymous — questions are attributed by name. If you need anonymity (e.g. concerns about psychological safety), use Pulse Check (anonymous sentiment voting) or anonymous team health assessments instead.
Best practices
- Ask in public, not 1:1. If a question is useful for one person, it's probably useful for the whole team.
- Upvote rather than re-ask. If someone already asked your question, upvote it — that's how leadership knows which questions matter most.
- Answer publicly. Once answered, the Q&A entry becomes a record everyone can refer back to. Slack DMs disappear; Q&A persists.
- Keep answers concrete. "We'll discuss it" is rarely as useful as "Yes, we're doing X because Y."
Audit & retention
Every question creation and answer is recorded in audit_logs (actions wave_qa_question_created and wave_qa_question_answered). Q&A entries persist for the lifetime of the wave and remain visible in the wave's history afterward.
Related reading
- Waves overview — how waves frame Q&A
- Pulse Check — anonymous sentiment voting (the right channel when anonymity matters)
- Boosts — when you need help, not an answer
- Roles & Permissions — who can do what in Q&A