📎 Webclip
Have better meetings—in person or remote
Remote meetings lose many of the informal cues that make in-person discussion workable, so misunderstandings last longer and decisions take more time. The article suggests making the meeting purpose explicit, using short messages, agreeing on terminology, and ending with a clear recap of decisions and action items.
Reading notes#
- Software teams often depend on product owners and business analysts to translate business needs into features, and that handoff works better when everyone shares the same understanding.
- In-person meetings benefit from side conversations, quick clarifications, and immediate responses, while remote calls reduce those informal checks.
- A short written summary or a brief opening explanation can help people understand why the meeting exists and what needs to be achieved.
- Domain terms can mean different things to technical and non-technical people, so teams should align on the company’s definitions.
- In fast chat conversations, short messages help preserve the thread of discussion and make replies easier to follow.
- Asking simple either-or questions can narrow a topic quickly and reduce confusion.
- When a decision is being debated, it helps to restate the fundamental options and their rough cost so the group can choose faster.
- Mockups can clarify UI changes even when they are simple and informal, because vague instructions can otherwise be implemented incorrectly.
- Meetings often contain separate subtopics, and each one should end with a brief summary of the decision and next steps so errors are caught before the work is finished.
