Values

Every values page reads the same. Integrity. Excellence. Innovation. Words picked because they sound good in a pitch deck, not because anyone checked what keeping them actually costs.

I sat down to write this page the same way and got three sentences in before I threw it out. Every value I'd picked felt performed the moment I tried to explain why it mattered.

So I started over with a harder rule: nothing goes on this page unless it already cost me something real, a feature I killed after building it, a client conversation I didn't enjoy having, six months of tracking my own confident calls and finding out how often they were wrong. That cut the list by more than half.

If a value on this page never cost me anything, I cut it before you got here.

Understanding is the one delegation I never make

I hand AI the draft, the structure, the first pass through a dataset too large to read by hand myself. I hand it a good share of thinking too, letting it surface options I wouldn't have generated alone.

What I don't hand over is deciding whether any of that is actually right. I've caught myself typing a prompt before I'd worked out what I believed, and watched the answer come back sounding just as confident either way. That's the one delegation I won't make twice.

I can't see my own blind spot by trying harder

A fish doesn't experience water as water. It's just what's there, invisible because it's everywhere. I've caught myself running the same tunnel vision on my own thinking, certain I was seeing clearly when I was only seeing what my own frame let through.

Trying harder doesn't fix this the way effort fixes most things. The machinery that builds my experience is built to hide its own operation, so I need something outside the frame, a second opinion, a client's confusion, a number that refuses to move, before I can even see there's an edge to look past.

A good outcome doesn't mean I made a good call

For six months I tracked every confident call I made and checked it later against what actually happened. Some of the calls that turned out fine were wrong reasoning that got lucky. Some of the ones I doubted most were right for reasons I hadn't considered going in.

I'd rather trust the record than the feeling. A good outcome tells me the bet paid off; it doesn't tell me the bet was sound, and confusing the two is how confident people keep making the same mistake without ever finding out.

Your budget and your calendar are your real strategy, not what you say about it

The same self-account I can't fully trust when I'm judging a decision, I can't fully trust when I'm describing my own priorities either. Ask most people what they're prioritizing and you'll get a clean answer. Look at where their money and their hours actually go, and the two rarely fully match. That gap isn't dishonesty so much as it's easier to describe a strategy than to live inside its real constraints.

I hold myself to the same test I'd apply to a client: not what I'd say if you asked, but what my own calendar and spending actually show. I won't pretend that's a settled score. It's a standard I check myself against, not a receipt I can hand you.

Telling you it's handled isn't the same as you understanding it's handled

That same test gets harder once someone else is waiting on the answer. "It's handled" is the sentence I reach for when I want a client to stop worrying, and it's the sentence I trust least when someone says it to me. It reports how the speaker feels, not what actually happened or what almost went wrong.

I try to close that gap before you have to ask, not reassure you after you already did. A status update that makes you feel calm isn't the same as one that makes you actually understand what's true.

The outcome doesn't respect the boundary

That same gap doesn't stop at what I tell you. It shows up at the edge of my own job description too.

"That's not my department" doesn't change what you actually experience. A channel can perform perfectly while the system around it fails: rankings climb and revenue never moves, because the problem was never the channel. I follow a problem past the edge of my own role, my title, my discipline, because the outcome is what I actually owe the market, not the process that's supposed to produce it.

Finishing isn't the same as solving

The same test applies to my own output, not just my role. Eric Ries spent a chunk of The Lean Startup on a simple, uncomfortable idea: a team can hit every release date on the roadmap and still not know if it made anything better. Shipping velocity gets treated as proof of value delivered, when the two are actually independent.

I've built features that worked exactly as specified and moved nothing that mattered. Now I ask the harder question before the faster one: not did we ship it, but did it change anything for the person using it.

Changing a mind takes longer than a reporting cycle, and that mismatch kills good ideas

The same gap between what got measured and what actually got proven shows up on a longer clock too. I've watched a good decision get killed a quarter early because the numbers hadn't moved yet, and nobody could tell whether that meant it failed or just hadn't had time to work. Perception moves on a six-to-eighteen-month timescale; reporting happens every quarter, and that mismatch punishes patience.

Failing positions don't usually persist from stubbornness. They persist because the cost of staying is invisible while the cost of changing course is immediate and visible to everyone in the room. I watch for that pattern in my own decisions now, not just in the org charts I used to diagnose it in.

Data gets you closer, not there

Measurement narrows the gap between the map and the ground. It rarely closes it: tracking has holes, and a dashboard is still a map. Every metric I add answers a question I already knew how to ask; it doesn't tell me which question I stopped asking to make room for it. And a survey only ever reaches what someone's willing to say out loud; most of what actually moves a decision never shows up in what people tell you about it. I'd rather do the harder work of making contact with what's actually happening than trust a number that can't push back, even though that's the slower way to be right.

Every person added to a decision adds a conversation with everyone already in the room

The same blind spot scales with headcount too, not just with metrics. Add one person to a four-person decision and you haven't added one conversation. You've added four: one with each person already in the room. Capacity grows in a straight line. Coordination cost grows by the square of the group size, and past a certain point the math wins regardless of how good everyone in the room is.

I learned this the expensive way, watching a team model built for speed slow down every time it grew. Four wasn't an arbitrary number I picked. It was the largest group I could add to a decision without the coordination cost quietly eating the reason I'd added them.

Success doesn't make me right, it makes me harder to correct

Rising authority insulates a person. That insulation gets defended by whoever's around them agreeing more than they used to. When something goes wrong inside that bubble, it's easier to blame the person in the seat than the seat itself, and when something goes right, the credit lands on the person regardless of what actually caused it.

I've felt the early version of that cycle start on small wins: a client praising a call I got lucky on, a post landing better than the argument deserved. Watching for it in myself is the only defense I've found, since nothing about winning makes the cycle announce itself.

That's the whole list, not the twenty I started with before the rule did its work. A shorter page that survived contact with the record beats a longer one that never had to.