before
poor data visualization
Poor data visualization yielded a complicated analysis page that should have otherwise provided valuable insights into the status of a project and its prospects. Due to report length issues already in motion, this page was also buried somewhere in the middle of the report.
lacking references
Appointments are our most valuable deliverable to our clients; however, this legacy report listed them without counts or reference to which client team member was responsible for them. As a result, this section typically created more questions than it answered.
too many pages
Typical project reports can span 10+ pages, with their most valuable contents residing on just a few pages that were scattered throughout the report.
after
clear and concise
My redesign prioritizes each report's most valuable data points by pinning a color-coded and clearly labled prospect status graph to the top of page 1, followed by designated breakouts of calling status as they apply to our 3 deliverables. Calling metrics are then automatically grouped by ideal granularity - including quarterly and annual grouping options - to ensure a concise and readable report.
more value in fewer pages
Because there are often so many, appointments still get listed at the end of the report; however, my redesign includes row counts and references to the client team member that was assigned to each opporutnity for internal tracking. Just a few more pages outlining all pending opportunities that are awaiting scheduled follow-ups (i.e., a pipeline) keeps this report under 5 pages.
even more...
à-la-modular
Modular controls on the new, client-facing report page (previously reports could only be exported by an admin, with limited options) allow client users to directly access and build reports to their required specs. Report sections can be omitted and granularity can be adjusted for inspection, ensuring usability and value.
dangerous wasted space
The top half of the first report page was wasted with oversized branding, contact information, and the project name, creating the foundation for an unnecessarily long report.
dangerous messy metrics
With a maximum granularity of monthly metric breakouts and summaries (e.g., totals calls, total hours, etc.) in a separate table from their respective calculations (e.g., calls per hour), metrics quickly become long and difficult to read.
the extra 7 pages (below) that I snipped from this example...