Catherine Madden
  • Home
  • Relay
  • About
  • Learn
Catherine Madden
  • Home/
  • Relay/
  • About/
  • Learn/
Catherine Madden

Financial Dashboards

Catherine Madden
  • Home/
  • Relay/
  • About/
  • Learn/

Financial Dashboard Design Examples

Some example documentation from a 10-week project focused on developing design guides for financial dashboards to be built by the client's dev team in Cognos. 

Select any image below to expand the view. Hover over the image to read a description of the document. 

  Research, Empathize, Define.  All projects start with a series of workshops (spanning from one 4-hour session to several day-long sessions) to explore the business challenges, establish empathy with the end users, and define the primary o

Research, Empathize, Define. All projects start with a series of workshops (spanning from one 4-hour session to several day-long sessions) to explore the business challenges, establish empathy with the end users, and define the primary objectives for the project. 

  Rough prototyping.  I produce hundreds of sketches to experiment with the right combination of data points, chart types, level of detail, and other functionality. I review it with clients through a presentation that helps them envision the fun

Rough prototyping. I produce hundreds of sketches to experiment with the right combination of data points, chart types, level of detail, and other functionality. I review it with clients through a presentation that helps them envision the functionality and interactivity. I prefer to get feedback on sketches (rather than a work in progress prototype) until we are pretty close to a final design to ensure the clients provide feedback that is focused on content rather than aesthetics. 

  Persona brief.   A brief description of each user persona as part of the final deliverable, which in this case is a detailed design document for the IT department to use as a guide to build out the full solution. The deliverable has many intro

Persona brief.  A brief description of each user persona as part of the final deliverable, which in this case is a detailed design document for the IT department to use as a guide to build out the full solution. The deliverable has many introductory pages which document the project evolution and an overview of the user personas which were developed in the initial workshops and validated throughout the project. 

  User flow.  Detailed dashboards often have several layers of detail to click through. It is important for both the development team and the users to have a clear understanding of the site architecture and user flow. 

User flow. Detailed dashboards often have several layers of detail to click through. It is important for both the development team and the users to have a clear understanding of the site architecture and user flow. 

  Annotated wireframes (1 of 2).  Example of a detailed annotated wireframe. Each design was created in close collaboration with the business users and IT team to ensure maximum usability within the technical constraints identified by the softwa

Annotated wireframes (1 of 2). Example of a detailed annotated wireframe. Each design was created in close collaboration with the business users and IT team to ensure maximum usability within the technical constraints identified by the software and data teams. 

  Annotated wireframes (2 of 2).  Example of a detailed annotated wireframe. Each design was created in close collaboration with the business users and IT team to ensure maximum usability within the technical constraints identified by the softwa

Annotated wireframes (2 of 2). Example of a detailed annotated wireframe. Each design was created in close collaboration with the business users and IT team to ensure maximum usability within the technical constraints identified by the software and data teams. 

  Design guide.  The final pages of the detailed design document include style guides to ensure that user's aesthetic expectations are met once the IT team builds out the full application. 

Design guide. The final pages of the detailed design document include style guides to ensure that user's aesthetic expectations are met once the IT team builds out the full application. 

1 2 3 4 5 6 7
Previous Next
  Research, Empathize, Define.  All projects start with a series of workshops (spanning from one 4-hour session to several day-long sessions) to explore the business challenges, establish empathy with the end users, and define the primary o
  Rough prototyping.  I produce hundreds of sketches to experiment with the right combination of data points, chart types, level of detail, and other functionality. I review it with clients through a presentation that helps them envision the fun
  Persona brief.   A brief description of each user persona as part of the final deliverable, which in this case is a detailed design document for the IT department to use as a guide to build out the full solution. The deliverable has many intro
  User flow.  Detailed dashboards often have several layers of detail to click through. It is important for both the development team and the users to have a clear understanding of the site architecture and user flow. 
  Annotated wireframes (1 of 2).  Example of a detailed annotated wireframe. Each design was created in close collaboration with the business users and IT team to ensure maximum usability within the technical constraints identified by the softwa
  Annotated wireframes (2 of 2).  Example of a detailed annotated wireframe. Each design was created in close collaboration with the business users and IT team to ensure maximum usability within the technical constraints identified by the softwa
  Design guide.  The final pages of the detailed design document include style guides to ensure that user's aesthetic expectations are met once the IT team builds out the full application.