A merchant service can be useful without being the right default for every merchant. I think this becomes especially important when a paid option offers a benefit whose value depends on the business’s circumstances. The product team may see an opportunity to increase uptake by including it automatically. That commercial convenience does not establish that every user needs the service or understands the choice being made on their behalf. A well-defined option can be successful precisely because customers are able to decline it.
The fictional accelerated-settlement proposal at Serravon in 2011 brought that question into focus. Research involved three hundred merchants: 120 were interested in earlier settlement, while 180 said the standard service was adequate. The commercial sponsor preferred the paid accelerated service as the default package. I chose an explicit option with timing, price and conditions visible, retaining a usable standard route. A sixty-merchant pilot then recorded twenty-two selections of acceleration and thirty-eight of standard settlement.
Identify the need before deciding the default
I would begin with the job the option is intended to do for the merchant. Earlier settlement may matter in a particular operating situation, but its usefulness cannot be assumed from the name of the feature alone. The research needs to examine that context rather than merely ask whether faster sounds attractive. The fictional case gives bounded evidence about the businesses consulted; it does not provide financial advice or establish a universal cash-flow benefit. A real proposition would need its own assessment of customer need and feasible delivery.
The default decision should follow that understanding. A default is consequential because some users will accept it without treating the choice as a separate enquiry. I would therefore ask whether the product’s purpose supports including the option for everyone or whether explicit selection better reflects the different needs observed. This is not a claim that every default is wrong. It is a requirement to justify the choice through the proposition and its users, rather than let a desired uptake figure decide the design first.
Treasury and operating colleagues also need to establish what the service can actually deliver and under which conditions. The product team cannot promise universal timing through a headline or turn a commercial preference into an operational commitment by placing it in the package. I would make those dependencies visible while defining the option. The customer should encounter a proposition whose conditions are understandable, and the delivery teams should not inherit a broader promise than they have assessed or authorised.
Keep the standard route credible
An option is not meaningful if the alternative becomes obscure or needlessly difficult to use. In the case, we retained the standard settlement route as a credible service for merchants whose needs it met. I did not want the product to describe it as an inferior failure state merely because the new paid feature was more prominent. Different requirements can support different choices. The team should be able to explain those choices without using the language of progress to make every customer feel that the new option is automatically necessary.
Price and timing belong in the same decision account as the benefit. If the customer sees the attraction first and encounters material conditions only after selection, the product may record uptake without establishing a well-understood choice. I would work with the relevant owners on the presentation and service terms before interpreting adoption as evidence of value. The fictional narrative contains no live offer or specific settlement deadline; it illustrates the product judgement rather than supplying a banking or payment recommendation to readers.
A$2.1 million supported the development work. The sixty-merchant pilot provided evidence of choices within that group, not a market-wide preference or a financial return on the expense. Twenty-two merchants selecting acceleration did not make the thirty-eight standard selections failures. The latter could be consistent with the research that found many businesses adequately served by the existing route. The product’s purpose was to offer a suitable choice, so success needed a more thoughtful account than the largest possible adoption percentage.
I would still investigate why users choose either route. A low selection rate can reveal unclear communication or a service that does not meet the intended need. A high rate can reflect usefulness, misunderstanding or the effect of presentation. Neither figure interprets itself. The next enquiry should examine the proposition and the customer’s understanding rather than assume that more is always better. The fictional case records the decision and observed selections without pretending that those counts settle every question about continuing value.
Interpret selection within the proposition’s purpose
The sponsor gave up the larger immediate uptake expected from default inclusion. That was a commercial trade-off I needed to explain directly. I believed the narrower choice better matched the differing needs we had observed. The decision did not prove a profit improvement, universal customer benefit or perfect comprehension. It established a product approach and a pilot account. A credible leadership narrative should preserve those limits while still describing the judgement that made the option different from the initial proposal.
Adoption objectives can distort that judgement if they are set before the intended population is understood. A service for a particular need may have a naturally limited audience. Asking the team to maximise selection across everyone can encourage it to obscure the alternative or expand the promise. I would agree what evidence of a well-served customer looks like before using uptake as the main measure. The chosen account should recognise the possibility that a customer is well served by deciding the paid option is unnecessary.
The product also needs a clear account of later changes. A merchant’s circumstances may change, or the service may no longer suit the purpose for which it was selected. I would ask the team to define the relevant change or exit path with the responsible owners, rather than regard the initial selection as the end of the product relationship. The details depend on the actual service. The principle is that the choice should remain understandable beyond the moment the business first encounters the new feature.
For a board reader, the material question is whether the product’s commercial objective remains aligned with the need it claims to serve and the conditions of delivery. Directors can ask management how that alignment is evidenced without deciding individual interface or settlement choices. A product executive’s experience can help identify where adoption is being used as a proxy for value without sufficient support. The contribution should remain within collective oversight, respecting the operating and specialist responsibilities that determine what the institution can offer.
I would describe the accelerated-settlement case as a decision to preserve different legitimate choices. The standard service remained useful for many merchants, and the paid option had a defined place alongside it. The pilot’s thirty-eight standard selections did not invalidate the proposition; they helped show why the alternative needed to remain credible. A product succeeds through the work it enables and the promise it fulfils, not simply through the proportion of customers persuaded to take the newest available option.