In-My-Day Anchoring
He measures every present-day topic against a past baseline. The past is his fixed standard for quality, effort, and manners.
Pattern Snapshot: In-My-Day Anchoring
- What it looks like: Every current topic gets scored against a past benchmark.
- Where you see it: Conversations about work, technology, manners, and young people.
- What drives it: Authority Preservation, Desire for Stability, Experience Shield.
How to Spot It
- He says “In my day” before giving an opinion on almost anything current.
- The present almost always scores worse in the comparison.
- He cites how apprentices behaved, how hard people worked, how things were built to last.
- He is not just telling a story. He is using the story to rank the present.
- The benchmark never changes. The world keeps failing it.
The clearest sign: he reaches for the past automatically. You mention a new colleague. He talks about what discipline used to look like. You mention a product. He says they do not make them like that anymore.
What It Means
The past is where his competence lives. He was skilled, respected, and certain of the rules. Anchoring there keeps him the measure of things.
- Authority Preservation: The comparison keeps him the expert. He sets the standard. Everyone else performs against it.
- Desire for Stability: A fixed standard feels safer than a moving one. The past does not revise itself.
- Experience Shield: His history is his credential. The anchor is the credential in action.
This pattern is different from Story Loop. Story Loop retells events. In-My-Day Anchoring uses events to rank the present. It is also different from Experience Shield. Experience Shield blocks proposals. In-My-Day Anchoring evaluates everything, including things he has no stake in.
You see this pattern most in The Patriarch and The Stabilizer.
What You Can Do
- Do not argue the comparison. Arguing makes the past more important. It does not make it less.
- Ask for the standard behind it. “What did that teach you that we should keep?” He moves from judge to source.
- Grant what was genuinely better. Some things were. Saying so costs nothing and opens the door.
- Connect his baseline to the present problem. “So the standard was X. How would you apply that here?”
Say something like:
“What did that teach you that we should keep?”
“So the rule back then was craftsmanship first. What does that look like with what we have now?”
Do not say: “Times have changed.” He knows. He thinks it went in the wrong direction.
At Work
Every proposal in the meeting gets a 1995 benchmark. He says the new system is more complicated and the old one worked fine. The team loses ten minutes explaining why the comparison does not hold. It does not work. He brings out another example.
Stop defending the present. Turn the anchor into a requirements source. Ask him directly: “What did the old system get right that this one has to get right too?” He gives you a list. That list is useful. You now have his buy-in to anything that meets those criteria.
Footnote
He is not being difficult. The past is where he was at his best. The anchor is how he stays connected to that. This pattern sits close to Experience Shield. Both come from the same source: his history is his authority.