3. How to Support Team Performance
The PMP® Reasoning Architect
This page provides guidance on the main concepts.
The book provides the full reasoning architecture and judgment training.
Click here to view the book on Amazon.
Executive Summary
This chapter synthesizes key principles for supporting team performance, drawn from Orlando Casabonne’s book, THE PMP® REASONING ARCHITECT. It prepares for the ECO 2021 Task Support Team Performance. The central thesis refutes the management cliché that “pressure makes diamonds,” arguing instead that high performance is a “structural outcome” derived from a well-architected system of support, not from anxiety or force. The primary threat to performance is identified as “silent erosion,” a gradual decay in a team’s functional capacity caused by recurring blockers, unbalanced workloads, and disengagement. This erosion signals a broken support structure, not a lack of intent from team members.
Effective leadership requires a shift from supervision, which extracts value, to support, which builds capacity. This involves adopting a “behavioral posture” of pattern recognition rather than relying on lagging indicators like KPIs. The framework provides a toolkit of specific techniques, including the Situation–Behavior–Impact (SBI) model for blame-free feedback and the Feedforward approach to focus on future improvement. Crucially, leadership actions must be made visible and traceable through artifacts like the Performance Feedback Log and Individual Development Plan (IDP). These tools convert behavioral insights into hard evidence, creating a sustainable system for developing team capability.
1. The Core Philosophy: Architecture Over Anxiety
The foundational premise of this framework is a direct challenge to the conventional wisdom that high-pressure environments create exceptional results. The source material posits that this is a dangerous myth. In team dynamics, excessive pressure does not create diamonds; it “usually just makes dust,” leading to fatigue and eventual structural failure.
Performance is presented not as a byproduct of force, but as an outcome of intentional design. As one source states, performance “comes from architecture, not anxiety.” This requires leaders to move away from a model of supervising and extracting value toward one of supporting and building capacity. The distinction is critical:
• Supervision: An extractive process that focuses on watching people work and enforcing compliance. This is compared to administration, not leadership.
• Support: A constructive process that builds the team’s capability, resilience, and capacity to create value. It is a leadership function that anchors improvement in reality.
The ultimate goal is to build structural coherence, creating a team that can withstand pressure because its support systems are robust, its feedback loops are clear, and its growth is intentional.
2. The Primary Threat: Silent Erosion
Project failure often begins not with a dramatic crisis but with a quiet, gradual decay of the team’s ability to function. This phenomenon is termed “silent erosion.” It is described as the “rust, not the fire,” meaning that by the time a manager sees an explosion like a missed deadline or a client complaint, the underlying structural damage has already been done.
The leader’s role is to detect the early, subtle symptoms of this erosion. These are not found in KPIs, which are lagging indicators, but in behavioral signals.
Symptoms of Silent Erosion:
• Recurring Blockers: The same problems reappear in multiple retrospectives without resolution.
• Friction and Missed Handoffs: The workflow between team members is inefficient and marked by delays.
• Unbalanced Workloads: Certain individuals are consistently overloaded while others are underutilized.
• Gradual Disengagement: Team members become passive. This is observable in behaviors like cameras being turned off in virtual meetings or a silent chat channel.
• Lack of Accountability: Responsibilities become unclear and commitments are not met.
Crucially, the framework argues that these failures are “rarely a matter of intent.” Most team members want to do good work. When they underperform, it is a signal that the system around them is broken: feedback is missing, recognition is absent, or their professional growth is “unanchored.”
3. The Leader’s Toolkit for Performance Support
To combat silent erosion and build a high-performing system, a leader must use specific, deliberate techniques. These tools are designed to be behavioral systems that create psychological safety and make growth observable and repeatable.
Feedback Delivery Techniques
Effective feedback is the cornerstone of performance support. The goal is to strip judgment from observation and focus on actionable improvement.
|
Technique
|
Description
|
Purpose
|
|---|---|---|
|
SBI Model
|
Situation–Behavior–Impact: A structured method for delivering fact-based feedback. For example: “In this morning’s client meeting (Situation), you arrived 10 minutes late (Behavior), which meant we had to repeat the intro and the client lost time for questions (Impact).”
|
To remove identity attacks (“You’re unprofessional”) and focus on the objective cost of an action. This preserves psychological safety and prevents defensive reactions.
|
|
Feedforward
|
A future-oriented approach that pivots immediately from a critique to a follow-up goal. Instead of dwelling on a past mistake, the conversation becomes, “So, next time, let’s try this specific strategy…”
|
To maintain forward momentum and transform a mistake into a learning opportunity. It contrasts with feedback, which can feel like an “autopsy of what went wrong.”
|
|
Microlearning Triggers
|
Using a “teachable moment” to provide immediate, targeted feedback and learning right when an event occurs.
|
To avoid the ineffective and often damaging practice of saving up all feedback for a formal annual review, ensuring that guidance is timely and relevant.
|
Growth and Recognition Methods
Recognition should be a strategic tool for development, not merely a reward.
• Visibility Rotation: This practice involves assigning high-visibility or strategic tasks to developing team members, such as letting them present a demo to stakeholders or lead a retrospective. This is more powerful than a generic “employee of the month” award because it serves multiple purposes:
◦ It builds the individual’s confidence and competence.
◦ It publicly signals the leader’s trust in that person.
◦ It makes the organization’s leadership pipeline visible.
Recognition is thus transformed from a simple “pat on the back” into a “platform” for growth.
4. Making Leadership Visible: Essential Artifacts
A leader’s intent is invisible; therefore, performance support must leave a visible, structural trace. Artifacts are the tools that convert behavioral insights and verbal conversations into “persistent evidence.” They create a system of continuity, accountability, and fairness.
Key Artifacts for Performance Support:
• Performance Feedback Log: A dynamic record of performance observations, both positive and negative, captured as they happen. This log prevents recency bias and provides a complete, traceable history of an individual’s development over time.
• Individual Development Plan (IDP): A living document connecting a team member’s personal growth goals with the project’s needs. It answers the “what’s in it for me?” question and ensures development is proactive and strategically aligned.
• Recognition and Rewards Register: A structured record of acknowledgments that contextualizes recognition, ensures fairness, and reinforces team values.
• Behavioral Baseline Tracker: A register for comparing “before and after” behavioral states following a feedback intervention. This provides data to validate that leadership actions resulted in measurable change.
• Check-In Notes / Coaching Memos: Concise records of informal feedback sessions that capture context and track the cumulative progress of improvement efforts.
• Retrospective Notes: Aggregated team reflections that help identify systemic patterns, frictions, and opportunities for collective improvement.
5. Case Study: The Overcommitted Developer
A scenario from the source material illustrates the practical application of these principles.
• The Situation: A developer named Alex produces high-quality, elegant code but consistently misses deadlines. His inaccurate time estimates create delays and burnout for the downstream testing team.
• The Wrong Approach (Pressure): A manager applying the “pressure makes diamonds” theory would assume laziness, demand Alex “work harder,” and potentially damage morale or cause a talented employee to quit.
• The Right Approach (Structure):
1. Diagnosis: The manager analyzes the data and realizes the root cause is not laziness but unrealistic estimation and a blind spot to downstream consequences.
2. Feedback: The manager uses the SBI model to discuss the timeline variances and their impact on the QA team, carefully avoiding any attack on Alex’s skill or intent.
3. Structural Solution: Instead of just saying “estimate better,” the manager designs an improvement plan. Alex is paired with a tester for a short period to build empathy and review estimation methods together.
4. Verification and Recognition: After two sprints, estimation accuracy improves. The manager acknowledges this growth publicly, celebrating the new capability and reinforcing the desired behavior.
By applying structure instead of pressure, the manager kept the talent, fixed the process, and turned a performance failure into a new organizational capability.
6. Application Across Delivery Models
The philosophy of support is universal, but its mechanics must adapt to the project’s context.
|
Delivery Model
|
Application of Performance Support
|
|---|---|
|
Agile
|
Support is continuous and peer-based. Psychological safety is paramount to enable open feedback in retrospectives. The leader acts as a servant leader, removing obstacles. Peer recognition is a key tool.
|
|
Predictive
|
Support is more formal and structured, linked directly to the documented plan, milestone reviews, and KPIs. The leader’s role is more directive, but feedback models like SBI remain essential.
|
|
Hybrid
|
The leader must be “bilingual,” combining real-time coaching from Agile with formal tracking and milestone-based reviews from Predictive. This ensures learning and accountability are synchronized.
|
7. Common Pitfalls
Even well-intentioned leaders can fail at performance support. Common mistakes include:
• Vague Feedback: Offering calorically empty praise like “Good job, keep it up” provides no nutritional value for growth.
• Ignoring the “How”: Focusing only on deliverables while ignoring toxic behavior from a high-performer allows silent erosion of team culture.
• Confusing Recognition with Favoritism: Failing to ground recognition in clear, transparent criteria.
• Appraisal as Evaluation: Treating performance reviews as a final judgment rather than a developmental opportunity, which erodes trust.
8. Conclusion: The Mindset of a Reasoning Architect
Supporting team performance is not about enforcing compliance; it is about enabling improvement. The leader’s role is to be an architect of the team’s capability, building a system that allows good people to do great work. The core principles of THE PMP® Reasoning Architect advocate for a fundamental shift from being a monitor to being a manager who actively builds, reinforces, and sustains the team’s capacity to deliver value.
The framework leaves leaders with two critical questions for reflection:
1. How consciously do you transform performance feedback into collective learning rather than just correction?
2. Do you sustain alignment through presence or only through measurement?