Old promises, new burdens: conventional and reasonable colleagues renegotiate
How conventional and reasonable colleagues can honour earlier commitments without turning temporary exemptions into permanent privileges.
Conventional and reasonable colleagues can agree a new allocation by separating a commitment people have already relied on from an arrangement that has simply been renewed. The first calls for care during the transition. The second needs a current reason. Reliability need not mean leaving the same people with every additional burden.
This collaboration concerns how long old agreements should hold. Conventional relates to ideas and change; reasonable relates to interests and accommodation. They belong to different dimensions and are not opposites. One person can hold both preferences. Neither label gives someone an automatic right to preservation or authority over allocation.
Conventional: an agreement has a history
A conventional person may value a familiar arrangement because others have organised their work around it. Practical, attached to established approaches and building on experience can describe this preference. An agreement has created expectations, beyond the words on the page.
This contribution protects trust in commitments. An exemption may originally have been granted because a team temporarily took on another task. Looking only at the present allocation could hide that contribution. Asking about the origin can make a seemingly arbitrary advantage understandable.
The pitfall is leaving the original reason unexamined. An exception that once made sense does not automatically suit every subsequent round. Newer colleagues should not silently inherit an indefinite burden either. Continuity becomes more concrete when the actual promise and its duration are clear.
Reasonable: preserving an agreement also has a cost
A reasonable person seeks a workable balance between personal and shared interests. Fair-minded and willing to give and take are useful descriptions. This preference does not require everyone to do exactly the same thing.
Its contribution is showing who now sustains the old arrangement. Exempting one group may require another to cover more often. A rule can provide predictability for its beneficiaries while making everyone else’s workload less predictable. That consequence belongs in the discussion about reliability.
The pitfall is turning an earlier promise into a bargaining chip too quickly. A new equal split may look tidy on paper while disrupting plans made on the strength of a confirmed agreement. Negotiating the next period and silently withdrawing a current commitment are different actions. Each needs an explicit answer.
The articles on introducing change with a conventional person and negotiating with a reasonable person explain the individual preferences. Here the particular issue is the boundary between an existing promise and a future entitlement.
Exceptions can have different standing
| Statement | Possible concern | Question to settle |
|---|---|---|
| “We already agreed this” | Plans rely on a specific commitment | What was confirmed, and for how long? |
| “It needs to be fairer now” | Others keep absorbing the extra work | Who carries which recurring burden? |
| “It was allowed last time” | A temporary exception has become routine | Does its original reason still apply? |
| “Let’s split it halfway” | A quick compromise avoids the difficult issue | Can the burden be divided, and what remains uncovered? |
Preferences do not establish motives. Defending an agreement does not prove selfishness; reopening it does not prove unreliability. Establish the actual arrangement before judging character.
Example: exemption from a monthly stock count
In this fictional situation, two teams share a monthly stock count. One team is exempt while clearing an archive of old records. That project has finished, but the exemption remains in the new rota. The other team still does every count.
A contribution focused on continuity asks what was promised. The confirmation email ties the exemption to the archive project. Separately, the next two counts have already been scheduled without the exempt team. A reasonable assessment shows the current burden: the temporary contribution has ended, while the counts keep recurring.
The colleagues keep both facts in view. They honour the two scheduled counts and agree a shared allocation for the period that follows. This gives the transition a boundary. The earlier arrangement is not retrospectively dismissed as unfair, but neither does it create unlimited exemption.
For the new allocation, counting turns is insufficient. A count may take longer when more stock arrives. Both teams agree how to account for extra counting work and who arranges cover for absences. A swap applies to one named count; it does not establish permanent exemption. Responsibility and availability determine who prepares the rota, rather than a personality label.
If clearing the archive still requires demonstrable work, that remaining effort must enter the discussion. The example therefore does not prescribe ending all exceptions after two rounds. The transition must fit the actual commitment and remaining workload.
Three agreements for a dependable transition
- Separate a promise from repetition. Recover the specific reason and duration of the exemption. Repeated use alone does not establish an indefinite agreement.
- Name what is being protected now. Record which confirmed arrangements stand and which round starts the new allocation. Do not let “for now” conceal endless renewal.
- Give a new exception boundaries. Tie it to a task, period or condition and identify who carries the additional work. An occasional swap changes the underlying arrangement only when explicitly agreed.
Comparing personal user guides can help discuss continuity separately from balancing interests. Personal User Guide for work offers a shared vocabulary. The useful joint question is: which expectation still deserves protection, and which burden needs a new allocation from now on?
Comments
No comments yet. Share the first one.