Android KitKat

Read the campaign story

Google and Nestlé announced Android KitKat in September 2013, pairing the operating system’s confectionery naming convention with a real consumer brand. Nestlé’s UK announcement describes specially branded packs and a prize promotion. Fast Company’s contemporary coverage identifies JWT London and a campaign that included a mock technology-style product demonstration. This case focuses on the UK and US-facing partnership within an international rollout.

The collaboration worked at more than the logo level. The software name became a familiar chocolate name, while the chocolate was described using the language and presentation of a technology launch. Packaging offered a physical route into the digital promotion. This is strategically distinct from the original Have a Break platform: the central mechanism is reciprocal category borrowing and a named partnership, not a new execution of the everyday-break occasion.

Editorial reading: A partnership can create attention when each brand makes the other easier to see in a new way. The existing dessert convention supplied a reason for the naming choice, reducing the sense of an arbitrary sponsorship. The mock demonstration then let ordinary product characteristics become humorous specifications. The audience could enjoy recognising the borrowed format while still understanding the object being presented.

The humour must not obscure practical distinctions. Buying chocolate did not install software, and compatibility or prize eligibility depended on actual terms. A contemporary co-branding programme needs clear roles, permissions and customer support responsibilities. It should also consider whether linking a food product with a technology audience creates inappropriate targeting, especially where minors may encounter the promotion.

A small business can test a limited partnership with a complementary organisation around one genuine shared convention. Explain what each side contributes and create an original demonstration that borrows a recognisable format without misleading people. Ask customers what is included, who provides it and what conditions apply. If the partnership generates excitement but confusion, simplify the offer before expanding media.

The sources verify the announcement, packaging plan and creative treatment, not a causal increase in chocolate or device sales. Planned pack volumes are not treated as delivered reach. The practical lesson is to make the connection between partners meaningful and operationally clear. Cross-category humour can refresh familiar products when the exchange benefits both stories and the customer can still understand exactly what is being offered.

Find a real connection

A naming convention can make a partnership coherent.

Clarify the offer

Co-branding should not blur product or prize conditions.

Separate plans from outcomes

Pack plans are not verified reach or sales.

A small test for another brief

Editorial reading of the challenge: how to use a credible shared convention to let two categories reinterpret each other through a clear partnership.

Accurate offer comprehension and mutual brand attribution.

Stop if the partnership misleads about compatibility, prizes or audience suitability.

• Identify one genuine shared convention.
• Define each partner’s contribution and conditions.
• Test inclusion, provider and eligibility understanding.