Here's the mistake everyone makes about themselves: I spend my time doing X, so X must be my strength. I'm drawn to planning, so I must be a good planner. I gravitate to building, so building is what I bring to the table.
Pull and competence feel like the same thing. They're not. They're perpendicular. You can be drawn to planning but produce vague plans. You can be drawn to building but produce sloppy work. You can be drawn to questioning purpose but ask the wrong questions every time. The gravitational pull toward an activity and the actual skill to do it well are completely different facts about a person.
This isn't a minor nuance. It changes the entire way you should read your own work.
What attention actually is
This needs a careful definition, because "attention" gets used loosely and that looseness creates real problems.
When I say "attention," I don't mean what you spend hours on. I don't mean effort. I don't mean interest or passion. I mean something more specific: the pull that forms in your mind before you've decided anything.
Every making situation has six activities running through it. Six different ways to engage with what's happening. And when you walk into a situation, your perception doesn't fire equally across all six. It latches onto one. A question forms. That question is your attention.
Some people walk in and the first thing they see is the gap between what's needed and what's achievable. Can we actually pull this off? That's their perception organizing the situation. Others walk in and immediately see what the thing should be, the shape of the solution, the gap between what's intended and what's been specified. Others see resource gaps, or untested assumptions, or process problems the output is revealing, or concrete work that could be produced right now.
These aren't decisions. They're orientations. The filter that makes certain features of a situation feel urgent while others don't register at all. Two people walk into the same room. One sees a capacity problem. The other sees a purpose problem. Neither is wrong. Both are partial. And neither chose which question to ask first.
Why pull doesn't track skill
There's a plausible story for why pull should predict ability. If you're drawn to something, you do it more. Practice makes better. So preference and competence should converge over time.
Sometimes they do. But the convergence is contingent, not guaranteed. And it's not the interesting thing about attention.
The interesting thing is what your attention pattern predicts about what you miss.
Attention is finite, that is, it sums to one. So whatever gets the lion's share is claiming budget from everything else. The activities that don't feel urgent to you get starved. Not because you've decided they don't matter but because your perception genuinely doesn't foreground them. You don't see the need, so you don't meet it, and you don't notice you're not meeting it.
This is a super secret diagnostic power: Not "what am I good at?" but "what does my perceptual filter systematically fail to see?"
Take someone whose attention naturally flows to production. Building things, turning ideas into artifacts, closing the gap between concept and reality. They can be phenomenally productive. But that attention has to come from somewhere. It might be flowing away from the question of whether the right thing is being built. Away from checking whether ambition has outpaced capacity. Away from reading output for what it reveals about the process that produced it. The production can be prolific and fundamentally misaligned. And they won't see the misalignment, because seeing it would require the very attention they're not giving.
The strengths inversion
Most self-assessment tools treat your pull as your gift and build from there. Find what you're drawn to, develop it, orient your career around it. It's a comforting story. And it skips the question that actually matters: what if the thing you're drawn to is also the thing currently breaking your work?
If you over-attend to specifying what things should be, you can spend years perfecting a blueprint that never gets built. The architecture becomes the deliverable. Revision after revision feels like progress. But the blueprint never collides with reality, which means reality never gets to tell you where you're wrong.
If you over-attend to building capacity, you can spend years preparing. One more course. One more tool. One more process upgrade. Every step defensible. Every step delaying. The actual making stays one preparation away, forever.
If you over-attend to optimizing your process, you can get extraordinarily efficient at producing things nobody asked for. The quality metrics improve. The velocity increases. And none of it connects to actual need, because the activities that would provide that signal aren't ones your attention foregrounds.
Every one of these pathologies comes from a genuine strength running without the counterweight that would keep it useful. And the person stuck in one usually can't see it. The activities that would generate the corrective signal are the ones their perception systematically skips.
Not "what are my strengths?" but "what do I systematically miss?" The first question flatters. The second one is useful.
Mastery isn't flattening
People hear this and land on: "So I need to be equally good at everything?"
No. You can't flatten the pull, and you shouldn't try.
What mastery develops is two specific capacities. Diagnostic skill: reading what a situation actually needs regardless of what your attention screams at you. And override capacity: acting on that diagnosis even when it runs against the grain of your preference.
Your attention is a gravitational field. The activities you naturally orient toward are massive bodies. Effort falls toward them without your deciding it. Mastery isn't the absence of gravity. It's escape velocity. The field stays. You learn to steer within it.
Both capacities can fail. Diagnostic failure: you misread what the situation needs, so you attend to the wrong activity with perfectly good intentions. Override failure: you read it correctly and can't make yourself act on it. The pull wins even though you know better.
Both get worse under load. Fatigue, time pressure, cognitive overload. These are the conditions where gravity wins.
Attention is a skill
If you take this seriously, you stop treating your default orientation as your identity. "I'm a builder" or "I'm a planner" becomes a description of where your attention budget concentrates, and therefore what it starves.
You start reading project failures diagnostically. Not "what went wrong?" but "which activity was chronically under-attended, and does that match what my pattern would predict?" A project that built precisely what was specified and still failed? That's a Validation signature, a failure to test output against actual need. A project that prepared endlessly and never shipped? That's a Solution-starved pattern. A project that shipped constantly and never improved? That's a Verification gap. Each failure has a structural shape, and that shape is predictable from the attention profile.
You develop a different relationship with the activities you find boring. They're not weaknesses to route around. They're the blind spots where your work is most likely to break. Knowing that lets you build compensation: collaborators who see what you don't, checkpoints that force the questions you skip, structures that route attention to where your pattern naturally starves it.
Your making pattern is where your attention wants to go. It's not a ceiling. It's a starting point. What you build with that knowledge is the work.