Streamline your project management and boost efficiency with Management by Exception (MBE), a cornerstone of PRINCE2 that empowers teams while keeping leadership focused on critical issues.
Let’s dive into this principle, clarify its application, and explore its broader use in organizations, all while keeping communication clear and effective.
Unpacking Management by Exception in PRINCE
PRINCE2 organizes projects into distinct management levels: the Project Board, the Project Manager, and the Project Team. Each level carries specific duties, ensuring smooth operations. Specifically:
- Business Commissioning level: Makes project level decisions.
- Project Board: Makes high-level decisions.
- Project Manager: Oversees daily operations.
- Project Team: Delivers the project’s outputs.
MBE drives efficiency by delegating authority downward. Instead of micromanaging, the Project Board sets tolerances—predefined limits for project objectives like time, cost, quality, scope, risk, and benefits.
These boundaries empower lower levels to operate independently, escalating issues only when tolerances are breached. Consequently, this approach saves time and sharpens focus.
When Does MBE Kick In?
As long as the project hums along within tolerances, the Project Manager handles operations without bothering the Project Board, except for routine updates or stage completions.
However, if an issue exceeds these limits—an exception—the Project Manager swiftly drafts an Exception Report for the Board. This ensures critical issues get prompt attention, keeping the project on track.
Examples of Tolerances in Action
To grasp MBE, consider these practical examples:
- Quality Tolerance: Imagine you’re designing a smartphone (let’s call it the X-Phone). The keyboard must last seven years for the average user, with a ±5% tolerance. If testing shows it falls short, it’s an exception requiring escalation.
- Scope Tolerance: The X-Phone project includes must-have features (e.g., 5G connectivity) and optional ones (e.g., a stylus). Teams can choose which “nice-to-haves” to include, but mandatory features are non-negotiable.
- Benefit Tolerance: The project aims to boost market share by 10%. If projections dip below this, it triggers an exception.
- Risk Tolerance: If a key supplier can’t deliver components meeting specifications, this breach demands Board intervention.
By setting clear tolerances, MBE ensures smooth communication. Project Managers tackle daily issues, while exceptions flow upward, keeping the Board focused on strategic decisions. Thus, MBE sharpens efficiency and clarity.
Applying Management by Exception Beyond PRINCE2
Now, let’s zoom out and explore MBE as a general strategy, particularly from a budget perspective. In complex industries, MBE streamlines processes by empowering teams to handle routine variances while escalating significant deviations to leadership.
What Is Management by Exception?
MBE focuses on identifying and addressing significant deviations from expected financial or operational results.
For instance, a company controller might flag expenses exceeding the budget by 20% or $10,000, whichever is greater. This approach ensures managers tackle only the most impactful issues, saving time for strategic priorities.
Moreover, MBE can be tailored. Smaller variances go to lower-level managers, while major ones escalate to senior leadership. This flexibility enhances decision-making across the organization.
Why Use MBE? The Advantages
Adopting MBE offers clear benefits:
- Saves Time: Managers review only significant variances, freeing them for high-value tasks.
- Streamlined Reporting: Automated systems can generate exception reports at set intervals, minimizing manual effort.
- Empowers Employees: Teams handle routine issues independently, fostering initiative within budget constraints.
- Proactive Auditing: Large exceptions trigger pre-audit reviews, ensuring compliance and readiness.
These advantages make MBE a powerful tool for efficiency. By focusing leadership on what matters, organizations operate more smoothly.
Potential Pitfalls to Watch
Despite its strengths, MBE has challenges:
- Flawed Budgets: If budgets are poorly set, irrelevant variances can overwhelm analysts, wasting time.
- Added Overhead: Financial analysts are needed to monitor and report exceptions, increasing costs.
- Centralized Control: MBE relies on a top-down structure, which may not suit decentralized organizations where local managers handle issues directly.
- Assumes Managerial Fixes: MBE assumes only managers can resolve variances, potentially overlooking frontline employees’ ability to act swiftly.
To mitigate these, organizations must ensure robust budgets and clear communication. Otherwise, MBE’s effectiveness could falter.
Best Practices for Implementing MBE
To make MBE work, follow these steps:
- Set Clear Standards: Define standard operating procedures to establish what constitutes an exception. For example, a 20% price deviation might require escalation, while smaller variances stay with the team.
- Map Approval Levels: Align approval workflows with your organization’s structure. A three-tier system might suffice for smaller firms, while larger ones need more granularity.
- Define Exception Thresholds: Specify what triggers escalation at each level. For instance, a sales rep might handle 15-20% gross margin deviations, while larger ones go to a manager.
- Distribute Exceptions Wisely: Decide how many exceptions each level should handle. Perhaps 20% go to senior leadership, 30% to mid-level managers, and 50% to frontline staff.
- Balance Approvals and Rejections: Aim for an 80-20 rule, approving exceptions 20% of the time. If exceptions become too common, revisit your MBE framework or retrain staff.
Additionally, leverage AI-driven insights to set accurate thresholds. Reliable data ensures sound decisions, strengthening your MBE approach.
Active vs. Passive MBE
MBE comes in two flavors:
- Active MBE: Managers proactively address potential issues to prevent escalation.
- Passive MBE: Managers step in only when major exceptions arise.
Both styles work, but active MBE often prevents bigger problems, while passive MBE suits hands-off leadership. Choose what aligns with your organization’s culture.
Flowchart for Escalating Issues in PRINCE2
To clarify MBE in PRINCE2, here’s a simple flowchart for escalating exceptions:
- Monitor Project Metrics: Track time, cost, quality, scope, risk, and benefits against tolerances.
- Identify Variance: Detect if a metric exceeds its tolerance (e.g., cost overrun >10%).
- Assess Impact: Determine if the issue requires immediate escalation or can be managed locally.
- Draft Exception Report: If escalation is needed, the Project Manager prepares a detailed report.
- Escalate to Project Board: Submit the report for Board review and decision.
- Implement Board Guidance: Follow the Board’s directives to resolve the exception.
This structured process ensures clarity and efficiency, keeping projects on course.
In conclusion, MBE, whether in PRINCE2 or broader organizational contexts, empowers teams, streamlines communication, and sharpens focus on critical issues.
By setting clear tolerances, defining escalation paths, and balancing autonomy with oversight, you can master this approach.
Ready to implement MBE? Start by defining your standards and watch efficiency soar.
Did you know you get a full 12-month membership access to our PEOPLECERT Accredited PRINCE2 7th Edition Foundation Exam Masterclass, AND our PEOPLECERT Accredited PRINCE2 7th Edition Practitioner Exam Masterclass – PLUS all our other (over 30) Project Management Accredited Masterclasses – PLUS 7 days/week one-to-one online support (Microsoft Teams) from Dave Litten (ex-examiner), for just €299 for 12 months?
PRINCE2® 7 Foundation and Practitioner
Learn PRINCE2® 7 Foundation and Practitioner Online
** Enhance your PRINCE2 career now **
PRINCE2® Masterclass gives you the skills necessary to manage projects effectively and achieve your objectives.
Get 7 days a week 12 months one to one coaching with ex PRINCE2 examiner Dave Litten.
PRINCE2® is a globally recognized project management framework. By completing both the Foundation and Practitioner courses through our self-paced e-learning, you will develop an understanding of the methodology and learn how to effectively adapt it to any project.
The PRINCE2® 7 Foundation and Practitioner Masterclass is PeopleCert Accredited and guarantees to take you from PRINCE2 Novice to PRINCE2 Practitioner with our famous video learning, study guides and practice exams.
What Does the Masterclass Cover?
The PRINCE2 Foundation examination assesses your knowledge and comprehension of the PRINCE2 project management methodology as detailed in the syllabus. The PRINCE2 Practitioner examination, on the other hand, gauges your ability to apply and tailor the PRINCE2 method. Candidates who pass the Practitioner exam should be able to start implementing the method on an actual project with some guidance. However, their effectiveness may differ based on their experience in project management, the complexity of the project, and the level of support they receive in their work environment.
