Agulha Digital — Wound Care Documentation

Overview

Prontuário da Ferida is a digital wound care documentation product for healthcare professionals. I lead product discovery for it: from interviews with healthcare professionals who treat wounds, to the MVP scope, user stories and roadmap.

The product is in development. This case shows the discovery and definition work, and marks clearly what is defined and what is being built.

The Problem

Wound care documentation has to be precise enough to support clinical decisions, yet quick enough to fit into a busy routine.

What do healthcare professionals need to document wound care reliably, and what would make them adopt a digital tool in their daily work?

My Role

I own product discovery end to end: I plan and run interviews with healthcare professionals, synthesise needs, map clinical workflows and adoption barriers, define the MVP scope and translate research into user stories and requirements. I shape roadmap decisions with the engineering co-founder, weighing feasibility, health-data privacy and clinical usability.

Approach

• Interviews with healthcare professionals to understand their workflows, needs and everyday challenges.
• Workflow mapping of clinical routines in practice, including where adoption could fail.
• Requirements and user stories for the core areas of the product.
• MVP scoping and prioritisation with the engineering co-founder.

Evidence & Insights

• Adoption depends on fitting into the clinical routine. That is why mapping adoption barriers was part of discovery from the start.

Decisions & Experiments

• Defined the MVP scope from the research, with requirements and user stories. Done
• Building the first version of the product. In development
• Features outside this scope stay in the backlog until the MVP has been used and evaluated in practice. Proposed

The details of the product’s features are confidential.

Outcomes & Learnings

So far, discovery has produced a shared understanding of clinical workflows and adoption barriers, a prioritised MVP scope, user stories and requirements, and a roadmap agreed with engineering.

• Clinical usability is a product requirement, not a polish step.
• Privacy constraints shape scope early. Deciding what not to collect is as important as deciding what to build.
• Discovery continues after definition. What we learn from real use will keep feeding the backlog.

Next Steps

• Complete the MVP and test it with healthcare professionals in their real routine.
• Define adoption and usage metrics for the first release.
• Use what we learn in practice to prioritise the next iteration.