Solutions / Product direction
Product direction
What gets built, for whom, and how you notice
I come in as product manager: I talk to the people who use it and the people who pay, and I leave a prioritised backlog and a weekly rhythm for decisions.
What this is
Product direction, here, is one renewable month. I come in as product manager: I talk to the people who use it and the people who pay, and I leave the problem, the scope and a simple metric, a prioritised backlog and a weekly rhythm for decisions. At the close it is written what continues and what is dropped. Writing the code, facilitating more than one squad, and paid market research are not in the month.
Experience
This is the craft of the last ten years. I was product manager for ecommerce and for customer service at Falabella, I managed delivery of AI products and the corporate portfolio, and I am now technical product owner of an AI SaaS. As Scrum Master at Zenta I coordinated engineering, QA and the business. The month does not add another endless list of ideas: it leaves decisions, stories ready to build, and a rhythm.
How I work
I use two ways of ordering the work. They are not creeds. Each one fits a different moment.
Waterfall
First we write the whole path and what sits outside it. Then we build in that order. It fits when the scope can already be named: a six-screen site, an integration between two systems, an Odoo start with three modules. You know what you will receive before we begin.
Scrum
The work is split into short weeks. Each week something usable is shown, and we decide what comes next. It fits when the detail is still being found: an agent's tone, the question that actually reaches the bot, the priority in a backlog.
The published package is the frame: scope, timing, and what is quoted separately. That is waterfall. Inside it there is a weekly review: we look, we correct, we carry on. That is Scrum. I hold a Scrum Master certificate and Scrum Foundations, plus a Green Belt for when the problem is operational rather than fashionable.
Who it is for
Founders and teams who are building and need product judgement, not another endless list of ideas.
What the package includes
- Discovery with users and with the business
- Problem, scope and a simple metric
- A prioritised backlog and stories ready to build
- A weekly decision rhythm
- A close of the month: what continues and what is dropped
Quoted separately
- Writing the product's code
- Facilitating more than one squad
- Market research paid to third parties