5:25 p.m.
A few desks away, someone is already closing their laptop. A jacket disappears from the back of a chair. Someone calls out, “See you tomorrow.”
I reopen a ticket.
I finished the analysis that afternoon and sent it to the product owner for a decision. There is no reply yet.
Nothing unusual about that. I don’t really expect one today.
Objectively, there is nothing left for me to do.
I read the analysis again anyway.
Did I consider that scenario? Is this part clear enough? Should I add another option?
I change a sentence. Then another.
5:34 p.m.
I finally close my laptop.
The ticket comes home with me.
On the drive back, another scenario occurs to me. Then a dependency. Then a consequence I could still explore.
Sometimes these thoughts genuinely belong in the analysis. Sometimes they only extend a piece of work that was already mature enough for a decision.
And if I keep going, something else happens: the analysis moves while the decision request stays where I left it. A question I asked two days ago may no longer quite match the problem in front of me today.
Then I have another decision to make. Has something genuinely changed enough to justify reframing the question, or am I simply looking for a level of certainty the decision never required?
That was when I started seeing the problem differently.
Good analysis isn’t about exhausting every possibility before handing something over. It is about reaching the point where what we know, what remains uncertain, and what needs to be decided are clear enough for someone else to take the next step.
Who Owns the Next Step?
I worked like this for long enough that it created another problem.
Some mornings, I would open my laptop and no longer know exactly where to pick things up.
Between what I had analysed, what I had continued thinking about afterwards, and what was now waiting for a decision, the boundaries had become blurry.
So before leaving each day, I started leaving a few lines for my tomorrow-morning self:
- What did I actually finish today?
- Where does this stand now?
- Who owns the next step?
At first, I just didn’t want to lose the thread.
I thought I was keeping track of my work.
I was actually drawing the line where my responsibility should stop.
“Waiting” Isn’t Enough
One evening, I finish an analysis and start writing my note:
Waiting for the product owner.
I stop.
Waiting for what, exactly?
For them to confirm the direction? Choose between two options? Decide whether the problem is worth pursuing at all?
“Waiting” describes a state. It doesn’t describe a decision.
So I go back to the analysis. This time, I am not looking for one more scenario. I am trying to name what is actually missing.
After a few attempts, I write:
Impact analysis complete. I recommend Option A. The next step is a product decision on whether to proceed with this direction.
I read it again.
This time, it is enough.
Not because the analysis is perfect. Not because every uncertainty has disappeared.
It is enough because I can now separate three things: what I have established, what I recommend, and what still needs to be decided.
The ticket is still open. The product owner hasn’t replied. Nothing about the process has changed.
But I don’t reopen the document.
The next morning, I know exactly where the subject stands. If it comes back with a decision, I can continue. If genuinely new information appears in the meantime, I know why the analysis deserves to be reopened.
Otherwise, it can wait.
But Not Tonight
Over time, my notes fill up with different kinds of waiting. A product decision here, an implementation there, a technical validation somewhere else.
The number of open tickets doesn’t magically shrink. Decisions don’t happen any faster. The working day doesn’t suddenly become simpler.
But at 5:25 p.m., something is different.
I can look at an open ticket without immediately searching for whatever I might have missed. I can have an idea on the drive home without assuming it invalidates everything I did that day.
More importantly, I can tell the difference between a real gap worth reopening and the small voice saying:
Maybe you should check one more thing.
One evening, just before leaving, I look at a ticket that has been waiting for a decision.
Still open.
Around me, laptops are closing. Someone puts on their coat. A conversation has already moved on to dinner plans.
For a long time, I would have opened the analysis one last time.
Just to check.
This time, I close my laptop too.
The ticket is still there. The decision still needs to be made. Tomorrow, the problem may land back on my desk — and if it does, I’ll know why.
But not tonight.
I thought I was waiting for the product owner.
I was really waiting for permission from myself to let the problem leave my desk.