Expertise · Product Owner
Evolving a tool based on what users really need.
Needs analysis, backlog management with the IT department, steering enhancements: several activities in my career are directly aligned with the logic of the Product Owner role.
The role in brief
About the roleWhat is a Product Owner?
In a product organisation, the Product Owner is generally responsible for maximising the value delivered by a product. They carry the functional vision for the delivery team, formalise needs and order the backlog according to expected value.
This description is a general reference point. It does not describe my experience, which is presented in the next section.
What my career documents
Documented experienceReal activities, close to the role
Analysing business needs, scoping and writing functional specifications
Carrefour Banque et Assurance
Managing tool enhancements and the backlog in collaboration with IT
Carrefour Banque et Assurance
Coordinating business and technical teams
To optimise customer relationship and HR management tools.
Carrefour Banque et Assurance
Identifying and escalating malfunctions, proposing functional improvements
Carrefour Banque et Assurance
Gathering and formalising requirements in functional workshops
With business teams, institutional clients, internal teams and software vendors.
NEEVA
Writing, validating and tracking functional specifications
NEEVA
Qualifying and prioritising defects
As part of user acceptance testing.
NEEVA
Cross-functional work with technical and product teams
FDJ United
How I approach it
My approachFunctional value before features
Understand usage
Observe and listen to users before deciding what to build.
Formalise the need
State the problem to solve clearly, not just the imagined solution.
Structure requests
Group, clarify and make readable the requests that feed the backlog.
Coordinate
Build a shared understanding between business and technical teams.
Track and verify
Ensure the delivered enhancement meets the stated need, using acceptance testing.
In full transparency
About the roleWhat my career does not claim
My career history does not include an official Product Owner job title, nor a formal Scrum framework (sprints, ceremonies). The items presented here describe activities I have genuinely carried out, which form a solid foundation for an opportunity in this type of role.
Related areas of expertise
Trainer
Sharing knowledge, making tools understandable and supporting users until they are autonomous.
- Training end users and administrators
- Designing practical materials
- Onboarding new staff
- Change management
Manager
Organising a functional team's work, developing its skills and monitoring quality.
- Managing a team of 7 people
- Organising activity
- Skills development
- Quality monitoring
Project Manager / Business Analyst (AMOA)
Leading functional projects from requirements to go-live, at the interface between business teams, IT and software vendors.
- Requirements gathering and specifications
- Configuration and data migration
- User acceptance testing
- Business / IT / vendor coordination
Support Lead
Turning support into a lever for service quality: qualify, resolve or route, document and improve.
- Analysing and qualifying requests
- Incident and defect management
- Documentation and quick-reference sheets
- Working with technical and product teams
Product Manager
Starting from the problems users and business teams face to identify the enhancements that matter.
- Understanding user problems
- Identifying necessary enhancements
- Optimising tools and processes
- Business / technical coordination
Does this expertise match your needs?
Let's discuss your context, your projects or an opportunity.