Privacy by design: your project stays in your control as a portable JSON file.
Make complex products make sense
Think in objects.
See the whole system.
Make sense of complex products. Define what matters, connect the pieces, and bring your model into view.
Watch the product filmYour workspace, yours
A JSON file you own.
Structured, readable file you can reuse pretty much anywhere.
GitHub sync is the only way to keep your project data in the cloud.
We do not store your project data in Supabase.
Try a different perspective
One model.
Every connection.
Follow the same Client, Order, Product, Provider, and Payment through the model.
EXAMPLE PROJECT / CommerceOne model. Different perspectives.
PERSPECTIVE 01 / 04
Interactive illustration / Based on the supplied product example / Illustrative modelWhat > How > With > Who
Start with what your product is about
Before the screens,
find the structure.
A product is more than a collection of screens. It is a system of things people recognize, relationships they understand, and actions they need to take.
A shared vocabulary.
Client. Order. Product. Provider. Payment. Give the important objects a name, then define their content and properties. Make assumptions visible before they become interface decisions.
Context changes everything.
Which Client places an Order? Which Products does it include? Explore the relationships and cardinalities that give your product its structure.
From nouns to possibilities.
Define what people can do with each object. Consider roles and permissions, then explore how the same object appears in different contexts.
A connected way to work
Keep the model in the conversation.
All the way through.
Objects & cards
Describe the domain with content, metadata, and calls to action.
Relationships & roles
Make connections explicit and reason about who can do what.
Flows & behavior
Place objects in context and think through actions, decisions, and paths.
Different views
Compose representations that refer back to the objects in your model.
A few useful distinctions
Get your bearings.
What is Object-Oriented UX?
OOUX is an approach to organizing experiences around the meaningful objects in a domain, their relationships, their content, and the actions people can take. An Order, for example, remains an Order whether you encounter it in a list, a detail view, or a fulfillment flow.
Is this the modeling application?
This is the introductory site for Thinking in CARDS, previously called OOUX Tool. The example above is a small interactive illustration. It does not open or modify projects in the modeling application.
Do I need to know OOUX to explore this?
No. Start with What, then explore How, With, and Who. Each perspective reveals a different part of the same commerce system.
Does the example save my changes?
The illustration uses predefined sample data and does not create a project or save personal information. Switching perspectives changes only what you see on this page.
Less ambiguity. More shared understanding.
Your next interface starts
with a clearer model.
Think through the exampleFour perspectives. One connected system.
Built on the shoulders of object-oriented thinking.
Thinking in Cards draws inspiration from Object-Oriented UX (OOUX), coined by Sophia V. Prater, creator of the ORCA Process.
We’re grateful for her contribution to the design community and the foundations that helped shape this project.
Thinking in Cards is an independent project and is not officially affiliated with OOUX or Rewired UX.