During training, you hear, “Ask for input early” and “Think for yourself and take action.” The next day, you show someone a proposal you have started, only to hear, “Come back when you've worked it out more.” But when you submit a finished version, the response is, “Why didn't you ask me first?” This is a hypothetical example, but it illustrates a moment when the right time to share your work suddenly becomes unclear.
The feeling that “something doesn't add up” can be a starting point for rethinking how work gets done. But that feeling alone cannot tell you what the other person intended. To take something useful from the experience, you need to turn it into a question, while leaving room for your own explanation to be wrong.
1. Separate what happened from what you think it means
In the example above, what you can establish is that early consultation was encouraged, revisions were requested when you shared a work-in-progress proposal, and expectations for when to submit it had not been communicated. “This manager dislikes initiative” is an interpretation you have constructed from that information.
Interpretation is necessary for thinking things through. Even so, other explanations are possible: there may not have been time for a review, essential background information may have been missing, or the other person may have had a different idea of how developed a “draft” should be. You do not need to erase your frustration. Just try not to pack the feeling and your explanation of its cause into the same sentence.
A two-part note can help: “Observation: I showed a proposal with the purpose and budget sections blank and was asked to resubmit it.” “Hypothesis: We may not have agreed on what information is needed before asking for input.” Written this way, the note lets you check the conditions later and revise your interpretation.
2. Assess the message and the person's behavior separately
You can agree with someone's explanation of why trust matters and still question how that person treats you. Both responses can coexist. Separating the merits of the message, the person's actual behavior, and its effect on the recipient helps you avoid judging everything solely by whether you like or dislike the person.
Still, one exchange is not enough to conclude that a gap between words and actions is a persistent pattern. If you clarify the submission requirements next time, do the explanations line up? Do the standards change even under the same conditions? When you ask a question, do you get a specific answer? After noticing a contradiction, what you need is more observation rather than a verdict.
You can turn the same lens on yourself. Do you say, “Feel free to ask,” then sigh whenever someone asks a question? If noticing someone else's behavior leads you to change one of your own habitual responses, the insight has already become a next step.
3. End your reflection with a small experiment
Kolb's account of experiential learning connects experience, reflection, conceptualization, and experimentation.[1] The note-taking process introduced here is a proposed way to apply that idea at work. Writing things down does not, by itself, guarantee learning or a better workplace.
For example, after an experience of being stopped when you showed a draft, you might think, “Perhaps the discussion would move forward if I brought the necessary information.” Next time, put the purpose, options, and unresolved points on one page and add, “At this stage, I'd just like to check the direction.” Making clear what you want reviewed makes it easier to compare the responses.
Record the outcome, too. If the discussion moves forward, that lends support to explanations involving insufficient preparation or mismatched expectations. If the standards change every time, even after you have clarified them, you need to investigate another possible problem. An experiment may also show that your own assessment was wrong. When you retain that revision as part of the lesson, your note becomes knowledge you can use again.
4. Should you change how you write, or rethink the submission rules?
When work keeps being sent back, it helps to distinguish procedures from underlying assumptions. Improving the way you work within existing goals and rules is known as single-loop learning; questioning the goals or decision rules themselves is known as double-loop learning.[2]
Putting the main point of a proposal first, reducing the number of attachments, or changing the time you ask for input are improvements to the process. By contrast, asking, “Are we getting confused because we're using the same review for evaluating finished work and discussing its direction?” or “Do we need to agree in advance on what the person doing the work can decide independently?” brings the underlying arrangements into consideration.
Questioning those arrangements is not always the better choice. If you forgot an attachment, attach it. In the middle of an urgent response, there may be no time to reopen a discussion about the organization's purpose. Widen the question when the same difficulty persists despite changes to the process. Being able to describe a problem in broad theoretical terms and being able to choose an appropriately sized improvement are different skills.
5. Do not stop at “They lack metacognition”
Examining your own understanding and judgment is central to this process. But it is difficult to assess someone's metacognitive ability from a single remark. Deciding that “this person cannot reflect on themselves” also leaves you less room to examine your own hypothesis.
Japan's Ministry of Economy, Trade and Industry (METI) has a framework called “Fundamental Competencies for Working Persons,” organized into three competencies and twelve component abilities. Its materials on “Fundamental Competencies for Working Persons in the Era of the 100-Year Life” explicitly address self-awareness and reflection.[3] The absence of a separate component named “metacognition” does not mean that this Japanese framework leaves reflection out.
In day-to-day work, specific questions are easier to use than the instruction to “improve metacognition.” “What was I taking for granted?” “Did I communicate that assumption to the other person?” “Do I have evidence that could rule out an alternative explanation?” Try adding these three questions to your own notes before evaluating someone else.
6. Separate the ability to frame a question from the conditions needed to act
If you define the problem as “Team members don't ask for input early enough,” you are likely to look for ways to increase how often they ask. If you define it as “We haven't agreed on when work is ready to discuss,” you may instead clarify what is needed for an initial review or create an opportunity to check in. Changing the problem definition changes the work required. Which explanation fits, however, must be checked against information from the workplace.
Nor does asking a good question necessarily mean that you can change a system on your own. Who makes the decision? Who will take on extra work? Can you set aside time to try it? Explanation, coordination, authority, and cooperation all matter. A single rejected proposal is not enough to conclude either that you lack ability or that the environment is entirely to blame.
Edmondson's 1999 study of 51 teams at a manufacturing company found an association between psychological safety and learning behavior.[4] It was an observational study within one company, not a causal guarantee that increasing trust will always improve performance. It gives us a reason to consider time and support structures alongside how easy it feels to ask for help.
Psychological safety here concerns a team's shared belief that it is possible to take interpersonal risks, such as asking questions or raising concerns.[4] It does not mean accepting every suggestion or lowering quality standards. Making it possible to share a draft and examining that draft rigorously should be compatible.
7. What helps next time may be a one-page note, not a long essay
You might keep a record like the one below. This is a suggested way to keep observation and interpretation separate, not a format whose effectiveness has been validated in a specific study.
- Event: I submitted a draft to discuss its direction, but it was assessed as finished work
- Difficulty: I could not discuss the points I wanted to check before making substantial revisions
- Hypothesis: We have not established a shared distinction between asking for input and seeking approval
- Alternative explanation: I did not explain the purpose or constraints well enough for the other person to make a judgment
- Next check: Before submitting, ask, “For this review, are we looking at the direction or how complete the work is?”
- Outcome and revision: Briefly record the response and what to change next time
This can be easier to apply in another workplace or with another person. A working principle such as “Agree on the purpose of the first review” travels more readily to the next situation than a note saying, “That person is difficult.”
You can also put a limit on how much you record. When no further information or next step emerges, stop reflecting for the day. Not everything needs to become an article, and it is fine to respond to an exhausting experience simply by resting.
8. Learning from a situation does not mean you have to stay and endure it
If a situation feels unsafe, for example because you are repeatedly insulted when you ask questions or make suggestions, or penalized for seeking advice, you do not need to keep experimenting. Keep options for protecting yourself in view, such as speaking with someone you trust or considering a change in responsibilities or in how you engage with the situation.
If you keep records, limit them to what is necessary for work and follow your company's information-handling rules. Do not copy customer information or internal documents onto personal devices or reuse them directly in a public article. Removing names may not be enough to prevent identification in a published example. Remove distinctive dates, job titles, and phrasing, and distinguish illustrative hypothetical examples from records of actual events.
What you take from that sense of disconnect need not be only proof that you were right. It can be a small, usable option: “Next time, agree on the purpose before submitting,” or “Under these conditions, seek advice elsewhere.” Making just one decision easier tomorrow is enough for the experience to be useful.
References (4)
[1] Experience Based Learning Systems. “8 Things to Know About the Experiential Learning Cycle.” An explanation of Kolb's experiential learning cycle. https://learningfromexperience.com/themes/experiential-learning-theory-videos/
[2] Argyris, C. (1976). “Single-Loop and Double-Loop Models in Research on Decision Making.” Administrative Science Quarterly, 21(3), 363–375. https://doi.org/10.2307/2391848
[3] Ministry of Economy, Trade and Industry, Japan. “Fundamental Competencies for Working Persons in the Era of the 100-Year Life” (in Japanese). https://www.meti.go.jp/policy/economy/jinzai/Ecforthe100-yearlife.pdf
[4] Edmondson, A. (1999). “Psychological Safety and Learning Behavior in Work Teams.” Administrative Science Quarterly, 44(2), 350–383. https://dash.harvard.edu/entities/publication/13a7b031-0fdd-45ec-a7e0-2b80e2bc679f
