I’m interested in the little things a founder refuses to let slide.

The extra step a customer shouldn’t have to take. The product that works but still feels wrong. The sale everyone wants to close, except the person who knows what delivering it will do to the business.

Those decisions can start before anyone has a neat way to describe the company.

From the founder’s point of view, some of them may barely feel like decisions. Of course we fix that. Of course we don’t charge for that. Why would we make someone call us twice?

Then the company grows.

Someone new joins and makes a perfectly reasonable choice that the founder hates.

That’s the moment I find interesting.

The new person may have followed the brief, met the target and done what would have earned them a promotion at their last job. The founder still looks at the result and says, “That’s not how we do things.”

There is something to understand in that disagreement.

Maybe the founder is protecting a standard customers value. Maybe they’re protecting a personal preference that has outlived its usefulness. I wouldn’t want to decide which without looking at what the choice changes for customers and for the people doing the work.

But if the standard matters, “you should just know” won’t carry it very far.

A new employee needs to understand the trade-off. What are we willing to spend more on? When will we disappoint someone? What should happen when making life easier for a customer makes this month’s numbers look worse?

That is where I start to see the company taking a particular shape.

If the founder personally fixes every problem, the customer benefits from the founder’s involvement. Passing on the standard takes more work. People need enough context and authority to make the decision themselves, including when following the standard has a cost.

I think this is an overlooked part of positioning.

People can search for words to explain what makes the company different while the clearest evidence sits in decisions they have been making for years. Finding language for that can help. It can give the team a way to recognize a pattern and discuss it.

The wording still has to survive an ordinary working day.

I’d want to look at a decision made while the founder was away. A refund someone approved. A deadline someone challenged. A feature someone left out, even though a potential customer asked for it.

What did the person consider? What did they protect? Did the company back them when the consequence arrived?

I don’t expect everyone to imitate the founder. That can turn a business into a very elaborate guessing game.

I’m interested in whether people understand the standard well enough to apply it to something the founder hasn’t encountered yet.

That would give me more confidence than a room full of people who can repeat the same sentence.

Image: Patagonia’s founder.