Skip to content
Jamiu AbdulfataiProduct Designer
← All projectsView visual case study

PRODUCT DESIGN CASE STUDY

Reporting Portal

Reporting Portal project overview

MY ROLE · Dashboard information architecture and responsive UI

Reporting Portal

I designed Reporting Portal to help a manager see what needs attention before getting lost in project totals. The dashboard brings risk, tasks and milestones into one view.

01What I wanted to solve

I worked on the metrics row, filters, task board and responsive layout in light and dark themes. The main question was how quickly someone could identify the work that needed a decision.

02The decisions that mattered

Lead with numbers someone can act on.

I prioritised tasks due, at-risk and critical items over a reassuring project count.

Make waiting work visible.

I gave Review its own board column, alongside To Do, In Progress and Done.

Keep the overview useful on a phone.

I reduced the mobile layout around the metrics and a single board column, with filters for project, team, dates and status.

03See the work

The screens below show how those decisions came together.

Reporting Portal in light mode: key metrics row, filter bar, and a four-column task board beside upcoming milestones
Reporting Portal in light mode: key metrics row, filter bar, and a four-column task board beside upcoming milestones
More screens and supporting work
The same dashboard in dark mode, with the metric cards and task board colour-coded by status
The same dashboard in dark mode, with the metric cards and task board colour-coded by status
Reporting Portal's mobile layout shown on a phone
Reporting Portal's mobile layout shown on a phone

04What I can show, and what I would test

The evidence is the dashboard design and its responsive states. I would test whether managers can find the day’s at-risk work quickly, and whether teams need a separate blocked state.

View project presentation All projects