Skip to content

My method, from idea to production.

How I run a product day to day: the full cycle, properly tooled testing, my sprint practices, and what it changes for the team.

The full cycle, from need to production.

  1. UnderstandNeeds gathered with the business, the field and partners.
  2. ScopeScope, business rules, specs and user stories.
  3. PrioritiseBacklog ranked by value, shared roadmap.
  4. Build3-week sprints, coordinating business, IT and vendors.
  5. TestFunctional acceptance testing by journey, in Qase.
  6. ReleaseGo-live, change management, progressive rollout.
  7. RunSupport, incident triage, improvements, tracked indicators.

Testing, properly tooled Acceptance test suite restructured in Qase, test cases generated and automated with AI, every fix retested and every incident turned into a regression test.

My practices, sprint after sprint.

  1. Align functional and technicalBusiness needs and technical work in a single roadmap, broken down into epics then user stories.
  2. Prioritise the backlog by valuePrioritisation workshops with the business; customer feedback is qualified then fed into the backlog. What we don't do is decided, not suffered.
  3. 3-week sprintsRefinement, planning, review and retrospective, tracked in Jira; specs and user stories written with the team and vendors.
  4. Three amigos before every sprintProduct, development and QA review each user story together: rules, edge cases and acceptance criteria are clear before a line of code is written.
  5. Test before releaseEnd-to-end testing, journey by journey; every incident becomes a regression test replayed with each release.

What changes when you work with me.

The expertise is the what. Here is the how: six habits I keep from one engagement to the next.

  1. I speak both languages, tech and business.

    I challenge an architecture with the devs in the morning, decide a roadmap with the business in the afternoon. Nothing gets lost in translation.

  2. I focus effort where it counts.

    Not everything is a priority. I protect what creates the most value and own the trade-offs, without turning the team into a feature factory.

  3. I make run and transformation coexist.

    On a critical product, you don't shut down the service to modernise. I structure RUN and BUILD in parallel.

  4. I deliver, and it lasts.

    The rituals I put in place still run after I leave. Migrating 23,000 users with zero interruption doesn't happen by chance.

  5. AI is part of my toolkit.

    I use it to automate workflows, speed up discovery and design features, in my process and in the product.

  6. I hold the relationship as much as the product.

    A critical project always goes through tension. My job is to keep business, engineering and leadership talking when things get tight, and moving in the same direction.