When someone on a network marketing team says, "This is how we do it," stop and label what "this" actually is. It may be company policy, a team habit, or one person's preference. Those are three different kinds of guidance, and teaching them as if they carry the same authority creates avoidable confusion.
The practical rule is simple: every instruction should travel with its source and its level of authority.
Company policy controls what the company requires
A company policy is an official requirement or restriction. It may cover product claims, returns, recurring orders, approved materials, compensation, customer data, or distributor conduct.
Do not teach a remembered version when the current document is available. Give the person the document name, where it can be found, and the date you checked it. If the wording is unclear, ask official support instead of filling the gap with team confidence.
Policy answers a narrow question: what does the company require, allow, or prohibit? It does not automatically tell every operator the best way to run a conversation or organize a week.
A team habit is a shared operating choice
A team habit is a method people use because it helps them coordinate. The team may hold a weekly call, use a certain customer follow-up note, or review product questions in a shared meeting.
That can be useful. It is still not company policy.
Say, "Our team uses this method because…" Then name the purpose. Perhaps it prevents unanswered questions, keeps records in one place, or gives new people a repeatable starting point. A team habit should be open to review when it no longer serves that purpose.
This distinction matters because a useful process can become empty theater when people repeat it only because an upline taught it years ago. A method earns its place by helping the work, not by acquiring unofficial authority.
Personal preference belongs to the person
Preference is the lightest category. One person likes morning calls. Another writes follow-up notes immediately. Someone else may prefer a printed checklist to an app.
Teach preference as an option, not a character test. "This works for me" is honest. "Serious people do it this way" turns taste into pressure.
The difference also protects duplication. If a system depends on everyone copying one person's schedule, vocabulary, or personality, it is not truly repeatable. The article on whether a teammate can repeat the system without you explains that test in more detail.
Use a three-line label before teaching a rule
Before giving an instruction, write:
- Source: Where did this instruction come from?
- Authority: Is it policy, team method, or preference?
- Reason: What problem is it meant to prevent or solve?
For policy, include the current official location. For a team method, name the result you will review. For preference, make it clear that another workable choice is allowed.
This takes less than a minute, but it changes the listening experience. The learner knows what must be followed, what can be improved, and what can be adapted.
Correct the label when you learn more
Sometimes a supposed policy turns out to be team folklore. Sometimes a casual practice turns out to be required. Correct the record plainly.
Say what you taught, what the current source shows, and what changes now. Do not protect your image by quietly changing the instruction and pretending it was always clear.
This is the same discipline that separates product education from a product pitch: verified facts, interpretation, preference, and unknowns should not be blended.
People can work with a rule they understand. They cannot make a sound decision when policy, culture, and personality arrive in the same costume. Label the instruction, show its source, and leave room for the right kind of choice.
