OCE.12:4.3 - Perform the working conversation

Choose the smallest conversation that can produce the needed result.

Before shared work, conduct a brief. State the intended result and current conditions. Ask participants to explain their contribution and its limits; identify missing capability, access, time or help. Agree how to raise an objection, report an exception and obtain help. Confirm who can make each decision. Close with the next contribution and the conditions that would stop or change it.

When the situation changes, conduct a huddle. Bring forward the new fact and the affected contribution. Reassess the immediate work, burden and help with the relevant participants. Take decisions about allocation, priority or authority to the person authorized to make them.

For role performance, work with the participant. Clarify the expected result and limits of the assignment, and check the participant’s understanding of them. Discuss how the person’s aims and concerns affect the contribution. Compare observed work with the expected result and assignment limits. Help the person enter the role, maintain attention on its contribution or arrange a handover. Follow the applicable assignment rules and safety requirements when the person leaves or hands over the role. Agree one next contribution or a specific repair and obtain feedback from that work. Difficulty performing a role is insufficient grounds for a judgement about the person’s personality.

After an episode, conduct a task-focused debrief. Reconstruct what happened from the work and evidence. Ask what helped, what failed, which explanation remains uncertain and what should change next. Agree who is responsible for the repair and how its effect will be observed. Protect participants who report error. Keep disciplinary decisions and clinical care with the responsible practitioners.

For a conflict between contributions, make the incompatible requests explicit, with the evidence, consequences for participants and authority needed to change them. A short conversation may settle a limited change: obtain acceptance from those whose work or conditions would change, and take any remaining decision to its responsible decision maker. Use the branch below when a mutually acceptable arrangement still has to be constructed. Agreement to discuss the conflict is only the start of that work.

OCE.12:4.3.1 - Obtain an agreement on incompatible contributions

The immediate result is agreement on who will contribute what and under which conditions, or a specific unresolved condition or refusal. Use this branch when cooperation requires an agreement that has not yet been reached.

Prepare participation and the means to negotiate. Obtain willing participants, time and a safe way to raise objections, consult represented people or decline a proposal. Identify those affected by the proposal, those able to provide its contributions and those authorized to commit them. A representative needs a mandate covering the proposed change; where it is missing, obtain the represented party’s response before treating the contribution as agreed. Include people whose existing work would be displaced, even if they were absent from the first meeting.

Choose a negotiation Method that the participants can use, with a competent facilitator when needed. For example, the CBI Mutual Gains Approach brief explains how to prepare around interests, mandates and alternatives, develop combinations of terms before commitment, discuss reasons for sharing costs and benefits, and arrange follow-through. A team already using the voluntarily adopted protocol described in CB.13 can continue with it under its stated conditions. Confirm that participants can perform the selected Method; obtain qualified help or develop the needed capability under step 4.4, allowing for its time and cost.

Recover the condition behind each objection. Ask which needed result the proposal would prevent or which protected condition it would violate, and what observation or change could answer the concern. Distinguish a required outcome from an assumed means. “The complete interface must be ready by day 20” may combine a need for daily data with an untested assumption that automatic control must arrive in the same release. Confirm this interpretation with the party that set the requirement; only someone authorized to change it may relax it.

Choose the work that can answer the objection. For a disputed technical possibility, obtain evidence from a qualified specialist. An assumed necessary means can be reconsidered with B.5.QD.CF. A dispute about consequences may need D.4 to examine different value premises and develop alternatives. Obtain a missing mandate from the party entitled to grant it. Establish what information participants may share and keep protected information confidential. A relevant condition that is withheld or unknown remains unresolved.

Construct and investigate whole proposals. For each condition, ask what else could supply the needed result: change the proposed scope, timing, performer, support or distribution of burden. Combine compatible changes into an arrangement that each party can assess, while retaining the applicable technical, safety and institutional constraints. Explore proposals before asking for commitments. Include what each party can feasibly do if no agreement is reached; refusal can remain preferable to an unsupported commitment.

When acceptability depends on an unknown, formulate the question that would change the choice and obtain the contribution needed to answer it. A proposed read-only release may need an engineering probe and an offer of support from the provider. Agree the probe’s question and cost. Before doing it, assess how conducting it could affect participants and ongoing work, agree the conditions needed to protect them, and obtain the required permission. Permission for the probe does not authorize introduction. Return the evidence with its limits. Then revise the whole proposal: a support offer can change price, local workload and displaced work as well as technical feasibility. If the probe rules out the release, revise or reject that option.

Make the burden and terms discussable. Show what each participant would receive, provide, pay, defer or risk under the same proposed arrangement. Use reasons the parties can examine, such as measured support demand, protected service capacity and the value of the first usable result. Let them question both the estimates and the proposed distribution. Agreement on how to compare proposals may help, but a favorable combined score does not establish a party’s acceptance.

Estimate the effort and cost of preparation, representation, consultation, facilitation and subject inquiry. Include waiting for replies, implementation, continuing support, monitoring and possible renegotiation; identify the work these activities displace. Resolve contested allocations with the people authorized to decide them. If investigation or negotiation would exceed its authorized effort, obtain a revised allocation, reduce the question or stop.

Obtain acceptance of one complete version. Present the revised scope, contributions, limits, timing, resources and change conditions together. Ask each party, directly or through an authorized representative, whether they accept their contribution and conditions in that arrangement. Distinguish acceptance, conditional acceptance, refusal and an unanswered question. A condition such as “only with funded support” is not satisfied by agreement to seek funding. If an amendment changes another participant’s burden or benefit, return the same amended version to the affected parties; consult the represented people when the mandate no longer covers it.

Keep the accepted terms and remaining questions usable by those who must act. Silence, attendance and a majority’s preference do not establish mutual agreement. Where a party refuses or a necessary condition remains unmet, identify what prevents agreement. The parties can revise the proposal or leave it unagreed. An authorized decision without mutual consent, where available, needs its own grounds and should be presented as that decision.

Return the result to the receiving work and revisit changed conditions. Give those responsible for the work that requested cooperation the accepted contributions and conditions, or the unresolved issue. When the agreement concerns an engineered product and the organization that provides it, use OCE.7 to coordinate the product and organization architecture decisions through their constraints and required contributions, with each decision made under its own authority. Use the agreed terms and remaining uncertainty in SYSE.6 when deciding the engineering architecture, or in SYSE.24 when choosing how to obtain an engineering result. Where a promise is being established or changed, use OPS.13 to establish its accepted terms. Agreement alone supplies neither technical evidence nor permission for introduction, and does not establish that the work has been performed.

Agree how a consequential change will reach the affected parties and who will obtain their responses. If promised support disappears, identify which accepted contributions depended on it, obtain feasible replacements and return the altered whole for acceptance. Keep independent results whose conditions still hold. If no replacement supports the proposed use, return the dependent choice to its decision maker, the unmet support need to the person responsible for arranging it, and any affected promise to the party authorized to change it. Until an authorized revision occurs, the existing commitment still applies.

OCE.12:4.3.2 - Construct a usable result in a facilitated discussion

Use this branch when the discussion must produce an explanation, design or proposal on which subsequent work will depend. Begin with its receiving question. For example: can the modules work together under the agreed load, and what supports that answer? State what the receiver must be able to decide or do with the result. Then choose a way to construct it and obtain the people able to perform that work.

Recover the relevant objects, claims and relations. For the module question, distinguish claims about individual modules from claims about their interaction. Identify the configuration each claim concerns, its supporting observations and the conditions under which they apply. Ask the specialists to examine the dependencies: does one module’s output meet the other’s input requirements, and do the separate tests exercise their joint operation? Combine the answers into an explanation of the proposed whole. Two successful component tests can still leave an interaction unsupported.

Work through a missing or disputed relation with the contributor who can resolve it. Evidence from an earlier configuration requires an applicability judgement; an untested interaction may require a joint test, a narrower claim or a revised design. Develop those alternatives far enough that the receiving decision maker can compare their consequences. Retain uncertainty when the needed result cannot yet be obtained.

An integrator constructs the connected account with the domain specialists. A facilitator can perform this contribution too when their competence supports it; otherwise arrange for someone who can. Facilitation helps participants hear objections, inspect evidence and work together. It does not make their separate statements into a justified whole merely by collecting them.

An agenda or canvas can help expose gaps; follow the reasoning the problem requires. Before relying on the result, trace the receiving decision through the explanation, and change one consequential condition to see which conclusions or actions must return for reconsideration. If participants can only repeat their individual views, obtain the missing construction or domain contribution. Another round of speaking turns may leave the same gap.

Apply the receiving-use question to coaching as well: which later action should improve, how will the proposed help address the observed difficulty, and what observation could show that it did? A reflective conversation can supply that help. An assignment conflict still needs a work-allocation decision, and a technical uncertainty still needs the relevant professional answer.

OCE.12:4.3.3 - Prepare a proposal for decision and first use

Use this branch when people need to examine a proposed organizational change before committing to it, or an agreed change has yet to become a workable first contribution. Begin with the result another person will use. Follow how the proposed practice would produce it: which working product changes, who prepares and receives it, and which tools, access, learning or help must be available. Retain an adequate existing arrangement. A short brief may suffice when the proposal and conditions are already settled.

Bring the needed judgement into preparation. Ask the decision maker and affected participants whose advice they need to assess the proposal and which question that person could help answer. A trusted former colleague, peer or specialist outside the formal project may influence the decision. Offer an appropriate explanation or permitted example through an agreed contact; let the recipient consult privately when that is preferable. Seek the grounds of the returned concern, including what would answer it. An adviser may clarify a consequence without speaking for the people who bear it or having authority to commit their work.

Concentrate on advice and affected interests that could change the decision. A credible technical objection needs the relevant specialist’s answer; a concern about burden needs examination of the work and its receivers. When a material question remains confidential or inaccessible, agree a narrower way to examine it or retain the uncertainty. Exhaustively discovering everyone’s informal contacts is neither necessary nor a condition for proceeding.

Make the proposed work and its consequences examinable. Explain how the proposed arrangement would produce the needed result and compare it with the present way of working. Use one representative task, its working products and the receiving decision. Let participants expose extra operations, missing inputs, displaced work and consequences they cannot accept. Separate a misunderstanding from a true disadvantage or an unsupported promise of benefit. Repair the explanation through dialogue, obtain the missing domain answer through 4.3.2, or revise the proposal. An understood proposal can still be declined.

Discuss the contribution and its conditions far enough to know what must be done before bargaining over personal appointments or titles. Include actual competence, authority and available resources whenever they change feasibility; postponing those questions would conceal a defect. Examine consequences for both current service and the change work, using OCE.11 where they compete. Preparation itself needs time for explanation, consultation, trials and revision. Use an adequate answer already available; limit new inquiry to a question whose answer can change the decision enough to warrant that burden.

Obtain a decision on a workable proposal. Where contributions conflict, use 4.3.1 to construct and obtain agreement on the whole arrangement. Identify who can authorize its start and commit each required contribution through OCE.6. If the participants cannot commit a needed resource, take the proposal and its unresolved condition to the person who can; keep the dependent start conditional. An institutional rule may permit a decision despite disagreement. Name that rule and retain the objection instead of reporting mutual consent. When a refused voluntary contribution is necessary, obtain an acceptable alternative or leave that use unagreed.

Keep responsibility for organizing the change distinguishable from responsibility for running and receiving the resulting work; one person can hold both when the arrangement permits it. Make the effective decision, its scope, timing and conditions recoverable in the form the organization uses. A promise to find time or support later leaves that condition outstanding. Authorize only the preparation, trial or use whose conditions are satisfied; retain an unresolved issue, refusal or deferral where they are not.

Make the agreed start mutually visible. Give the people whose actions depend on one another the same accepted proposal and effective decision. In a brief or a suitable shared exchange, let them confirm their contribution, the help available and how an exception will reach someone able to respond. Each needs to know what the others have actually undertaken, including the arrangements for an absent shift or provider. A readable update with the necessary responses can supply this result without a launch meeting. Attendance or silence leaves an unconfirmed contribution unresolved.

Use this exchange to confirm what is settled and expose what changed. A new substantive objection returns to the affected inquiry, agreement or decision; an announcement cannot close it. Identify which work must wait and which preparation can continue under its own conditions. When a revision changes another person’s work or reliance, obtain the affected response and communicate the resulting version before that use. Existing commitments remain effective until their authorized change.

Obtain the first useful handover. Put the working product, access, permitted help and receiving contribution in place. When a checklist supports the occasion, CHK.3 locates its questions where observations and answers can change the work. Use the subject practice’s criteria to produce and check the result; give the receiver the applicable result and unresolved questions. Follow what the receiver can actually do with it. Opening a form or reporting agreement leaves that handover untested.

Arrange a first assisted use when assistance is needed, and retain that condition in the result. A failed attempt may reveal a missing explanation, unavailable means or an unworkable arrangement; return that difficulty to its supplier rather than repeating the announcement. Use OCE.9 when the question is whether the organization can provide the whole capability, and CHK.3 for ordinary later use of the aid. One successful handover can justify its bounded continuation without establishing independent performance, recurring provision or usefulness across the organization.