What Is the "Be Proactive" Double Bind?
The "be proactive" double bind looks like this:
- You act on your own judgment, and you're told, "Don't just do things on your own."
- You check in first, and you're told, "Figure it out yourself."
- You suggest an improvement, and you're told, "That's not what I meant."
- You do nothing, and you're told, "You lack initiative."
- Your role and authority stay vague, but you're still held fully responsible for the results.
In this situation, it's hard for anyone to take initiative.
Whatever you choose to do gets shot down.
And this isn't only about one person's motivation.
It's a setup that demands initiative without creating any conditions where initiative can happen.
When Instructions Keep Changing After the Fact, the Work Never Ends
A moving-goalpost instruction is when new conditions or standards that were never shared at the start get added after the work is done or handed in.
Of course, requirements sometimes change midway through a job.
But when it happens almost every time, problems pile up:
- You can't tell what "done" means
- You redo the work again and again
- You can't predict how long anything will take
- Only the person doing the work takes on more responsibility
- Even when you ask, the standards never get clearer
- In the end, you're labeled as "not understanding" or "lacking initiative"
When you put this into a log, it can show something like this:
It wasn't the person's lack of ability. The definition of "done," the criteria for decisions, and the scope of responsibility were never defined.
The Problem of Verbal-Only Instructions and Refusing to Keep Records
In workplace trouble, people sometimes get annoyed when you try to keep a record.
For example:
- You confirm something over chat and are told that's "rude"
- You're asked to explain things out loud instead
- Instructions are given verbally only and leave no trace
- Later someone says, "That's not what I meant"
- With no record, the misunderstanding gets pinned on you
Of course, talking face to face isn't bad in itself.
But in work where misunderstandings and changed goalposts are common, you need a record.
Keeping records isn't about attacking the other person.
It's so that things can be checked later.
In particular, it's safer to put revision requests, deadlines, who is responsible for what, and decision criteria in writing as much as you can.
What to Write Down in a Structured Log
To make moving-goalpost instructions and the double bind visible, a single remark isn't enough.
Keep track of the following items.
| Item | What to look at |
|---|---|
| The first instruction | What were you asked to do? |
| Check-ins along the way | When, with whom, and what did you confirm? |
| What you did | What did you create, revise, or propose? |
| Conditions added later | Had they been shared at the start? |
| What got rejected | What exactly was called "wrong"? |
| Decision criteria | Were they stated clearly? |
| Authority | Did you have the right to decide? |
| Responsibility | Is only the blame coming your way? |
| Similar past cases | Is the same pattern repeating? |
Filling in this table makes the problem much easier to see.
Case Study: A Generalized Workplace Trouble Log
The case below is generalized from elements seen in several workplace troubles.
Background
In a work-improvement project, the person in charge prepared materials in advance and asked the people involved to review them.
What happened
- They submitted a first draft, and a major rewrite was requested afterward
- They were told, "That's not what I meant"
- Many small resubmissions kept coming up
- They were asked to explain things verbally, and confirming over chat was met with annoyance
- On the day itself, small tasks like guiding guests, arranging the space, and preparing things were added
- The authority to decide stayed vague, while responsibility for the outcome landed on this person
- In the end, they were questioned on "initiative," "not understanding," and "acting like a leader"
What the person in charge had actually done
- Prepared materials ahead of time
- Submitted a draft before the deadline
- Asked for reviews
- Made the requested revisions
- Offered alternative plans
- Proposed turning the process into clear steps and standardizing it
- Tried to leave a trail in chat and documents so things could be checked later
The structure that emerged
- The definition of "done" wasn't clear in advance
- The decision criteria were handed down after the fact
- Responsibility was bigger than authority
- Initiative was demanded, yet proactive proposals were rejected
- No time or effort was set aside for reducing dependence on one particular person
- Individual effort was being used to patch holes in the company's system
Example summary for when you ask for advice
In a work-improvement project, the person had prepared materials, asked for reviews, and made revisions in advance. Even so, last-minute revisions came up several times, with unclear decision criteria and no clear definition of "done." On top of that, confirmation was mostly verbal, so it was hard to leave a record. As a result, responsibility has concentrated on this one person, and it has become hard for them to ask questions or make proactive proposals.
Summary: Don't Ask "Who's at Fault?" Ask "What Keeps Repeating?"
In workplace trouble, it's easy to focus on "who's to blame."
But what a log is really meant to show is
what keeps repeating.
- Are moving-goalpost instructions happening again and again?
- Does the situation stay verbal-only, with no record left?
- Is initiative demanded while proactive proposals get shot down?
- Is responsibility handed over without any authority?
- Is there talk of reducing dependence on one person, without any time given for standardizing the work?
Once you can see these, you can explain the problem as a flaw in how the workplace is set up, not as an emotional dispute.
Workplace trouble is vague when you look at one remark at a time.
Put it in time order.
Keep the exact words.
Write down what you did.
Look for what it has in common with the past.
Organize it as a structure.
That helps when you ask for advice, when you try to improve things, and when you need to protect yourself.
