Skip to content

How We Ask for Feedback at Causify

TL;DR

Feedback can be toxic; clarity and kindness are the antidotes to frustration and wasted time.

Asking for feedback can feel awkward, and giving it can be just as uncomfortable.

In many companies, the feedback process can devolve into struggles over punctuation or vague critiques that don't provide real value. Conversely, receiving requests for feedback often means wading through poorly constructed documents or hastily generated AI content, combined with unrealistic deadlines.

This leads to frustration, wasted time, and the final product often suffers as a result. Eventually, the cycle discourages both asking for and giving feedback altogether.

How We Ask for Feedback at Causify

At Causify, we implement straightforward, polite, and effective guidelines that make feedback constructive rather than painful.

How to Ask for Feedback#

  • Be clear about what you need.

    • Is it an early draft? A work-in-progress? Or just a sanity check on a near-final piece? Spell it out.

  • Clarify the review's requirement level.

    • Is feedback optional or mandatory? Let people know what you want—don't leave them guessing.

  • Set realistic deadlines.

    • Everyone's juggling their own tasks, so don't ask for feedback on a draft you sent 10 minutes ago.

  • Avoid sending AI-generated content as is.

    • Sure, we all want to leverage AI, but it shouldn't replace your own quality. No one wants to sift through a novel of AI ramblings. Either summarize or share the prompts you used.

  • Utilize LLMs effectively.

    • Conduct initial revisions using prompts that invite meaningful changes, like:
      • "Suggest improvements and corrections."
      • "Rewrite concisely using bullet points."
    • Steer clear of excessive emojis, em dashes, and decorative elements; they signal to others that the content may lack genuine effort.

  • Become proficient with Google Docs.

    • It's a tool, not a mystery box. Use it to format correctly and organize efficiently. Don't let your document look like a toddler went to town with crayons.

How to Give Feedback#

  • Be kind.

    • Even if you think the draft is a catastrophe, couch your critiques in kindness; aim for collaboration, not demolition.

  • Skip performative feedback.

    • If you're only suggesting changes to seem engaged, just don't. Focus on what genuinely improves the work.

  • Disagree respectfully.

    • For minor issues, preface your comments with "Nit:" or "Typo:". If it's major, say so without sounding like a bulldozer.

  • Prioritize the big picture.

    • Look at the content and ideas, not just the nitty-gritty grammar stuff—let AI handle that.

  • Make feedback actionable.

    • Instead of throwing out vague phrases like "make it pop," offer something specific, like "can you clarify the key takeaway?"

The 4 Levels of Feedback#

We've broken down feedback requests into four levels. Why? Because context matters:

  1. FYI

    • No review needed, but feedback is appreciated.
    • Example: "Here's a quick look at how we reorganized the company documents."

  2. Review-the-Draft

    • Aim: Direction check.
    • Example: "Here's the rough outline of the tech roadmap. Does it make sense?"

  3. Review-and-Improve

    • Aim: Enhance a draft.
    • Example: "Here's a draft that's outside my expertise. Please strengthen the technical aspects while keeping the style."

  4. Review-and-Approve

    • Aim: Final check before publication.
    • Example: "This SOP is ready for publication. Please give it a close look for accuracy. If all good, I'll move forward."

Mechanics#

  • If using Google Docs:

    • Always use Suggesting mode for edits. That way, team members can see changes without going rogue.
    • Use comments to provide context or clarifications—just hit Insert > Comment, and tag team members with @XYZ.
    • Remember, the document owner still has the final say—they're the one whose name is on it.

  • Add tasks to team members' TODO lists.

    • Keep it organized. Create a review task in Asana that includes:
      • A clear link to the document.
      • Specify the type of review required (draft, improve, approve).
      • A realistic deadline.