A People Operations executive reflects on 2.5 years of building contextual history with one AI, onboarding a second, transferring organizational knowledge between them — and discovering that classic I/O psychology concepts applied to all of it.
It started the way most useful things do: without a plan.
About two and a half years into my role as VP of People Operations, I realized I had been having a running conversation with an AI — ChatGPT, at the time — about nearly every significant work challenge I was navigating. Workforce analytics. HRIS architecture. Org design. Business cases. Executive communications. Leadership decisions I wasn't ready to talk through with anyone inside the organization.
Somewhere in all of that, I had accumulated something I hadn't set out to build: a living record of how I think.
It wasn't a database. It wasn't documentation. It was closer to what you'd get if you could read someone's professional subconscious.
The Knowledge Transfer Problem
When I started working with Claude — which has genuinely different strengths — I hit the same wall every organization hits when a key employee leaves: the new person is capable, but they don't have the context. They don't know the history. They don't know how you think, what you've already tried, or what matters.
So I did what I would have done with a new director joining my team. I onboarded Claude.
Not by uploading files. By transferring knowledge the way knowledge actually transfers — with documentation, examples of quality work, communication preferences, recurring priorities, historical context, and calibration over time. I shared how I make decisions. What I care about. Where I've been burned. What kinds of outputs I find useful and what reads as generic to me.
It worked. But what happened in the process was more interesting than I expected.
AI Job-Skill Fit: A Classic I/O Problem
One of the foundational concepts in Industrial-Organizational Psychology is person-job fit — the idea that performance improves when an individual's capabilities align well with what the role actually requires. Hire for the wrong fit and you get friction, underperformance, and frustration regardless of raw capability.
What I noticed, gradually, was that the same principle applied to AI systems.
| Capability | ChatGPT | Claude |
|---|
| Longitudinal memory & context | Strong — 2.5 years of accumulated history | Limited at first; built over time |
| Strategic conversation | Strong — iterative, relationship-aware | Strong — rigorous, structurally precise |
| Large document synthesis | Adequate | Exceptional |
| Visual artifacts & design | Limited | Strong — website, decks, structured outputs |
| Long-form writing & editing | Good | Excellent — nuanced, voice-preserving |
| Org context & leadership style | Deep — years of calibration | Developing — through deliberate onboarding |
Different tools. Different fit profiles. Different jobs. The right response wasn't to pick one — it was to understand what each was actually good at, assign accordingly, and manage the handoffs between them. Which is, again, exactly what you'd do with a team of people.
The Unexpected Output: A Leadership User Manual
Here's the part I didn't anticipate.
To transfer context effectively, Claude had to do something unusual: it had to analyze and articulate how I think. Communication patterns. Decision preferences. Leadership tendencies. What I find motivating. Where I tend to overcomplicate. How I process ambiguity. What quality looks like to me versus what adequate looks like.
What emerged from that process was the most detailed and accurate leadership profile I have ever received. More nuanced than any 360 feedback I've been through. More honest than most coaching conversations. Grounded in actual behavioral evidence rather than survey responses.
I was attempting to train an AI. The AI ended up training me.
Not in a mystical sense. In a very practical one: the act of making my thinking legible to a system that needed explicit context forced a level of self-reflection that implicit, accumulated organizational knowledge never demands.
What I Took From It
The biggest surprise wasn't how much work AI could absorb. It was how much organizational psychology still mattered.
Onboarding. Role clarity. Capability development. Knowledge transfer. Performance enablement. Job-skill fit. Every concept that governs how humans integrate into organizations turned out to apply — with remarkable fidelity — to how AI systems integrate into a leadership operating model.
That probably shouldn't be surprising. The underlying challenge in both cases is the same: you have a capable system, and the question is whether the context, structure, and role definition around it are good enough for that capability to actually show up.
Most organizations that struggle with AI adoption aren't struggling because the technology is insufficient. They're struggling because they've skipped the organizational work that would make the technology useful. They've bought the hire before building the job.
I've spent fifteen years arguing that HR should function more like an engineering discipline. It turns out the inverse is also true: AI adoption, done well, looks a lot like good people management.
The technology was new. The people science wasn't.
