Journal logo

Shane Murphy: A Bahamas Rewards Example That Starts With the Conditions

Explain a proposed benefit before inviting someone to rely on it.

By Shane MurphyPublished 5 days ago • 3 min read
Shane Murphy: A Bahamas Rewards Example That Starts With the Conditions
Photo by Michael Walter on Unsplash

By Shane Ian Murphy | Global Secure founder commentary

A rewards headline is easy to remember. Its conditions can be much harder to find. When I consider an invented Bahamas travel purchase for Global Secure design, I want to know whether a person can explain the proposed benefit before making the purchase. The exercise does not describe an available Bahamas offer.

Imagine that a traveller sees a reward beside a potential booking. They need to understand what qualifies, how the benefit is calculated and when it becomes available. An attractive percentage should lead to an explanation of its basis. It should not require the person to guess whether the figure applies to the purchase, a discount or another amount.

Timing is particularly important. A benefit shown as pending should be distinguishable from one ready to use. If a proposed offer depends on completion of a purchase or another condition, that relationship belongs in the explanation. A total that combines different states can make a screen look simpler while making the customer’s position harder to understand.

There should also be a clear account of exceptions. What happens in the design if a purchase is cancelled or changed? Who answers a question about eligibility? A concise explanation can point to detailed conditions without hiding the facts most likely to influence the user’s immediate decision.

I would test the wording by asking a reader to complete this sentence: “I receive this benefit if…” If the answer differs from the actual proposed rules, the copy needs work. The person should not need a second conversation to correct the central impression created by the first screen.

A useful review exercise would present the invented reward in three states: advertised, pending and available. Ask a reader to describe what they believe they can do with the benefit in each state. If all three screens create the same impression, the wording may be hiding an important distinction. The team should identify the exact point at which the conditions are satisfied and ensure that the visible description reflects that stage. A customer should be able to understand the difference without learning the internal terminology of the rewards system.

The example should also include a changed purchase. Suppose the traveller alters the booking before it is completed. The proposed offer needs an explanation of how that change would be evaluated under its actual conditions. The exercise should not invent an answer for convenience. It should record the question and identify the rules that would need to be written or checked. That keeps the design discussion honest about the difference between an attractive idea and a fully specified customer offer.

Comparisons need care as well. A person may judge a reward against a lower purchase price elsewhere. The product should provide enough information for them to assess the offer on its actual terms, without suggesting that a benefit automatically makes every purchase better value. The customer decides what matters to them. Clear amounts, conditions and timing support that decision more effectively than language implying that the existence of a reward settles the whole question of whether the purchase is worthwhile.

I would finish by checking the later explanation against the original headline. Can the customer reasonably connect the benefit they receive with what they first saw? If a detailed explanation substantially changes the obvious meaning of the opening statement, the headline needs revision. The goal is continuity between invitation and outcome. In a proposed travel experience, that continuity can help make a rewards feature understandable across discovery, purchase, fulfilment and any subsequent question about the customer's eligibility or recorded balance.

For me, rewards are part of the product’s responsibility to explain itself. In this hypothetical Bahamas scenario, a good design allows someone to decide whether the offer is useful to them. That starts with accurate conditions, understandable timing and a visible route for questions.

Disclosure: This founder commentary was drafted with AI assistance. Illustrative cover photograph; it does not depict a company project or asset.

business

About the Creator

Shane Murphy

Shane Ian Murphy: co-founder/partner, Tri-Party Tokenisation; founder/CEO, Global Secure Technologies (planned 2027 launch); co-founder/partner, Dual Party Capital. Partner, RougeN International Corp. Formerly of Limitless Mobile.

Enjoyed the story? Support the Creator.

Subscribe for free to receive all their stories in your feed.

Subscribe For Free

Reader insights

Comments

There are no comments for this story

Be the first to respond and start the conversation.

Sign in to comment
    Written by Shane Murphy