Print Evolved, Internal Production Tools

Print Evolved relied on several ageing internal systems that split logic across multiple tools. Operators had to jump between interfaces depending on the customer, carrier or product, creating confusion, inconsistent data and frequent batching/dispatch errors.

I redesigned and rebuilt the internal platform as three modern, responsive apps with clear responsibilities:

• Production → batching, conflict handling, printing, packing, dispatch
• Print → SKU creation, order management, customer rules, invoicing
• Admin → user management, role based access, shared configuration

My role covered end-to-end UX, UI, prototyping, design systems and React/Next.js implementation.

Legacy systems had grown fragmented over time. Different parts of the workflow lived in different tools, meaning:

• Operators had to memorise exceptions and routing rules
• Dispatch flows changed depending on which system a job came from
• Data was duplicated or inconsistent
• Training new staff took too long
• Errors during batching and dispatch were common

Teams needed a single, predictable workflow and a modern UI that matched how they actually work.

1. Map real workflows

I shadowed operators on live jobs and mapped end-to-end journeys from a job entering the system, through batching and printing, to final dispatch. This helped me understand the core actions operators performed dozens of times a day (create batch, add/remove jobs, resolve conflicts, print paperwork) and the common points of friction.

2. Define a clear system boundary

Three apps with distinct responsibilities:

• Production = operational workflow
• Print = product, order and commercial logic
• Admin = user management, role based access, shared configuration

This removed the need to jump between systems.

3. Design high-frequency flows

In Figma, I designed:

• Job selection & filtering
• Manual batch creation
• Conflict detection & resolution
• Dispatch steps
• SKU creation & editing
• Order & invoicing screens

The focus was always on speed, clarity and reducing cognitive load.

4. Build a reusable component system

I created a shared design system used across both apps: tables, filters, batch cards, forms, status badges, modals. Implemented in React + Storybook.

5. Front-end implementation

Built the interfaces in Next.js, TypeScript and Tailwind, collaborating closely with backend engineers to ensure business logic and UI behaviour aligned.

• Reduction in dispatch errors
• Operators now complete workflows inside one app, not three
• Faster onboarding and fewer mistakes
• A unified, modern UI for both production and commercial teams
• Reusable components accelerate future internal tools

This reduced mis-batching and gave operators more confidence during peak cycles.