top of page

Report Package Usecase

The Challenge

Establish Oracle in the Financial Reporting Cloud Services market by capitalizing on our strength in Finance.

  • Corporate reporting processes involve many people in a coordinated effort to publish accurate financial or other performance related information to both internal and external stakeholders.

  • The reporting solution needs to support the rigid controls necessary to protect the privacy and accuracy of data, while at the same time support the collaboration necessary to orchestrate the assembly of a final report stitched together from many supporting documents.

  • User experiences throughout this process vary tremendously based on one’s role. For example, Executive Report Owners who are responsible for a report’s structure and its review process have a much different experience than executives with final sign off authority who are not involved in the report construction at all, but are legally held accountable for the information within it.

The Goals

  • Deliver a secured, collaborative and process driven service for creating, publishing and filing financial and management reporting that includes numeric and textual content.

  • Ensure that the process is highly scrutinized through iterative and collaborative reviews and approvals.

  • Ensure trust in the published reports through traceable single-source of truth.

  • Utilize Web, Office and Mobile access whether online or offline.

My Role

  • Member of core team setting vision and direction for the new service.

  • User experience lead, driving design direction and responsible for delivering it from the ground up.

  • Managing additional design tasks and resources.

  • Mentoring junior designers on the team.

Users Profiles

All user roles expected to use the service were identified and mapped in our established user model.

rp_user_profiles.png

Collaboration Map

Narrative reporting needs were identified in the user model to better understand the relationships between users and artifacts in their context and typical workflows.

rp_collaboration_map.png

Existing “manual” Workflow

Guiding principles and antomies for entities and environments were defined. A navigation model was established. And a high-level integrated and collaborative workflow was proposed.

rp_existing_workflow.png

Proposed Model

The existing report creation process was researched and visualized to identify pain points to help develp insights for opportunities and solutions:

  • Manual and unstructured.

  • Not traceable and prone to inaccuracies and mistakes.

rp_proposed_model.png

Proposed Lifecycle

A structured and mostly automated workflow lifecyle, from defining the report package to publishing the report was mapped out.

rp_proposed_lifecycle.png

Iterative Design

Multiple iterations of the design were explored, reviewed and evaluated with end users and stakeholders.

V1

Issues: Lacks high-level status/metrics, provides information that is not needed all the time, and actions are far from tree nodes.

report_center_v1.png

V2

Issues: Busy and wastes realestate using vertical accordion. Also, accordion breaks table flow when 1st or 2nd are collapsed.

report_center_v2.png

Usability Testing

The entire flow was tested with end users and findings were incorporated in the final design.

rp_usability_test.png

Final Design

Delivered Results

The report package service has been well received by customers and the impact was measurable:

  • Reduced Budget Book execution time by 25% initially, will be more!

  • Reduced disparate manual processes to gather data.

  • Increased collaboration across multiple departments.

  • Provided timely and accurate information.

  • Improved Reporting Process – simpler, faster, less complex and more reliable.

  • Ability to use Microsoft Office products increased the comfort level for adoption.

  • Provided integrated analytics process to deliver an executive level reporting package

  • Consistency at corporate & across properties in the areas of process, reports, and analytics/insights

And responded with a redesign to address the issues:

  • Simplified and reduced height of phase headers and made selected phase more obvious (tab-like.)

  • Introduced a list view as default, with an option for a drill-down folder view.

  • Only included current responsibility column and moved the remaining workflow in right pane.

  • Provided an option for a compact view, which would persist once user switches to it.

rp_redesign_1.png
rp_redesign_2.png
rp_redesign_3.png
rp_wizard_1.png
rp_wizard_2.png
rp_add_doclet.png
rp_review.png
report_center.png

© 2020 by Mahmoud Nagib.

bottom of page