top of page

FIELD NOTE | 

July 4, 2025

Hard Isn't the Same as Rigorous

Some difficulty belongs to the problem. Some belongs to the way we've designed the work. Knowing the difference matters.

For a long time, when something was harder for me than it seemed to be for everyone else, I assumed the thing that needed to change was me.

Try harder. Learn the rule. Build the compensating system. Figure out what everyone else seemed to know.

I got very good at this.

The concept of legally mandated accommodations forced me to reckon with the possibility that I hadn't been on a level playing field. It still took me years to accept that I was disabled enough to deserve—and, more importantly, need—things that made some parts of life easier.

Easier was the part I struggled with.

I had internalized a strange standard of evidence: if I could do something at all, then I couldn't really need help doing it.

The cost didn't seem to count.

It didn't matter how much preparation it required, how exhausted I was afterward, what else I couldn't do because I had spent my capacity there, or how elaborate the systems around the task had become. Successful completion was treated as evidence that the environment worked.

Including by me.

I had already demonstrated that I could do it the hard way. I could white-knuckle my way through an environment that wasn't particularly interested in how my brain worked. I could compensate. I could build systems around myself. I could learn how to word things so another person didn't find offense where none was intended. I could survive a tremendous amount of sensory and cognitive load and still perform.

Being capable of surviving something is not the same as being well supported by it.

Before I was interested in systems design, I was interested in architecture. I spent too many years studying the design of built environments for it not to have shaped how I think about systems now. One idea in particular stayed with me: use a material in the way it wants to be used.

Pay attention to its properties. Maximize its strengths. Don't force the material to conform to the method simply because the method is familiar.

I don't think I realized I was writing about people.

Including myself.

I've spent much of my career in startups, where difficulty can become part of the mythology.

At one company, I worked with a senior leader who was deeply skeptical of adding much operational structure. When I pushed on some of the resulting friction, the explanation was often some version of: It's a startup. We move fast. It's hard here.

And some of it was.

Startups contain enormous amounts of difficulty you don't get to choose. You don't know whether the thing you're building will work. You have incomplete information and limited resources. The organization is changing while you're trying to build it. Customers surprise you. The market moves. Decisions sometimes have to be made before you know enough to feel comfortable making them.

That's hard.

But there is another kind of hard.

Nobody knows who owns the decision. The information needed to make it lives in three people's heads. The same emergency happens for the fifth time because nobody has stopped to build the mechanism that would prevent the sixth. People spend their capacity compensating for the absence of structure and then the resulting exhaustion is offered as evidence that startups are simply demanding places to work.

Some difficulty comes with the territory.

Some difficulty we keep choosing.

And some has been around long enough that we've forgotten it was a choice at all.

I don't think those should receive the same amount of reverence.

I think these are versions of the same mistake.

We look at what someone managed to accomplish under difficult conditions and treat their ability to accomplish it as evidence that the conditions were necessary—or at least acceptable.

But endurance doesn't tell us that.

Sometimes it only tells us what someone was capable of enduring.

This has changed the way I think about rigor more broadly.

Some difficulty belongs to the problem.

Some difficulty belongs to the way we've designed the work.

Those are easy to confuse because both feel hard to the person experiencing them.

Building something genuinely new is difficult. Making consequential decisions with incomplete information is difficult. Learning something you do not yet know is difficult. Telling someone the truth when the truth is uncomfortable is difficult. Caring for people is difficult.

But finding the information you need because it lives in six systems isn't rigor. Waiting three weeks for an approval nobody can explain isn't rigor. Sitting through a recurring meeting because nobody has clarified who can make the decision isn't rigor. Making someone infer expectations that could simply have been stated isn't rigor.

It's friction.

And removing friction doesn't lower the standard. It leaves more capacity for the difficulty that actually belongs to the work.

We have plenty of real difficulty available to us.

Maybe good design isn't about making everything easy.

Maybe it's about being much more discerning about where we spend difficulty.

The standard can remain high. The work can remain hard. The problem can remain ambitious.

We can spend our difficulty somewhere more interesting.

bottom of page