> ## Documentation Index > Fetch the complete documentation index at: https://docs.topicflow.com/llms.txt > Use this file to discover all available pages before exploring further. # Giving Feedback > How to provide effective, actionable feedback # Giving Feedback Effective feedback is specific, timely, and actionable. Here's how to give feedback that helps people grow. ## How to give feedback in Topicflow 1. Go to Feedback and click "Give Feedback" 2. Select the recipient 3. Write the feedback (see guidelines below) 4. Choose visibility (private, shared with manager, or public) 5. Optionally link to a goal, project, or meeting for context 6. Submit — the recipient receives a notification ## What makes feedback effective **Specific, not vague** ❌ "Good job on the project" ✅ "Your project plan clearly outlined milestones, dependencies, and risks, which helped the team stay aligned" ❌ "You need to communicate better" ✅ "The project update was sent 2 days after the deadline and didn't include the budget variance explanation we discussed" Specific feedback is actionable. Vague feedback is forgettable. **Timely, not delayed** Give feedback soon after the observed behavior: * Within a few days for constructive feedback * Immediately for positive feedback (or in the moment) Delayed feedback feels disconnected from the event and harder to learn from. **Balanced, not one-sided** Effective feedback includes: * What was done well (to reinforce) * What could improve (to develop) If you only give positive feedback, people don't know what to work on. If you only give constructive feedback, they don't know what to keep doing. **Actionable, not judgmental** ❌ "You're not a good communicator" ✅ "Your emails to stakeholders could include more context about why decisions were made" Focus on behaviors and actions, not character or identity. **Linked to impact** Explain why the behavior matters: * "Your detailed code reviews help junior engineers learn best practices" * "When updates are late, it delays decisions and creates uncertainty for the team" Understanding impact makes feedback more meaningful. ## When to give formal vs. informal feedback **Informal feedback (in conversation)** * Quick observations during one-on-ones * Immediate reactions to work ("This looks great") * Minor course-corrections ("Let's include more detail next time") Informal feedback happens all the time and doesn't need to be documented. **Formal feedback (documented in Topicflow)** * Significant observations that should be part of the performance record * Feedback that will be referenced in performance reviews * Patterns observed over time (not just one-off events) * 360-degree feedback from peers or stakeholders If you'd want to reference it during a performance review, make it formal. ## Giving constructive feedback Constructive feedback is harder to give but critical for growth. **Structure for constructive feedback:** 1. **Observation**: Describe what you observed (factual, not interpretive) 2. **Impact**: Explain the effect of the behavior 3. **Suggestion**: Offer a path forward **Example:** * **Observation**: "In the last two sprint planning meetings, you interrupted teammates while they were presenting their work" * **Impact**: "This made it harder for them to share their ideas fully and may discourage participation" * **Suggestion**: "Try waiting until they finish their point before jumping in with questions" **Delivery tips:** * Give constructive feedback privately (use private visibility) * Focus on recent, specific examples (not "you always...") * Assume good intent (people usually aren't trying to underperform) * Be open to their perspective (there may be context you don't have) **When constructive feedback should be immediate:** * Safety issues * Urgent misalignment with team or company values * Significant mistakes that need correction before they compound For most constructive feedback, choose a private setting (like a one-on-one). ## Giving positive feedback Positive feedback is easier to give but often neglected. Don't skip it. **Why positive feedback matters:** * Reinforces effective behaviors * Builds confidence * Makes constructive feedback easier to receive * Creates a culture of recognition **How to give meaningful positive feedback:** ❌ "Great work!" ✅ "Your demo to the customer was excellent — you anticipated their questions, explained technical concepts clearly, and made them feel heard" ❌ "You're doing well" ✅ "You've shipped 3 features this month while maintaining high code quality and helping onboard the new engineer — that's strong execution and mentorship" Specificity matters for positive feedback too. **Public vs. private positive feedback:** * **Public**: Use for accomplishments that should be celebrated broadly (shipped a major feature, demonstrated a core value, etc.) * **Private**: Use for personal growth observations or feedback that might embarrass the person if shared widely ## Requesting feedback before giving it Sometimes it's helpful to ask if someone is open to feedback before launching into it: * "I have some feedback about the presentation — is now a good time?" * "Can I share an observation about how the meeting went?" This is especially useful for constructive feedback in informal settings. For formal feedback submitted through Topicflow, the system handles delivery, so no need to ask first. ## Common mistakes when giving feedback **Sandwiching** (positive-constructive-positive) This pattern feels formulaic and people tune out the constructive part. Just be direct and balanced. **Saving feedback for reviews** If you notice something in March, don't wait until the June review to mention it. Give feedback when it's relevant. **Vague praise** "You're great" doesn't help someone know what to keep doing. **Feedback as criticism of character** Focus on actions and behaviors, not identity ("You're careless" vs. "This report had several errors"). **Giving feedback publicly that should be private** Constructive feedback should be private. Praising someone publicly is great; criticizing them publicly is harmful. ## Best practices **Make feedback a habit** Give feedback regularly (weekly or bi-weekly), not just during review cycles. **Balance positive and constructive** Aim for a ratio that's weighted toward positive, but include constructive feedback when needed. **Link feedback to goals or projects** Contextual feedback is easier to understand and act on. **Follow up on feedback** If you gave constructive feedback last month, check in on progress. **Model receiving feedback** If you want others to be open to feedback, demonstrate that you are too. ## What's next Learn how to ask for feedback Understand visibility controls Use AI to help write feedback Give feedback during one-on-ones