All product families

Cards and learning

Plan a complete activity, from choosing a card to understanding the response.

Start with the experience

Define the learning sequence before deciding how many cards or controls to include. A useful brief explains what the learner sees, what action they take, what they hear and how they try again. Printed card count alone does not describe the number of interactions in the product.

Discuss this format

Plan the product together

Use the first review to connect the physical format, the content and the operating sequence.

Build a content manifest

Assign an identifier to every card, side or activity. Connect that identifier with its artwork, recording and language. Identify duplicates and any intentional repeats. The recognition method and content loading process are specific to the selected platform and must be checked for your configuration.

Make first use understandable

Review orientation, insertion or placement, controls and how the device sits in use. Test what happens when a card is reversed, changed quickly or presented twice. Decide what the user should hear when a card is unsupported or not recognized.

Treat extra activities separately

If a drawing surface, screen or additional game is needed, describe its operation in the brief. Specify how the user enters and leaves that activity. Do not assume that visually similar reader platforms share the same functions, card sets or audio update methods.

Check the whole packed set

Verify every card against the manifest, rather than demonstrating only a few. Count the packed contents and review storage, instructions and language identification. An activity that works at a desk should also be understandable when the set is opened for the first time.

Prepare a useful sample brief

Provide a reference for each decision and agree how the sample will be reviewed.

AreaBring to the briefReview on the sample
ContentCard IDs, artwork, files and learning objectiveEvery card maps to the intended response
HandlingOrientation, controls and start sequenceInsert, remove, repeat and recover
PackCard count, storage and edition labelsThe full set is complete and identifiable

Explore product references

Open a reference to read its use context, development questions and quotation preparation notes.

Questions before you begin

Resolve the scope before treating a reference as a production specification.

Can we use our own recordings?

Include scripts, approved recordings, languages and content rights in the brief. File compatibility, track mapping and the loading process are reviewed against the selected configuration.

What can be customized?

List appearance, content, controls and packaging changes separately. The team can then distinguish changes supported by the starting platform from work that needs further design or engineering.

How are MOQ and timing confirmed?

Share an order estimate, variant list, target market and shipment date. MOQ, tooling, sample scope and lead time depend on the actual specification and are confirmed in the project quotation.

What should we approve before production?

Agree the sample identifier, materials, control behavior, content manifest, artwork and packaging record. Keep open points separate from approved items and confirm which revisions need another sample.

Read the development guide