Stay Open to Being Changed — for the ESTJ

You don't change your mind in public, because in your world changing your mind looks like an admission that you were running things wrong. You're the one who sets the standard, enforces the procedure, and tells everyone how it's going to be done. When you reverse a call, you're not just adjusting a private opinion — you feel like you're undercutting your own authority, telling the team the person they followed last week didn't know what they were talking about. So you dig in. You defend the policy, the deadline, the way you've always done it, and you defend it with full conviction even on the days when a quieter part of you has already clocked that the evidence stopped supporting you a while ago.

Here's the trap specific to you: you confuse consistency with correctness. Because you value order and reliability so highly, you treat 'I said it, so I'll stand by it' as a virtue, when often it's just sunk cost wearing a uniform. Staying open to being changed doesn't mean becoming wishy-washy or letting feelings overrule the facts — that would horrify you, and rightly so. It means treating your own conclusions like any other system you manage: something that gets audited, tested against reality, and upgraded when a better input arrives. The strongest operators you've ever respected weren't the ones who never updated. They were the ones who updated fast, cleanly, and without drama, and somehow came out looking more credible, not less.

You defend the rule long after the rule stopped working

You're the keeper of the proper way. A procedure exists, you learned it, you enforce it, and you've watched it deliver results, so when someone proposes a change you instinctively guard the existing order. That instinct is genuinely useful — most 'new ideas' really are half-baked, and you've saved teams a fortune by refusing to let people reinvent a wheel that rolls fine. But the same reflex makes you the last person to notice when a rule has quietly gone obsolete. The conditions shifted, the rule didn't, and you keep enforcing it because enforcement is what you do, not because it still produces the outcome it was built for.

Watch for the moment you start defending a policy by its history instead of its results — 'this is how we've always handled it,' 'this is the standard,' 'because I said so.' Those are the phrases you reach for when you've lost the actual argument but won't concede the ground. A rule is a tool for getting a result; the day it stops getting that result, defending it isn't discipline, it's malfunction. The competent move isn't to abandon structure. It's to ask, coldly and on the merits, whether this particular structure still earns its place.

Conceding a point feels like losing the chain of command

For most people, changing their mind is a quiet internal event. For you it's a public, structural one, because you operate inside hierarchies and you're usually near the top of them. If you admit the new hire was right and you were wrong, it doesn't feel like updating a fact — it feels like the org chart wobbled, like authority just leaked downward. So you hold the line past the point of reason, not because you still believe the position, but because reversing it in front of the team feels like it costs you command. That fear is real, and it's also backwards.

Authority built on never being wrong is brittle, and everyone around you knows it — they just stop telling you things, which is the exact failure mode you'd fire someone else for. Authority built on being the person who follows the evidence wherever it leads is far harder to shake. When you say 'good catch, we're changing course,' you don't lose the room; you prove your judgment is anchored to reality rather than to ego, and that is precisely what makes people willing to be led by you under pressure. Conceding a point cleanly is a command move, not a surrender.

You decide fast, then guard the decision instead of the goal

Your speed is a strength. You don't agonize; you assess, you call it, you execute, and you move while slower types are still circling the problem. But that same decisiveness has a cost you rarely audit: once you've committed, you switch from evaluating the decision to defending it. New data arrives and you treat it as an attack on a settled matter rather than as information. You confuse 'I already decided' with 'the question is closed,' and so you steer the project toward proving you were right instead of toward the result you actually wanted.

The fix is to keep the goal sacred and hold the decision loosely. Separate the two out loud: 'the objective is X; my current plan is Y; Y is a means, not the point.' When someone challenges Y, that's not insubordination, it's free quality control on your own execution — the kind of feedback you'd pay a consultant for. Set yourself an explicit trigger: if the numbers move past a line you name in advance, you change the plan, no debate, no face-saving. That isn't flip-flopping. That's the difference between a manager who hits targets and one who defends a doomed plan all the way into the ground.

Build the update into your system on purpose

You don't run on vibes; you run on process, so don't try to 'be more open-minded' as a personality goal — that's vague and you'll never measure it. Instead, engineer openness into how you operate, the way you'd build a checkpoint into any workflow. Pick the two or three people whose judgment you actually rate and give them standing permission to tell you when you're defending something dead. Make 'what would change my mind here?' a question you ask yourself before you lock a position, and write the answer down so future-you can check it.

Treat a clean reversal as a logged win, not a hidden embarrassment. After a project, run a short post-mortem on your own calls: which ones held up, which ones you should have updated sooner, and what the early signal was that you ignored. Do that a few times and you'll start catching the signal in real time — that small internal flicker of 'I don't fully buy this anymore' that you currently override. The goal isn't to second-guess everything; you'd grind to a halt and hate it. The goal is a tight, deliberate loop where strong opinions stay strong exactly as long as the evidence backs them, and not one day longer.