There have been several points in my career when the hardest part of an assignment was not actually doing the work. It was figuring out what everyone believed the work was supposed to include.
That can be surprisingly difficult to recognize at first because the request itself may sound clear enough to move forward. You understand the subject. You know how to produce the work. You have enough experience to make reasonable decisions about what belongs and what does not. Then the first version comes back, and you realize someone else had a very different picture in mind.
That does not necessarily mean either person was wrong. Two reasonable people can hear the same assignment and make different assumptions about the level of detail, the purpose, or what a useful finished product should look like. The problem is that those differences are often invisible until someone has already invested the time to build something.
At that point, you are no longer only revising the work. You are also trying to understand whether the expectation changed, whether you misunderstood it, or whether the full expectation had simply never been made clear in the first place.
I have encountered enough versions of this over the years to know how quickly the work around an assignment can become as demanding as the assignment itself.
The definition of "good" matters
Some expectations are easy to communicate because they are tangible. There is a deadline, a format, a required piece of information, or an established process that everyone understands.
Other expectations are much harder to see. Someone may want something concise because the past no longer matters as much as what happens next. Someone else may believe the history is essential because it explains how the current situation developed. Both approaches can be defensible, but if that conversation never happens, the person producing the work has to choose.
Usually, we make those choices using the information we have. We consider the audience, the purpose, what is available, and what seems most useful. That is part of doing good work, and it becomes much harder when the standard appears only after the choice has already been made.
I have been on both sides of that problem. Running a business for years taught me how easy it is to assume that something is obvious because I have lived with it long enough to stop noticing everything I know. What feels like a clear request to me may contain years of context that another person does not have, and that has made me more careful about the difference between giving someone an assignment and giving them enough understanding to make the judgments the assignment requires.
Information is not the same as understanding
There is another version of this that I have experienced more than once, especially when taking on work that already has some history behind it. Technically, the information exists. There may be prior examples, documents, conversations, and people who know how things have been done before. You can have access to all of it and still spend an enormous amount of time figuring out what matters, what is current, and what everyone else already assumes you know.
Access to information is not the same as an effective transfer of knowledge.
A person who has been close to something for a long time may know immediately which example matters and which one is outdated. They know why a particular decision was made, which preference belongs to whom, and what happened six months ago that still shapes how people approach the work today. The person coming into it sees the same material without those connections.
That does not mean they cannot figure it out. Most capable people will. They ask questions, study what came before, find the people who hold the history, and slowly build enough understanding to make better decisions. But figuring it out is still work.
The invisible part starts to accumulate
One unclear expectation is manageable. So is one missing piece of context. The difficulty is what happens when that discovery process becomes part of almost everything you are doing.
You might begin an assignment and realize you first need to locate the right precedent, only to make a decision and later discover an expectation you did not know existed. Something that initially seemed contained can keep expanding as new conversations reveal pieces everyone else assumed were already included.
None of those moments has to be dramatic on its own. In fact, that may be why the effect is so easy to underestimate. The visible work continues. Things get finished. Questions get answered. Revisions get made. What is harder to see is the amount of mental effort being spent continually recalibrating what the work actually requires.
That kind of ambiguity is different from complexity. I do not mind difficult work. Some assignments should require thought, judgment, and experimentation. The exhaustion comes when a significant part of the thinking is not about solving the problem itself, but about trying to establish what problem everyone believes you are solving.
Boundaries are harder when the work is still being defined
I have also learned that it is difficult to set reasonable boundaries around work when you do not yet understand its full shape. Before I can say how long something should take, what I can reasonably absorb, or where my responsibility ends, I need some sense of what I am actually agreeing to. That sounds obvious until you notice how rarely work arrives that neatly.
Sometimes you agree to the thing as it was initially described, then discover additional expectations as you go. Sometimes you realize a responsibility includes far more coordination than the visible deliverable suggested. Sometimes you cannot tell whether the new request is a reasonable evolution of the work or another responsibility quietly becoming part of it.
I am still learning how to handle those moments well. My instinct has often been to figure it out first and worry about the boundary later. That approach can keep things moving, and there are situations where flexibility is necessary. But it can also create a problem of its own because once you repeatedly absorb the ambiguity, it becomes difficult for anyone else to see what the work actually required from you.
Capability can hide a lot. If the deadline is met and the finished product looks right, there may be no visible sign of how much searching, interpreting, reconstructing, and adjusting happened behind it.
Sometimes the work around the work becomes the work
I do not think every assignment needs to be perfectly defined before anyone begins. That is probably unrealistic, especially in work that is collaborative, fast-moving, or genuinely new. I also do not think feedback means something went wrong. Good work gets challenged and revised, and sometimes another person sees something I did not.
The distinction I keep coming back to is whether the work is evolving because people are learning together or whether someone is repeatedly discovering expectations they were somehow already supposed to know. Those experiences can look almost identical from the outside, but from the inside, they feel very different. One gives you more information to improve the work. The other leaves you continually rebuilding your understanding of what the work was supposed to be in the first place.
I have encountered both throughout my career, and I am getting better at recognizing the difference. I ask more questions earlier. I try to understand who the work is for, what matters most, and what a useful outcome actually looks like before I assume everyone has the same picture in their head. I also know I will not always catch every gap before I begin. Sometimes the only way to discover what is missing is to get into the work and find it.
What I am trying to resist is the assumption that if someone manages to keep delivering, the ambiguity must not be costing them very much. People do not only get tired from the amount of work in front of them. Sometimes they get tired from having to continually figure out what the work actually is while they are already responsible for getting it done.
