What is an MBR meeting?

Let us start with the complete form of this word, before going into the details.

MBR Meeting: Monthly Business Review Meeting

Similar to MBR there are Weekly and Quarterly meetings. 

WBR Meeting: Weekly Business Review Meeting

QBR Meeting: Quarterly Business Review Meeting


These meetings are famed mechanisms used within Amazon.


A mechanism is a process that converts inputs into desired outputs on an ongoing basis.

Mechanisms allow us to learn and improve from mistakes/defects, enable scalable process-based solutions, and prevent institutional knowledge through documentation.

The three components of a mechanism are the tool, the adoption, and the inspection.

  • The tool transforms inputs to outputs, 
  • the adoption sets incentives for stakeholders
  • the inspection ensures continuous delivery of desired outputs.

For example in MBR meetings: 

  • Inputs include monthly meetings, attendance from team members, and key performance indicators from the business. 
  • The output is a cadence for monitoring goal progress.


Running an MBR Meeting

  • Let the advisors review the metrics (5 min)
  • MBR Owner provides an oral interpretation of data (5 min)
  • MBR Owner provides suggests several "experiments" to the CEO based on data.  (10 minutes)
  • CEO approves, MBR Owner executes (1 minute)


Tips for MBR

  • MBR requires Monthly participation and analysis
  • If you are in charge of the metrics, show metrics that help others make decisions and draw conclusions, not you.
  • Use the below MBR template



  • Have some hypotheses about the monthly metrics, especially for dips and peaks.
  • KPIs and data should be small enough to fit in a single Excel on a mobile phone in a normal font


Comments

Post a Comment

Popular posts from this blog

Software Architecture Techniques - Part 6

Question 1: What is the 20-minute rule, and when is it best to apply it? Answer: The "20-minute rule" for software architects is a time management technique that encourages dedicating short, focused bursts of time (around 20 minutes) regularly to learn new technologies, tools, or industry trends. The goal is to increase the architect's technology width, which refers to broadening their knowledge and understanding of different technologies and practices beyond their current expertise. Here's how the 20-minute rule can be applied: Consistent Learning : Set aside at least 20 minutes each day or several times a week to engage in learning activities. This could include reading articles, watching videos, attending webinars, or exploring documentation related to new technologies or architectural concepts. Focused Approach : Use the 20-minute sessions to maintain focus and avoid distractions. Eliminate interruptions during this time and fully immerse yourself in the learning ...
Read more

Software Architecture Techniques - Part 2

Question 1: What are the two dimensions of the risk assessment matrix? Answer: The risk assessment matrix typically consists of two dimensions: Likelihood : This dimension assesses the probability or likelihood that a risk event will occur. It is often represented on a scale from low to high or with numerical values (e.g., 1 to 5, where 1 is low likelihood and 5 is high likelihood). The likelihood helps in understanding the chances of the risk event happening. Impact : This dimension evaluates the potential consequences or impact of the risk event if it occurs. It is also represented on a scale from low to high or with numerical values (e.g., 1 to 5, where 1 is low impact and 5 is high impact). The impact helps in understanding the severity of the risk if it materializes. By combining the likelihood and impact assessments, organizations can categorize risks into different levels of criticality, such as low, medium, and high risk. This information is valuable in prioritizing risk respon...
Read more

Software Architecture Techniques - Part 3

Question 1: What is irrational artifact attachment, and why is it significant with respect to documenting and diagramming architecture? Answer:  Irrational artifact attachment is a cognitive bias that occurs when individuals become overly attached to certain artifacts, such as documentation and diagrams, without considering their actual usefulness or relevance to the architecture or project. It refers to the tendency to treat artifacts as inherently valuable or important, even when they may not provide substantial benefits or are outdated. This bias can be significant with respect to documenting and diagramming architecture for several reasons: Misleading Focus : When individuals are irrationally attached to specific artifacts, they may focus on maintaining and updating those artifacts rather than on the actual architectural decisions and their impact on the project. This can lead to a misallocation of time and effort. Loss of Agility : Outdated or unnecessary artifacts can impede ...
Read more