TicketCo Terminal / Original published motion study
01 / TicketCo Terminal
The context
A published self-service ticket-terminal presentation, combining the interface with a physical product context. Part of my broader TicketCo product-design work through Cefalo.
Reading the problem / TicketCo Terminal
A short film has to orient the viewer first.
The terminal presentation makes a self-service ticketing product tangible through hardware and interface views.
A published product presentation does not establish a hardware launch or a measured sales result.
How can a short film make a self-service ticketing concept understandable?
Evidence: the project account and the attributed artifacts on this page. Process drawings and interaction studies are reconstructed explanations; numerical research or business results are included only where separately supported.
02 / TicketCo Terminal
The design focus
- Product and interface presentation
- Interaction sequence and visual hierarchy
- A film that explains the experience
The process / TicketCo Terminal
A direction.
A way to build it.
The terminal presentation makes a physical product context and an on-screen interaction understandable in a short sequence.
A schematic of sequence and overlap, not a dated project schedule.
Choose the product takeaway
Identify what the viewer needs to understand about the self-service experience.
Plan object and interface beats
Establish the terminal before following the interaction that gives it meaning.
Explore the product sequence
Connect the physical context, interface scene and closing message in motion.
Review reading time
Check that product movement leaves the interaction and message understandable.
How can a short film make a self-service ticketing concept understandable?
The viewer first needs to recognize the terminal as a product, then understand its interface and interaction. Closing on the physical context ties the sequence together. The narrative explains a self-service experience without requiring a complete operational walkthrough.
Journey map / TicketCo Terminal
See the whole task in context.
Choose a step to connect the person’s intent with the interface and the design decision.
Current intent
Introduce the terminal
A published product presentation does not establish a hardware launch or a measured sales result.
- Interface context
- Product introduction
- Review question
- Which legacy actions must remain directly accessible to experienced organizers?
Representative task sequence and recovery path, not a measured emotional curve or historical research map.
Behind the experience
From composition to a consistent deliverable.
For TicketCo Terminal, this map connects “Introduce the terminal” to “Close on the product”. Read across to follow the task, then select a layer to inspect the interface, design and delivery references behind it.
| Layer | Introduce the terminal | Show the interface | Explain the interaction | Close on the product |
|---|---|---|---|---|
| The task | Introduce the terminal | Show the interface | Explain the interaction | Close on the product |
| Visible interface | Product introduction | Product introduction | Interaction sequence | Product takeaway |
| Design checkpoint | A published product presentation does not establish a hardware launch or a measured sales result. | Give the interface a recognizable physical setting. | Show the interaction at a pace the viewer can follow. | Resolve the sequence with a bounded product takeaway. |
| Implementation reference | Identify what the viewer needs to understand about the self-service experience. | Establish the terminal before following the interaction that gives it meaning. | Connect the physical context, interface scene and closing message in motion. | Check that product movement leaves the interaction and message understandable. |
| Recovery | Incomplete configuration → explain the missing field → return to the action | |||
A reconstructed delivery map: the implementation row summarizes design-process dependencies, rather than claiming to document the original backend architecture.
Orient, demonstrate, resolve.
Reconstructed comparison of design approaches. These are review studies, not a claim that both directions were historically tested or shipped.
What this direction changes
Orient, demonstrate, resolve
Explains the object before the interface sequence becomes the focus.
Introduce the object before following the interaction.
The storyboard reconstruction sets aside a product introduction, an interface sequence and a final takeaway. Physical and screen context should reinforce one another: the terminal gives the interface a setting, while the interaction explains why the object matters.
01 / Product introduction
TicketCo TerminalIntroduce the terminal
OpeningResolve
Show the interface
Give the interface a recognizable physical setting.
02 / Interaction sequence
TicketCo TerminalExplain the interaction
OpeningResolve
Explain the interaction
Show the interaction at a pace the viewer can follow.
03 / Product takeaway
TicketCo TerminalClose on the product
OpeningResolve
Close on the product
Resolve the sequence with a bounded product takeaway.
Try the interaction
TicketCo Terminal / Composition study
TicketCo Terminal01 / 03
View 01
Product introduction
Give the interface a recognizable physical setting.
TicketCo TerminalIntroduce the terminal✳
Starting context
Introduce the terminal
Product messages must remain readable while the view moves.
Balance the terminal headline with interface labels and the closing product message. Moving product views must leave enough reading time for each.
Illustrative type-role specimenTicketCo Terminal
Introduce the terminal.
Close on the product.
HeadingInteraction sequence
24 / 30 px · regularBodyHow can a short film make a self-service ticketing concept understandable?
16 / 26 px · regularLabelClose on the product
12 / 18 px · regularStateIncomplete configuration → explain the missing field → return to the action
12 / 18 px · regularPortfolio-font hierarchy illustration; the source does not establish the exact client font or token scale.
Choose what the film needs to explain.
Which legacy actions must remain directly accessible to experienced organizers?
An interaction sequence should make one useful idea understandable before moving to another angle. A dramatic product reveal does not by itself explain how the terminal is used.
Which patterns can web and native experiences share, and where should platform behavior differ?
The closing message should reflect what the presentation demonstrates. Showing a concept clearly is different from documenting a hardware release or a measured increase in ticket sales.
Align product shots with the interface sequence.
The published presentation joins a self-service terminal with its on-screen experience. A motion handoff needs the product context, approved interface scenes and the intended reading order, so edits preserve the explanation rather than only the visual rhythm.
For future AI-assisted presentation work, provide the existing terminal assets and the specific message the cut needs to communicate. Review legibility and sequencing before adding promotional claims to the output.
This is an original published terminal presentation, not evidence of a hardware launch or measured sales uplift.
Accessibility & standards
Access belongs in the design.
For this ticketing experience, prioritize seat-selection alternatives, availability announcements, reservation time limits and recovery without losing a selection.
WCAG 2.2 AA · EN 301 549 · APCA · WAI-ARIA · Platform guidance
Turn the palette into usable roles
Document approved text/background combinations for body text, large text and UI components. Assess functional content against WCAG 2.2 AA; use APCA to refine type size and weight.
Carry identity without losing meaning
Provide non-color cues, readable type hierarchy and accessible template reading order. Review captions and a reduced-motion alternative for product films and animated applications.
Make the rules usable in production
Include accessible color tokens, component states and content guidance in designer, developer and Claude/Codex references. Logo presentation alone does not establish interface accessibility.
Review scope & standards references
These are design references and review priorities, not a claim that this historical project passed a WCAG audit. Record criterion-level evidence, assistive-technology and device results, unresolved issues and retest outcomes before making a conformance statement.
APCA supplements the WCAG 2.2 contrast checks; it does not replace them. WCAG 3 remains a draft. EN 301 549 v4.1.1 is the latest published edition checked on 6 November 2026; its publication and its formal EU legal citation are separate matters. Confirm the applicable procurement or legal baseline with the client.
Outcomes & scope
What the work delivers.
- Published product presentation. This is not evidence of measured sales uplift or a hardware launch.
Results are described within the documented project scope. Illustrative studies are identified separately from original project artifacts.
Review & next iteration
What needs to hold up in use.
Use these questions to review TicketCo Terminal against the behavior the design is intended to support.
- 01
Can a viewer recognize the product before its interface changes?
- 02
Do the selected views preserve the reading hierarchy?
Project-specific acceptance questions for a future review, not reported usability-test results.
Reflection / TicketCo Terminal
What I’d carry forward.
A short film can make unfamiliar hardware easier to understand. Product orientation and the order of interactions should guide the camera and transitions.