Get To Versus Have To

My CTO at Alpine Security had a habit I noticed in the first week I worked with him.

He would start a sentence, catch himself, and restart it. "I have to rewrite the assessment report tonight. Sorry, I get to rewrite the assessment report tonight." Every time. Client escalation on a Friday. A three-flight travel day. A retest nobody wanted. He would trip over the phrase, back up, and swap two words.

It was refreshing. I was used to being around technical people who ran on grievance, and here was someone who sounded genuinely grateful for his life and for what he got to spend it on. I liked it without understanding it. I filed it under personality, the way you file someone's taste in music, and assumed it was just how he was wired.

What I did not do was try it. That took a few years and one very long week, and now it is one of maybe five sentences from that entire company that I still use daily.

What I Believed Instead

My whole operating model was obligation. I was good at obligation. Air Force Academy, engineering degrees, a wall of three-letter certifications, then a company to run. The way I got things done was by making them non-negotiable. Have to was the engine. If I told myself I had a choice, some part of me would take the exit.

So I stacked up duties and dragged them behind me. Deliverables I had to review. Calls I had to take. A payroll I had to make. Flights I had to catch. On the outside that looks like discipline and it wins awards. On the inside it feels like being a very reliable pack animal.

And here is the part I did not see for years. Obligation was not neutral. It was quietly telling me a story about myself every hour of the day: things are being done to you. You are the person the work happens to. That is a small sentence with a very long tail.

The Wall

The week it broke open was an ordinary bad week. A medical device client had a submission deadline, a finding landed late, and the fix pushed a retest into a weekend that already had my name spoken for. I remember sitting in the office before six in the morning with cold coffee, listing everything I had to do that week, and feeling something closer to resentment than fatigue.

The resentment was the tell. I was resenting a company I had built on purpose, work I had chosen, clients I had pitched to win. Nobody had assigned me any of it. I had signed up for every single line on that list, and I was carrying all of it like a sentence someone handed down.

Then I heard him in my head, tripping over the phrase and backing up. I get to.

The Epiphany

Here is what I finally understood. "Get to" is not positive thinking. It is not gratitude journaling, and it is not pretending a hard thing is fun. It is a claim about authorship.

"I have to" says the decision happened somewhere outside of me and I am complying. "I get to" says I chose this, and I am choosing it again right now. Same task. Same deadline. Same weekend. What changes is who is holding the pen.

That is why it works on hard things and not just pleasant ones. I do not tell myself the retest is delightful. I tell myself I built a firm whose entire job is catching the flaw before it reaches a patient, and this weekend is what that looks like when it is real. If I would not choose it, that is information too, and it means something bigger needs to change than my vocabulary.

Which is the second half of the epiphany. If you try "get to" on a thing you genuinely would not choose, it will not hold. The phrase is a lie detector as much as a reframe. Most of my list passed. A couple of items did not, and those were the ones I needed to renegotiate or hand off, not repeat affirmations at.

Why It Is An Identity Swap, Not A Mood Trick

I have written about your primary question, the single sentence your mind runs on repeat under everything. "Have to" and "get to" work at that same layer. They are not describing your day. They are casting you.

Say "have to" a hundred times a day and you are rehearsing a character who is acted upon. That character does not push back on scope, does not pick the harder client, does not take the shot with the founder, because none of that is his to decide. Say "get to" and you are rehearsing an author. Authors renegotiate. Authors quit things. Authors also carry heavy things without becoming bitter about them, because they know they picked them up.

This is also why it is not soft. I have watched the language of obligation quietly kill ownership on good security teams. When an engineer says "I have to run this scan," the scan gets run and nothing else gets seen. When the same engineer says "I get to look at this device before anyone gets hurt," you get the finding that was not on the checklist. The words are upstream of the standard of work.

The Practice

It is small and it is boring, which is how I know it works.

For one week, catch the phrase out loud. Not in your head, out loud, the way my CTO did, and yes it is awkward in front of people. Trip over it, back up, swap it. "I have to fly to Dallas Tuesday. I get to fly to Dallas Tuesday." You are not trying to feel better. You are checking whether the sentence holds.

Then keep a short list of the items where it does not hold. That list is your real work. Mine had two entries the first time, and dealing with them was more useful than any productivity system I have tried.

Old Sentence Versus New Sentence

Read the right column and notice something. Every one of those is harder than the left column, not easier. That is the point. "Get to" does not shrink the task. It gives the task an author.

What Changed

I stopped feeling like the work was happening to me. My calendar did not get lighter, and I did not get more relaxed, which is not really my factory setting anyway. What changed is that resentment mostly left, and resentment is the tax you pay on a life you chose but will not admit you chose.

A guy I worked with a long time ago tripped over two words in front of me for a year until I heard him. That is the whole thing.

You do not have to read this post. You got to.