How to Get Feedback on Project Briefs

In the first edition of my newsletter, I shared the concept of "sharing before ready" and how it helped me prep for board meetings. Here’s a glimpse: I had the privilege of working for Max Yoder at Lessonly, where he wrote the book Do Better Work, which is required reading for me annually. One of the chapters, "Share Before Ready," is a value I’ve applied repeatedly, especially for board meetings and complex projects. What does "share before ready" mean? From Do Better Work (pages 18-19): "When what’s getting done matches what’s needed… Communicating more is the surest way to do that. When we shorten feedback loops, allowing others to preview and inform what we’re working on, we increase our odds of ending up with gold.” Do you want gold? I know I do. Unfortunately, when I decide to power through and silo my work, or deliver a polished, finished product without feedback…I deliver bullsh#t. This hasn’t been more true than when I started at Jellyfish and prepared for my first board meetings. Long story short, I was delivering sh#t, not gold. The reason? I wasn’t sharing before ready. Thanks to Andrew Lau, who introduced a "share before ready" who has implemented our version of share before ready, called red teaming, where part of the executive team plays the role of a board member, asking hard questions and poking holes in your story. My first red team board decks were brutal. But I realized they were just another version of sharing before ready, and now, I welcome the red team process. Steps to Share Before Ready 1. Outline Ideas: Spend 30-45 minutes drafting a rough outline. What message are you trying to convey? I start with a Google Doc filled with initial themes and talk tracks. 2. Get Initial Feedback: Seek early feedback from your CEO or manager to confirm your direction. From Max: “Find people who’ll benefit from your project’s success, respect you enough to challenge your ideas, and have time to help.” 3. Build First Draft: Use the feedback to create a skeleton draft of your section. For me, this includes main points and supporting data. 4. Red Team First Draft: Bring in your CEO, manager, or peers. I often include our sales leader, CEO, and co-founder. Ask them to challenge your data and assumptions. 5. Build Second Draft: Using first-round feedback, build out the first formal draft with more details and data. 6. Red Team Second Draft: Add fresh eyes to the second red team by involving additional peers. 7. Rinse and Repeat: Continue refining with red teams until your board meeting section or project is fully prepared. Preparing for board meetings (or pushing major projects forward) is challenging and daunting, but sharing before ready allows growth and nailing the board meeting! Involve your team early on and challenge yourself; you will thank me later.

Try this strategy to get better feedback from your team Picture this: You just spent 15 minutes of a group meeting reviewing your plans for an upcoming project. You painstakingly walked through each detail, key opportunities, potential roadblocks, and next steps. You brought this group together to help provide feedback. But now you’re now staring at a room (or a Zoom screen) of completely silent colleagues. “What feedback do you have?” you ask. A few shrugs. A half-hearted “Looks good.” And…nothing. I’ve been there. Want to get better feedback on your ideas from your team? Try this simple shift: Instead of asking, “Any feedback?”, reframe it to: “What’s missing?” Why this works: ✅ It signals your idea isn’t final and there’s room for their input. ✅ It makes team members feel more comfortable pointing out gaps or concerns. ✅ It invites collaboration rather than approval. ✅ increases buy-in. Because when people contribute, they commit to the idea. This strategy is especially valuable when developing new strategies, launching a program, or preparing for a big presentation. The best ideas are built together. When will you use the “What’s missing” strategy this week? Try it, and message me to let me know how it goes. I’d love to hear!

Most researchers don’t get bad feedback. They ask for it badly. They spend weeks perfecting their grant… then scramble for last-minute comments with a vague “let me know what you think.” I’ve done this too. But great feedback isn’t luck—it’s a system. Here’s what I follow every time: 1️⃣ Start early. Be specific. Don’t send your full draft with a vague ask. Break it into 3 feedback stages: Concept → Is the idea clear and compelling? Scientific merit → Are the aims rigorous and feasible? Writing → Is this persuasive and easy to follow? Each type solves a different problem. Don’t blur them. Example: Instead of “thoughts?”, ask: “Can you assess whether the aims match the outcomes?” Small shift. Big difference. 2️⃣ Choose reviewers like a casting director One person ≠ all feedback. Be intentional: Scientist → Review your Approach Detail person → Check writing flow Newcomer → Read Aims for clarity You, as PI, need fresh eyes too. Step back. Re-read later. You’ll catch more than you expect. 3️⃣ Give context and constraints Don’t just send a Word doc and hope. Frame the ask: What feedback do you need? What’s your deadline? What sections to focus on? How much time will it take? Example: “I’m sharing my Specific Aims. Can you check if the aims are clear, significant, and linked to outcomes? I’d appreciate it by next Friday.” Clear input = clear feedback. This system changed everything for me. Feedback is no longer a black box—it’s part of the process. How do you approach feedback on grants or proposals? --- P.S. Join my inner circle of 6000+ researchers for exclusive, actionable advice you won’t find anywhere else HERE: https://lnkd.in/e39x8W_P BONUS: When you subscribe, you instantly unlock my Research Idea GPT and Manuscript Outline Blueprint. Please reshare 🔄 if you got some value out of this...