Acomdev — Task & Sequence Approval System
UI/UX design for a task and sequence creation system with multi-level approval, rejection, and resubmission — focused on making complex enterprise workflows readable and actionable.
01 Project Overview
Designed screens and flows for creating tasks/sequences and managing them through multi-level approval and rejection. The objective was to reduce ambiguity around status, ownership, and next action in a dense enterprise workflow.
02 Business / Product Context
Acomdev is an enterprise IT organization providing tailored technology solutions spanning cloud ERP, data analytics, custom software development, and cybersecurity. This product area needed a clear way for teams to define work items and move them through structured review gates.
03 The Design Challenge
Complexity to address
- Tasks and sequences with multiple approval levels
- Approval, rejection, and resubmission states
- Risk of users misunderstanding progression or current owner
- Dense workflow logic that can feel opaque in a flat UI
Design objectives
- Support create → submit → review → approve/reject → rework
- Make status and progression visible at every step
- Clarify role-based actions per approval level
- Keep information hierarchy calm under workflow complexity
04 Understanding the Workflow & Requirements
The design approach started by mapping the operational sequence: how a task or sequence is created, submitted, reviewed at each level, and either advanced or returned for rework. Requirements centered on state clarity, reviewer actions, and resubmission without losing context.
05 UX / Problem-Solving Approach
06 User Roles / System Actors
Actors were framed by workflow responsibility rather than invented personas.
Task / Sequence Author
Creates items, defines workflow structure, submits for review, and updates after rejection.
Level 1–N Approver
Reviews submitted work, approves to advance, or rejects with reason for rework.
Final Approver
Completes the approval chain and confirms the item as fully approved.
07 Information Architecture / Workflow Diagram
Primary approval chain with a rejection branch back to rework and resubmission.
Approved path
Rejected path
08 Key User or Task Flows
Create & configure
Author defines the task/sequence and sets the multi-level approval path.
Submit for review
Item enters Level 1 with clear status and reviewer ownership.
Approve or reject
Each level either advances the chain or returns the item for rework with visible state change.
Resubmit or finalize
After updates, the author resubmits; after final approval, progression is complete and unambiguous.
09 Ideation & Wireframing Approach
Early structure focused on list/detail layouts, status indicators, and action placement for approve/reject before high-fidelity styling. Wireframes were used to validate progression visibility and reduce competing actions on review screens.
10 UI Design & Design Decisions
Status before content
Current stage, owner, and outcome were prioritized visually so users could orient before reading dense details.
Role-appropriate CTAs
Approve / reject / update / resubmit were designed as explicit primary actions tied to the active state.
Level visibility
Multi-level review was represented as a clear path so users could see where an item sits in the chain.
11 Design System / Components / Auto Layout
Reusable status badges, review action bars, table rows, and form blocks were built in Figma with Auto Layout so approval states and list/detail patterns stayed consistent across screens.
12 Interaction Design & Prototyping
Key paths — submit, approve across levels, reject to rework, and resubmit — were connected in an interactive Figma prototype for stakeholder walkthroughs and design handoff.
Open Figma Prototype
Explore the anonymized task/sequence approval flows. Client branding removed for confidentiality.
13 Key Design Considerations
14 Reflection / What I Learned
Complex approval systems succeed when progression is as visible as the form fields. Designing Acomdev reinforced that workflow clarity — states, owners, and next actions — is the core UX problem in enterprise task management, not decoration.