Say where the understanding came from

It moves the mistake from your head to the space between two people. Thirteen separate conversations say that “I assumed” is heard as jumping to a conclusion without checking, while “my understanding was” or “it was my understanding that” is heard as a communication gap — the email was unclear, the brief changed — and that managers treat the second more kindly; three conversations say the word “assume” carries its own baggage, and three accounts in one note say the word is heard badly in professional settings. Single accounts describe what the phrase buys: it stops the conversation short-circuiting into an immediate reprimand and gives you room to explain what you were working from; it tells the listener you reached a conclusion from information rather than from nothing; and one account says it can prompt the other person to apologise for not being clear. Two conversations offer “presume” as a swap that avoids the familiar joke about assuming, and two corrections in these conversations settle which is which — this page checked a dictionary: to presume is to take something as likely on reasonable grounds; to assume is to take it as true with little or no proof — with the caution from two accounts that “presume” can sound stiff, or presumptuous, out loud. One account says the phrase works because it turns an action you did into a state you were in, which is exactly why the next question is the one that matters.

That the phrase does not do the thing it is sold as doing. Two corrections in these conversations, each argued out, say “it was my understanding” does not convey ownership: it leaves room for you to have misunderstood, which puts the error back on the interpretation rather than on the source, and one account says it does the same work as “I was told” — it defers responsibility or leaves things ambiguous rather than taking clear ownership. Four separate conversations say the softer phrases — “I was under the impression”, “it was my understanding” — can land as blame-shifting or insincerity, and damage trust if you lean on them; three accounts in one note say “under the impression” in particular sounds passive-aggressive, and one account says it implies some third party misled you. Two conversations say overuse, or the wrong tone, turns the phrase into a tic that colleagues find insufferable, and two conversations say it is used deliberately as a cover-your-back move, to sound creative rather than negligent; one caution says the more widely the trick is known, the less it works. Above all, one caution and one account say the phrase shifts the burden of proof to you: the listener will ask what the understanding was based on, and if you cannot say, the phrase fails and you have made it worse. One contraindication puts it plainly — do not use it if you had no basis, because it invites scrutiny of exactly the decision you cannot defend. If your error really had no source, the honest page for you is the one about admitting you are wrong, linked below, not this one.

Where the belief came from. Two separate conversations say the phrase is a trick that hides the real problem — not verifying — and that a professional cites the source rather than saying “my understanding was.” The accounts give the principle and not the wording — specific examples of citing a source in a live conversation are one of their own listed gaps — so the shapes on this page (“the email of the fourth said Friday,” “in Tuesday’s stand-up we agreed this”) are the page’s own, not theirs. Single accounts give the reasons. It is checkable, so it does not sound like a shield. It creates a record of who decided what, which one account says protects you even when it looks like pointing at a colleague. It helps the team find where the wire actually crossed, so the next person does not cross it too. And it makes the phrase itself honest: “my understanding, from your email of the fourth, was Friday” is a sentence that survives the follow-up. One account adds the other half of the move — after the source, the fix: what you will do now, and what you will check next time — because a person who explains and proposes reads as part of the solution rather than as someone defending a position. One prerequisite in these conversations says you must have had a real basis for the belief before you call it an understanding. For anything risky, one account keeps the instruction in writing before acting on it, so the source exists when you need it.

Then say so, four separate conversations say: admitting “I assumed, and I should have checked” shows the accountability that earns respect, where a euphemism reads as dodging. Seven accounts in one note see “I assumed” as a reasonable, accountable thing to say, and single accounts call it the honest admission of acting without certainty — the correct word when that is what happened. One exchange, three accounts to three, argues whether “I assumed” signals incompetence or healthy ownership, and its own decider is tone and frequency: one wrong assumption is human; the same one twice is a pattern, and one caution says that when the pattern is the problem, no word will fix it. One account says the real fix for “I assumed” is not a synonym but a habit — ask, and repeat back what you heard to confirm it — and one says the danger of the word was never rudeness but looking uninformed, which a source cures and a synonym does not. The argument between softening and admitting is rendered below with its counts; the decider the accounts themselves give is the culture of the workplace and the size of the error, and the source — where the belief came from — is what this page adds to both sides.

The accounts here defend it more than the popular tip does. The tip these conversations began from said to drop “I was told” because it defers responsibility; two exchanges, one account to five and one to six, push back that “I was told” is, in the cases they give, the exact and honest description — you were given an instruction and you followed it — and that replacing it with “my understanding” shifts onto you an error that belongs to whoever gave the order. Four accounts in one note say they use it deliberately for that reason, and three in another say it protects them from a superior’s mistakes. Single accounts go further: a worker with no authority to deviate from training cannot fairly be asked to own an outcome they were not allowed to change; when a supervisor’s order caused the problem, the accountability goes back to the supervisor; and one account would rather name the person who insisted — “I warned” and the name — than be vague, because vagueness protects nobody, least of all you. Two accounts say the phrase is neutral in itself, a statement of how information reached you, and one caution says it turns evasive only when it is used to dodge a plain factual question — is the printer fixed? — that you could simply answer. One correction reads the whole argument as a choice of tools: “I was told” is for saying the decision was not yours; “my understanding was” is for saying the reading was. Use the one that is true.

Two separate conversations say no: a manager looking for fault will hear “my understanding was” as either “I was wrong” or “I acted without knowing,” and the words you pick change nothing, because the listener’s intent matters more than the phrasing. One caution says a boss who loses their temper over a small assumption is telling you about the workplace, not about your sentence, and one account on that side of one exchange says the answer to that is a different job — which is more than this page can help you do. Two conversations say to pick your words by who you are talking to, and one says the same words land as humble in one room and presumptuous in another. Three cautions say tone overrides everything: a neutral phrase delivered flat implies fault, delivered firm shifts it, and delivered with an edge is an insult whatever the words. Two accounts say perception of all of these phrases differs by person and by country, and one says that in Britain “I figured” is heard as ungrammatical and quietly resented; how any of this travels outside English-speaking offices, and how it works in writing where there is no tone at all, are gaps in these conversations. Two conversations carry the joke that anyone hearing the phrase can simply reply “so you assumed…” — and the people telling it add that the underlying advice is still sound.

A handful from single accounts, each with its use. “To the best of my knowledge” lets you answer with confidence and leaves room to be wrong when experts are in the room. “Did I explain that properly?” in place of “do you understand?” removes the suggestion that the listener is slow, and one account says people with status will say yes to the second and ask a real question after the first. “As I am sure you are aware” lets you remind a superior of something without sounding as if you are correcting them — with the caution from one account that questioning someone’s awareness can put their ego on guard. “It appears to be broken” rather than “it is broken” acknowledges what you do not know and spares you a lecture from whoever does. “I was led to believe” makes the belief circumstantial rather than a guess, and “I made the connection” describes reasoning rather than a leap. One account works by a rule that covers all of these: talk about the matter, never about the people in the room, yourself included. And one account says the mirror of owning a mistake is claiming good work in plain words too, rather than deflecting the credit. None of these is a substitute for the source; each is a way of speaking when you have one.