I casually mentioned that we should revisit some spreadsheets from older marketing campaigns.
There were leads we had been unable to reach at the time. Organizing those records and making another attempt might uncover a few opportunities.
Later, I discovered that the team had put aside what they were doing and started working through every lead, one by one, going back two years.
A passing suggestion had become a substantial assignment.
The team was acting on something I had raised. But the scale of the response exposed how much meaning could be left unstated in a simple sentence.
I had mentioned an opportunity.
They had rearranged their priorities around it.
Your authority travels with your words.
A leader can be thinking aloud while the person listening believes a decision has been made.
“We should look into this” may sound exploratory to the speaker. To someone reporting to that person, it can sound like the next assignment.
The employee may assume the leader has already considered the existing workload and decided that this new task deserves attention first.
That assumption becomes particularly costly when the task has no clear boundaries.
In this case, “older campaigns” could mean a small sample from one previous campaign or a complete review of two years of records.
“Try again” could mean testing whether another attempt is worthwhile or systematically working through every unanswered lead.
The broad idea was understandable. Its priority, scale, and stopping point were open to interpretation.
A task can be clear while its place in the workload is unclear.
Leaders often explain what they want considered without explaining what should happen to the work already underway.
That leaves the employee to decide whether the new request replaces, delays, or follows existing responsibilities.
When the request comes from someone with authority, giving it immediate attention can feel like the safest choice.
But a team cannot make sound priority decisions if every new comment appears to override the previous plan.
A useful discipline is to communicate four things whenever an idea could create meaningful work.
- Its status. Are we considering an idea, investigating its potential, or proceeding with a decision?
- Its priority. Should this begin now? What, if anything, should move down the list?
- Its scope. How far should the person go? Define the first useful step before opening an unlimited assignment.
- Its checkpoint. When should the person return with findings before committing more time?
For the older leads, a clearer instruction could have sounded like this:
“This is an idea worth exploring. Keep the current priorities in place. First, review a small sample of the older unanswered leads and bring me a recommendation on whether a wider effort makes sense. Let’s agree on the scope and time available before starting.”
That wording gives the opportunity a place in the workload and a boundary around the initial effort.
Employees also have a useful question to ask.
“Should this replace something already on my list, and how far do you want me to take it?”
That question becomes especially valuable when a request could expand into hours or days of work.
It allows the employee to move forward with a clearer understanding of the decision being made.
The leader still carries responsibility for making the intended priority explicit. People should not have to infer it from tone, enthusiasm, or how casually a comment was delivered.
The greater your authority, the more carefully you need to distinguish between an interesting possibility and work you are asking someone to perform.
Your sentence may take ten seconds.
The assignment someone hears may occupy the rest of their week.
Which passing suggestion might your team currently be treating as a priority?