Supervisors were responsible for identifying which lessons required localization, prioritizing them by market and stage, and assigning writers accordingly.

The existing workflow required manually scanning dense datasets with limited structural guidance.

Filtering, prioritization, and assignment were all handled within a single table view. This meant supervisors had to:

• Mentally large datasets
• Interpret priority of assignments manually
• Assign writers without clear workload visibility

This Tool exposed data, but didn't support decision making clarity.

I spoke directly with the Localization Supervisor to understand the workflow and where friction occurred in her day-to-day coordination.

The issue wasn’t missing features.
It was structural overload.

Before redesigning anything visually, I mapped the process into stages:

• Narrow down what needs attention
• Review production status
• Assign writers
• Monitor progress

Separating these steps clarified how the interface could better support each one.

The Prioritizer introduced:

• Persistent filtering by market and status
• Clearer priority grouping
• Inline writer assignment
• Structured dataset refinement

The goal wasn't to simplify the work, it was to structure it more intentionally.

FLUX was used to track active localization tasks across languages and markets.

The original interface displayed over 20 columns within a single spreadsheet-style view, combining filtering, status tracking, and assignment in one dense surface.

Too much was happening in one place.
Supervisors had to:

• Filter large datasets
• Track production stages
• Assign freelancers
• Monitor deadlines

All within the same interface.
The complexity of the domain was unavoidable, but the interface amplified that complexity.

Reviewing the Existing Tool

The issue wasn't a lack of information, it was how tightly everything was coupled together.

Filtering, tracking, and assignment were blended into one continous task.

I broke the process into clearer operational stages:

• Refine the dataset
• Review production status
• Assign freelancers
• Monitor workload and progress

This separation guided the redesign.

The FLUX redesign introduced:

• Segmented task views
• Persistent filtering panels
• Clearer separation between status indicators and action controls
• Structured grouping by market and language

The goal was to maintain necessary data density while reducing cognitive strain.