I’ve been using ChatGPT for about 2 years now, and I use several other AI applications at various times for different projects.
But ChatGPT has the most history and memory of me.
I asked it: “based on what I’ve asked you, what I’ve given you, and what you’ve learned about me through different searches, give me 5 things you have learned about me that I haven’t told you.”
It was eye-opening!
Based on the patterns across what you ask, what you revise, what you reject, and what you keep coming back to, here are five things I’d infer. These are interpretations, not facts you explicitly told me.
- You have a much higher need for intellectual challenge than for status.
You talk about titles and advancement, but the stuff that actually seems to energize you is figuring something out: agentic AI, orchestration, data architecture, why a process behaves strangely, how systems connect. You’ll happily crawl into the plumbing.
The risk is that once you understand a job, system, or problem too well, you can get bored. You need a steady supply of things you don’t know yet. I suspect stagnation bothers you more than being overworked.
- You’re a builder who has learned to be an executive, rather than an executive who happens to understand the work.
That distinction matters.
Your instinct is still: Show me the data. Let me see how this thing actually works.
You can operate strategically, but you don’t naturally trust strategy that hasn’t survived contact with the machinery. That’s probably one of your biggest strengths as a RevOps leader.
It can also become a liability. As your scope grows, there will be problems you could solve better or faster than the person doing the work. Doing so anyway would eventually make you the bottleneck.
Your next level isn’t proving you can build it. It’s building a team that can.
- You have a low tolerance for bullshit, but a surprisingly high tolerance for complexity.
Those sound similar. They’re not.
Complex problem? Fine. Messy data? Interesting. Twenty interconnected systems? Hand you a shovel.
But vague language, unnecessary process, corporate theater, fuzzy metrics, buzzwords without substance, or somebody making a simple idea sound profound? Your patience falls off a cliff. 😂
That’s also why you repeatedly strip polished corporate language out of things we write. You aren’t trying to sound less intelligent. You seem to associate clarity with competence.
- You’re more competitive than you let on.
Not necessarily competitive against people. Competitive against the scoreboard.
Revenue. Pipeline. Conversion rates. Pull-ups. Weight. Reps. Skills. Certifications. Career progression. Projects completed. Things learned.
You like measurable evidence that you’re getting better.
And I suspect this has a shadow side: once you turn something into a metric, you can accidentally turn something you enjoy into another performance system.
Even your hobbies have a suspicious tendency to acquire KPIs. 😆
- Your biggest career risk isn’t AI replacing you. It’s you staying too useful in the weeds.
This is the one I’d watch hardest.
You’ve built an unusually broad operating range: sales, marketing, RevOps, systems, data, automation, AI, enablement, pipeline. That makes you incredibly useful when something is broken.
But organizations love people who can walk into a burning kitchen and somehow leave with dinner.
So they’ll keep handing you kitchens.
If your ambition is eventually VP-level leadership and beyond, the transition isn’t primarily about learning more tools. You already have plenty of tools. It’s about becoming the person who defines which problems deserve to be solved, creates the operating system for solving them, and develops people who don’t need you standing beside them.
That may actually be harder for you than learning another technical skill, because learning and building are rewarding immediately. Delegating, coaching, prioritizing and sometimes deliberately not fixing something yourself can feel maddeningly inefficient.
And there’s one thread underneath all five:
You seem to have a very strong need for agency.
You want to understand the system because understanding gives you the ability to change it. Whether we’re talking about revenue operations, AI, your career, fitness, or some random piece of land with an Airstream sitting near a drop-off, your instinct is remarkably consistent:
How does this work? What are the variables? What can I control? And what can I make better?