Skip to main content

"Action-Oriented, Stakeholder-Focused" MoM Structure

 I. Meeting Header:

  • Meeting Title: Clear and concise (e.g., "Project X Status Update," "Q3 Planning Meeting").
  • Date and Time: Record the date and time the meeting took place.
  • Location/Platform: Indicate where the meeting was held (e.g., Conference Room A, Zoom).
  • Attendees: List the names and roles of everyone who attended.
  • Absent: List the names of key individuals who were invited but did not attend.
  • Meeting Owner: Who was in charge of the meeting ?
  • Document owner: Who is in charge of the documentation ?

II. Key Discussion Points (Concise Summary):

  • Purpose: Briefly summarize the main topics discussed.
  • Format: Use bullet points for brevity.
  • Content:
    • Decision Points: Clearly state any decisions that were made.
    • Key Information: Summarize any crucial information shared.
    • Key Questions: Summarize the key questions that were raised.
    • Open Issues: Note any issues that remain unresolved.
  • Stakeholder Focus: Frame the summaries in terms of their impact on stakeholders.
  • Example:
    • "Decision: Approved the revised timeline for Project X, with the new completion date of [Date]."
    • " Key Information: Marketing presented the Q3 campaign plan."
    • "Open issue: The impact of new regulation on project X is still under investigation."

III. Action Items (Clear and Assignable):

  • Purpose: Document every required action.
  • Format: Use a table or clear list format.
  • Content:
    • Action Item Description: What needs to be done? Be specific.
    • Owner: Who is responsible for completing the action?
    • Due Date: When is the action due?
    • Priority: What is the priority of this item ?
    • Status: Status of the action item (e.g., Not Started, In Progress, Completed).
  • Example:
Action ItemOwnerDue DateStatus
Finalize the revised timeline for Project XJohn Smith2024-03-15In Progress
Review marketing Q3 campaignJane Doe2024-03-20Not started

IV. Next Steps:

  • Purpose: Outline what will happen next.
  • Content:
    • Follow-Up Meeting: Is there a follow-up meeting scheduled? If so, when?
    • Decisions: What actions will be taken based on the decision ?
    • Next Steps: what actions need to happen before the next meeting ?
    • Deadlines: Remind stakeholders of key deadlines.
    • Responsibilities: Who is responsible for the next steps.
  • Example: "The next Project X status meeting is scheduled for [Date] at [Time]."

V. Attachments/References:

  • Purpose: List any documents or resources referenced in the meeting.
  • Content:
    • Link to the referenced documents.
    • Name of the document.
    • Author of the document.
    • Version.

VI. Distribution:

  • List who received the document.
  • Date the document was sent.

Key Principles of This Framework:

  • Action-Oriented: The focus is on action items and next steps.
  • Stakeholder-Focused: The content is tailored to stakeholder interests.
  • Clear and Concise: The language is direct and to the point.
  • Organized: The structure is clear and easy to follow.
  • Trackable: Action items are clearly assigned, tracked, and closed.

How to Use This Framework:

  1. Prepare: Before the meeting, create a template using this framework.
  2. Capture: During the meeting, capture the key discussion points, decisions, and action items.
  3. Assign: Make sure each action item has a clear owner and due date.
  4. Distribute: Share the MoM with all attendees and relevant stakeholders promptly after the meeting.
  5. Follow up: Follow up to ensure that the actions are completed.
Labels:

Comments

Post a Comment

Popular posts from this blog

Hexagonal Architecture (Ports & Adapters Pattern)

Hexagonal Architecture , also known as the Ports and Adapters pattern, is a software design pattern that aims to create a decoupled and maintainable application by separating the core business logic from external concerns (like databases, APIs, and UIs). Structure of Hexagonal Architecture A typical Hexagonal Architecture has three main layers: 1️⃣ Core Domain (Application Logic) This contains the business rules and domain models. It is completely independent of external technologies . Example: If you’re building a banking system , this part would include logic for transactions, withdrawals, and deposits . 2️⃣ Ports (Interfaces) These are interfaces that define how the core interacts with external components. Two types of ports: Inbound Ports (driven by external inputs like APIs, UI, or events) Outbound Ports (used to interact with external services like databases, messaging systems, etc.) 3️⃣ Adapters (Implementation of Ports) These are concrete implementations of the ports, re...
Post a Comment
Read more

Recursion & Choice

Understanding Recursion and Choice Diagrams with Examples Understanding Recursion and Choice Diagrams with Examples Recursion is a powerful concept in programming where a function calls itself to solve smaller instances of the same problem. It's often used in solving complex problems that can be broken down into simpler subproblems. In this blog post, we'll explore the basics of recursion, understand choice diagrams, and see examples to illustrate these concepts. What is Recursion? Recursion occurs when a function calls itself directly or indirectly to solve a problem. A recursive function must have a base case to terminate the recursive calls and prevent infinite recursion. Here's a simple example of a recursive function to calculate the factorial of a number: public class RecursionExample { public static void main(String[] args) { int number = 5; int result = factorial(...
Post a Comment
Read more

Frameworks

  Communication Frameworks: BLUF:  Google's culture strongly emphasizes efficiency and directness, so getting to the "bottom line up front" is very common. SCQA:  Used in presenting proposals, making recommendations, and structuring project plans. PAS : Used in selling ideas and influencing others. BAB : Used in selling ideas and influencing others. Sparklines : Used in presentation to influence others. STAR:  Widely used in Google's interview process and performance evaluations. Problem-Solving/Decision-Making Frameworks: 5 Whys:  A fundamental technique for root cause analysis, and Google is known for its emphasis on data-driven decision-making, which often involves digging into the root causes of problems. Systems Thinking:  Given the complexity of Google's systems, a systems thinking approach is essential. The Four Questions : Used in post-mortem to review an incident. Human factors : Used in post-mortem to avoid the blame culture. Time Management/Prior...
Post a Comment
Read more