Creative Workload Platform

01

Business context

The platform was created to improve visibility across creative demand, available capacity, workload allocation, deadlines and upcoming delivery pressure. Existing planning methods made it difficult to understand whether the team could absorb new work and where bottlenecks were forming.

02

The challenge

Convert scattered operational data into one planning view that answers the questions leadership actually asks: can we take this on, who has room, and what is at risk?

03

Role & responsibilities

• Defined the product concept and planning logic.
• Designed the data and workflow inputs.
• Designed dashboard and management views.
• Built the application independently.
• Modelled capacity translation and feasibility checking.

04

Strategic approach

1. 01Begin with the operational challenge rather than the dashboard.
2. 02Define the data and workflow inputs that already exist in the team's process.
3. 03Encode planning logic — translate raw demand and availability into decisions.
4. 04Design management views for allocation and capacity decisions.
5. 05State known limitations and current development status openly.

05

Team & stakeholders

• Built independently, informed by the day-to-day planning needs of a five-member creative team.

06

Solution & capabilities

—

Technology & data

Capacity is modelled using estimated workload units and available designer capacity, with the intention of translating incoming demand into clearer allocation and feasibility decisions.

07

Process & workflow

1. 01Operational challenge→
2. 02Data and workflow inputs→
3. 03Planning logic→
4. 04Dashboard and management views→
5. 05Allocation and capacity→
6. 06Limitations and status→
7. 07Next-stage roadmap

08

Outcome & status

• No verified quantitative outcome is currently available for publication.
• The prototype creates a clearer view of workload pressure, capacity and upcoming deadlines, supporting more informed allocation and planning discussions.

—

Known limitations & next stage

• Some workload and allocation calculations are still being refined.
• Data quality depends on consistent Jira fields and date inputs.
• Some team-load calculations require additional validation.
• Workload-allocation logic is still under development.
• The platform is not yet a fully automated planning system.

Next stage: Strengthen Jira data mapping, validate capacity calculations, improve team-load visibility and move the prototype toward a more reliable internal beta.

09

Gallery

Interface and campaign visuals are placeholders until sanitised assets are supplied. Confidential product, customer and commercial data is excluded.

10

Video