The ESTJ and the System That "Used to Work"

If you lead with the ESTJ pattern, your nostalgia doesn't look like anyone else's. You don't ache for a lost feeling or a softer time the way a more sentimental type might. You ache for a system that worked. You look back on the team that ran like clockwork, the company before the reorganisation, the years when people respected the chain of command and did things the proper way — and you're certain that back then, the operation was sound and the present one is a slow-motion failure. Your version of grieving the past is comparing it, point by point, against a present you've decided is sloppy.

And because order and standards are the things you care about most, you don't just feel this privately — you enforce it. 'That's not how we used to do it' becomes a verdict. You hold up the remembered system as the correct one and treat every deviation from it as decline. The problem is that the system you're defending is not the system that actually existed. Memory has quietly run the same edit it runs on everyone, cutting the friction and inefficiency and keeping only the parts where things ran your way — and you, of all people, are using that doctored record as a management standard.

Your memory deleted the friction, not the order

Here's what your recall does, and it's worth seeing plainly because you pride yourself on dealing in facts. When you remember the operation that 'used to work,' you remember the order — the clear roles, the procedure being followed, the standard being met. What gets deleted is the friction it took to hold that together: the people who quietly resented the rules, the inefficiencies everyone worked around, the talent that left because the system was rigid, the problems the procedure couldn't solve. You're not comparing the present to the past. You're comparing the present to the highlight reel of the past.

That's a measurement error, and you'd never tolerate it in a report. If a manager handed you a comparison that counted all of today's costs against none of last year's, you'd send it back. Yet that's exactly the comparison running in your head every time you say things were better before. The old system had defects you've stopped logging because they're no longer in front of you. The new one has all its defects on full display because you're living in them. Like for like, the gap is far smaller than it feels — and sometimes it runs the other way.

Defending the old way is not the same as upholding standards

You tell yourself you're upholding standards, and that matters to you, so this distinction is the important one. There's a real difference between defending a standard — the quality bar, the result, the reliability — and defending a method, the specific way it used to be done. You conflate them constantly. When you block a change because 'the old way worked,' you're usually not protecting the outcome; you're protecting a familiar procedure that happens to be the one your memory has polished.

The cost is that you become the person standing in the way of things that would actually meet your standards better. A new process that's faster, a tool that removes a step you used to do by hand, a younger colleague's method that hits the same result with less waste — you reject these on reflex because they aren't the remembered way, then call the rejection 'rigour.' It isn't. Rigour would mean testing the new method against the old on the metrics you claim to care about. Nostalgia dressed as discipline just keeps you loyal to a procedure long after the reason for it has gone.

You're managing the present team against ghosts

This one does real damage, because you don't keep the comparison to yourself — you hand it to the people in front of you. The team you've got now is being measured against a former team that exists only in your edited memory, and they can feel it. 'The people I used to work with would never have let this slip.' 'Back then, you didn't have to be told twice.' You think you're holding the line. What the present team hears is that they're a disappointment compared to people they never met, against a standard you've inflated.

Nobody can compete with a ghost, because the ghost has been stripped of its flaws and yours haven't been. The real former team had its slackers and its conflicts too — you've just forgotten them. So your current people stop trying to win an unwinnable comparison and start quietly disengaging, which confirms your story that things have gone downhill, and the loop tightens. You're not failing to lead a worse team. You're failing to see the team you actually have because you're busy grieving one that never ran as cleanly as you remember.

Audit the past like you'd audit anything else

The fix is one you're actually well built for, once you turn your own tools on the problem. You're good at facts, comparisons, and honest accounting — you just haven't applied them to your nostalgia. So audit it. The next time 'it used to be better' fires, force the full ledger: name three concrete problems the old system had that you've stopped counting. The person who quit. The workaround everyone hated. The result it never actually delivered. Put those back on the balance sheet and the comparison gets honest.

Then point your standards forward instead of backward. The thing you genuinely value isn't 1998, or the old org chart, or the way it was — it's a sound, well-run operation that delivers. That's available now, in the present, with these people and these tools, if you'll define the outcome you want and let the method be current. Enforce the standard, not the memory. The good old days weren't the standard; they were one imperfect attempt at it, sanded smooth by time. The real operation worth running is the one in front of you.