NeoCards: Objects Worth Keeping

Previous essays have described the same object without naming it. This one gives it a name: NeoCards, objects worth keeping.

1

Why a name now

Over the last two months I have written about one object from several directions. It began as a card arriving in an email, with a front that never changes and a flip that can. It became a card that accumulates history, then a card that rewards attention where points reward purchases. Most recently it became something a customer keeps rather than consumes, and a small piece of software the person holds.

Multiple essays have described the same object without naming it.

Ideas without a name get discussed as features of something else. Named, they can be discussed as a category, tested, and built on. So the object now has a name: NeoCards. The name is not a new feature. It names an object whose behaviour, economics and architecture differ from a message, a web page or an app.

The name places it beside NeoMails within NeoMarketing. NeoMails are messages worth opening; NeoCards are objects worth keeping. A separate primer sets out how the two fit together. This essay is about the object.

2

What a NeoCard is

A NeoCard is an object worth keeping: a fixed front that carries identity, and a reverse that keeps growing.

The front holds everything that makes the card recognisable: its artwork, name, number, set, edition and issuer. It never changes, because ownership, trade and completion only mean something if everyone is holding the same thing.

The reverse holds everything the card can do. On the day it is collected, that is a story, much as the back of a cigarette card carried one a century ago. Over the months that follow, the issuer can add a guide in the owner’s language, a short film, a question, fresh data or a relevant offer. The card gains capability without becoming a different card.

A NeoCard can arrive anywhere: in an email, attached to an order confirmation, through a code on a pack, or from a friend. Once acquired, it lives in the owner’s album, whichever route it took.

A message is something you were sent. An app is somewhere you go. A card is something you have.

3

Built to KEEP

NeoCards are built to be kept, and four jobs earn that.

Figure 1. Four jobs earn the keep, and each creates something the brand can measure. Trust sits underneath all four.

Collect. Every card belongs to a finite set, so what the owner has and what they are missing are both visible. An incomplete set is a reason to come back that no reminder email can match. Collecting creates progress.

Evolve. The reverse gets deeper after the card is acquired. A card that held only a story on day one may hold a spoken guide, a film and a challenge by the end of the year. Evolution creates return.

Exchange. Cards move between people, as gifts or trades. A duplicate becomes a reason to contact a friend, and the brand earns reach to that friend rather than buying it through media. Exchange creates reach.

Play. The owner does things with the card: listens, watches, answers, declares a plan, acts on an offer. What the owner declares (going in December, with family) is written by them, on an object they keep. Play creates declaration.

Collect creates progress. Evolve creates return. Exchange creates reach. Play creates declaration.

Play means interaction, not gamification. A bank’s card on investing ideas is played by learning and answering, not by spinning a wheel.

4

Trust by design

A card that can change must prove what it was, who changed it and why.

Trust is not a fifth job. It is the layer underneath the four, and it has four parts: identity, provenance, permissions and history. Every card has a permanent identity. Every version the issuer publishes is kept. Every update is dated and attributed. The owner’s own notes and answers are stored apart from the issuer’s content, and belong to the owner.

The issuer can add to a card. It cannot silently take it back or rewrite what was there. Without that guarantee, Evolve would be a liability: an object that changes without a record is an object nobody can rely on.

5

The ethos

Five rules keep NeoCards honest.

  • The brand issues the card but is not its subject. A paint company issues a set on the colours of India, not twenty of its own products. The set must be worth collecting even if the logo disappeared.
  • Rewards amplify play; they do not define the card. A prize can start a habit. If a card needs a prize to be kept, the card is weak.
  • The card may grow deeper. It must not grow wider. Capability arrives one layer at a time, and every layer is about the same subject. A card that fills with unrelated functions becomes an app nobody opens.
  • Identity is fixed. Rendering can adapt. One card can speak Kannada to one owner and English to another, and still be the same card.
  • Kept is not enough. Kept and returned to is the asset. A card that is kept but never revisited is an archive, not a relationship.

6

How the idea developed

The idea was not designed in one piece; it was assembled.

Got, Got, Need introduced the object: a card that arrives by email, with a permanent front and a flip that can change, and an argument that the inbox was the right room for it.

IndiaVotes added time: a physical card freezes a moment; a digital card accumulates history.

The Brand Digest showed what cards do for a channel: cards, sets and albums give a stateless medium memory.

Points Reward Purchases. Cards Reward Attention. made the economic case. Points cover the moments of purchase; cards cover the far larger stretch of time between them, with the brand as issuer rather than subject.

Kept Media found the missing dimension. Paid, owned and earned describe how media arrives; kept describes what remains. It also corrected the first essay: I had confused the best delivery rail with the thing being delivered.

When a Card Becomes Software described the object’s physics. The front is identity; the reverse is software; the card can change without becoming a different thing.

NeoCards gathers all six under one name.

Figure 2. Six essays, each adding one piece, before the object had a name.

7

What would prove this wrong

A name is only worth having if the thing it names works. Three failures would show it does not.

  • No return. Owners collect cards but never come back to them, and the reverse grows for nobody.
  • No credit. Engagement rises while Issuer Recall stays flat. People love the cards and forget who issued them.
  • Wider, not deeper. Issuers keep adding unrelated functions until the card becomes an app in miniature, and owners stop turning it over.

The test is not whether people like the idea of cards. It is whether a card received today raises the chance of attention tomorrow.

**

Objects worth keeping

NeoMails are how a brand earns attention, one message at a time. NeoCards are how it keeps that attention once it has been earned. The primer that follows explains how the two pillars work together.

NeoMails earn attention. NeoCards compound it.

**

Key points

  • NeoCards names an object six essays had described: an object worth keeping.
  • A NeoCard has a fixed front that carries identity and a reverse that keeps growing.
  • NeoCards are built to KEEP: Collect, Evolve, Exchange, Play, creating progress, return, reach and declaration.
  • Trust sits underneath: identity, provenance, permissions and history.
  • Five rules: issuer not subject; rewards amplify play; deeper not wider; identity fixed, rendering adapts; kept and returned to is the asset.
  • A message is something you were sent. An app is somewhere you go. A card is something you have.

Published by

Rajesh Jain

An Entrepreneur based in Mumbai, India.

Leave a Reply