Ortiva
Shared ownership, made understandable
Complex ownership, made clear
A mobile-first product that helps people understand what they own, what an action changes, and which records they can trust.
Case-study scope
What was completed, without inflated claims
This page separates the working first release from future direction. It does not claim public adoption or investment performance.
People needed a clearer connection between an asset, their share, its history, and the effect of each action.
First use, asset review, action confirmation, portfolio history, and support states were shaped as one coherent experience.
Loading, failure, pending, completed, empty, and restricted states were designed rather than left as edge cases.
Public adoption, partner operations, and long-term behaviour remain future validation work.
The problem
Make ownership feel concrete
The interface had to reduce complexity without hiding risk, limits, or uncertainty.
Fragmented context
Value, documents, activity, and rights can easily appear as unrelated screens.
Unclear action impact
Before confirming, people need to know the amount, fees, resulting position, and recovery path.
Hidden restrictions
Unavailable actions and role limits need an explanation, not a silent disabled button.
Weak trust after errors
Pending and failed actions must remain traceable and recoverable.
Conceptual interface preview
One product story across three moments
The preview illustrates the intended interaction logic; values and assets are examples.
Portfolio value
₺ 24,860
Clear allocation, recent activity, and the next useful action.
Coastal Residence
18 units
Ownership meaning, documents, income rules, and relevant limits in one context.
Latest activity
Completed
A human-readable record with amount, fee, resulting position, and support path.
Key decisions
Clarity before visual polish
The strongest decisions made risk and system state easier to understand.
-
01
Define one source of truth
Every screen uses the same ownership, value, and activity definitions.
-
02
Preview consequences
Important actions show their financial and ownership impact before confirmation.
-
03
Keep state visible
Pending, completed, failed, and restricted states remain distinct.
-
04
Design recovery early
Support context and next steps are part of the original flow, not an afterthought.
Evidence and next validation
What exists and what comes next
- Core journeys
- Portfolio and activity views
- Permission model
- Failure and recovery states
- Usability sessions
- Operational partner feedback
- Accessibility review
- Outcome measurement
- Broader asset coverage
- Additional platforms
- Expanded reporting
- Partner integrations
Have a complex product?
Make the hard parts understandable
Tell us where people lose confidence and what a good outcome needs to look like.