I’ve done my best product work when the right people are involved early enough to change the direction.
For me, that means the client, Product, UX, and Engineering working together to understand the problem and explore what might solve it. Each brings something the others need. I want those perspectives shaping the work while there’s still room to learn.
That doesn’t require everybody in every meeting. It requires a way for people who know different parts of the problem to contribute before we’re committed to an answer.
Discover the problem together
The client knows the business. Product brings priorities and tradeoffs. UX focuses on the people doing the work and how we’ll find out whether an idea helps. Engineering understands the system and what it will take to make the experience reliable.
Those are starting points. Engineers have good experience ideas. Clients notice awkward workflows. Product can challenge a research assumption. I can ask whether a technical approach gives the person using it what they need.
We still need to test our understanding with those people. A client’s account of a problem is valuable, and so is seeing what happens when someone tries to complete the task.
I like working with people who know things I don’t. The useful part is what happens when their knowledge changes my approach.
Give the first pass room to develop
I’ve worked in situations where I explore a problem, produce a first pass, and that first pass starts moving into development. Meanwhile, I’m still seeing questions we haven’t answered.
Now we’re trying to resolve them while someone is already building. The experience changes underneath them, and people get confused about what was agreed.
A prototype gives us something concrete to use, question, and improve. Before we treat it as a commitment, I want us to understand what it demonstrates and what remains unresolved.
On a small change, that conversation can be quick. Complex work deserves enough iteration to understand the experience, the constraints, and the risks we’re accepting. Engineering belongs in that exploration from the beginning.
Respect includes disagreement
I want colleagues to challenge my assumptions, and I want to be able to explain when a proposed shortcut makes the experience harder for someone using it.
I put it this way:
There are hills that you die on and ones that you don’t.
If I see a significant risk, I should explain the consequence and help find another approach. I also need to listen when someone else’s expertise changes the picture.
Sometimes the decision belongs to somebody else. Once the tradeoffs are understood and the person responsible makes the call, I can support it. My contribution includes helping that direction succeed.
Shared participation works better when decision ownership is clear.
Stay with the outcome
Collaboration continues during implementation. I want purposeful checkpoints where we look at what’s taking shape and ask whether it still solves the problem. That might mean trying an early build, checking a risky interaction, or giving the client and people using the product a chance to test it.
AI can help me make an idea tangible sooner. The team still has to judge its usefulness, test the assumptions, and decide what is ready to build. Faster output gives us more to work with; the responsibility stays with us.
And sometimes a decision goes wrong. My response is:
We understood the risk. We made a decision. It went sideways. Now we got to fix it.
We need to understand what happened, own our part, and help correct it. The person who made the decision has responsibilities. The rest of us still have a stake in getting the product back on course.
The optimism is practical
This is how I prefer to work. I can adapt to different structures, deadlines, and levels of access to the client. I look for opportunities to bring the right people into a question, make a risk understandable, or check the work before a misunderstanding travels further.
The optimism comes from believing that capable people can solve difficult problems together. We can respect expertise, change our minds, make decisions, and keep contributing when the result needs work.
Everybody has a stake in the outcome. I want us to build that way.
Thanks for the read.
