How to Fill Out Designer Feedback — Ticket Difficulty

---

Last Updated: May 8, 2026

---

---

PURPOSE

This section is designed to capture real examples of what makes sublimated uniform tickets easy or hard. The information you provide gives Ryan structured data to coach Account Managers on stronger asset handoffs—for example, encouraging clients to send vector files instead of low‑resolution or AI‑generated images.

Your Role & Responsibilities as a Designer

• Complete the Designer Feedback | Ticket Difficulty card on every ticket you work on.

• Once familiar, this should take less than 30 seconds per ticket.

• Pay particular attention to tickets that feel Hard or Very Hard, as they offer the most insight.

• Be honest and specific; detailed feedback directly supports improvements for the entire team.

How to Complete the Card

1. Open the ticket.

2. Scroll to the **Designer Feedback | Ticket Difficulty** card in the left sidebar.

3. Fill in the key fields:

   1. Ticket Difficulty (Very Easy → Very Hard)

   2. Main Difficulty Cause (check all that apply; red badges indicate the most significant pain points)

   3. What made this ticket Easy or Hard? – this is the most important field for learning

   4. Estimated Hours & Actual Hours

   5. File Types Received

4. 4. Use the “Other” fields only when none of the existing options fit.

Best Practices

• No fields are strictly required; complete the fields that are relevant to your ticket.

• The more specific your comments in the text box, the more useful they are for Ryan’s coaching and for improving processes.

• You may fill out the card while you are working on the ticket or just before you close it, whichever fits best into your workflow.

---

 

Designer Feedback | Ticket Difficulty

---

OVERVIEW

The Designer Feedback | Ticket Difficulty card is now available in the left sidebar for every ticket. This card is a structured place to record how challenging each ticket is and what factors contribute to that difficulty.

On this card, you can:

• Select the overall Ticket Difficulty level: Very Easy, Easy, Medium, Hard, or Very Hard.

• Identify the Main Difficulty Causes, such as asset quality or client requirements.

• Record the File Types you received (for example, vector vs. low‑resolution or AI‑generated files).

• Indicate Logo Complexity & whether Pattern or Texture Recreation was required.

• Enter both Estimated Time & Actual Time spent on the work.

• Use the Notes field to add any relevant details, including whether additional cleanup was needed for AI files compared with client‑provided vector artwork.

The team will focus on collecting this data over the next one to two weeks to review patterns, refine estimates, and improve asset handoff practices. Please begin completing this card on your tickets as part of your regular workflow.

---

STEP-BY-STEP GUIDE

1. Find the new Designer Feedback section in the left sidebar 0:00

• The Designer Feedback Ticket Difficulty card is now available in the left sidebar of every ticket.

• This is where designers will log feedback about how difficult a ticket was and what made it difficult.

• The goal is to collect consistent data for the next 1–2 weeks so the team can review patterns and improve future estimates.

---

2. Rate the ticket difficulty 0:11

• In Ticket Difficulty, choose one of the following:

  • Very Easy

  • Easy

  • Medium

  • Hard

  • Very Hard

• Pick the option that best matches the ticket overall.

• The extra levels help distinguish between tickets that are only slightly difficult vs. extremely difficult.

• The team especially wants to track both the easy and hard ends of the scale.

---

3. Select the main causes of difficulty 1:07

• Use the Main Difficulty Causes section to explain why the ticket was difficult or easy.

• You can select multiple causes if needed.

• The options are pre-built and color-coded by difficulty.

• Examples mentioned include things like:

  • Low-res assets

  • AI-generated files that needed cleanup

  • Client-provided AI files that were usable but still required extra work

• If none of the listed causes fit, choose Other and type in your own explanation.

• If nothing applies, enter N/A.

---

4. Add notes to clarify the situation 2:07

• Use the text field to briefly explain what made the ticket hard, easy, or somewhere in between.

• This is the place to add context that the dropdowns do not capture.

• Keep it short but specific enough to help the team understand the ticket later.

---

5. Enter estimated time and actual time 2:23

• Fill out both:

  • Estimated time: how long you thought the ticket would take before starting

  • Actual time: how long it really took after completion

• This helps compare expectation vs. reality.

• Example:

  • Estimated: 2.5 hours

  • Actual: 5 hours 15 minutes

• If you finished faster than expected, that’s useful too.

---

6. Record the file types you received 2:51

• In File Types Received, select the file format(s) you worked with.

• Options mentioned include:

  • PNG

  • PSD / Photoshop

  • AI-generated

  • Low res

  • Vector

  • Other

• These are helpful, but they are considered less important than the main difficulty cause.

• If you received a file type not listed, use Other.

• If none apply, enter N/A.

---

7. Rate the logo complexity, if relevant 3:33

• Use Logo Complexity when the ticket involves logo work.

• Choose the level that best matches the design:

  • Simple text / basic shape

  • Medium / detailed but clean

  • Complex / intricate / multi-layer / gradient / texture

• This helps the team understand how demanding the logo work was.

---

8. Indicate whether patterns or textures had to be recreated 3:59

• For Patterns / Texture Recreation Needed, choose:

  • Yes if you had to recreate a pattern or texture

  • No if you did not

• If yes, add a short note describing what was recreated.

• Example: a wave/ocean pattern that took extra time to rebuild.

---

9. Mark whether the ticket is useful for training or examples 4:35

• Answer the question about whether the ticket would be good for training/examples.

• Options mentioned:

  • Yes

  • Maybe

  • No

• Use this to flag tickets that could be helpful as reference material later.

---

10. Understand how multiple designers can contribute 5:04

• More than one designer may fill out parts of the same ticket.

• Different people can add relevant details for their portion of the work.

• For example, one designer may fill in logo complexity, while another adds additional context later.

• The system keeps the information in one place so the ticket history stays visible.

---

11. Track time across multiple contributors 5:50

• If multiple designers work on the same ticket, the estimated time and actual time can be updated as work progresses.

• The transcript explains that time can be combined across contributors to reflect the total effort.

• This lets the team see the full time spent on the ticket instead of splitting it into disconnected pieces.

• The history shows who changed what, so updates remain traceable.

---

12. Use the sidebar consistently for the next 1–2 weeks 7:13

• The new feedback fields are already built into the left sidebar for every ticket.

• There is no major training required—just fill in the fields as you work.

• The team will review the collected data after about one to two weeks.

• If you have questions, ask the team, but otherwise just use the sidebar as part of your normal workflow.

---

✅ COMPLETED