modal & nav catalogued
of viable ways forward
with all stakeholders
Tables, forms, nav, flows
IA, nav schema, POC
Backtesting, shipped
Investment type governs which detail fields appear. UMA has expanded options. SMA has fewer required fields.
Account Type Entry
Type Selection
Investment type
Source Total
Trading Group
Account a Name
(Duplicate Acct Alert)
Options (SMA)
(Managed Account)
Workflows are embedded within table constructs. Instructions are sometimes clear, but actions are often obfuscated behind a button or interaction.
Consider leveraging an overlapping Panel System (Drawer, side-modal) — any time there is a user task, provide a consistent platform/paradigm (think panel/drawer) for the user to accomplish the task at hand.
- Table data and performing actions affecting said data are intermixed within existing HTML table structures
- Tasks/User Actions are not always intuitive or clear; user-action sequencing is obfuscated behind a button/interaction
- Limited to none in the way of help/utility (tooltips) or instructional context
- Simplified tables optimized for viewing (removing baked-in workflows)
- Separating READ ONLY data: optimize for display viewing
- Layer atop a modal (drawer/panel/etc) for focused workarea/taskarea
- Leverage tooltips and nested panels for additional context / instructions / links to resources
- With simple and efficient tables, comes room for optimization and bona fide feature development
Consider how we approach and deliver data through a card system. Identify key data sets based on user behaviors — think: daily workflows/tasks.
Using that, create components around those focused data sets that we call into a card-centric UI paradigm.
- All data is housed and displayed in tables, engineered to accommodate all viewing and utility needs the user may have
- Workflows are designed/engineered to exist within these table constructs; logical paths/solutions created by product developers may not align with users' product expectations
- Focused information backed by UX and engineering logic
- Reimagined/refactored filtering system, based on 'data as components' ethos
- Future-ready: as in, tablets or phones, or clouds
| ☐ | Date Received | Actions | Due Date | Service Order # | Account # | IP/IP Team | Order Type | Request Status | ✎ | Task | Task Details |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ☐ | 01/15/2024 | — | 01/22 | SO-2241 | ACC-8832 | Team A | Standard | Pending | ✎ | Review | Awaiting approval |
| ☐ | 01/16/2024 | — | 01/23 | SO-2242 | ACC-9910 | Team B | Expedited | In Progress | ✎ | Submit | Missing docs |
We are able to affect the ordering of columns on an as-per (ad hoc) basis. Given that capability, we decided to move the checkbox to the first column position.
Please take notice that the checkbox is contained in its own individual container cell. We have matched the HTML table structure with our 'reskin components'.
(own cell)
Simply put, this means we were able to adjust color of cell borders and fill, the icon sprite, the padding therein, and for fields with text, the font used for those.
Mental delineation needed for FIGMA/DESIGNER PROCESSES versus FUNCTIONAL/REAL LIFE PARAMETERS:
This particular screen requires 11 columns but per the FIGMA PROCESS used to create generic base tables, it is unable to accommodate that need without a refactoring from a FIGMA/DESIGN standpoint (i.e. detach and customize).
Maintain current Figma component structure as-is. Apply brand/system colors, typography. No structural changes to markup. Fastest path; most constrained.
Allow for structural flexibility as conveyed above. More brand and system uniformity. Allows real-life column counts, custom cell logic, proper checkbox isolation.
*Scenarios as defined in conversation with Jason and Naresh
- Table Container
- Table Header Components
- Table Pin's Header
- htTable Components — Instance Display Headers
- Table Cells
| Person | Role | Focus |
|---|---|---|
| Christopher | Support + Facilitate | Enablement, unblocking |
| Eileen | Ownership TBD | To define in session |
| Isabella | Ownership TBD | To define in session |
| Zack | Conversational UX Lead | End-to-end process structure |
Reference notation from whiteboard top-right: VDA SYTH (+B...) — likely references the Voice/Data Architecture synthesis artifact and additional B-track workstream.
Currently, workflows are embedded within table constructs. Sometimes the instructions are clear, but often actions are obfuscated behind a button or interaction.
Consider leveraging an overlapping Panel System (Drawer, side-modal). Any time there is a user task, provide a consistent platform/paradigm (think panel/drawer) for the user to accomplish the task at hand.
WORKFLOW ISSUES
- Table data + performing actions intermixed in HTML table structures
- Tasks/User Actions not always intuitive; sequencing obfuscated
- No help/utility (tooltips) or instructional context
KEY BENEFITS
- Simplified tables optimized for viewing
- Separated READ ONLY data display
- Layered modal/drawer for focused task work
- Tooltips + nested panels for context
- Room for optimization and feature development
Consider how we approach and deliver data through a card system. We could identify key data sets based on user behaviors — think: daily workflows/tasks.
Using that, we might create components around those focused data sets that we call into a card-centric UI paradigm.
DATA DISPLAY ISSUES
- All data displayed in tables engineered for all viewing + utility needs
- Logical paths created by product developers may not align with user expectations
KEY BENEFITS
- Focused information backed by UX + engineering logic
- Reimagined filtering: data as components
- Future-ready: tablets, phones, clouds
Consider a consistent paradigm/protocol for any workflows. So, if the user has a form to fill, or action to be notified of, or item requiring their attention and approval, all those actions come from a consistent place.
For instance, this side-panel offers a vertical format which is ideal for walking users through a workflow/protocol. Listing out fields, prompts, etc in a desired order.
With nesting, we can provide additional help/resources/guidance/etc without disrupting the workflow or creating visual noise.
...and or reference information, via the scrim area on the left. Can refactor current action buttons.
SCHEDULE A PAYMENT
Panels vs. Tiered cards? Maybe nested cards, if there's a need. Tiered cards?
Reference examples of conversational UX patterns that progressively guide users through complex flows — feeling like a conversation rather than a form.
Expand in more detail what Surabhi has put together already.
- Common Pain Points?
- Known Issues?
- New Unknowns?
Tactically: there are a few particular scenarios that Bryan would appreciate seeing solutioning for.
OR HOUSEHOLD FLOW
Captured from live system — represents the as-built state prior to any redesign.
Legacy flowchart representing the original documented flow architecture before screenshot audit.
Manual entry
User supplies all data from scratch at each step
Preload flow
System pre-populates; user confirms or edits deliberately
Overlay comparison
Normalized effort across the full workflow — the shaded gap represents total lift reduction
This side-panel offers a vertical format ideal for walking users through a workflow/protocol — listing out fields, prompts, etc. in a desired order. With nesting, we can provide additional help/resources/guidance without disrupting the workflow or creating visual noise.
Loading/processing states that communicate system activity to the user without abandoning context.
Three tooltip variants: bare context, condensed with navigation surfaced, and workspace/drawer form.
While the work was led by the housing product lead we can see how some of those were reviewed, iterated and organized into a more visual application.
This was a formative experience to work with a colleague on resolving problem — is it 'Indexization' or is it 'Indexing'?
LANDING PAGE
CUSTOMIZE S&P500
INTELLIGENT INDEXATION
BESPOKE BASKET
BUILD YOUR OWN
| Security | Weight % | Sector | Action |
|---|---|---|---|
| AAPL | 7.2% | Technology | Include |
| MSFT | 6.8% | Technology | Include |
| AMZN | 3.5% | Consumer | Exclude |
| TSLA | 1.9% | Auto/Energy | Review |
- Investment Objectives — complete
- ESG Preferences: toggle + exclusion chips
- Risk Parameters — volatility + drawdown
- Optimization — rebalancing + TLH toggle
- AI recommendation output — TBD
- Tracking error range — confirm with stakeholder