“Let’s circle back” can be a useful way to pause a conversation. But when the real question is Can we make a decision?, it often leaves everyone in the same place: talking about the topic again next week.
A clearer approach is to name the decision, offer a recommendation, and ask the right person for an answer by a realistic time. If the answer can’t be made yet, agree on what’s missing and who will get it. That way, “later” becomes a plan rather than a hiding place.
Why “Let’s Circle Back” Goes in Circles
Imagine a meeting about two designs for a new website. Everyone shares an opinion. Someone says, “Let’s circle back,” and the meeting ends. Was the team waiting for customer feedback? Did the manager need to choose? Was someone supposed to revise a design? Nobody is quite sure.
The phrase isn’t the villain. Sometimes a discussion genuinely needs more time. The problem is that “circle back” describes another conversation, not the outcome that conversation needs to produce.
A useful question is: What would have to happen for this topic to stop returning to the agenda? Perhaps someone needs to approve a draft, choose between options, or identify a missing fact. Once you know which, you can ask for that instead.
This is also why sounding smarter at work rarely requires fancier words. It requires making the point easy to find. If your request tends to get buried under background, try leading with the point.
The Four Parts of a Good Decision Request
You don’t need to deliver a miniature presentation every time you want an answer. Most requests need four things:
- The decision: What, specifically, needs to be chosen or approved?
- The options or recommendation: What are the realistic paths, and which do you suggest?
- The decision-maker: Who has the authority to make the call?
- The timing: When is an answer needed, and what depends on it?
Put them together:
“We need to choose a design for the homepage. I recommend option B because it uses the approved copy and requires fewer changes. Maya, can you approve B or tell us what needs to change by Thursday at noon? Design needs the answer to prepare the final files.”
That’s longer than “Let’s circle back,” but it saves the group from having to guess what comes next.
Asking for a decision is not the same as demanding agreement. “Can you approve B or tell us what needs to change?” gives the other person room to raise a concern. It simply makes the question answerable.
In larger groups, confirming who makes the final call matters. Atlassian’s DACI decision-making framework, for example, distinguishes the person who drives a decision from the approver who makes it, as well as people who contribute advice or need to hear the outcome. You don’t have to announce a four-letter framework at lunch; you can just ask, “Who needs to make this call?”
What to Say Instead, Depending on What You Need
There is no magic replacement phrase. Choose words that match the actual obstacle.
When the group is ready to choose
“We’ve discussed both options. Can we choose one now?”
Or, if you have a view:
“My recommendation is option A. Is there a reason we shouldn’t move ahead with it?”
The second question invites a specific objection rather than another round of general impressions.
When you need someone’s approval
“Could you approve the draft by Thursday at 2 p.m., or let me know what you’d like changed?”
Make sure the person you ask can actually approve it. A roomful of enthusiastic agreement won’t help if the decision belongs to someone who wasn’t there.
When a fact is missing
“We can’t choose yet without the cost estimate. Can Jordan get that by Wednesday so Maya can decide on Thursday?”
This is a perfectly good reason to wait. It’s also a much better plan than scheduling a meeting and hoping the estimate appears by magic.
When priorities are the real decision
“We have time to finish one of these this week. Which should take priority?”
Sometimes people are debating how to do the work when they haven’t agreed on which work matters most. Asking the underlying question can spare everyone a remarkably detailed discussion of the wrong thing.
When you’re speaking to a client or manager
“To keep the planned delivery date, we’ll need your choice between A and B by Friday. Would that give you enough time to review them?”
The deadline has a reason, and the question acknowledges the other person’s schedule. If you need help finding that balance, see how to communicate urgency without saying “ASAP”.
If Nobody Can Decide Yet, Decide What Happens Next
A delayed decision is not necessarily a failed meeting. Sometimes the options have changed, an important person needs to weigh in, or the consequences deserve more thought.
Rather than pushing for an answer everyone will regret, ask three smaller questions:
- “What information is missing?”
- “Who will get it or resolve the concern?”
- “When can the decision-maker review it?”
Suppose a team is choosing a venue but hasn’t confirmed accessibility requirements. “Let’s circle back” leaves the concern floating. “Sam will confirm the requirements with the venue by Tuesday; we’ll choose after that” gives it an owner and a next step.
It also helps to separate input from approval. “Does anyone have concerns we should consider?” gathers perspectives. “Maya, are you comfortable approving this?” asks for a decision. Both questions can be useful, but one cannot quietly substitute for the other.
McKinsey’s guidance on decision meetings similarly recommends being clear about whether a meeting is meant to produce a decision, rather than beginning with a broad topic and hoping a decision emerges.
How to Ask in an Email Without Writing a Novel
An email request can be even simpler because the recipient can see the question in front of them. Put the decision near the top, then include only the context needed to answer it.
Subject: Decision needed by Thursday: homepage design
Hi Maya,
Could you choose between homepage designs A and B by Thursday at noon? I recommend B because it uses the approved copy and requires fewer revisions.
If neither works, please tell me the main change you need. Once you decide, I’ll send the direction to the design team.
Notice what the email doesn’t contain: a history of every discussion about the homepage. The MIT Communication Lab’s email guidance likewise advises giving readers a clear action to take within a deadline when you need something from them.
If the deadline is flexible, say so. “Could you decide by Thursday? If you need more time, tell me what would be workable” is more useful—and more courteous—than treating every request like an emergency.
Close the Loop, Even When the Answer Is “Not Yet”
A decision request deserves a clear ending. After a meeting, write down what was decided, who will act on it, and any outstanding question. If no decision was made, record the reason and the agreed next step. Atlassian’s guidance on meeting action items emphasizes a clear owner, task, and target date—details that keep a next step from disappearing into the notes.
If you need to follow up, skip the accusatory “We already discussed this.” Try: “Checking on the homepage decision: can you approve B by Thursday, or is there a change you need first?” For more wording ideas, see how to follow up without sounding passive-aggressive.
You don’t have to ban “Let’s circle back” from your vocabulary. Just don’t let it be the last thing you say. Add the question that moves matters forward: “What do we need to decide, who can decide it, and when?”