KFC Rewards: turning loyalty into a habit worth sharing
Designing Reward Sharing for the KFC Rewards Arcade, so customers could pass on a prize they had won and introduce someone else to KFC Rewards. KFC UK & Ireland.
- Role
- Senior Product Designer
- Period
- 4 months
- READ TIME
- 9 min
- +12%
- Loyal customer engagement
- +6%
- New customer sign-ups
- +7.5%
- Reward click-through

Evolving loyalty beyond the transaction
Data showed that KFC customers weren't using rewards often, indicating they needed more reasons to return to the app and use the rewards programme. The new Rewards Arcade gave them a chance to win prizes. My part of the process was the reward functionality and presentation from when a customer won a new reward. I explored how letting a customer gift a reward to a friend or family member could help KFC reach its goal.
Loyalty that gave customers few reasons to return
Most loyalty journeys end with the person who earned the reward. They buy something, collect a reward and redeem it later.
KFC wanted to increase engagement among existing customers and bring new people into the programme.
One feature, a connected loyalty system
- —Antavo powered reward management. Its rules affected whether a reward could be shared, who owned it afterward, how a coupon worked and how it would be redeemed. I worked through those constraints early so the journey we designed could actually be built.
- —RAPP led the wider Rewards Arcade campaign. Reward Sharing needed to make sense alongside that work and feel consistent wherever a customer entered the journey, including outside the app.
How might we give existing customers more reasons to return to KFC Rewards and encourage new customers to join?
Leading the design from discovery to delivery
I led the design of Reward Sharing from discovery through delivery. I worked with Product, Engineering, Commercial and our external partners to understand what customers needed, define the feature, test the experience and prepare it for release.
Balancing three perspectives at once
There were three things to balance throughout:
| Perspective | What it demanded |
|---|---|
| Customer needs | Rewards that felt valuable, clear and simple to redeem |
| Business goals | More engagement and new customer acquisition |
| Technical reality | An experience Antavo could support within the timeline |
A workshop to choose the right opportunity
Before designing the feature, I ran a remote workshop with the Product Owner, Product Manager, Engineers, Designers and Commercial Revenue team. We looked at ways to grow engagement and sign-ups, then weighed them against customer value, feasibility and business impact.

We considered:
- —Reward Sharing
- —Making the Arcade more visible across KFC touchpoints
- —Promoting the free sign-up reward more prominently
Reward Sharing gave existing customers something useful to do with a prize while giving a new customer a reason to join. The workshop helped us agree on that direction before detailed design began.
A customer had won a reward. The question for us was whether giving it to someone else could also give that person a reason to join.
A transaction becomes a habit
- Purchase
- Collect reward
- Redeem reward
- Purchase
- Win reward
- Share reward
- Friend joins KFC
- Both engage
- and again
Reward Sharing added another person to the loyalty journey. That sounds like a small addition to the Arcade, but it introduced questions about who owned a reward, when it could be shared, how the recipient claimed it, and what happened if they were new to the app. I had to make that journey clear to customers while working within the rules of KFC’s loyalty platform.
We needed the reward to feel worth sending and straightforward to claim. The design had to work with Antavo, the platform managing reward ownership, coupons and redemption, and with the wider Rewards Arcade campaign led by RAPP.
Reward sharing was rare in quick-service
I reviewed loyalty experiences including Costa Coffee and McDonald’s to see how they handled sharing and engagement. Sharing existed in some programmes, but I did not find it widely used across the quick-service products I reviewed.
That gave us a useful starting point. We could look at sharing patterns customers might already recognise, while working out how those patterns would fit KFC’s rewards and Antavo’s rules. I brought those examples into early conversations with Product and Engineering about the interaction and its likely complexity.

Five requirements that defined “done”
I worked with the Product Owner on acceptance criteria so Design, Product and Engineering were working towards the same experience.
Personalised rewards
Customers needed to understand which reward they had won, why they had received it and whether they could share it.
One-time sharing
A reward could be gifted only once. The rule had to protect the programme and be easy for customers to understand.
Rewards Arcade integration
Sharing needed to follow naturally from winning a reward in the Arcade.
Expiry reminders
Customers needed a reminder before a reward expired so they had a chance to use it.
New customer registration
Someone receiving a reward who was not yet a member needed a route through sign-up before claiming it.
Designing the flows before the screens
Once we had agreed on the requirements, I mapped four journeys: sharing a reward just won, sharing one already held, receiving one as an existing member, and receiving one as a new customer.
The flows let us work through ownership, coupon rules, expiry and error states before development.
As Engineering investigated what Antavo could support, I updated the journeys with them. They gave us a shared way to discuss the edge cases instead of discovering them after the screens were designed.
Resolving structure before detail
I used wireframes to explore where customers would find rewards they could share, how a recipient would claim one, and how we would introduce a new customer to KFC Rewards.
I reviewed those options with Product and Engineering while the designs were still easy to change. Their feedback helped me account for platform constraints before moving into high-fidelity UI.

New behaviour, familiar language
I designed the final screens using KFC’s existing design system. The new behaviour needed clear signals: whether a reward could be shared, who owned it, whether it had already been sent and what the customer should do next.
The journey began when someone won a reward. They could share it, their friend could receive it, and the friend could redeem it through the reward screen already used in the app. I wanted the sharing step to feel like part of KFC Rewards, with no separate way of claiming a prize to learn.

You've won 
Share the reward 
A friend receives it 
A friend has seen it
Building for what comes next
The work introduced elements that could be useful beyond Reward Sharing, including personalised reward tags, status indicators, instructional banners and information cards. I added them to KFC’s Figma design system so another loyalty feature could use the same patterns.
That also gave the team a consistent way to show reward status and explain unfamiliar actions as the programme grew.

A pattern designed to teach, then disappear
I had recently worked on a feature at KFC that increased calls to Customer Service. Customers were not expecting the feature or did not know how to use it. As a result of this, I designed the explainer as a pattern that could be reused when KFC introduced an unfamiliar experience.
As the project was moving towards the RAPP marketing release deadline, I did not have time to do an in-depth user testing session but still felt it was important to get user input so I did guerrilla testing with people on the street.
The question in testing was how much explanation customers actually needed before using the Arcade and sharing a reward to understand it and feel confident using it.
Trusting the pattern over the copy
I ran guerrilla usability testing, paying particular attention to the instructional carousel. Participants swiped through it without spending much time on the supporting copy.
That changed my approach. The interface was already giving them enough direction, so I removed the extra instruction. It left customers with less to read before they could get on with the experience.
After participants' suggestions, I also removed arrow icons next to the carousel circles. This gave the screen a cleaner look and gave components more white space to breathe.
Design didn't stop at handoff
I prepared the Figma files and interaction details for Engineering and made sure the reusable components were ready to use.
I stayed involved during implementation. Regular check-ins gave us a way to answer interaction questions, respond as we learned more about the platform and review builds against the design. That mattered for a feature with several routes into it and rules that customers should not have to think about.
You've seen how it was designed.
Now experience it.
Rather than simply reading about Reward Sharing, step inside the product and experience the behavioural journey that inspired the feature.
This takes around 20 seconds.
Tap the bucket to experience a customer's moment of winning — and see how the choice to share sets the loyalty loop in motion.
Now imagine this behaviour repeated across thousands of customers.
The interaction you just experienced represents a single customer journey. After launch, this behavioural loop helped increase engagement, encourage new customer acquisition and strengthen long-term loyalty.
Here's what happened when the feature reached real customers.
Impact across engagement and acquisition
We designed Reward Sharing to give existing customers another reason to engage and to bring new customers into KFC Rewards. After launch, loyal customer engagement increased across the wider Rewards Arcade. Reward Sharing recorded increases in new KFC Rewards sign-ups and reward click-through.
- +12%
- Loyal customer engagement
- +6%
- New KFC Rewards sign-ups
- +7.5%
- Reward click-through
- +10.5%
- Loyal customer engagement
- +4.25%
- New KFC Rewards sign-ups
- +5%
- Reward click-through
All three measures remained up in the second month.
The interface was only one part of getting Reward Sharing into customers’ hands. The workshop helped us choose where to focus. The flows helped us work through Antavo’s rules. Testing showed us where we could remove explanation, and working with Engineering throughout helped us carry those decisions into the build.
The best outcomes came from alignment, not design alone
I’m proud that we took a familiar reward journey and made it useful to someone beyond the customer who won it. The work also left KFC with patterns it could reuse in later loyalty features.
For me, the hardest part was keeping the customer journey simple while the rules behind it were anything but simple. That meant making decisions with Product, Engineering, Commercial and our partners throughout the project, not just at the point of handoff.
Want to work together?

