An airline programme can run on a sophisticated operating model and still leave members confused at the first step. Terms appear before anyone has explained them. A message promises a specific option, then sends the reader to a general page. The programme team knows the process so well that it no longer sees what a newcomer finds puzzling. None of this is visible from inside the building.
This article develops loyalty marketing our founder led, where a Nordic airline sat within an international programme portfolio and the documented scope covered engagement and customer experience. We do not claim responsibility for the airline’s identity, and we assign it no share of the portfolio’s collective results. The subject is narrower and practical: the order in which a participant meets information, and whether they can see what to do next.
The questions a member brings to the first screen
We define the programme action before anyone writes a headline. What should the member understand after reading? What should they be able to do next? What might stop them starting? Every member who arrives at a participation page is silently asking three questions, and a page that answers them in order is most of the way to being usable.
Before a member starts
What is this?
The offer in one plain sentence, in the words the member saw before they clicked. No programme jargon until it has been explained.
What do I need?
Membership, balance, account access or anything else required, stated before the member commits time to the steps.
What happens next?
The steps in the order they happen, where the member will end up, and what confirms that it worked.
Clarity does not require a cold or technical tone. The page can be polished and appealing. What it cannot do is make the member infer the offer from a photograph and a broad statement about possibility. The main proposition appears early, unfamiliar terms are explained where they first appear and the action is specific enough to act on.
Information order decides whether the page works
We work within the airline’s approved brand system and use space, typography and image selection to guide attention. The programme message needs enough emphasis to be noticed without competing with every other element on the page. A calm hierarchy is a functional choice: when everything is emphasised, a member scanning for the one instruction that matters cannot find it.
The order we would usually test is simple. The promise, repeated accurately from the message. The action, visible without scrolling on most screens. What the member needs before starting. The steps. Then the conditions, grouped and easy to find, with the most consequential ones nearest the action rather than at the foot of a long page. Partner identification is stated clearly, particularly where the member will move into an environment that looks different from the airline’s main website.
This is the work we describe as customer journey and website experience design: arranging information around the decision a reader is making, while preserving every detail that genuinely matters. It is a different discipline from writing the campaign, and it often decides whether a good campaign produces any participation at all.
The page after the click
The landing experience is where a clear campaign most often becomes complicated. We would check whether the page repeats the promise accurately, whether the action is visible and whether it answers the questions a cautious member might ask. Instructions should describe the steps in the order the member takes them, not in the order the platform processes them.
A participation route, step by step
- RecogniseThe member sees the offer they were promised, in the same words, and knows they are in the right place.
- CheckThey confirm they are eligible and have what they need, before investing effort.
- ActOne clearly labelled action. If it leads to a partner, the page says so before the click.
- CompleteThe member gets a visible confirmation that the action worked.
- Know what followsWhat happens now, when, and where to go with a question.
Each step has a typical failure. Recognition fails when the page uses different words from the message. Checking fails when eligibility is hidden in a terms link. Acting fails when the button label is vague. Completion fails when the member is not sure anything happened. The last step is the most neglected: a member who has finished but does not know what follows is the one most likely to contact support. Where the partner’s environment looks different, a short line of continuity helps; we look at that handover from a brand angle in keeping the partner destination recognisable.
The same page on a phone
A layout that looks elegant on a large screen can become awkward when conditions, partner information and navigation stack vertically. On a desktop, the action and the conditions may sit side by side. On a phone, whatever comes first in the code comes first on the screen, and a long introduction can push the action several screens down. The agency has to see the page as a participant sees it: limited patience and no inside knowledge.
Information order, desktop and mobile Example
Two columns, read together
- Promise and action in the main column
- Requirements beside the action
- Steps below, conditions grouped to one side
- Partner explained near the action
One column, read in sequence
- Promise in one line
- Action, visible on the first screen
- Requirements as a short list
- Steps, then conditions in a labelled section
- Partner note directly above the button that leaves the airline
An illustration of ordering decisions, not a screenshot of a delivered website.
The mobile order is not the desktop order compressed. It is a separate set of decisions about what the member must see before they scroll, and it should be reviewed on real devices rather than in a resized browser window.
Familiarity changes what the page has to do
The broader programme work covered acquisition, engagement and retention. On the page itself, that translates into two very different readers. A new participant needs a short explanation and some reassurance before starting. An existing participant already understands the option and wants the action, fast. One page can serve both if the action sits high and the explanation is available without being in the way, for instance as a short “new to this?” section below the button rather than a block of text above it.
Familiarity also shapes what arrives before the page. Members may see an introductory asset, read a fuller explanation and later receive a reminder, and each needs to land on a destination that matches the stage they have reached. That is a matter of sequencing follow-up communications, and the page has to make sense for someone who skipped every earlier message.
The brief connects these decisions. It should name the audience, the approved proposition, the destination and the reporting objective, so the airline, programme partner and campaign team review the same page against the same intent. Without it, the review tends to default to whatever metric is easiest to retrieve.
A production usability checklist
A short checklist preserves clarity when several teams are editing at speed. It supports judgement; it does not replace it.
- Action visibility: the main action can be found without scrolling on a typical phone
- Unfamiliar terms: every programme term is explained where it first appears
- Conditions: the ones that could stop participation sit near the action, in plain language
- Destination continuity: the page repeats the message’s offer in the same words, and the partner handover is announced
- Confirmation: the member can tell the action worked and knows what follows



