Information design and PoC for a Backlog status-sharing UI

A support UI that helps production teams share what needs attention in Backlog, without replacing Backlog itself.

Key points

  • PoC design and implementation of a support UI using the Backlog API
  • Surfaces high-priority cases, stalled updates, and missing next actions
  • Information design focused on shared awareness, not management
Area of work
Development / implementation
Period
May 2026

Background

I planned, designed, and built a support UI for the director team, using issues, comments, and update status already stored in Backlog.
The aim was to make missing shared context, unclear next actions, and uneven review load visible as an observation layer on top of Backlog.
After a PoC in real work, the team valued being able to see member load and case status that the default Backlog screens made hard to grasp, and a formal rollout across the business unit was decided.

Challenge

  • Case status and items that needed attention were easy to bury in Backlog
  • Standups lacked a shared view of what to check that day, so confirmation stayed verbal
  • It was hard to see each director's review load and which cases were stalled
  • Issue titles and comment conventions differed by team, so a third person could not read status quickly

What I did

  • Planned, designed, and implemented a support UI using the Backlog API
  • Defined observation states such as needs attention, caution, and waiting
  • Rebuilt the UI so each person's checks for today appear first
  • Set up Netlify and GitHub Actions to fetch and publish Backlog data on a schedule
  • Documented comment conventions and naming rules as part of the Backlog operating requirements
  • Ran a password-protected PoC on Netlify against live cases

What changed

  • Standups could identify what to review in a short time
  • Built an observation layer that supports shared awareness without replacing Backlog
  • Iterated the information design and observation logic against live case data
  • Made member load and case status visible in a way the default Backlog screens did not
  • Adopted as a standard tool for the business unit, with a rollout to all cases decided

Design notes

Design for shared awareness, not management

The UI observes whether work can proceed safely and whether status is shared, rather than completion rate or hours.

Shaped for standup use

Instead of a deep analysis screen, the UI is meant to show who should check what today in about five minutes.

What improved

To reduce missing shared context and uneven review load in production, I planned, designed, and implemented a Backlog API support UI. After the PoC, the business unit adopted it as a standard tool, together with Backlog operating improvements, and decided to roll it out across all cases.

Notes

  • Planned, designed, and implemented a case-observation tool using the Backlog API
  • Built a scheduled update pipeline with Netlify and GitHub Actions
  • Ran a password-protected PoC on Netlify against live cases
  • Visualized high-priority cases, stalled updates, owner load, and missing next actions
  • Helped standardize Backlog comment conventions and naming
  • After the PoC, adopted as a standard tool with a full-case rollout decided
  • Shared the GitHub repository internally so engineers could improve it together