Strip Ambiguity From Recommendations
Turn vague recommendations into specific action, owner, time, and confirmation requests.
Pressure exposes vague verbs. Words like consider, revisit, circle back, and monitor can be fine when a team is exploring. They become risky when a decision is needed. The listener has to infer whether the sender means now, later, someone else, or only a general concern. SBAR's Recommendation beat exists to remove that guessing. The four fields of an executable recommendation A pressured recommendation should answer four questions: what action, who owns it, by when, and what confirmation is needed. BLUF puts those fields first when time is tight. SBAR explains why. A readback verifies that the receiver heard the…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in