{
  "id": 18305099,
  "title": "Giving feedback to your manager: a guide for developers",
  "url": "https://urgent.news/2026/11/05/giving-feedback-to-your-manager-a-guide-for-developers",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-05T12:45:03.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/sascha-ms/giving-feedback-to-your-manager-a-guide-for-developers-i1o"
  },
  "original_language": "en",
  "account": "Feedback to your manager is a topic rarely discussed in the workplace. While there are guides and workshops for feedback flowing downward, upward feedback often ends in awkward conversations or anonymous surveys. As both a developer and a team lead, the author recognizes the significance of providing feedback to managers, as they may be unaware of certain issues. The article offers a simple flow, useful phrases, and tips for team leads to facilitate this process.\n\nTo give effective feedback to your manager, it should be small, timely, and private. Begin by asking about the background, then provide a concrete observation and its impact, and conclude with a suggestion. Avoid waiting to give feedback, as it tends to be more harsh when criticism has accumulated. Key insights from the article include:\n\n1. Honest upward feedback is crucial for changing behavior and improving performance.\n2. Preparing for the conversation takes only five minutes, involving bullet points on a sticky note covering the specifics of the situation, impact, background, desired outcome, and personal reasons for addressing the issue.\n3. The recommended four-step process involves asking for permission, understanding the background, describing the observation and its impact, and concluding with a shared next step.\n\nThe author emphasizes the importance of speaking up, as it benefits both the developer and the manager, leading to improved behavior and stronger working relationships.",
  "summary": "Feedback to your manager is the kind of feedback teams talk about least. For feedback that flows down, there are guides, models and workshops. Sideways, there are code reviews. But upwards? It usually ends with a sigh in the office kitchen or a checkbox in the anonymous employee survey. I care about this topic from both sides. As a developer, I know the uneasy feeling of telling my own team lead…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}