In a sales training session, we started with the four-colour framework in Surrounded by Idiots, then tried placing customers into different roles. The opening question was how salespeople could adapt their communication to different styles. The exercise raised another question: how much of the “colour” we see reflects a personal preference, and how much reflects the work someone needs to complete?

This note first explains how we can use the colours to observe communication, then revisits our role-play attempt and the observation it prompted. The business examples are independently written fictional exercises. They are neither actual customer conversations nor a transcript of the session.

The basic idea: people may listen for different information first

Thomas Erikson uses red, yellow, green and blue to describe four behavioural and communication styles in Surrounded by Idiots. The author connects these categories to a DISC-related framework. We retain the colour names as prompts for discussion. See the publisher’s book introduction and the publisher’s extract from another book by the author for this background.

For our work exercise, I translate them into four possible entry points: results, possibilities, stability and evidence. This is an action-oriented shorthand, not a formal assessment. One email is insufficient to establish someone’s fixed personality.

Red: start with the result and the choices

Red prompts me to notice whether the recipient wants the conclusion, available options and the decision owner quickly.

A conversation can stall when sales starts with the background, describes every difficulty and only then explains what can be done. The recipient interrupts: “Which option do you recommend?” Sales may feel that the explanation was disregarded; the recipient may still be waiting for information they can use to decide.

I would put the conclusion first, followed by choices and constraints: “There are two routes. Keeping the current requirements needs a resource check. Accepting some changes would allow a feasibility review. Today’s decision is which requirement can be discussed.” The supporting information follows.

The aim is a clearer decision. A concise reply must retain risks; sounding decisive does not justify an unverified price or delivery commitment.

Yellow: understand the intended experience, then narrow the direction

Yellow prompts me to notice whether the recipient is exploring ideas, seeking possibilities or looking for someone to understand the value of a concept.

Responding to every new idea with “impossible”, “too expensive” or “we haven’t done that before” can stop exploration early. Agreeing enthusiastically with everything creates a different problem: many directions and no clear starting point.

I would first ask, “Which part of the user experience should this idea improve?” Then bring the discussion to something that can be compared or tested: “Let’s retain these two directions, identify the information and validation each needs, then decide which to pursue.”

Acknowledging an idea should help turn it into a workable task. An appealing concept does not establish technical feasibility.

Green: explain the change and make the next steps predictable

Green prompts me to notice whether the recipient is concerned about coordination, who a change affects and how much of the existing arrangement can remain.

Sales may see a minor adjustment. The recipient may need to rearrange stock, production, inspection or receipt. “We’ll make a small change; it should be fine” leaves all that additional work unexplained.

I would state the scope, affected activities, transition arrangements and review point: “This round proposes assessing this change only. Other requirements retain their confirmed revision. The responsible owners will check the affected information and validation before a decision on switching.”

A predictable arrangement is more useful than repeated reassurance. Risks and open questions still need to remain visible.

Blue: provide a basis that can be checked

Blue prompts me to notice whether the recipient needs definitions, revisions, criteria and evidence before making a judgement.

“The sample has improved” reports progress. The recipient may still need to know what improved, which sample revision was compared, which requirements were checked and what remains untested. That gap can leave sales wondering why the questions continue after an explanation.

I would separate the current revision, checks performed, findings and unfinished work. Where evidence is missing, mark the point as unverified and agree who will supply it.

Detail should support a particular judgement. A large collection of documents can still leave the recipient unable to decide if it does not connect the evidence to the relevant requirement.

Preparing the exercise: express the same situation in different ways

The preparation conversation included several activity designs: identifying a concern from a sentence, rewriting one message for four styles, using customer role cards and reflecting on a difficult conversation. These were preparation proposals. The available record does not establish that every activity was completed, so I do not present them as the session’s actual sequence.

Their shared practice principle is simple: keep the business facts consistent while changing the order, emphasis and decision requested.

Consider an independently written fictional scenario: a customer proposes a packaging change, but the relevant validation is incomplete. Sales cannot yet confirm a production switch.

Entry pointAn emphasis to try
Red: results and choicesState that a switch cannot yet be confirmed. Clarify whether to retain the existing option or continue assessing the change, with the conditions for each route.
Yellow: direction and possibilitiesClarify the desired user experience, retain useful options and select a validation question.
Green: stability and coordinationExplain what stays unchanged, which activities are affected and when readiness to switch will be reviewed.
Blue: criteria and evidenceShow the revision, validation requirements, known findings and missing records needed for confirmation.

Every version must retain the fact that validation is incomplete. Describing four different project states to suit four styles would defeat the exercise.

What we tried: placing customers into roles

We did try placing customers into different roles. This moved the discussion beyond how someone usually speaks towards why they might ask that question from that position.

In my feedback after the training, I observed that the apparent colour was not necessarily determined by personality; the job could have a substantial influence. For this article, I would express that as an observation to keep checking: communication can reflect personal preference, role responsibility and the current task together.

To protect identities, I do not list which customer was associated with a colour or reproduce personal evaluations. The following generalised questions illustrate how role-taking can deepen the discussion:

  • From purchasing: might this person need an equivalent comparison and a defensible reason for the selection?
  • From quality: might they need acceptance evidence before taking responsibility for a confirmation?
  • From project coordination: might they need timing and open issues to organise the next activity?

These questions assign no fixed colour to a job. They suggest different possible reasons for the same question. A title such as buyer or quality manager is also insufficient to establish someone’s actual task.

From guessing a colour to confirming an action

If the exercise ends at guessing the colour, salespeople may simply acquire another vocabulary for describing people. The useful next step is to turn an observation into a question that can be checked, then a specific action.

Using the same fictional change scenario:

An easy initial judgementA question to checkUseful information to provide next
They keep rushing us and just want it overDo you need decision options or an arrangement for the next activity?Available routes, constraints or a milestone summary
They pick at details and won’t approveWhich requirement still lacks evidence and prevents confirmation?Relevant criteria, revision and validation records
They keep changing ideas without directionWhich part of the user experience matters most to retain?A narrower direction and a validation question
They resist change and won’t cooperateWhich arrangements under your responsibility would this change affect?Impact scope, transition plan and review points

A follow-up exercise could place the same fictional customer in different tasks: exploring an idea, comparing options, checking validation and planning a switch. In each round, sales would first clarify the current task, then adapt the response. This is a proposed next exercise arising from the observation, not a completed training outcome.

I would assess three things: whether the salesperson understood the immediate task, supplied useful inputs and left a clear next step with an owner, timing and deliverable. Agreement about the colour can remain a discussion topic.

This attempt made me willing to keep the colours as an entry point for training. They make associations easy and help people start discussing communication experiences. The habit that needs practice comes after the association: what supports my explanation of this person’s behaviour, and will my reply help them complete their work?

Related note: Is the customer being difficult—or doing their job?


Based on the training preparation conversation and my feedback on the role-play attempt. No attendance figures, verbatim exchanges, votes, scores, specific group arrangements or training outcomes have been reconstructed. Customer, company and personal identities, commercial figures and identifiable project details are omitted. Examples are generalised exercises. The colours support communication reflection, not personality diagnosis, ability assessment or fixed job classifications.