Skip to content
Floskool

Chapter 1 · The resource

Organize feedback and approvals

Free lesson 8 minGroup Flopilot

Follow this course in your space: your progress is saved, and the community answers your questions.

Follow for free

Feedback is where a project that started well can get stuck. A comment by text, another by email, a third from the business partner who hadn't seen anything until now, then "actually, let's go back to the first version." None of this is bad faith. It's the lack of ground rules.

Those rules fit in six points, to announce at kickoff.

1. One channel

Pick one place for feedback, and only one: a single email thread, the shared folder, or the comments in a project tool. If feedback arrives somewhere else, copy it into the right channel and reply there.

Thanks for your message! I'm copying it into [the channel] so we keep
all the feedback in one place, and I'll reply there.

2. One decision-maker

On the client side, one person approves. Others can share their opinion, but with that person, who then sends you a single, settled list. Ask during the kickoff call: "Who has the final say?"

  • Web agency client: the owner approves, not each of the five employees.
  • Nonprofit: the board chair or the person the board designates, not every volunteer.
  • Wedding photographer: the couple, not both families.

3. A set number of feedback rounds

Write in the scope how many rounds are included (two is common). One round means: you send a version, the client sends back a list of feedback, you make the changes. Beyond that, it's an extra request (see the previous lesson).

Name the round every time you send something:

Here's version 2 (feedback round 2 of 2).
Please send me all your feedback by [date], in one message.

4. Feedback grouped in one go

One comment a day for two weeks is two weeks lost. Ask for a single list, with a deadline. Give a template to help:

FEEDBACK: [project name], version [n]
Sent by: [name]    On: [date]

1. Where: [page, slide, photo #, room]
   What's wrong: [description]
   What you'd like: [description]

2. Where:
   What's wrong:
   What you'd like:

5. Written approval

"Looks good" on the phone isn't an approval. Ask for a written sentence, even a short one:

So we can move on to the next step, could you confirm in writing
that version [n] is approved? A simple "Approved" in reply is enough.

File that reply with the project. If someone revisits a choice three weeks later, you know where the decision stood.

6. Reporting a bug with an annotated screenshot

For a website, an app or a document, "it doesn't work" isn't enough to fix anything. A good bug report answers three questions:

  • Where: the page address, the screen, the slide number, and on which device (phone, computer).
  • What: what happens, with an annotated screenshot (a box or an arrow on the problem).
  • Expected: what should have happened.
BUG REPORT
Where: [page / screen], on [phone or computer, browser]
What: [what happens] (screenshot attached, problem circled)
Expected: [what should have happened]

Example: "Where: Contact page, on iPhone. What: the Send button is hidden under the footer (screenshot, circled in red). Expected: the button visible below the form."

Some project tools let you paste a screenshot and mark it up right there. In Flopilot, that's the "Report / suggest" button: you choose bug, change or idea, paste the screenshot, add a box, an arrow or some text, and it becomes a task. Without a tool, your phone's screenshot editor does the job just fine.

Feedback checklist

  • The feedback channel is announced at kickoff
  • The client's decision-maker is named
  • The number of rounds is written in the scope
  • Each delivery states the round number and a deadline
  • Feedback arrives as a single list
  • Each stage is approved in writing
  • Bugs are reported with where, what, expected

Your turn

Write the "How we handle feedback" paragraph you'll add to your next kickoff message: channel, decision-maker, number of rounds, time to reply. Five lines max. Then save the feedback template and the bug report template in your templates folder.