Inconsistent Feedback Loops
Similar to a lot of companies and teams, clunky processes and feedback loops plagued Headway and its clients with a mix-and-match clutter of emails, PDFs, screenshots and more. It was enough to make their collective heads spin, and all but stop projects along the way.
Gathering all the feedback in one location was an enormous task, often filled with back-and-forth Slack, emails, texts and conversation. And that was just one piece. Gathering all the information without missing any vitals details, comments, suggestion or feedback was another. Especially if or when the feedback contradicted each other.
We sat down virtually with Senior Designer Breanna Clemens, Developer Matt Mcgee, Designer Sam Pecard, Partner & CTO Jon Kinney, Developer Jake Hebert and Partner & CEO Andrew Verboncouer to discuss how Punchlist has changed the feedback game for good.
And their responses? Well, they may just surprise you.
How did you typically gather feedback before Punchlist?
Breanna’s response is a familiar one. “Previously, I would take screenshots and drop them in a shared document with my comments,” she said.
Matt chimed in: “On one particular project, the team was just using email along with Word documents and screenshots to provide feedback.”
Designer Sam mentioned “grabbing full-page screenshots and bringing them into Figma or creating lists in task cards within Asana,” a loathsome task all too familiar for the designers in the group.
Jon Kinney, Partner & CTO, chimed in next. He noted he spent time creating cards in project management tools like Jira, Github issues, Pivotal Tracker, Asana, etc, while Jake, a Headway developer, wishes he could use those tools.
Instead, “our clients would often create Google sheets or just filter feedback in Slack,” Jake said. “It was always a lot of overhead.”
Partner & CEO Andrew felt the pain of requesting feedback in one way, but receiving it in another.
“We would request feedback in our design tools,” he said, “but they were always out of date with the current copy and images, so it was confusing. We'd also get it in Notion or other word docs, but felt disconnected.”
Confusion. Disconnection. Not exactly the experience Headway wanted for their team or their clients.
Thankfully, this wasn’t the end of the story.