Designing RedStack: A remote workflow system - a case study

RedStack is a remote execution platform that lets individuals or teams upload structured workflows from anywhere, and have them executed step-by-step on-site. This is especially useful in domains where physical procedures need to be carried out precisely without the designer (of the workflow) being physically present.

💡For a deeper look into how I approached research, product thinking, and system design using AI workflows, you can read my companion case study here 👉Architecting a “Remote Execution Platform” with AI-augmented UX workflows - a case study.

---

Note: This is a redacted case study. Designs, some domain-specific details and images have been changed, abstracted, redacted to respect confidentiality agreements.

---

Overview

This case study focuses on the design of the end-to-end workflow creation and management experience, which involved:

• Designing the dashboard

• Managing workflow libraries

• Creating and submitting new workflows

• Building the workflow-builder interface

• Mobile app experience for on-site executors

My role

I was the solo product designer responsible for end-to-end design, which involved,

• Research (domain, product, market and competitor)

• Creating necessary UX artefacts

• Working mid-fidelity prototypes (AI prototypes)

  • The entire workflow was AI-augmented and I produced working prototypes using v0 (by Vercel) instead of resorting to routine wireframes.

• Design system

• Final UI

Workflow summary

For context, the setup involved remote workflows, protocols, and physical execution by on-ground executors.

It had two completely different users.

• One, a primary user (workflow designer) responsible for designing complex remote procedures or workflows (structured instructions), and

• The other, an on-site executor executing those procedures step by step, using tools or instruments.

In this case study, I refer to primary user-authored workflows as ‘procedures’ for abstraction, though the original system may use different terminology

The vision: Primary users upload a procedure remotely, have it carried out on-site by executors, and receive traceable results.

Key screens

Below are a few representative screens from the redesigned platform. These have been abstracted and rebranded to protect confidential elements.

🔐 Login

A clean login screen with a split layout.

📊 Home

Overview of total workflows, status breakdown, and recent activity

📁 Workflow vault

• Table view with search, filter, and action controls.

• Status pills help scan progress at a glance.

🔧New workflow

• Lightweight form to capture workflow metadata

• Simple, non-distracting layout focused on clarity

🔧 Workflow builder

• A canvas where designers can drag and drop blocks from a left panel.

• Actions like "Save" and "Submit" are sticky and accessible.

Design system

Designing the mobile app for executors

While the web app focused on workflow creation, I also designed a mobile experience for on-site executors, the people actually carrying out the workflows in physical environments.

Highlights

• Every screen is purposefully minimal.

• Workflow-builder UI is block-based and structured for future extensibility.

• Design system - Reused components and design tokens across screens ensuring consistency and reduced dev effort.

• AI-assisted prototyping - All mid-fidelity screens were generated and validated using ChatGPT + v0.dev.

Outcome

This project taught me how to design for complexity. While the final screens may appear minimal and clean, they’re backed by dense flows for multiple user roles.

The experience helped me develop a stronger lens for simplifying complex solutions.

NDA + Status Note

Due to confidentiality, some technical details have been changed, abstracted. I’d be happy to walk through the full design thinking and designs in a private conversation.