UX of a customer area in wealth management
Facilitate the exchange and consultation of information without trivializing the confidentiality requirements of the profession.
Why this needs a dedicated approach
A complex space discourages use; an overly simplified interface can hide the necessary responsibilities and access levels.
What the system should make possible
A sober and understandable route, adapted to users, documents and validations actually planned.
Signals that justify a dedicated project
A customer area becomes useful when it simplifies an already defined relationship. It must not concentrate sensitive data without clear access rules.
The documents are exchanged through several channels without a common vision of their status.
Customers struggle to distinguish between information, expected action and document to be validated.
Employees do not share the same rights or responsibilities on a file.
A visible, usable outcome
Design must start with users, documents and responsibilities before choosing features.
Role-based journeys
Views adapted to the customer and employees according to the responsibilities defined.
Actionable information
A hierarchy that distinguishes consultation, document request and expected validation.
Controlled access
A scope of security and traceability proportionate to the actual intended uses.
Points to define first
Implementation, trade-offs and tools are adapted to the client’s context and detailed during discovery.
- Access and roles defined
- Readable financial information
- Tailor-made experience
Questions to answer before designing
These answers determine the right scope and prevent a tool or channel being chosen before the business need is clear.
Which users access which information and for what purpose?
What actions commit the client or the firm and require proof?
Which existing tools should remain the reference source?
A response built around your context
BlackStone designs the interface and the functional scope with the stakeholders before any development or connection.