Strategic closure of a digital product

Personal trainers

Not every project delivers results at launch. In some cases, the outcome lies in stopping at the right moment.

This case documents the decision to discontinue a digital product aimed at personal trainers, based on viability analysis, contextual assessment and usage data. The decision was not driven by lack of execution, but by the understanding that continuing would no longer be a responsible choice for the business.

Person using a tablet with a stylus to analyse a research spreadsheet, with columns organised by categories and user responses.

The project

The initiative began with the proposal to develop a digital solution for personal trainers, focused on organising training programmes, tracking clients and supporting professional routines.

From the outset, the product was treated as a hypothesis. Before justifying continued investment, it was necessary to confirm whether there was real space for this solution within its context of use.

Design entered as an instrument of investigation, responsible for structuring questions, organising analysis and reducing decisions based solely on conviction.

The real challenge

The problem was not the interface; it was deciding whether the product should exist.

As the work progressed, it became clear that the central question was not how to build the solution, but whether there was justification to sustain it.

Several signals repeated consistently:

the market already had established solutions in the same space
the technical effort required was high relative to the perceived gain
the proposition depended on significant changes in user behaviour
the risk of investing without proportional return was concrete

Moving forward would have meant proceeding by conviction rather than evidence.

Discovery and research

Discovery was conducted to test the hypothesis, not to confirm it.

Direct conversations were held with personal trainers, existing tools were analysed, and real working routines were observed. The gap between stated needs and actual adoption became apparent quickly.

Barriers to use and retention emerged early and repeatedly. The issue was no longer about scope adjustments or feature prioritisation. The misalignment lay between required effort, context of use and expected return.

At that point, persisting ceased to be a strategic decision.

Data as the basis for decision-making

The data was not used to justify a prior decision. It was used to determine whether continuing made sense.

The information collected was organised to compare technical effort and expected return. The question was not how much value could be generated, but how much it would cost to find out whether that value existed.

The analysis revealed a consistent pattern: the most promising opportunities required investment that was too high for an uncertain return. The risk ceased to be calculated and became disproportionate.

Feature prioritisation matrix for the project, relating business value and technical effort, with initiatives distributed across low and high impact.

The decision to discontinue

In light of the evidence, the decision was to discontinue the product.

Not due to a lack of commitment, but because continuing would have required further resources for an increasingly indefensible hypothesis. Ending the project at that point avoided waste, preserved focus on more promising initiatives and reduced the risk of overloading the team with a product that would be difficult to sustain.

The decision was documented, communicated and aligned with stakeholders as a normal part of the product process.

Design role

Design did not act to enable a ready-made solution, but to support decision-making.

The work involved structuring investigation, transforming data into comparable scenarios and supporting the business with analytical interpretation, even when this led to an uncomfortable conclusion.

Ending the project was also part of design’s responsibility.

Observed impact

Even without a launch, the effects were tangible.

Additional development costs were avoided, the team was redirected to higher-return initiatives, and the risk of maintaining ongoing effort on a fragile hypothesis was eliminated.

The process strengthened leadership’s decision-making maturity, reinforcing a culture in which data carries more weight than attachment to the initial idea.

Learnings

Not every good idea should become a product
Data does not limit creation; it prevents unproductive persistence
Stopping at the right moment requires more maturity than continuing without evidence
Strategic design also involves saying “no” when proceeding would no longer be responsible.

Closure

This project reinforced the role of design as an agent of discernment within the product process.

Here, delivering results did not mean launching a solution, but making the right decision at the right time, safeguarding resources, focus and the people involved.