notes · thoughts ·
The ticket had the task, but not the reason
Sometimes the implementation is clear while the customer problem and success criteria are missing. Sharing why we are building should be part of development too.
Sometimes I know exactly what to do without really knowing why. The ticket says which API to integrate and which screen to change. But it does not show what is troubling the customer or what should improve through this change.
At first, I thought I wanted more involvement in planning. Looking closer, the frustration was less about not making every decision myself than about having less information to understand the problem while still being responsible for solving it.
Without the reason, even small implementation choices lose their basis. When I find an unexpected state, it is harder to judge what matters most or whether there is another way beyond building exactly what was requested. Completing a feature can drift away from solving the customer’s problem.
We do not all need the same role
I am not asking for a team where everyone handles everything from planning to development. I want a team where people can do their own jobs while understanding what the thing they are building means to users.
Even a short shared view of the core customer problem, the scope of this change, the criteria for success, and what remains undecided would help. It need not be a perfect document from the start. If I write down my understanding and correct what is wrong, we can at least notice when we are working from different assumptions.
When context stays in one person’s head, that person has to keep explaining and everyone else has to keep asking. If the reason drops out while requirements are passed along, each stage may be completed while the overall purpose grows unclear.
I hope asking about the background of a requirement is not seen only as an attempt to take over decisions. It can be a question needed to implement it well. When I ask, I also want to begin by saying that I want to understand the user problem, rather than opening with criticism of the decision. Alongside building, I would like us to keep sharing why we are building.