Hey 🙂
There’s something I’ve noticed about getting feedback from my team.
When I send a draft in a Google Doc, I get slow feedback. When I send something that looks close to the finished thing, I get fast feedback.
I don’t have science to back this up, but my working theory is that a Google Doc feels unfinished. It doesn’t feel urgent. It’s a wall of text that asks people to read line by line and imagine what it could become. Most people aren’t good at that — and honestly, why should they be? That’s your job as the person building the thing.
A landing page in a Google Doc is not a landing page. It’s words. And words without context are hard to respond to.
Here’s what I’ve started doing instead. After Julia and I spent ninety minutes today going from zero to a topic and draft copy for our next online masterclass, rather than dropping the copy into a shared doc and waiting for replies, I asked Claude to turn it into an HTML mock-up based on an existing page we’d done before. Then I dropped the HTML file into Netlify, which hosts it instantly and gives me a real URL. The team clicks a link, sees something that looks and feels like a web page, and I get feedback the same day.
I did the same thing with our Q1 NPS survey results. Instead of sharing a Google Sheet full of rows and columns, I had Claude produce a two-page PDF summary. Clean, branded, readable, done. People actually read it, and loved it!
The point is to not let the presentation of a thing become the reason people don’t engage with it.
If you want faster, better feedback from your team, make the thing look as real as you possibly can before you send it. AI tools make that surprisingly easy now.
What information or data are you currently sending to your team for feedback? Experiment with Claude and see how quickly you can make it more visually compelling.
🗣️ 👀
Chris.