Position vs. Slope: The Diagnostic That Predicts Your Future
Position can be recovered. A flat slope cannot.
What did your last performance review actually measure? Your title that quarter. Your output on the projects your manager happened to see. Your behavior in the meetings she happened to attend. All of it true, none of it the whole story. That’s the snapshot — where you’re standing right now. And if you have a Spiky Profile, the snapshot has a habit of lying to you, because it captures your Position and misses the thing that actually decides your future: your Slope.
Position is where you are. Slope is where you’re heading — the direction the photograph is moving. Almost nobody looks at it, including the people grading you.
Here’s the strange part. The Spiky mind is often better at reading Slope than anyone in the room. You walk into a stuck project and feel the path forward before anyone’s said it out loud. You sense the org quietly rotting under a healthy-looking quarter. You notice the relationship drifting toward roommate status while the calendar still says everything’s fine. That’s not luck and it’s not a hunch. It’s the same pattern-recognition engine that makes it hard to stop thinking about a problem at 2 a.m. Pointed outward, it reads trajectories. It sees where the line is going while everyone else is admiring where the dot is sitting.
The catch is that the same engine that reads everyone else’s Slope tends to go quiet on its own. You can diagnose a colleague’s flatlining career in ten seconds and spend three years not noticing your own.
So let me show you the diagnostic by telling you about the month it made me visible.
Early in my career, fresh out of a master’s, I landed on a data conversion project for a major global energy company — one of the largest in the world. Data conversion means taking a company off its old software and onto new software without losing or corrupting anything in the move. Tedious work, careful work — not what you picture when you finish a graduate degree, and I’ll admit I was a little deflated to be doing it.
My Position, in that moment, was junior analyst doing the unglamorous job. That’s what the snapshot said. That’s what anyone glancing at the room would have read.
Then a requirement came in late: a category of records called milestone contracts. Three hundred million dollars’ worth. They couldn’t be moved with the standard automated approach — they were built differently from everything else, and migrating them meant mastering a finicky SAP tool called the Legacy System Migration Workbench. Everyone else on the project had spent a year preparing their pieces. The milestone contracts had no owner. The room went a little quiet around them, the way rooms do when something hard lands and no one wants it.
I said I’d take it.
Not because I knew how. Because I knew I could learn how — and that’s a different kind of knowing. I did the obvious thing: bought the manuals on Amazon with my own money and read them at night. I tested the tool against every other object I could get my hands on, over and over, until I understood not just how it worked but how it broke. Inside of thirty days I’d gone from never having touched it to being the person who understood it best on the project. The work was tedious. The way I metabolized it was not.
That’s the Spiky tell, and it’s worth naming precisely. It wasn’t only the speed of learning. It was the willingness to step into the unowned problem, plus a kind of overcommitment to the outcome I couldn’t switch off — staying late not to look good but because three hundred million dollars in stuck contracts genuinely bothered me, the way an unfinished thought bothers you until you close it.
Then came Go Live — the window where everything has to migrate cleanly, all at once, inside a locked timeframe. I set the tool to process the contracts. It crashed. The transaction bounced and the whole batch failed.
But I’d already broken this thing a hundred times in practice, so I wasn’t guessing. I’d learned that even when the tool couldn’t build a full contract in one pass, it could create an empty one — and it could fill an existing one. So mid-crisis I stopped the batch and rebuilt the approach on the spot: create the skeletons first, then run a second pass to populate the items inside them. Two moves instead of one. It worked. The contracts migrated cleanly on the first day of Go Live — three hundred million dollars that would otherwise have hung in limbo for another month or more, revenue not arriving, a marquee client exposed, and instead it just worked.
Here’s the diagnostic point, and it’s the whole reason I’m telling you this. My Position never changed during that month — on paper I was the same junior analyst I’d been on day one. But my Slope went vertical, and from that point on I wasn’t the person who did data conversion. I was the person who solved the problem no one else would touch. Nobody promoted me into that. I read a trajectory — I can become the one who owns this — and walked the line until the snapshot caught up.
This is why the Spiky Profile is so easy to misjudge — by others and, more dangerously, by yourself. In a trough week your Position looks bad and the snapshot screams that you’re falling behind. But the snapshot is a lagging indicator, reporting on a past that’s already gone. Your Slope — what you’re learning, what you’re stepping into, how fast you metabolize the new thing — is the leading indicator, and it’s the only one that predicts where you actually land.
And underneath it all sits one asymmetry: you can recover from a bad Position, but you cannot recover from a flat Slope. A weak snapshot with a steep trajectory becomes a strong snapshot on its own — give it time. A strong snapshot with a flat trajectory is just a slow decline that hasn’t announced itself yet.
That’s why the most dangerous situation in any life is a high Position sitting on a flat Slope — precisely because it feels so safe. Strong title, comfortable pay, predictable days. By every visible measure you’re winning, and by the only measure that decides the next five years, you’re drifting. And the cruelest version is the Spiky one: a mind that can read trajectories better than almost anyone, sitting inside a role that quietly pays it to stand still.
So here’s the move: a six-cell grid.
Draw it small. Three rows — career, health, finances. Two columns — Position and Slope. One rule before you fill anything in: never add or multiply the two columns together — they measure different things. You read them side by side, one row at a time.
Fill the Position column, one to ten. This is the snapshot — where you stand today. Career: title, pay, standing. Health: how you’d read today’s checkup. Finances: the number in the account right now. Be honest, not generous.
Fill the Slope column, negative five to positive five. This is the trajectory — which way the line is moving. Career: are you learning faster than last year, or coasting on what you already knew? Health: is your fitness rising, holding, or sliding fifteen minutes of sleep a year without your noticing? Finances: is your savings rate compounding or leaking? The number isn’t about today. It’s about the direction.
Read each row for the gap. A high Position next to a positive Slope is fine — strong and still climbing. A low Position next to a positive Slope is also fine — it’ll fix itself if you hold the line. The dangerous row is the one where Position is high and Slope is flat or negative: the comfortable snapshot sitting on a quietly falling line. It’s almost always the row you’d least expect, because it’s the part of your life you stopped auditing precisely because it looked fine.
Now extrapolate the worst Slope. Take your lowest Slope number and draw that line forward five years. Don’t soften it. If it keeps running exactly as it runs today, where does it land you? That projection is the destination your current trajectory is actually pointed at — and seeing it while a few degrees of correction can still change where you arrive is the entire reason to run this. Discomfort now is cheaper than surprise later.
The Slope column is always the one to act on. Position is just accumulated Slope — the past, already banked and unchangeable. Slope is the part you still hold the controls on, and reading it means pointing that pattern-recognition engine at yourself for once. Most capable people have never separated their Position from their Slope on paper, and the first time they do, the dangerous row is obvious — and so is where the next month belongs.
Slope is also what the Architect’s Equation’s Extrapolation factor is actually measuring — the audit and this grid are two instruments reading the same dial. The thing to carry out of today: stop grading yourself on the snapshot. Anyone can read your Position, including people who wish you well and have no idea where you’re going. Your Slope is yours to read, yours to steer, and the only number that’s ever told the truth about where you’ll end up.
If you want the next move in your inbox, subscribe — it’s free, every week. The full architecture is in the book, The Spiky Profile, coming soon.