A story that serves as an argument—for or against. Your call.
Weuday, noun. The eighth day of the week. The day when the time, the light, and the traffic are all aligned, like the three hands in a working clock, and the energy that was stuck somewhere finally gets released. The day people do what they never get round to on the other seven days.
There is a calendar for it further down, with five days you can open.
You can read everything ever written about swimming. The water is still cold, the first length still hurts, and nobody at the pool cares how much you have read.
Many of the things we call learning at work are reading about swimming.
So let me ask the uncomfortable question about this story before you do.
You arrive with something that hurts. Support tickets increasing while the graph goes up. Two functions who have stopped speaking except through a project manager. A customer who cannot describe what you do. You pick the situation that sounds like yours, you read what I think, and something lands. You nod at your screen.
On Monday you walk back into a place where the person who could act on it has no particular reason to. The tickets are somebody's number and the fix is somebody else's quarter. The reorg is four weeks away. And the person you would have to convince is the one who made the decision you are now questioning.
You did not lack information. You never lacked information.
I call it a second-hand day. A day that feels as if it has already been lived by somebody else, somewhere. Plenty of good people spend years in one.
Nobody in this industry is short of answers. We are short of reasons.
A story cannot fix it. Nothing I write changes what your organisation rewards on the last Friday of the quarter, and I would rather say so here than let you find out on your own time.
Every city has a junction where the traffic dies. The people who drive it know it intimately. They know which lane fills first, which signal is mistimed, which turn nobody expects. They know it far better than the transport department does, and they have known it for years.
What is missing at that junction has never been knowledge. It is that no single person's job gets worse while it stays broken.
Your product has junctions like that. You already know where they are. If you are honest, you knew before you opened this story.
It runs the other way too.
Something happens to a person on a hill road when a waterfall appears where they were not expecting one. Or the evening they order something unfamiliar at the restaurant they have been going to for nine years, and it turns out to be the best thing on the menu. Or the phone call saying somebody in the family has been offered a doctoral position.
Something opens. They are more generous for a week. They tell people about it.
We do not take those chances at work anywhere near often enough. We order the same thing. We take the road we already know, in the name of predictability, and then wonder why the team feels flat in a quarter where nothing actually went wrong.
It does happen at work. Somebody borrows how a hospital runs its rota, or how a restaurant seats people who arrive without booking, drops it into a product problem, and the room changes. Same feeling as the waterfall, on an ordinary Tuesday. And exactly like the junction, nobody's job gets better for finding it.
Curiosity without incentives is a hobby. I have had both, and the hobby years were lonelier.
Here is the part that took me years, and it is the only reason I built this.
When you agree with something and still cannot do it, you have not failed to apply something you read. You have found the thing. The constraint is the finding. The wall you hit on Monday is a more accurate description of your organisation than anything in your strategy deck, and most teams never name it out loud because naming it feels like complaining. Framing is just going back to check the given—the thing everybody accepted without argument.
So the questions on this site are not here to make you more aware. They are here so that everyone in the room sees the same problem at the same time. Right now it is your private frustration. Asked out loud, in front of the people who can act, it becomes a specific and inconvenient fact that somebody has to answer for.
That is how an incentive actually moves. Not because a leader read something. Because enough people could describe the same problem precisely enough, often enough, that ignoring it began to cost more than fixing it.
Which is why none of this asks you to be better informed. It asks for something slower and far more useful: the capability to frame what is in front of you, the habit of going to look when you do not know, and enough conviction to say it in a room where it is not yet welcome.
Those three are not talents. They are practised, they are contagious, and they are the only things I have seen survive a change of leadership.
Remember that we are all support functions. Design exists to make engineering's work land, engineering to make marketing's promise true, marketing to make sure the thing we built meets somebody who needed it. I have never once been called into a problem that belonged to a single team.
Think of the spatula in a kitchen. It folds, it scrapes, it saves the pan at the moment everything is about to catch. It never makes it onto the poster for the dish. For me, it wins the best supporting actor award in the kitchen.
Teams who know this hold each other up when the quarter goes badly. Teams who do not, hand each other the blame and call it accountability. Or they do not bother about it at all.
Which brings me back to the three hands. Curiosity, framing, and incentives. Any one of them turning alone gets a team nowhere, and most of us have spent a year or two turning exactly one.
When all three point the same way, work stops feeling like negotiation and starts feeling like the thing you live for.
That is the eighth day, and nobody hands it to you. A Weuday. No reorg produces it. You build it slowly, out of the questions you were willing to ask before the incentives had caught up.
And if your framing is already sound and you do not want to explore scenarios, I am genuinely glad you looked in.
Go and spend the weekend somewhere else. A local museum. The library. A council meeting at the city hall. A gathering for somebody in your family who would notice you being there. You have earned it, and you will come back with more than this story could have given you.
Your strength is in your periphery. Not in what you find here, but in the question you are willing to ask on a Monday—before the incentives have moved, and before anyone has asked you to.
Any day can be a Weuday. Want to try?
{{ modal.statement }}
{{ modal.take }}
“{{ modal.question }}”
Finish the story first, and then explore the scenarios on Framing.