• Vidext

Automation of Ad Hoc Design Requests

Automation of Ad Hoc Design Requests

Design requests are now a manual and decentralised process. It creates a reliance on email which can be disorganised and lack of visibility for users and designers. We need to address this problem for better workflow efficiency.

  • Length: 1 week

  • My role: UX Designer

  • Primary output: Design Handover Doc

Step 1: IDEATION and brainstorm

What is the MVP?

What is the MVP?

The solution proposed is an integration with Jira to automate the design request flow. This solution will tackle our existing problems by providing centralisation, email elimination and automated tracking. The platform serves as the single point of contact with the company.

step 2: empathise and define

The client's workflow is bilateral to the designer's

The client's workflow is bilateral to the designer's

"The client's workflow is bilateral to the designer's" means that the client's and designer's workflows are interdependent and mirror each other in a complementary way. Actions taken by the client (such as submitting a request or providing feedback) directly influence the designer's tasks (like reviewing the request or implementing changes), and vice versa. Each party's workflow progresses in tandem, with one side's actions enabling or shaping the other's responsibilities, creating a two-way relationship. Therefore, it is very important to define the workflows before jumping to designing.

Client's workflow

Client's workflow

Designer's workflow

Designer's workflow

step 3: MOod board

Establishing best practices

Establishing best practices

By researching how other platforms are doing it, we can easily define design patterns and best practices as well as get inspired to dive into the interface design.

step 4: Design Handover

Time to identify and address edge cases

Time to identify and address edge cases

By addressing these potential edge cases, the automation of ad hoc client requests can remain efficient, user-friendly, and resilient in the face of unexpected challenges.

Example output 1: Visual status of requests

Example output 1: Visual status of requests

Drawing inspiration from Jira's intuitive interface, the platform now enables users to effortlessly track the status of their requests at a glance. Each request is clearly categorized and displayed in an organized, visually streamlined layout, allowing clients to understand progress without digging through layers of information. With real-time updates and status labels, users can quickly identify whether a request is in progress, awaiting review, or completed, enhancing transparency and minimizing the need for additional follow-ups. This design empowers clients with a sense of control and clarity throughout the process.

Example output 2: Requests form

Example output 2: Requests form

Clients can now submit requests directly through the platform. The design and form fields were carefully crafted to ensure this new functionality works seamlessly. To achieve this, I used Typeform's interface design as if integrated into the platform, aiming to enhance ease of use and speed for clients. In terms of content, the proposed custom fields are name, description, priority, category, and the option to upload files.

Example output 3: Platform notifications and request tracking

Example output 3: Platform notifications and request tracking

It was important to work on the complexities of the invoice process for our clients. Many questions revolved around payment terms, registering payments and being able to track changes in the invoice as well as including the functionality to forward an email with the invoice attached from the platform. All of these small actions required special attention.