top of page
Search

Feedback Patterns

Updated: Dec 15, 2025



If your feedback process feels broken, it’s probably because you’re using a manufacturing mindset to do exploratory work. Drafts aren’t linear steps toward completion—they’re calibration tools. This piece outlines the feedback patterns that quietly derail teams, and what healthier collaboration actually looks like.


Although many of us create intangible things– software, ad campaigns, strategic frameworks– we are still tempted to imagine the creative process as an assembly line. Each person serves their role along the line, contributing to the product until it is finished. But that is a model for mass producing something that already exists, and a terrible way to make something new. 


You don’t need to be on a “creative” team to recognize this pattern. Most modern knowledge work—strategy, product, operations, even management—is exploratory before it can be operationalized. The failure isn’t a lack of creativity; it’s a mismatch between how we collaborate and the kind of work we’re trying to do.


If your team is producing iterations to get to a final product, or even an MVP, get that assembly line out of your head. We are not an assembly line trying to solve for repeatability. We are a group of interests and areas of expertise trying to solve for clarity. Think of the process as a visit to the optometrist. Each iteration gives us options, and if we’re able to identify the one that brings us more into focus, then the next iteration will be even sharper, until we have reached clarity and alignment.


As the connection point between creative teams and business stakeholders, I have seen certain patterns repeat across brands, campaigns and products. You may recognize the five most common examples below, even if you don’t work on a “creative” team. If you are involved in collaboration to reach goals, being able to recognize each pattern as you encounter it can help you steer teams back toward a healthy rhythm.



  1. The Healthy Rhythm



The process doesn’t have to be smooth to be healthy. The best creative projects start with a clear picture of what the end product needs to accomplish, and only a fuzzy idea of how it will get there. This is harder than it sounds. Most leads and clients have a clear idea of how they would start if they were doing it themselves, but aren’t totally sure where the process would lead them. The best investment of their time and effort is into a detailed description of what we want to accomplish. The team’s role is to figure out how to get us there. 


In a Healthy Rhythm, the first draft is the biggest effort. It usually produces multiple rough options with the goal of picking one and refining it. In practice this work often splits into “the safe option” and the “weird option.” This is common enough that it should be something to look out for. If the project lead is humoring the team by letting them explore the weird option, it would be better to eliminate that direction than to refine it. 


Even with its hiccups, the Healthy Rhythm is, at its core, healthy. The work progresses and sharpens over time. The feedback moves from the global, through a fork or two in the road, and on to the granular. 


Finding the Healthy Rhythm

  • Set clear objectives for the final product

  • Evaluate iterative rounds on how they address those objectives

  • Recognize wild/weird tangents and either decide proactively to give them a chance, or cut them outright



  1. The Big Reveal


Professional creatives are often tempted by the Big Reveal without even knowing it. In this scenario the team, or a proactive individual, has a vision for what they want to do, and they try to progress all the way to the final draft before sharing their work. This process puts ALL of the pressure on the first review, and usually there is something fundamental the creative has missed. 


The revision process is not simply about improving the work; it is about improving our shared understanding of what needs to be done. It is a conversation carried out over iterations of the project and it moves us into alignment over time. The Big Reveal attempts to skip all that, and has about a 5% chance of success.


Avoiding the Big Reveal

  • Set the expectation for what a rough draft should try to accomplish

  • When faced with a rough draft, provide rough feedback

  • If the team is reluctant to share the work, they are anxious about how you’ll react. Be prepared to respond as a collaborator, not an approver



  1. The Wordsmith (AKA The Pixel Pusher)


This is a trap laid for a client/lead with an eye for the work, but lacking the technical skills and experience to do it themselves. The project starts off well enough, but after early feedback it descends into a series of changes that are too specific– move that  section over here, switch these colors, change the tense of that sentence. But the issue isn’t taste; its timing.


There is a time for refinements at this level, but it comes after all of the major decisions have been made. The client/lead in this scenario is using the creative as a tool for trial and error rather than relying on them as a professional to find solutions to the problem laid out in the project brief. This process doesn’t always necessarily waste time, but it does erode relationships, making projects more difficult in the future.


Catching the Pixel Pusher

  • Creative execution is about decisions

  • Creative leadership is about direction

  • Be clear from the outset which role each person is serving




  1. Be My Hands


When the client/lead does have the technical skills and experience to do it themselves, they risk getting dragged into the How instead of focusing on the What. Instead of micromanaging pixels, they micromanage possibilities—treating the team like an extension of their own ideation process. 


This process follows a similar pattern to the Pixel Pusher, but the instructions are more general: try one that’s high energy; give me a version that is clean and minimal. When this process is allowed to repeat itself too many times, you end up with a leader who can’t delegate, and the rationale that “it will be faster if I just do it myself.”


Freeing the Hands

  • Provide feedback that names the challenges you want solved, not the solutions you want implemented

  • Understand the finished product is not going to look the way it would if you’d created it yourself, but there is opportunity for it to reach its goals more successfully



  1. A Brief Setback


When the brief is unspecific, when there isn’t a clear picture of what we’re trying to accomplish with a project, the first round of work can feel way off base. Often we don’t know what we want until we see it done wrong. 


Writers are used to the concept of the “sh*tty first draft” and learn early to rebound and redirect. Designers too should be seasoned in critique by the time they’re working for you professionally. Although this misstep can get a project off to a bumpy start, it usually leads to a much more clearly articulated set of goals. If we can’t start with clear objectives, this is one way to get there fast, and shouldn’t be seen as a disaster, either by the client or the creative. 


Embracing the Setback

  • If the first round looks like a disaster, usually the Ask wasn’t clear

  • Make it clear that this iteration is going in the wrong direction

  • Revisit the objectives in light of what we now know Wrong to look like


The common thread in all of these patterns is not talent, taste, or effort—it’s the mental model we bring to collaboration. When we treat creative work like an assembly line, we expect certainty at the outset, linear progress, and efficiency through handoffs. That model works when the goal is consistency and scale. It breaks down when the goal is understanding. Iteration isn’t a sign that something is wrong; it’s the mechanism by which groups come into focus together.


When drafts are treated as lenses rather than candidates for approval as-is, the work becomes a shared act of calibration. Each round sharpens the picture, not just of the artifact, but of the problem it’s meant to solve. Teams that understand this stop asking whether something is “done” and start asking whether it’s clear. And clarity—once it’s reached—turns out to be the only thing worth producing at the end of the line.



 
 
 

Recent Posts

See All

Comments


© 2025 by JUSTIN COYNE | ENAMEL MEDIA

bottom of page