David Schneller Portfolio

Enterprise Reporting Tool

A facelift brief that turned into a workflow redesign for enterprise-wide reporting

The client asked for a modern UI for a 20-year-old in-house application that collects figures from departments across a large enterprise, with the structure left as it was. A central team checks every submission, and the figures go into the company’s reporting.

I convinced the client to start with user interviews. They showed that the friction was in the workflow, not in the look.

What the interviews showed

With two to six questionnaires a year, nobody learns the application. Every visit starts from scratch, so the application has to remember the context for its users. Three decisions came out of that.

1. Your current questionnaire first, without setting a filter

The old dashboard showed everything the account could see. To get to their own questionnaire, people picked a division, a report object and a period, and waited for the page to reload after each step.

The old dashboard, rebuilt without client details: a dense grey page with a green header with a parameters panel for profile, unit system and report object state, division buttons and a report object dropdown, and below it a table of ten questionnaires with from and to date dropdowns, columns for year, site, questionnaire, coded processing status and role, and edit icons on every row.
  1. Division and report object have to be picked by hand, although the account belongs to one department.
  2. The timeframe has to be set with month and year dropdowns, which takes several clicks.
  3. Status is written in internal codes and is hard to scan for open tasks.

The account already knows which department and location a person belongs to. The new dashboard uses that and sorts by date, newest first. The current questionnaire and the last few are on top without a single filter. The filters are still there for anyone who needs another location or an older year.

The new dashboard: a filter row for date, division, report type, state and location above a table of questionnaires sorted by date, newest first, each row showing the month and reporting period, region, questionnaire type, the due date of the open one and a status in plain words with the time of the last edit.
  1. Division and location come from the account. They can be changed, but rarely need to be.
  2. To find older reports, the timeframe is set in quarters. That takes far fewer clicks and matches the survey cadence: yearly, half-yearly or quarterly.
  3. Newest first, so the questionnaire that is due now is the first row.
  4. Status says in plain words what happens next, for example that the questionnaire waits for the coordinator.

2. Fill in over several days, with several people

A questionnaire is a collection job. Someone fills in what they know, asks a colleague for the rest and comes back later. The redesign supports that instead of expecting one complete session.

Before

  • Saving only works when everything is complete and valid
  • Users started collecting data outside of the tool as a workaround
  • No overview of what is still missing
  • No trace of who contributed what

After

  • Every value is saved after it is entered. Come back any time and continue where you left off.
  • Work with multiple users on the same report.
  • Completion per category, and a list of what to fix before submitting
  • Each category shows who edited it last

3. Reviews in the application instead of in inboxes

Two people in the central team checked every submission. When a number looked wrong, they wrote an email or called, and the department corrected and submitted again. The department did not know whether its questionnaire had been accepted, and the central team kept track of open questions in their own mail.

In the redesign, inconsistencies are flagged on the category they belong to while people fill in, so many problems are fixed before the central team sees them. Supervisor and coordinator validate in the application, and everyone sees the same status.

The questionnaire overview brings decisions 2 and 3 together.

The questionnaire overview screen: six question categories listed with their completion status and who last edited them, a due date countdown, a list of editors, a flagged inconsistency, and a three-step progress bar from data entry through supervisor to coordinator validation.
  1. Each category shows how many questions are answered, so anyone coming back sees what is left.
  2. All editors and the responsible supervisor are listed, and each category shows who edited it last. Who to ask about a number is on the page.
  3. An inconsistency is flagged on its category before the central team has to find it.
  4. The three validation steps are visible to the department, not only to the reviewers.
  5. Submitting is possible once all categories are complete, and the page says what is still missing.

What we kept

The old application already showed last period’s answer next to each field, warned when a value looked implausible and showed which inputs a calculated value came from. That catches mistakes before the central team has to, so all of it stayed. What changed is room to explain: comment fields became large text areas.

One questionnaire category open for editing: questions with yes-no toggles and number fields that each show the answer from the previous report, a full-width comment field, a warning when an entered value looks implausible, and a calculated value with the inputs it was computed from.
A category with previous values, a plausibility warning, a large comment field and a calculated value.

How I worked

After kickoff workshops with the client I interviewed five users at different locations and sorted the findings in an affinity diagram with the team. I mapped the review process with the stakeholders. Wireframes and click prototypes went to the central team for review, because they check every questionnaire and chase every correction. The final designs went to the developers as Sketch mockups in Zeplin and as InVision prototypes.

What I take from it

Project Specs

Context
Client project at Cognizant for a large international enterprise
Duration
10 weeks
Used skills
User interviews, affinity diagramming, workflow analysis, stakeholder workshops, wireframing, Sketch, InVision, Drama
Division of work
Design by me, implementation by the client's web development team