Solution "stacks": Reducing cognitive load

Mid-way into a financial transaction process, the user is selecting “solutions” for a need that they expressed in an earlier step.

These “solutions” are accounts comprised of a three-part tuple: A work-breakdown-structure (WBS), a performer, and a B&R.

An example of this account tuple might look like: (Some WBS Name, CBC, 1234).

In this way, the following two tuples (which only vary by the performer) represent two different accounts:

(Some WBS Name, CBC, 1234) and (Some WBS Name, ANL, 1234).

As you can see, the WBS name is the same in those two accounts. Thus, if we simply listed all accounts for the user to choose from, the user would be bombarded with a lot of data-duplication to wade through - making it difficult to tell how the items are different.

In order to reduce the cognitive load that would have occurred, I came up with this “stack” approach. For solution accounts which have WBS’s which have multiple performers and/or B&R’s, an expandable “stack” is shown.