You Don’t Have to Be Exceptional Every Day

There were many days in my career when I completed everything I needed to do. I wrote the code, closed the tickets, answered the messages and attended the meetings. Nothing went wrong, nobody needed rescuing and the work moved forward exactly as it should have.

Yet I would still reach the end of the day feeling disappointed in myself.

I had done my job, but I had not done anything exceptional. There was no clever solution I was excited to tell somebody about, no impossible problem that only I could solve and no moment that made me feel particularly brilliant. It had simply been a normal day, and for a long time, normal did not feel like enough.

There is a particular kind of pressure in tech to be exceptional. We celebrate the person who solves the impossible bug, builds something impressive over a weekend or learns a new framework before most of us have finished our first cup of coffee. It can start to feel as though doing your job well is only the beginning. You should also be constantly learning, building, sharing and proving that you deserve to be there.

Some of that pressure came from the expectations I saw around me, but much of it came from within. I felt as though I needed to prove myself over and over again. Completing my work was simply what was expected of me. To feel proud of myself, I believed I needed to do something more.

The trouble with expecting yourself to be exceptional every day is that exceptional eventually becomes your minimum. The things that once would have made you proud begin to feel ordinary, and anything less starts to feel like failure.

At the time, I did not know that I had ADHD. I did not understand why my concentration and energy could change so much from one day to another. On some days, my brain would happily attach itself to a complicated problem and refuse to let go. On others, getting it to cooperate felt like negotiating with a toddler who had missed a nap.

Because I did not have an explanation for those differences, I treated them as personal failures. I expected the same level of focus, energy and output from myself every day. When I could not produce it, I assumed I was not trying hard enough.

Being diagnosed did not make the difficult days disappear, but it helped me understand them. Now, when my concentration or energy is lower, I can adjust instead of spending the whole day fighting myself and then feeling guilty because the fight made everything harder.

Looking back, I also realise that I never saw the people I admired having ordinary days. I cannot remember a leader admitting that they were struggling to concentrate, that their first idea had been terrible or that they had only managed to complete the basic work they had planned for the day.

I am sure they had those days. They were human, after all. But they never shared them, which meant I had nobody showing me that slower, messier and less productive days could exist alongside competence.

When leaders only show people their most productive and polished selves, everyone else is left comparing their ordinary reality with somebody else’s best moments. We begin to believe that capable people wake up exceptional and somehow remain that way until they close their laptops.

That is not how people work.

Some days you will solve the difficult problem. You will have the idea that changes the direction of a project or surprise yourself with how much you manage to accomplish. Other days, you will write the code, close a few tickets and go home.

That is still a successful day.

My definition of a good day has become much simpler as I have grown older. If I complete the tasks I planned to complete, I am happy. If I manage to do more than that, I am very happy. I no longer need every day to produce a story worth telling.

A large part of this change came from realising that my job is not my identity. I care about my work and still want to do it well, but it is one part of my life. It is not the proof that my life has value.

There are people I love, dogs waiting for cuddles, meals worth cooking slowly and an entire life that exists after I close my laptop. Setting clearer boundaries around my work has helped me protect room for those things, and it has changed what I expect from myself.

It has also changed how I respond when somebody on my team is clearly having a low-energy day. I do not immediately assume they are lazy, disengaged or becoming less capable. Sometimes a person is simply tired. Sometimes their brain is refusing to load properly. Sometimes today is not going to be the day when they produce their finest work.

I tell them to complete as much as they reasonably can and then go and rest. Tomorrow they may return with completely different energy and accomplish far more than they would have by forcing themselves through another exhausted afternoon. Rest is not the opposite of productivity. Sometimes it is what allows good work to happen again.

Of course, one low-energy day is different from a recurring pattern in which work is not being completed and nobody is communicating about it. Giving people room to be human does not mean removing accountability. It means responding to the situation that is actually in front of you instead of treating every imperfect day as a performance problem.

People cannot produce exactly the same amount of work, at exactly the same quality, with exactly the same enthusiasm every day. Even machines need maintenance, and they do not have meetings.

You are allowed to have days that are useful without being impressive. You are allowed to complete your work without turning it into a personal triumph. You are allowed to close your laptop without having learned a new language, launched a side project or discovered a revolutionary use for AI before dinner.

Ordinary work still matters. It keeps projects moving, supports the people around you and creates the foundation for the exceptional moments when they do arrive.

You do not have to prove your value every day. Sometimes doing what you set out to do is enough, and enough is worth being proud of.