CASE STUDY
Logo and brand design, digital design system, marketing website, and financial planning application.
My role in the project covered three primary design disciplines:
I collaborated with the lead developer while gathering requirements for the application. I also brought in another graphic designer to help brainstorm initial logo concepts and a junior UX designer in the initial phases of planning the flow of the application.
Adobe Creative Cloud suite of products
( XD, Photoshop, Illustrator, Indesign)
Zoom
July – October 2020
New start-up D2L was looking to build a new financial planning application targeted at independent advisors and their clients. They required branding, a website, a design system and the overall product design for their application.
The requirement was for me to lay the initial groundwork which their own teams would then extended upon later.
Using the design thinking framework, the project rolled out over four phases.
Below is the story of each phase:
PHASE 1
Due to the limited time allocated to this project and the large scope of work, I created three survey worksheets to do most of my discovery. The client was required to complete these before I started work on the project.
This worksheet set the tone and plan for the marketing website rollout and design. In addition I consulted in several workshops with D2L to unpack details of their software and provide my suggestions.
The following was covered:
The brand survey focused more on the brand itself, its' story and how it should be portrayed.
Topics around the following were covered:
This survey gave me a better understanding of the D2L business, its offerings and goals, as well as expectations for the project.
Topics around the following were covered:
Surveys and findings documentation:
Taking into consideration the various aspects the D2L brand wanted to embody, we began exploring various concepts before landing on the final designs.
D2L derived its name from 'Dark to Light', the company would help bring people's finances out of the dark and into the light. We explored this concept, anagrams and other marks while designing the logo. Work began with various sketches and was later moved to the computer for further refinement. After a few rounds and revisions, we landed on our final logo design.
Initial sketches and exploration:
Final logo design:
Carefully crafted style scapes were used to explore the visual look and feel for the brand. These described things like colour, visual direction, hierarchy and typography styles. This helped to visualise the context for how users could experience the brand visually.
Pictures representing our audience personas (identified in our discovery sessions) were placed into these mockups. This helped our stakeholders connect their target audience to the brands potential appeal.
Three mockups where provided and the last option below was chosen.
Style scapes created:
All elements (including logos) were delivered in a variety of formats, for light and dark, vertical and horizontal formats and the brand symbol. This was accompanied by a brand identity style guide for all the provided brand assets.
Pages from the brand style guide:
The product's goal was to digitise a process that was traditionally managed via PDF forms and Excel documents. Many examples of existing processes were shared with me to reference while designing.
I was also walked through the product's vision, functional requirements and we had several online workshops unpacking the expectations for the product deliverables.
Various sketches were also shared as we discussed the application business logic and end user requirements (some shown here).
Following the discovery work, I documented the project scope and application architecture. This helped to define what we were designing and building for, as part of the initial product handover.
With a structure in place, and several reference documents (Excel spreadsheets and PDF forms), I started mapping content to the application's structure.
This helped identify missing information, what was still required and helped me to ensure everything was accounted for as I started designing.
During our research phase, it became evident that we had two primary users with slightly different goals and requirements. Our goal was to make something simple and easy to use while creating a single application experience for all users.
This planning was done using wireframes, these showcased the application layout and patterns. Wireframes were then turned into flow diagrams for the two different user experiences.
Flow for independent advisors and wealth managers:
Flow for independent advisors and wealth managers:
Taking into consideration the various aspects the brand wanted to embody and the functional requirements for the application, we explored concepts before landing on the final designs and solutions. Below is a summary of some of these solutions.
As a web based application, I had to consider how the interface would translate from a large desktop format down to a mobile experience.
Colour psychology was used throughout the application to help users quickly identify the status or progress of various operations throughout the application.
Card designs showing status:
Table design showing status:
Examples:
To enable quick reference or financial health checks, I utilised the top area of each page to house key information and graphs.
All items that required user action were collated and listed under the notifications bell in the top toolbar. Clicking a notification would take the user directly to the relevant section within the application.
Within the top toolbar, in addition to the user profile link, I also included their financial advisors profile (if registered on the app). This provided the user with quick access to the advisors details .
This feature was designed to help maximise screen real- estate in the main content area of the application.
Iconography was carefully chosen and included next to the navigation list in the sidebar. With repeat use, users would learn what these icons represented, allowing them to collapse the sidebar to a more compact toolbar.
Advisors’ clients needed the ability to make changes on certain input fields within their profile. Their financial advisors needed the ability to review and accept these changes. Colour was used to show what needed attention or to indicate pending changes.
Proposed update
When a client edited content, the capture field changed colour and a “Proposed update” label is displayed. The client's proposed change could be canceled at any time before being accepted their advisor.
Proposed update
Original input
For the advisor, the proposed changes would adopt the ‘attention required’ status in red. Advisors could toggle between the proposed change and the original content while reviewing before accepting or rejecting the change.
A design system was also established during the process. All UI elements and components were documented and shared with the engineering team who translated the designs into code. This was also referenced during the next phase of the project when designing the marketing website.
The marketing website processes started by distilling the work done in the discovery phase. The website focused on landing the product and the specific needs and benefits of our two primary audiences.
Wireframes were put together to help define the different pages and how a user would move through the website. The primary goal of the website was to capture leads.
Content on these pages addressed all the user needs and frustrations we had identified. This was showcased by calling out various product benefits and features (see high fidelity designs below).
These pages provided ideal clickthrough landing pages from marketing campaigns that were targeting specific audiences.
Wireframes were then translated into high fidelity designs for final sign-off.
Below are the final designs that were handed over.
Homepage:
‘Individuals’ landing page:
‘Financial advisor’ landing page:
Pricing page:
LEARNINGS
User testing was done primarily by the stakeholders due to the NDA restrictions put in place at the start of the project.
I was, unfortunately, not able to see the final build of the application, due to the limited scope of work I was assigned to, but the team was very confident in the foundational work delivered, and the project was taken in-house for completion.
Due to the technical complexities of this project and limited time to execute, keeping an open dialogue with developer and the end client was key to this project’s success.
Always place components in the context of the screen to reveal more information about how they interact within the product and broader interface.
“Everything should be made as simple as possible, but not simple”
Albert Einstein