Reply With a Meeting, A DRI signal your agenda can’t ignore
How your calendar exposes DRI quality and delivery risk
In a previous article on the Meeting Ownership Ratio, I examined how a calendar exposes whether a consultant steers their time or is steered by others, and what that says about value and organisational effectiveness. This follow‑up looks at a very specific pattern behind meeting overload: you send a directed question by email, the person addressed should either know the answer or be in control of getting it, yet the reply is a meeting invite that pulls in several others and lands days or weeks out. When Directly Responsible Individuals (DRIs) do this repeatedly, or when many different DRIs do it, it hijacks your agenda and crowds out the work that actually moves delivery forward. The visible symptom is more meetings, the real problem is that the answer is slowed and risk can accumulate on the critical path.
A DRI is accountable for producing a clear answer or decision in writing. Async‑first practice, as described in the GitLab handbook, treats writing as the default and meetings as an escalation when a decision with trade‑offs truly remains. Put simply, an asynchronous reply solves the problem without adding yet another meeting to an already overloaded agenda, while a default meeting shifts time away from delivery and often pushes the answer into the future.
A thought experiment: capped meetings and capped invites
Imagine Outlook enforced a hard limit on how many meetings you could book each week, or capped the number of people you can add to meetings on a weekly basis. Would that affect you? What would happen? Most likely, people would pause to consider whether a meeting is truly needed, and attendee lists would be curated more carefully; the constraint would also raise awareness of the “meeting-overload-problem” and its cost, making the habit of replying with a meeting harder to sustain. It is not a practical policy, but as a lens it makes costs visible. You could even reflect this in metrics later, for example how often a person would “hit” a hypothetical meeting budget, how much avoided attendance time a tighter invite list would produce, or how many answers landed sooner because a cap forced an async path.
What a DRI is, and why it matters for email questions
A Directly Responsible Individual is a single named owner who is accountable for producing a clear answer or decision. Applied to email, the addressee is expected to reply in writing, or to explicitly delegate input gathering while still owning the synthesis and the final written reply. Ownership is visible when the answer shows up in writing, not when a crowd shows up in a room. Async communication is not a stylistic preference, it is an operating choice that protects focus time and increases throughput.
Good intentions, competence gaps, and the unintended effect of slowing the answer
Many people who reply with a meeting genuinely want to help. They try to bring the right people together or avoid giving an incomplete answer. Sometimes the deeper cause is different. There can be a role‑fit gap, the person is the nominal owner but does not truly control the information, cannot synthesise inputs into a position, or cannot deliver within an acceptable timeframe. There can also be low async fluency, no habit or template for collecting input and replying in writing. Whatever the cause, the effect under urgency is the same: when the invite lands far out, the answer slows, risk accumulates, and the project that depends on it loses momentum.
What effective DRI behaviour looks like, in the data
Viewed through the inbox and calendar, strong ownership has a distinct signature. Acknowledgements arrive quickly, a due‑by date is visible, inputs are gathered in writing, and a synthesised answer appears within the window. You rarely see a meeting invite as the first move. When a meeting does occur it follows a short pre‑read and results in a written outcome on the same day. On your side this looks like fewer meeting invites in response to factual asks, leaner attendee lists, the organiser documenting outcomes the same day, and faster turnaround on urgent items.
By contrast, facilitation‑over‑ownership produces a mirror image. Factual asks convert to meetings, invites land far out, attendee lists are broad, outcomes are undocumented, and another sync is proposed. In your data that looks like more meeting invites in response to factual asks, larger attendee lists, missing or late written outcomes, longer delays to a usable answer, and urgent items breaching their expected response window.
Where synchronicity helps, observationally
There are situations where synchronous discussion improves speed and clarity. High ambiguity with high urgency requires joint sense‑making, real decisions that demand commitment benefit from live convergence, and sensitive topics are often resolved faster face to face. The distinguishing feature in each case is the presence of a short pre‑read and a documented outcome. In the data, these meetings reduce time‑to‑decision and critical‑path unblock time, improve stakeholder alignment on the first pass, and correlate with high pre‑read compliance and smaller attendee lists. These are observations, not prescriptions, and they help separate useful synchrony from avoidable meetings.
Reading the signals of a failing DRI
Signals accumulate before anyone says “ownership problem ”. Factual questions consistently convert to meetings that are scheduled far in the future. Pre‑reads are missing or arrive after the invite. Large attendee lists produce no documented answer, and directed questions pass their due dates. The DRI cannot cite a source of truth, cannot name who owes which input by when, or cannot state a recommendation in a paragraph. Read these not as personal failings but as quality indicators for the role being performed. In particular, when the DRI is a consultant, the pattern is a neutral proxy for role fit and operating maturity. It tells you how work flows and how reliably answers appear when the project needs them.
Metrics and KPIs, focused on your own agenda impact
The indicators below are scoped to your perspective as the requester. They analyse how “reply with a meeting” behaviour shows up on your calendar and inbox, help you identify failing DRIs based on impact to your time, and translate that impact for management. Use them sparingly to trigger coaching and to evidence delivery risk. You will select the most relevant ones for publication later.
Pattern detection on your agenda, who replies with meetings
Reply‑With‑Meeting Rate (RWM). The share of your directed email questions that receive a meeting invite from the addressee within a defined window instead of a written answer. Rising RWM shows a default‑to‑meeting habit.
Proxy‑Invite Ratio (PIR). For those invites, the proportion of attendees added by the addressee who were not on the original thread. A high PIR points to facilitation instead of ownership.
Answer‑via‑Organizer Gap (AVOG). The percentage of such meetings after which the organiser does not provide the answer in notes or follow up. A high AVOG means “I convene, others answer.”
DRI Omission Rate (DRIOR). The percentage of invites lacking a named DRI accountable for the written answer before or after the meeting. If DRIOR is not close to zero, ownership is unclear or avoided.
MOR adjacency (MOR‑A). Your Meeting Ownership Ratio segmented for meetings spawned from your questions. If MOR‑A drops while RWM rises, others are reorganising your week.
Async Displacement Minutes (ADM). Minutes spent in meetings that ended in a factual clarification that could have been emailed. Use this internally to spotlight low‑value sync.
When the DRI is a consultant, a quality indicator rather than a confrontation
In enterprise settings the DRI is sometimes a consultant. The same analysis functions as an objective quality indicator for external and internal consultants in DRI seats, showing how reliably they convert directed questions into timely written answers, how much latency they inject, and what that costs the programme. Read the flow, not the person, map the sequence from ask to answer and compare it with your own calendar and inbox evidence. Aggregate and anonymise where possible, centre the impact on the critical path, and translate it into delivery time and avoided cost rather than opinion.
For the customer organisation, these signals help improve performance, effectiveness, and cost. They highlight where a consultant’s operating mode is misaligned with the DRI role, where ownership is de facto elsewhere, and where meeting‑driven coordination is crowding out progress. The same view helps vendor managers and engagement leads calibrate expectations, coach to the standard, and assign DRI responsibility to the person who already synthesises the answer, all without personalising the issue.
As a consultant, I apply the same lens to myself. I track my Meeting Ownership Ratio and favour written, asynchronous replies so I do not reorganise the client’s week with avoidable meetings. When my own metrics drift, that is a prompt to correct course. The point is not policing, it is a shared, data‑grounded view of ownership that lets the organisation raise the quality bar for all consultants performing the DRI role.
Closing
Reply with a meeting can be the right move in a narrow set of cases, yet most of the time a DRI who owns the answer in writing will be faster for the team and safer for the delivery timeline. Begin with ownership, state the due date, collect inputs asynchronously, and reserve meetings for genuine convergence with a strong pre‑read. The calendar looks lighter when you do this, but the more important effect is that the work moves. For further reading, consult the async communication and DRI guidance in GitLab’s public handbook, and consider Amazon’s use of narrative memos as a model for pre‑reads that make meetings shorter and decisions clearer.