# The Zen of PCI issue 14 drafts

Draft for Scott review

## Prioritize competing improvements with the context intact

Prioritize competing improvements with the context intact

Several useful improvements can arrive together. One would make a handoff clearer. Another would make the current guidance easier to find. A third would address friction in a different process. Each has a reason to exist. The next task is to understand their relationships and agree what should happen next.

A calm priority conversation makes the reasoning visible. It connects consequences, applicable constraints, dependencies, available capacity, and the person authorized to decide. The aim is an order people can explain and continue, with unresolved questions and work awaiting attention still visible.

In our fictional supplier-integration example, the team has checked clearer status vocabulary on one placeholder handoff. The live integration decision remains pending. The proposed vocabulary update, a better route to current guidance, and an unrelated process improvement now compete for the same contributors.

The placeholder check supports its specific scope. It does not approve wider rollout, settle the integration decision, or decide which other work may wait. Those questions still belong to the appropriate owners and established processes.

Start with what the work requires

Before ranking optional improvements, identify applicable obligations, deadlines, known issues, and any need for prompt escalation. Use the relevant assessment, risk, incident, corrective-action, and change processes where they apply. A discussion about capacity does not change a requirement or authorize someone to postpone required work.

Then make each proposed improvement specific enough to compare. What problem does it address? What supported consequence would continuing that problem have? What needs to happen first? Which people and decisions does the work depend on? Keep unknown impact or effort visibly unknown rather than filling a comparison with invented certainty.

In the fictional example, making the existing authorized guidance easier to find may be useful before asking colleagues to trial revised wording. That dependency deserves a conversation. It does not establish the order by itself or turn the coordinator's suggestion into an approved plan.

Leave a priority note people can use

Use five prompts to preserve the decision and the work around it:

Competing work: Describe the improvements under consideration, their purpose, and the supported consequences of the current condition. Keep the scope and limits of each observation clear. Link authorized participants to the approved references instead of copying evidence into a general planning note.

Constraints: Identify applicable obligations and deadlines, dependencies, required approvals, capacity, and uncertainty. Capacity informs the plan; it does not waive obligations. Route a conflict that the group cannot resolve to the person with the appropriate authority.

Decision owner: Confirm who can agree the order and who has accepted the resulting actions. Preserve decisions assigned to other roles. A participant's helpful suggestion or a name in a note does not establish authority, acceptance, or permission to defer work.

Agreed order: Record the supported decision and its rationale, including dependencies and what remains unresolved. Distinguish a proposed sequence from an accepted one. Keep work awaiting attention visible, with its owner and appropriate handling through the normal process.

Return point: Record when or under what relevant condition the order should be reconsidered. A changed deadline, new information, or a failed dependency may need an earlier decision. Follow existing required intervals and escalation routes. This note creates no new PCI frequency.

Use the note to support the actual work record. It does not replace a formal risk decision, approval, corrective-action record, or required procedure. Where acceptance or information is missing, say so and agree how the question will return.

Explain why something comes next

A useful rationale might identify a necessary dependency, a supported consequence, or an authorized commitment. It should give the next participant enough context to understand the choice. A simple numerical score cannot resolve an obligation, confer authority, or establish that known issues may wait.

If the available capacity cannot meet an applicable commitment, make that conflict visible promptly through the established route. Preserve any decision that remains pending. An agreed order is useful only when the people carrying it out understand both the next action and the limits of the agreement.

Try a small priority conversation

Use three fictional improvements and role placeholders. Write one priority note with the five prompts. Add an invented dependency and an unresolved approval. Ask a partner to explain the proposed order and identify who must decide before it becomes an accepted plan.

Revise any wording that implies unsupported authority, a waived obligation, or completed work. Keep the pending integration decision separate. This optional practice uses no real evidence, sets no PCI activity interval, and promises no assessment outcome.

Good prioritization leaves people with a reasoned next step, an accepted decision route, and a way to reconsider when the facts change.

Explore the free Program Maintenance guide
https://thrivepci.com/training/free/program-maintenance/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=thrivepci_newsletter_14_2026_11&utm_content=newsletter_14

## Prioritize improvements with the context intact

Several useful improvements can compete for the same contributors. What would help your team agree the next step without losing the context?

Issue fourteen of The Zen of PCI explores five prompts: Competing work, Constraints, Decision owner, Agreed order, and Return point.

Our fictional supplier integration brings together clearer handoff wording, findable guidance, and another process improvement. The live integration decision remains pending. A successful placeholder check has not approved a rollout or decided what may wait.

Begin with applicable obligations, deadlines, known issues, and escalation needs. Then compare consequences, dependencies, capacity, and uncertainty through the proper decision route.

Which part of your next priority conversation needs to become clearer: the competing work, the constraints, the authority to decide, or the reason to revisit the order?

Explore the free Program Maintenance guide
https://thrivepci.com/training/free/program-maintenance/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=thrivepci_newsletter_14_2026_11&utm_content=post_announcement

## Make the constraints visible before choosing an order

A capacity conversation becomes more useful when the constraints are visible.

Identify applicable obligations and deadlines, dependencies, required approvals, and known issues that need their established handling or escalation route. Then consider what the available people can realistically carry out.

Capacity informs a plan. It does not waive a requirement or give a coordinator permission to postpone required work. If a commitment and the available capacity conflict, bring that conflict to the appropriate authority through the normal process.

For discretionary improvements, keep unknown impact and effort visibly unknown. Avoid giving an invented number the appearance of a supported decision.

What constraint would someone need to understand before they could responsibly agree the order of your team's next preparation improvements?

Explore the free Program Maintenance guide
https://thrivepci.com/training/free/program-maintenance/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=thrivepci_newsletter_14_2026_11&utm_content=post_constraints

## A suggested sequence still needs an authorized decision

A coordinator can describe competing improvements and reveal a dependency. The resulting suggestion still needs the proper decision route.

In our fictional example, making current authorized guidance easier to find might help before a trial of revised status wording. That relationship deserves attention. It does not approve the trial or settle the pending integration decision.

Confirm who can agree the order, which approvals remain elsewhere, and who has accepted the actions. Keep a proposed owner or sequence visibly proposed until the relevant agreement is complete.

A name in a note does not establish authority, acceptance, or permission to defer work. Which decision in your current preparation plan needs explicit confirmation before someone treats a suggested order as an agreed one?

Explore the free Program Maintenance guide
https://thrivepci.com/training/free/program-maintenance/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=thrivepci_newsletter_14_2026_11&utm_content=post_owner

## Keep the reason for the order with the work

An agreed order becomes easier to continue when the next person can understand its reason.

Describe the supported consequence, dependency, or authorized commitment behind the choice. Keep applicable obligations and deadlines visible. Preserve the scope of the information used, including important uncertainty.

Then show what remains unresolved and which work is awaiting attention through its normal process. Keep ownership and handling visible instead of letting an item disappear beneath the next action.

A numerical score cannot resolve an obligation, confer decision authority, or establish that a known issue may wait. If the facts change, return through the appropriate route.

Could someone joining your next preparation conversation explain both why one improvement comes next and what still needs a decision?

Explore the free Program Maintenance guide
https://thrivepci.com/training/free/program-maintenance/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=thrivepci_newsletter_14_2026_11&utm_content=post_rationale

## Try a fictional priority conversation

Take three made-up improvements: clearer handoff wording, a better route to current guidance, and an unrelated process improvement. Use role placeholders and no real evidence.

Write five prompts: Competing work, Constraints, Decision owner, Agreed order, and Return point. Add a fictional dependency and an approval that remains unresolved.

Ask a partner to explain the proposed order. Who must decide before it becomes an accepted plan? Which actions have confirmed owners? What change would send the question back through the normal route?

Revise any wording that implies a waived obligation, unsupported authority, or completed work. Keep the pending integration decision separate.

This optional practice introduces no PCI activity interval. It does not replace required work, formal risk decisions, approvals, or assessment procedures.

Explore the free Program Maintenance guide
https://thrivepci.com/training/free/program-maintenance/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=thrivepci_newsletter_14_2026_11&utm_content=post_practice

## Make the next improvement easier to choose responsibly

A useful priority conversation leaves people with more than an ordered list. It preserves the constraints, the authorized decision, the accepted actions, and the reason to return when circumstances change.

The free Program Maintenance guide offers a starting point for considering the continuing work behind preparation. The thrivePCI pilot page provides a free sample and a request-details route for people exploring further training.

Practice with invented examples. Describe competing work, constraints, the decision owner, an agreed order, and a return point. Preserve normal approvals, evidence-handling, and required work.

Requesting details records interest. It does not place an order or enroll you. Training does not promise compliance or an assessment outcome.

Which part of your next priority conversation would benefit from a clearer shared reference?

Try the free sample or request pilot details
https://thrivepci.com/pilot/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=thrivepci_newsletter_14_2026_11&utm_content=post_pilot

## Editorial release suggestions

T+0 = actual publication day for issue fourteen
Day basis: calendar days

T+0 — Newsletter: Prioritize competing improvements with the context intact; Post: Prioritize improvements with the context intact
Publish issue fourteen and introduce five prompts for prioritizing competing improvements responsibly.

T+2 — Post: Make the constraints visible before choosing an order
Make obligations, deadlines, dependencies, capacity, and uncertainty visible.

T+5 — Post: A suggested sequence still needs an authorized decision
Confirm authorized decisions and accepted action ownership.

T+8 — Post: Keep the reason for the order with the work
Preserve the rationale, unresolved questions, and work awaiting attention.

T+12 — Post: Try a fictional priority conversation
Invite a fictional paired priority-note exercise.

T+16 — Post: Make the next improvement easier to choose responsibly
Connect the conversation to the free guide and request-details route.

Scott may adjust offsets for editorial readiness and audience conversation. These are publication suggestions, not PCI control intervals, engagement deadlines or claims about platform algorithm performance.
