In a sales training session, we used four colour labels to start a discussion about communication. We also tried placing familiar customers into different roles. One observation stayed with me: behaviour that looks like personality may also reflect the responsibility someone is carrying at that moment.
Salespeople remember reactions: someone sounds impatient, keeps asking for details, pushes on price or avoids giving approval. We start forming an impression of the person. From their side, however, our reply may be an input they need to complete another piece of work.
That gives me a practical starting point for the next conversation: find out which result this person needs to take responsibility for.
First, understand the task behind the question
The same question—“Why can’t this proposal be confirmed yet?”—can mean different things in different roles.
A buyer may need to explain the supplier choice and compare options on equivalent terms. A quality colleague may still need test records and acceptance criteria. A project lead may need to know which unresolved issue affects the next step.
The examples below illustrate the method. They do not describe actual customers or imply that everyone in a role thinks alike.
| What I hear | The task worth checking | What sales can provide |
|---|---|---|
| Repeated requests for a lower price | Comparing equivalent offers or explaining a selection | Specifications, quantity conditions, scope and differences together |
| Repeated questions about sample details | Making an acceptance decision against clear criteria | Sample revision, evaluation requirements and available validation records |
| An urgent request for a firm date | Coordinating the next activity or reporting project impact | Confirmed milestones, open issues and the next feedback time |
These are explanations to verify. A buyer may care most about supply continuity; a quality colleague may be coordinating timing. A job title helps me formulate a question. The person’s answer determines the next action.
Replace a personality judgement with three questions
Calling someone “demanding” gives me little help with the next reply. Understanding their task tells me what information to prepare.
When a conversation stalls, I want to establish three things:
- What needs to be confirmed this time? The option, sample acceptance or the next activity?
- What evidence or input is still missing? A comparison, validation records or an internally achievable plan?
- Who makes the decision, and how should I organise the information? My contact may gather inputs while someone else gives final approval.
For example, when someone says, “Just give me a firm date,” I could respond:
Which milestone do you need to confirm: sample completion, quality release or actual dispatch? What we have confirmed is… What still needs checking is… I will report the findings by the agreed time. If you need an internal update, I can organise it into a one-page milestone summary.
This addresses their task while preserving the limits of what we know. Urgency does not justify skipping checks or making an unsupported commitment.
Organise the same facts around the recipient’s task
Once the responsibility is clearer, I can change how I present the information.
For someone comparing options, show equivalent conditions and differences. For someone assessing risk, show criteria, validation evidence and unresolved items. For someone moving the project forward, show impacts, possible actions and who needs to confirm them.
The same person’s priorities may also change with the situation. They may welcome open exploration early in development and ask detailed questions at sign-off. I need to check the current task instead of interpreting every later reaction through my first impression.
However I organise the reply, the facts, unknowns and authority limits stay consistent. Understanding what someone needs to advance helps me route the issue to the right person. Decisions beyond their authority still need confirmation from the responsible owner.
Let a change of role change the reply in the next exercise
The role-play we tried suggested a useful follow-up exercise: give everyone the same fictional packaging change, ask them to prepare questions from purchasing, quality and project coordination perspectives, then have sales adjust the response.
Each round would check only three things: did the salesperson understand the recipient’s task, provide the information needed to move forward and leave a clear next step?
If a reply stays identical for every role, it is worth asking whether we have merely described the situation without helping the recipient make a judgement.
The colours gave us a memorable way into the training discussion. The habit I want to carry into daily work is this: when a reaction is hard to understand, first ask what the person needs to accomplish now and what useful input I can provide.
Companion note: A four-colour communication exercise: from styles to the customer’s job
Based on an observation from a sales training role-play. Colour labels are prompts for discussion, not a way to classify customers or assess individual ability. Role-based interpretations remain hypotheses to check. The table, wording and proposed follow-up exercise are generalised examples without identifiable customer, personal or project details.