Admin "Fill" Workflow – Case Study

Admin Fill workflow tracker showing color-coded progress across SKU, content, and SEO stages — Admin panel view: per-product readiness tracker with three stage checkboxes and aggregate progress bar.

TL;DR

Three employees owned separate stages of getting a product publish-ready. Each launch involved manual status checks and surprise blockers. I scoped and shipped a checkbox-driven, color-coded "Fill" tracker inside the admin panel - giving everyone a one-glance view of where each product stands across all three stages.

Context

CD-Log imports and sells e-tech across multiple categories. The website is the company's primary commercial channel, which means every new SKU has to clear three independent workflows before it can be published:

Stage	Owner	Work involved
SKU setup	Procurement-adjacent role	Pricing, supplier data, stock fields
Content	Content Fill	Descriptions, specs, images, structured data
SEO	Digital marketing	Titles, meta, taxonomy, internal linking

Each owner used their own working list. There was no shared, real-time view of where a product stood in the pipeline.

The problem

The friction surfaced in three specific patterns:

Surprise blockers at publish time. Products got pushed to "ready" only to be pulled back when one of the three stages turned out to be incomplete.
Manager check-ins. Team leads were spending real time asking "is X done?" - questions a system should answer.
No batch-level visibility. Launching a 30-product collection meant 30 individual status checks. Nobody had a holistic view.

Launches slipped, marketing campaigns kicked off without all SKUs live, and the same three employees were repeatedly the bottleneck.

The recurring cost of no shared visibility

Stakeholders & constraints

Stakeholders: SKU setup owner · Content Manager · SEO/digital marketing · Team lead · Dev Team

Key constraints: Build inside the existing admin panel (no new tool, no new login). Must be usable by non-technical content staff. No additional headcount. Compatible with existing product schema.

Approach & trade-offs

I considered three options:

Option	Approach	Verdict
A	Trello board per launch - quick setup, but creates a parallel system and doubles update work	Rejected
B	Single status dropdown (Draft/Ready/Live) - simple but too coarse to show which stage blocks	Rejected
C	Multi-stage checkbox tracker, native to admin, with color-coded progress + aggregate view	Selected

The trade-off I made deliberately: more dev investment now, in exchange for removing a recurring coordination tax forever.

The process

1. Problem framing & stakeholder interviews

Mapped each team member's current tracking method and identified where handoffs were failing. Confirmed the pain wasn't tooling - it was visibility.

2. Spec writing

Defined field definitions per stage, default states for new products, color-coded progress logic (empty / in-progress / complete), permissions model, and aggregate dashboard requirements.

3. Dev handoff & alignment

Walked the developer through the spec, prioritized per-product view first, aggregate dashboard second. Resolved schema compatibility questions upfront.

4. QA on staging

Tested the full product flow including edge cases - products that skip SEO, bulk-imported SKUs with partial data, permission overrides by team leads.

5. Rollout & iteration

Launched to the team, refined "complete" definitions during the first week based on real usage, shipped aggregate dashboard as a fast follow.

What I shipped

Aggregate dashboard: products sorted by stage status - the view managers use most.

Per-product checkbox tracker with three stages and color-coded progress
Aggregate dashboard with filtering by stage status and sort by oldest stalled
Default behavior rules for newly created products

What I'd do differently

What I did

Shipped per-product view first, aggregate dashboard second. Defined "complete" loosely and refined during QA. No automated notifications.

What I'd change

Build aggregate dashboard first (managers' primary view). Define "complete" rigorously upfront to avoid QA delays.

Skills demonstrated

Internal tooling Workflow design Cross-functional alignment Spec writing QA Status visualization Stakeholder management

← All case studies Next: Expo Ecosystem →