Dental AR App: Audit, Learning and Management of a Responsible Go-to-Market
Product Lead

The Challenge
The project arrived in its final development phase: an oral-health app designed to connect dental professionals with patients and to offer the latter a gamified augmented-reality experience for the prevention and care of oral health.
At first glance it seemed a technically advanced project, but the analysis revealed a far more complex situation. The app had suffered multiple deviations from the initial requirements, the documentation (Report, URS, technical specifications) was not up to date, and the delivered features differed substantially from the original scope.
In addition, bugs, quality problems, security gaps in the code and very limited collaboration from the vendor were identified. The design lacked real user validation: it had not been tested with dentists or patients, and there was no iteration process or functional feedback system.
The project risked being launched to market under conditions that could compromise the brand’s reputation and generate a negative impact on its digital ecosystem.
The Solution
As the person responsible for the final evaluation phase and go-to-market strategy, the first decision was to halt the launch and carry out a complete product audit. The action plan was structured in three phases:
1. Technical and documentary review
- I gathered and cross-checked all the original requirements, modifications and deviations accumulated during development.
- I carried out a functional and testing analysis in a pre-production environment, identifying gaps, critical bugs and regulatory risks.
- We prioritised documentation and traceability, establishing a project control baseline.
2. Validation with users and stakeholders
- I organised focus groups with dentists to present the app, carry out on-site testing and gather real feedback on experience, usability and perceived value.
- A backlog of corrections and improvements was built, focused on reaching a realistic and viable MVP, with an adjusted budget and clear dependencies.
3. Executive decision-making
I produced a report for the leadership committee, presenting three possible scenarios:
- Continue with the current vendor and absorb a development cost overrun.
- Externalise the code and work with a vendor specialised in the programming engine used.
- Close the project and abandon the launch.
Each alternative included the economic, technical, reputational and operational-risk impact, enabling an informed and transparent decision.
Results
The committee decided not to continue with the project. Although the decision meant halting the launch, the process delivered valuable learnings for the organisation:
- A high reputational risk was avoided, demonstrating strategic maturity and executive responsibility.
- A model for product auditing and digital-service validation was established that would later be applied in future developments.
- The culture of documentation, traceability and change control was strengthened, reducing the gap between business, development and compliance.
- Personally, it was a decisive experience in my career as a Product Manager, consolidating my judgement on how to define, test and govern the design of digital services.
Sometimes, leading also means knowing when to stop in time. This project did not end with a launch, but it did end with an essential learning: that innovation without control or validation is not progress, but risk.