When two conventional people work together: one preference, different habits

Two conventional people can work well together when they explain which habits each wants to preserve and why. A shared preference for familiar methods does not mean that both know the same way of working. Collaboration becomes clearer when experience is explained, the value behind a routine is identified and a common agreement is established. A difference in approach then need not become a dispute about who has always done things correctly.

For this combination, familiarity can be both an advantage and a blind spot. Both colleagues may appreciate something that is practical and has proved useful before. Agreement can follow quickly. Yet “the way we always do it” may refer to something different on each side of the table.

What does conventional mean for both colleagues?

In the personal guide, conventional describes a preference concerning ideas and change. It emphasises familiar possibilities, concrete applications and building on experience. Words such as tradition-minded, practical and comfortable with established methods can fit. This is a preference at work, not a political position or a judgement about intelligence.

ConventionalCuriousProgressive

Sharing a position on this scale does not mean that both people plan equally carefully, make contact equally easily or experience the same amount of stress. Those subjects have their own place in the guide. Expertise, authority and the quality of someone's work cannot be inferred from the word conventional either.

The explanation of Big Five openness provides the background to this preference. The introductory article about introducing change with a conventional person explores how a new approach can be assessed. Two conventional colleagues face an additional question: what happens when both want to protect an established method, but not the same one?

Shared experience can support the work

A familiar routine can contain practical knowledge that is absent from the instructions. Why does a request from that particular customer still receive a telephone confirmation? Why is a certain field mandatory? Why is an exception processed only after a second check? The answers can reveal an earlier mistake, agreement or dependency.

Two colleagues who favour established methods can give each other room to explore those reasons. A new approach does not have to be proposed constantly for the conversation to be useful. Existing knowledge becomes usable when both understand what quality it protects.

There is a limit to that reassurance. Experience from the same environment is not a second, independent confirmation. If both learned a step from the same predecessor, that does not establish whether the step is still necessary today. Asking when it last prevented a problem provides more information than two people nodding in agreement.

What is familiar to one can be new to the other

A colleague who groups files by customer may want to keep the complete history together. A colleague who organises them by the date a response is due may want to see which requests are waiting. Both are protecting an overview. Nevertheless, one arrangement may feel unusable to the other.

From the first perspective, a new arrangement could hide relevant exceptions. From the second, keeping files grouped by customer could leave outstanding work out of sight. Both concerns deserve an explanation. Neither proves that the other person is less practical or less committed.

It helps to separate three questions: what must be preserved, which action currently achieves that and which action is simply familiar? Customer history must remain available, for example. That does not automatically require one person's own folder structure. Visibility of outstanding work does not necessarily require a second set of records either.

Only after that explanation can the colleagues decide what needs to be organised jointly. A preference for the familiar gives neither existing method priority.

Where two conventional approaches can clash

The table suggests possible conversations, not fixed behaviour among conventional people. A second check may be required for a substantive reason. Two records may serve different purposes. The function of an action needs to be understood before it is treated as an unnecessary habit.

Example: two familiar records, one unclear status

Two colleagues start managing a customer inbox together. One previously used a spreadsheet; the other used categories in the mailbox. Both understand their own method, so they agree to keep using both for the time being.

A week later, a request is marked as resolved in the spreadsheet while the mailbox suggests that a reply is still missing. One colleague helped the customer by telephone but recorded the contact only in their own overview. The other sends another message. The customer is left with the impression that the earlier conversation was not known about.

The problem here is not that two conventional people are unwilling to change. They lack a shared definition of resolved and an agreement about where that status is recorded. Both existing methods could have been useful before without forming one reliable process together.

The colleagues therefore choose one existing record as their shared source for status information. The choice depends on access, required information and the workflow. A resolved status must now include what answer was given and where it can be found. A personal task list can remain as a memory aid, but it no longer determines whether a request is open or closed.

One colleague gives up a familiar way of managing status; the other may give up an established way of taking notes. Both contributions need to remain visible: customer history stays accessible and outstanding work stays identifiable. The aim is an agreement that both can use, rather than a winner among two old systems.

Unspoken agreement deserves a check

Especially when a conversation produces little discussion, one concrete request can reveal a difference. Both colleagues separately explain when they would consider it complete, what they would still check and whom they would ask about anything unclear. Their answers are then compared.

This is different from asking each other to prove that they remember the instructions. The exercise reveals knowledge that still exists only in someone's head. “A regular customer receives the usual exception” becomes transferable only when the exception, its purpose and its conditions are clear.

Someone who joins later also needs to be able to use the agreement. A colleague unfamiliar with the routine can point out where an explanation is missing. No particular personality preference is required. In this case, unfamiliarity with the procedure provides useful information.

Four agreements for shared confidence

1. The reason behind a habit is explained. Both identify the risk, customer agreement or necessary information it protects. “We have always done it this way” starts that explanation.
2. Shared work has a shared source. When information conflicts, it is clear which record takes precedence. Personal tools must not quietly replace that agreement.
3. A deviation is handled visibly. A practical workaround is recorded with its reason. If it is needed repeatedly, the instructions are explicitly reconsidered rather than allowing a second, unwritten procedure to emerge.
4. An existing agreement has a trigger for review. A new customer requirement, a discontinued system or a recurring error prompts a fresh assessment. The trigger and the authority to decide are agreed in advance.

Sometimes a mandatory procedure or an established system already limits the choice. It must then be clear who decides and where both colleagues still have influence. A personality conversation cannot replace a missing decision.

A shared preference needs a shared explanation

When two conventional people work together, their strength need not lie in constantly reinventing the work. They can find value in understanding, passing on and maintaining what is useful. That requires familiarity to be explained and allows both colleagues to have different habits without questioning their commitment.

A comparison of personal guides can show the shared preference alongside differences in other areas. A useful next step is to take one existing working agreement and have both colleagues explain what it means in practice. Personal User Guide for work provides language for that conversation, while the actual task determines which process is needed.