Approach / How I work
Start with the problem.
Stay with the product.
Good product work calls for judgment. The process should help people make better decisions and deliver something useful.
I use the approach that fits the team and the problem. Agile, Scrum, prototypes, and roadmaps can all help. Their value comes from what they make possible: clearer priorities, better collaboration, and a product that keeps improving.
Understand what matters.
Start with the people, the business, and the way the work happens today. Interviews, observation, and existing evidence help separate the visible request from the underlying problem.
What problem are we trying to solve, and for whom?
Make the direction clear.
Connect customer needs with business goals and technical constraints. Define requirements, identify assumptions, and choose priorities the team can explain. A useful roadmap gives direction while leaving room to learn.
What should we do next, and why?
Make ideas tangible.
Use workflows, prototypes, and early implementation to make decisions concrete. Bring stakeholders and engineers into the conversation before a polished interface makes an uncertain idea look settled.
What can we test before making a bigger commitment?
Deliver, learn, improve.
Work in manageable increments. Test with the people who will use the product, assess readiness, and watch what happens after release. Carry that feedback into the next set of priorities.
Did this improve the outcome we cared about?
People, decisions, technology
The way we work matters.
Make decisions together. Give designers, engineers, users, and stakeholders a clear understanding of the problem. Create space for their expertise, surface tradeoffs, and make ownership clear.
Measure what changes. A completed feature is a useful milestone. The stronger question is whether it helped the customer, the team, or the business. Use evidence that fits the product and acknowledge what is still unknown.
Use AI with purpose. AI can help explore ideas, create prototypes, and accelerate implementation. Product judgment, accurate information, user feedback, and careful review still determine whether the result is useful.
In practice
From research to working software.
At Spera, research and user interviews informed workflows, prototypes, backlog priorities, and release planning for a freelancer business platform. The work continued through testing, delivery, and maintenance.
Read the Spera case study