The bridge: Restoring humanity in the daily work
In the last post we defined the “Mountain” and the “Signal” at the top. Now it’s the time to talk about a common disconnect: teams who know how to build but have lost touch with the “why it matters” to the human at the other end. I sense a fear to talk to the users. Like a fear of change, or “Why should I ask them? They’ll change their mind anyway”.
If we look past the textbook definitions of Agile and look at the reality of the floor, we often see teams coding in isolation - silos tucked away in offices, far from the pulse of the user. I want to talk about users that use the product, wether they like the product or not, whether they complain about functionalities that they need or not. I’ve seen so many times this environment that i want to make sure people understand that this is not normal.
I want to be clear: This is not normal
Purposeful development
People thrive in a purposeful environment, wouldn’t you say so? In his book Man’s Search for Meaning, Viktor E. Frankl argues that the primary drive in a human being is the search for meaning. I agree. If purpose is our engine, why do we continue to work in teams with no clear scope beyond "clearing the ticket queue"?
When we ignore the principles of "satisfying the customer" or "harnessing change for competitive advantage," we aren't just being inefficient. We are robbing development teams of the energy to strive for better products and better work.
More importantly, we are robbing them of human interaction.
I believe human interaction is the bedrock of our mental well-being. Science consistently shows that people who are socially integrated and connected to their community live longer, happier lives. Why should our professional lives be any different?
When a development team hides behind a Product Owner, only asking for feedback at set intervals, they are cutting themselves off from the source of their purpose. What truly stops a developer from talking directly to an end-user?
In reality, nothing.
What to do?
Do you fear the users?
If you feel the “fear of the user” or the walls of your silo are too high, don’t try to tear them down overnight. Start by tuning your proximity, your team. Focus on what you can change, not what you don’t have any impact over:
Ask your PO if you can sit in on one client feedback session. Don’t speak, don’t judge. Just listen to the tone of their voice when they describe a pain point - if they do. There’s a case they won’t and this might be either because there isn’t one, or there would be but it’s too uncomfortable to raise it. Do not make assumptions - interview both parties separately afterwards.
Spend 30 minutes watching a user actually navigating the UI of the product. Don’t explain the features - just watch where they usually stumble, if they do. You’ll find more meaning in this interview than in 100 refined tickets
Next time you pick up a ticket, don’t ask how to build it. Ask: “Whose life does this make easier today?” if nobody knows the answer, that’s your signal to start a conversation.
Remember this
Your work exists to make life easier and more meaningful for the person on the other side of the screen. If you want to know how to reach them, stop guessing. The shortest, most effective path to a better product isn't a better process—it's a direct conversation.
