RICE FINANCIAL
A modular financial product designed for how people actually manage money.
007 / RICE FINANCIAL
Identity
- Role
- Product Vision & Creative Direction
- Category
- Fintech / Product Strategy / UX
- Discipline
- Product strategy & systems design
- Years
- 2026 — present
Role & responsibilities
- Product Vision & Creative Direction
- UX strategy & information architecture
- UI direction & design system
- Interaction and data-model thinking
Creative scope
- Product vision
- UX strategy
- Information architecture
- Dashboard & data design
- Modular design systems
- Mobile-first product thinking
- Performance-conscious UX
Scope & impact
Product strategy, UX, information architecture and data-heavy interface design at the systems level.
Status
RICE FINANCIAL is in development. What follows is product thinking, architecture and interface direction. There are no users, revenue, launch dates, funding or partnerships to report, and none are implied.
Product vision
Most financial tools ask people to behave like bookkeepers. RICE FINANCIAL starts from how people actually manage money: partial information, overlapping accounts, irregular income, shared obligations, and decisions made on a phone in under a minute.
Information architecture
The core structure separates accounts, entities, transactions and relationships so the same data can be organised several ways without duplication. Flexible grouping lets someone restructure how they see their finances without re-entering anything.
- Account and entity model that tolerates incomplete data
- Transactions as first-class objects with flexible attribution
- Grouping and views as configuration rather than fixed structure
Interface direction
The UI is modular: dashboards assembled from independent blocks, list and card views over the same data, detail surfaces that open in place. Density is treated as a feature, with powerful views for people who want them and quiet defaults for people who do not.
- Dashboard composed of interchangeable modules
- Paired card and list views for different reading modes
- In-place detail rather than deep navigation stacks
Performance & behaviour
Speed is part of the design brief. Interactions respond immediately and reconcile afterwards, with synchronisation treated as an interface concern rather than a backend detail, because a financial tool that hesitates does not get opened twice.
PERSONAL INTEREST