When colleagues approach the same task differently, it is tempting to explain the disagreement with a personality label. One person wants to start; another asks for more detail. But before deciding that someone is an “active” or “reactive” type, ask what the situation requires and what information each person has.
Meta-programs are discussed within neuro-linguistic programming (NLP) as patterns or preferences in how people attend to information and respond. If you use that vocabulary, treat it as a prompt for questions—not a way to read minds, classify employees or predict performance.
Separate an interesting framework from evidence
A systematic review of NLP in organizational settings included seven studies and reported some positive psychological outcomes, but raised concerns about research quality and overstated benefits. That does not establish that an interaction-style label can identify the best person for a job or reliably improve a team’s results.
My practical recommendation is to start with observable work, ask people directly about their needs, and test a clearly defined change. A useful conversation does not require agreement with an entire personality framework.
Ask about the situation, not the type
The same person may move quickly on a familiar task and seek guidance on an unfamiliar one. Before interpreting behaviour as a fixed preference, explore the context:
- Clarity: What outcome are we trying to achieve, and what does good work look like?
- Authority: What can you decide yourself, and what needs approval?
- Information: What detail is missing before you can act?
- Risk: What could go wrong, and which decisions can be reversed?
- Support: What training, time or resources would help?
“What would help you move this forward?” is more constructive than “Why are you so reactive?” It also leaves room for a genuine process problem that a label might conceal.
Turn preferences into working agreements
Invite colleagues to describe how they prefer to receive information and contribute. Some may welcome a written brief before a discussion; others may want a short conversation followed by a summary. Do not infer these preferences from appearance, eye contact, background or one meeting.
Then agree on a shared method that meets the work’s requirements. For example, circulate the decision question before a meeting, offer written input, name the decision owner and record the next action. Preferences inform the agreement; they do not excuse missed commitments or remove opportunities to develop.
For a wider starting point, see clearer conversations and team working agreements.
A small team experiment
This is a hypothetical example, not a client case study. A service team repeatedly delays quotations. The manager thinks one colleague lacks initiative; the colleague says pricing authority is unclear.
- Review a few recent delays together, without assigning personality types.
- Write down which quotations the colleague may approve and which exceptions need review.
- Agree what information an exception request must contain and who responds.
- Test the process for two weeks, with a route to escalate urgent or unusual cases.
- Review turnaround time, avoidable rework and both people’s experience.
If delays remain, investigate capacity, training and other dependencies. Do not treat an unsuccessful experiment as proof that the person has the wrong personality.
Keep communication respectful
Understanding someone is not the same as steering them covertly. Avoid unwanted touch, supposed “anchoring” tricks or assumptions that body language reveals hidden motives. In negotiation, make your proposal clear, ask what matters to the other party, check your understanding and leave room for disagreement.
Use practical listening and communication skills to clarify meaning. If you notice hesitation, ask a neutral question rather than declaring what the person must be thinking.
What about hiring and development?
Do not use informal meta-program labels as a hiring filter or a ceiling on someone’s potential. Define the work, examine relevant evidence of skills and use an appropriate, consistent assessment process. For formal selection or assessment decisions, seek qualified HR or assessment support.
For development, agree on a specific behaviour to practise and useful feedback. Keep reflection voluntary and avoid collecting personal disclosures that are not needed for the work.
Choose one conversation to improve
Start with one recurring misunderstanding. Ask what each person needs, make the next agreement explicit and review whether it helps. The aim is clearer collaboration—not a more elaborate set of labels.
If you would like support with a leadership or team challenge, explore executive coaching or book a free 15-minute fit call. You can also apply for the two-week free coaching offer. Applications are reviewed manually; completing the assessment does not guarantee acceptance.
