Khushboo
Portfolio case study / AFL - TELUS

AFL Distribution Quote Tracker

I designed and built an internal workflow portal that turned Jira Excel exports into a searchable, assignable, change-aware operations tool for distribution quote tracking.

Quote approved
1,351
Build segments
1,991
Changed records
1,730
Dashboard view of the AFL Distribution Quote Tracker
Executive summary

From static exports to an accountable quote workflow

The product was not just a dashboard. It became a workflow layer where teams could compare imports, identify exceptions, assign follow-up, add audit notes, and review history in one place.

Problem

Teams manually reconciled high-volume NGMR quote work across Jira exports, Excel filters, screenshots, and conversations.

Design response

Preserve the trusted spreadsheet structure, then add comparison, history, ownership, and workflow visibility around it.

Outcome

Users moved from lookup and manual comparison to filtered review, assignment, and tracked follow-up.

Product context

The existing workflow worked, but it was fragile

Users trusted Excel because it matched how they worked. The design challenge was improving speed, visibility, and auditability without replacing every habit at once.

  1. Jira exportRaw rows and parent-child records.
  2. Excel filtersManual slices by release, region, and status.
  3. ComparisonLook for new rows and changed values.
  4. ConversationConfirm owner, status, and action.
  5. Leadership readoutSummarize status and risks manually.
Design principles

Four principles shaped the product

01 Preserve trust

Keep workbook language, parent NGMR structure, and import rhythm visible instead of hiding the work behind abstract dashboards.

02 Show exceptions first

Make new work, missing quotes, cancellations, changed records, and unassigned rows impossible to miss.

03 Support exact-ID behavior

Let users paste NGMR IDs from Jira, Excel, messages, or screenshots instead of forcing dropdown discovery.

04 Turn review into action

Add assignment, comments, audit notes, and history so the portal becomes a workflow tool, not a passive report.

Product design
Import workflow screen with release year and file upload controls

A simple import flow built for trust

The product starts where the team already worked: Jira Excel exports. The import experience stayed deliberately simple so users could validate, preview, and compare a file before committing new data.

  • Excel-compatible
  • Validation-first
  • Low friction
Change tracking screen showing filters and field-level differences

Field-level comparison for daily change review

Instead of comparing spreadsheets manually, the portal surfaces the latest differences between import runs in a single review screen. Teams can focus on what changed and what needs follow-up.

  • Change-aware
  • Paste search
  • Field-level history
Filter interface for narrowing changed records by field, region, and BRD window

Flexible filters made change audits more usable

A major design challenge was helping operations teams narrow large change sets without turning the screen into a confusing report builder. Quick chips handled repeat tasks while deeper filters supported audits.

  • Filter taxonomy
  • Quick chips
  • Audit support
NGMR workflow table with comments, assignments, and audit fields

Not just a table - a task workflow for quote follow-up

The NGMR list organizes parent records with child build segments, then adds action fields so teams can assign ownership, add audit notes, review history, and drive follow-up like a lightweight task manager.

  • Parent-child view
  • Assignment layer
  • Audit notes
Impact

100% change capture, clearer ownership, better exception visibility

45% missed/mo -> 100%Change capture accuracy
1-2+ min -> <10 secNGMR change lookup time
Scattered -> assignedOwnership visibility
Manual checks -> surfaced viewException review clarity

The highest-value shift was replacing scattered Teams-message updates and monthly manual misses with one reusable operational workflow for accountability, action, and exception management.

Next case study