The decision does not end at the meeting; it ends 90 days later.

After each consulting session, professionals often ask clients a question: "Who on the team will remind us of this decision in three weeks?" This question is not just polite small talk. It is a way to check whether the decision just made will actually hold up through the first week. Practical experience shows that most decisions do not fail due to being wrong, but because they are forgotten.

Why the first 90 days are the most dangerous period

After the session, everyone leaves with good energy, a to-do list in hand, and a fairly high will. But as soon as they return to their desks, emails, meetings, and daily minor crises come rushing in. The agreed-upon tasks start to slide down, then further down, and eventually disappear.

Jeffrey Pfeffer and Robert Sutton refer to this as the "knowing-doing gap": organizations know what to do but fail to act. Not due to a lack of information, but because of a lack of mechanisms to sustain action. This gap does not close on its own. Someone, or some mechanism, needs to intentionally keep it from widening.

Sam Kaner, who laid the foundation for modern participatory decision-making practices, clarifies: a session does not end when a decision is made. It ends when the decision is sustainably implemented. The consulting session is just the starting point.

Factors to consider the level of monitoring

• Scale and implementation time: Strategic decisions can take months, involving many people who need to follow a structured process. A one-time, concise decision with fewer executors does not require a heavy machinery.
• Team's self-management capability: if the team is accustomed to taking responsibility and has someone proactively monitoring internally, the role of outsiders can be minimal. If the team does not have that habit, outsiders can be more helpful.
• Number of stakeholders: When decisions require cross-departmental coordination, internal accountability is often weaker. Everyone assumes someone else is handling it.
• Risk of unforeseen complications: Some decisions are clear at the conclusion but encounter blind spots during actual implementation. Monitoring helps detect early and adjust before straying too far off course.

When to choose which level

Common errors after the meeting

• Once finalized, everyone goes home: No follow-up meetings scheduled, no one assigned to maintain internal rhythm. Decisions quietly drift for the first two weeks, and no one pays attention.
• Too frequent follow-up becomes a burden: Too many meetings, the team feels more annoyed than helped. Follow-up without genuine resolution is just additional meetings for the sake of it.
• Only asking "is it done" without resolving: When things are stuck, the right question is "where is it stuck and what is needed to continue," not just "is it done?" Monitoring without genuine support means clients have no reason to bring up their issues.
• Thinking monitoring is someone else's job: Consultants can provide frameworks and resolve technical issues, but they cannot replace internal personnel responsible for pushing tasks forward daily. Both roles need to work simultaneously.

Review the previous period at the beginning of each session to create accountability. Without that mechanism, every to-do list is just a list of intentions.

Standards for tracking action items, Convene

This article is for reference. The scope, pricing, and specific commitments of Sinh Vũ are detailed in the proposal and signed contract.