Urgent.News

What's breaking now, across thousands of outlets.

Tech

Ask How They Think It Went Before You Tell Them

A colleague you are helping has just run their first design review. It went fine, mostly. They talked too long at the start, missed one direct question, and handled the hardest objection well. You have your three points ready. Before you say any of them, ask a question. How do you think it went? It sounds like a soft opening. It is actually the most useful move you have, for several reasons. Most…

When a colleague you're assisting has just completed their first design review, it's helpful to approach the feedback process with a specific strategy. Instead of immediately stating your three points, start by asking them how they think the review went. This soft opening can save you from having to deliver points that they may already acknowledge themselves. Most individuals will likely say they rambled at the beginning, allowing you to agree with them and possibly add a detail without needing to go through your list.

This approach not only makes the feedback stick better as it comes from the individual's own perspective, but it also gives you insight into what they are genuinely concerned about. They might be worried about an aspect you didn't notice as prominently, and by addressing this early on, you can better tailor your feedback. If they are overly critical of themselves, your role becomes about reconciling their self-perception with the reality of the situation.

After gathering their thoughts, listen to their entire answer without interrupting. This ensures you understand their full perspective before moving on to your list of suggestions. Ask one follow-up question: "What would you do differently next time?" Once they've finished, only then add any additional points you noticed and keep them brief.

It's crucial to end by agreeing together on a single action to take next time, focusing on something they can realistically implement on the day. This method, while taking a bit more time than simply telling someone how they did, proves valuable as it fosters a feeling of growth and improvement in the individual, rather than simply grading their performance.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

A migration merged on Tuesday was never going to run in production

Two developers on the billing team each wrote a database migration in the same week. The first one, adding a column for invoice language, became V41. The second one, an index, became V42.

  • Two migrations submitted in same week by billing team developers
  • Index migration merged and deployed on Monday, column migration merged Tuesday
  • Out-of-order migration skipped due to temporary Flyway setting

Design Events That Answer Product Questions: A Practical Tracking Plan

When someone asks why signup conversion dropped, a generic button_click event rarely answers the question. The team needs to agree on where the journey starts, what counts as completion, how users are…

  • Establish shared understanding of user journey
  • Document plan connecting business questions to events
  • Functional collector resolves event meaning disagreements

More from Thursday 1 October →