Run a weekly contradiction review before priorities drift

Leadership teams often describe priority problems as a shortage

Leadership teams often describe priority problems as a shortage of discipline. Sometimes the harder problem is contradiction. A sales promise assumes product capacity that the operating plan has assigned elsewhere. A hiring pause coexists with interview requests. A protected calendar block keeps disappearing under an external commitment rule nobody has revised. Each item can look reasonable in isolation. Together they cannot all remain true. A weekly contradiction review gives chief of staff support a bounded way to surface these collisions before teams quietly interpret them for themselves. The review does not make the chief of staff the final authority over every function. It prepares a clean choice for the leader who owns the tradeoff and records what changes afterward.

Collect contradictions from current operating sources, not from

Collect contradictions from current operating sources, not from rumor. Compare the leadership decision log, plan, calendar commitments, hiring approvals, project milestones, board actions, and published internal rules where access permits. Ask functional owners to flag cases in a simple form: statement A, statement B, why they conflict, consequence, responsible decision time, and likely owner. Preserve the wording and source date. Two statements may only appear inconsistent because they apply to different periods or scopes. The first job is to verify the collision, not dramatize it. Keep confidential source material in its approved location and use a restricted reference when broader participants need only the existence of the issue.

Prepare each verified contradiction as a decision, clarification

Prepare each verified contradiction as a decision, clarification, or sequencing question. A true decision needs options and consequences. A clarification asks the accountable leader which interpretation governs. A sequencing question may allow both commitments to survive if dates or resources move. Do not turn every tension into a binary choice. Sometimes the correct action is to gather missing evidence. Mark facts, assumptions, and recommendations separately. Name who developed a recommendation and who has authority to approve it. Chief of staff support can synthesize cross-functional context, but it should not disguise a personal preference as settled leadership direction.

Keep the weekly review short by resolving what

Keep the weekly review short by resolving what can be resolved beforehand. Source corrections go back to their owners. Duplicate records are reconciled with an audit note. Items already governed by a clear rule can be routed under that rule. The live agenda should contain collisions that need authority or cross-functional agreement. Order them by responsible decision time and consequence, not by the seniority of the person who raised them. If a topic requires specialist legal, financial, people, or security judgment, obtain the appropriate review rather than asking the meeting to improvise. The chief of staff protects the decision process by knowing when the leadership forum lacks the evidence or permission to choose.

Close every discussed item with an exact disposition

Close every discussed item with an exact disposition. One statement governs and the other is withdrawn. Both remain, with scope or timing clarified. A named owner gathers evidence by a set review point. The responsible leader accepts a documented risk. Or the team declines to decide and records the consequence. Update the authoritative sources, not only the contradiction list. Tell affected owners what changed, when it takes effect, and whether earlier work should stop. A decision that stays inside meeting notes leaves teams operating under the old contradiction. The chief of staff can coordinate the update, while substantive owners remain accountable for their plans and communications.

Measure the practice through recurrence and downstream repair

Measure the practice through recurrence and downstream repair. Look for the same contradiction returning, work abandoned after late clarification, parallel teams acting on different versions, and commitments reopened because an affected owner was omitted. A rising count may initially mean people trust the process enough to expose conflicts. A falling count may mean cleaner alignment, or it may mean issues moved back into private channels. Review cases. Ask whether leaders made timely choices and whether the changed direction reached the people doing the work. Over time, repeated contradictions reveal operating rules that need redesign. The weekly review succeeds when it prevents silent local decisions, not when its tracker reaches zero. It gives leadership a place to acknowledge that two sensible promises can collide and a disciplined method for deciding what becomes true next.

Protect the review from becoming a venue for relitigating

Protect the review from becoming a venue for relitigating every past decision. The question is whether current instructions conflict and what action the conflict now requires. Historical context belongs only where it affects authority, evidence, or the consequence of changing direction. Set a responsible decision time for each item and move unresolved work to the proper owner rather than carrying a vague debate week after week. If a leader consciously keeps tension in place, record the accepted consequence and the next trigger for review. That is different from accidental drift. Teams need to know whether they should continue under a difficult but deliberate choice or pause because leadership has not decided. When a contradiction involves a public or external promise, coordinate communication through the authorized relationship owner. Executive support should never issue a corrective commitment on its own. In a chief of staff hiring process, a contradiction exercise can reveal synthesis and restraint. Give candidates sources that disagree and see whether they verify dates, distinguish scope, and return judgment to the named executive. Confidence without traceability is not the skill being tested. A strong chief of staff makes the choice legible, keeps dissent intact, and ensures that the approved direction reaches operating systems after the meeting. Rotate through operating areas rather than relying only on whoever speaks first. Calendar, project, hiring, board, and stakeholder records may reveal different conflicts. The review owner should invite evidence from affected functions while keeping the live group limited to people needed for the choice.

Frequently asked questions