A thick binder or a cluttered digital folder arrives on your desk, containing the remnants of a project that was never quite completed. You are now the steward of this unfinished plan, tasked with moving it toward a conclusion. The immediate instinct is often to call a meeting to gather everyone involved and force a decision. However, the most effective way to handle an inherited mess is to first determine if a conversation is actually necessary, or if the clarity you seek can be found in a concise written update.
Assessing the pieces left behind
Before you invite anyone to a conference room, you must inventory the constraints. An inherited plan often carries hidden assumptions made by the previous lead. You need to identify which parts of the strategy are fixed and which are flexible. Look for the gaps: where did the previous person stop, and where does the logic fail to connect?
Consider the stakeholders involved. Some may have been deeply invested in the original direction, while others might have been sidelined. Your first task is to distinguish between those who hold the technical knowledge required to fix the plan and those who simply need to be informed of the new direction. Identifying this distinction prevents you from wasting the time of high-level decision-makers on granular troubleshooting.
The tradeoff of time and clarity
Every meeting carries a cost in momentum. For example, if you are trying to decide whether to pivot the project's primary objective or stick to the original, a face-to-face discussion can feel productive. Yet, meetings can sometimes obscure the very details you need to resolve, as participants may react to the energy of the room rather than the data at hand.
There is a meaningful tradeoff between the immediate feedback of a meeting and the deliberate precision of a written report. A meeting allows for rapid brainstorming, but it can also lead to consensus without true comprehension. A written update, conversely, forces the contributor to organize their thoughts and present a coherent argument, which can save you from the ambiguity of a verbal summary.
Choosing the right medium
If the decision requires weighing two distinct paths, ask the relevant experts to provide a comparison in writing first. You might ask, "What are the specific resource requirements for Option A versus Option B?" or "How does each path address the gaps identified in the previous phase?"
If the answers to these questions are clear and documented, a meeting may be unnecessary. If the written responses reveal deeper conflicts or unresolved technical questions, then you have a much more focused agenda for a live discussion. Use the written word to build the foundation, and reserve the meeting for the moment when the final choice must be made. By prioritizing a written briefing, you ensure that when you do finally sit down with your team, you are deciding on facts rather than debating interpretations.
