If you lead with the INTP pattern, you don't fall for the obvious version of this problem. You'd never describe your work as just a paycheck — that would be philistine, and you're far too interested in ideas to live that way. Your relationship to meaning is sharper than that: a task means something to you precisely as long as it's an unsolved problem. While there's a model to build, a mechanism to grasp, a question that isn't yet answered, you're alive in the work and it has all the colour in the world.
But here is the catch that's specific to how your mind runs: the meaning is tied to the puzzle, and the puzzle dies the instant you understand it. The moment you've grasped how the thing works, the curiosity is sated, the lights go out, and what remains — the building, the maintaining, the documenting, the actually-shipping — feels like grey, mundane transcription you have to drag yourself through. So your days don't drain because you treat work as money. They drain because you've quietly let 'interesting' be the only thing that's allowed to count, and interesting is the one thing that always runs out.
Novelty is not the same as meaning
Watch what actually happens across a typical project. The opening weeks are electric — a new domain, a fresh problem, a model assembling itself in your head — and you'd swear the work is deeply meaningful. Then you crack it. You understand it. And almost overnight the same project becomes a chore you resent, even though nothing about its purpose changed. The only thing that changed is that the puzzle got solved. What you were calling meaning was really just novelty, and novelty has a short half-life.
This matters because if novelty is your sole source of meaning, your working life becomes a series of cliffs: a thrilling climb followed by a dead drop the moment comprehension arrives, repeated forever. You'll keep concluding the job has gone meaningless and you need a new one — when in fact you've simply reached the part of every job that isn't a puzzle. Meaning that evaporates on contact with mastery isn't meaning. It's stimulation wearing meaning's clothes.
Anchor it to something that doesn't get solved
The fix is to deliberately attach the work's meaning to something that can't be exhausted by understanding it. A puzzle is finite — once solved, it's gone. But who your work actually helps, what it lets other people do, what it builds over time, what you yourself are getting steadily better at: none of those are solved and then over. They persist after the interesting part is mapped, which is exactly when you need them.
For you, the most reliable of these is mastery, because it speaks your language. Reframe the boring back-half of a project not as tedious transcription but as the only phase where you go from someone who understands the thing to someone who can reliably do the thing — a far rarer and harder skill than comprehension, and one you're conspicuously weak at. That's not beneath your intelligence. Closing the gap between knowing and executing is the hardest problem you personally have, and it doesn't get solved in a week.
The follow-through is where the meaning actually lands
Be honest about where your work tends to die: at follow-through. You grasp something brilliantly and then drift off before it's finished, because the meaning left when the mystery did. But the part you keep abandoning is the only part the world ever receives. Your elegant understanding helped no one and built nothing while it stayed in your head; the half-finished thing on your desk is closer to mattering than the perfect model you never executed.
So locate the work's meaning specifically in the stretch you're tempted to skip. Not in the moment you understood the problem — that moment was for you alone — but in the unglamorous act of carrying it all the way to something real that a person can use. When you tie meaning to landing the thing rather than to cracking it, the dull execution phase stops being a betrayal of your intelligence and becomes the place where your intelligence finally does something outside your own skull.
Detachment is comfortable, and it's costing you the colour
Your default is to stand back from your work — analysing it, optimising it, never quite inside it — and that distance feels like sophistication. But detachment is also how the days go quietly grey. If you relate to your work as an interesting object you observe from across the room, you'll feel the cool pleasure of analysis and almost none of the warmth of being invested in something that matters to you. The remove that protects you from caring also strips out the colour.
You don't have to manufacture some grand calling to fix this — that framing would rightly make you suspicious, and you don't need it. You only need to let yourself care, in a low-key, concrete way, about one downstream effect of what you do: a specific person it serves, a real thing it makes possible, a capability you're visibly growing. Caring about something small and actual is unglamorous and slightly uncomfortable for you. It's also the difference between a working life you watch and one you're actually in.
Your work doesn't go grey because you treat it as a paycheck — it goes grey the instant you've solved the puzzle, because you let novelty be the only thing that counts, and novelty always runs out. Anchor the meaning instead to what survives understanding: who it helps, what it builds, and the skill you're slowly mastering. Put the meaning in the follow-through you keep abandoning, let yourself care about one concrete downstream effect, and the colour stops draining out of every job the moment you finally get it.