LEARN. PRACTICE. GROW.Turn an intention into a shared outcome
In a fictional reconciliation project, automating the service can mean different things. Development counts scripts and APS counts avoided interventions; business wants exceptions resolved sooner. Start by defining who benefits, which cases belong to the population, and where measurement begins and ends. Then ask how each delivery contributes to that outcome. A small experiment may show that a routing rule is more useful than another page. Record the assumption and evidence that would justify changing direction. A shared outcome allows the team to revise its chosen means while retaining its purpose.
Facilitate a decision with criteria and limits
Two alerting options cause conflict between teams. Before voting, identify the problem each proposal addresses and agree observable criteria using synthetic events. If service recovery is mandatory, check it before comparing convenience scores. The option with the best interface does not automatically satisfy a missing recovery condition. During discussion, distinguish technical contributions from behavior that prevents participation. A specialist can raise a valid risk while also needing to respect an agreement against interruptions. Addressing that behavior does not require discarding the evidence. Record the decision and the condition for revisiting it.
Apply Scrum accountabilities in the right context
When the scenario uses Scrum, its accountabilities help resolve concrete disagreements. The Product Owner orders the Product Backlog; Developers size work and adapt the Sprint plan. A manager does not create capacity by unilaterally reducing an estimate. The Daily Scrum should support inspection and adaptation by Developers instead of serving only as a management report. If external change makes the Sprint Goal obsolete, cancellation authority belongs to the Product Owner. These rules apply to the explicitly stated Scrum context. A project using another approach needs its own agreement on responsibilities and decisions.
Represent people working on other shifts
A demonstration at 10:00 can exclude the very people operating the service at 02:00. Identify differing contexts: permissions, available support, language, and documentation access. Prepare material people can review before the meeting and an asynchronous response channel with a deadline and owner. Count represented roles, not just received messages. Three product replies do not replace the requested operational confirmation from the night shift. When reporting status, distinguish decisions made, pending conditions, and unknown information. Compare AI-summarized minutes with the original record before using them as a basis for commitments.
Plan learning as verifiable work
If every iteration consumes its capacity on features, an intention to train substitutes may never materialize. Reserve supervised practice, authorized access, and feedback time. Define what the person should be able to execute and when they should stop and escalate. Then record evidence by task. In the exercise, A has João and Ana qualified; B only Ana; C João and Luís; D only Luís. Under a local rule requiring two people per task, B and D have gaps. Attendance at a shared session does not prove everyone can execute every task. Target learning where coverage is missing.
Exercise: criteria before voting
Use the synthetic table below in an options review. The fictional rule requires demonstrated recovery; utility is compared afterward. Option A has the highest score but is ineligible. B is best among the two options meeting the condition. Explain this to someone preferring A and offer a concrete route: demonstrate recovery and compare again using updated evidence. Then prepare an English message stating the decision, its basis, and the next step. Agreeing to investigate does not promise future approval. The lesson connects purpose, participation, and evidence with decision authority.
Synthetic decision fixture, not bank policy
option | recovery demonstrated | utility
A | no | 92
B | yes | 84
C | yes | 78
Rule: eligibility first; maximize utility only among eligible options.
Result: B. A may be reconsidered after applicable evidence changes.In a fictional funds service, the alerting team tests three options and selects B because it meets mandatory recovery. A remains under investigation with an explicit criterion and owner.
Common pitfalls
Confusing popularity with eligibility, counting messages as role representation, lowering estimates to fit work, and accepting automated summaries as authorized decisions.
Related topics: Autonomy, collaboration, and adaptive teams · Integrated planning: capacity, dependencies, and forecasts · Change, context, and evidence-based improvement
An adaptive team learns from observable outcomes. Decisions need context, criteria, relevant participation, and explicit authority.
Reference: PMP Examination Content Outline July 2026 · PMP ECO July 2026; BigSavant PMP 2026.7