The Six-Month Email Chain vs. The Hallway Conversation
Let me tell you about two feedback experiences that couldn’t be more different.
The Corporate Saga:
Picture this—it’s my last corporate job, and we need to change our product packaging. Sounds simple, right? Wrong.
First, I draft a proposal. Then it goes to my manager. She adds comments and sends it to her director. He schedules a meeting with the US leadership team. We debate for three weeks and finally agree on an approach.
Now comes the fun part: We need consensus from our Japan office.
The proposal gets translated. We schedule a call, but there’s a 13-hour time difference, so someone’s always exhausted. The first meeting is mostly introductions and context-setting. The second meeting, they have questions—thoughtful questions that require data we didn’t include. Back to the drawing board.
We revise the proposal. Legal reviews it. Finance adds their perspective. We send the updated version to Japan. They schedule internal discussions. Three weeks later, we get feedback through email: “We appreciate the thorough analysis. However, we have concerns about the impact on our distribution partners.”
More revisions. Another round of meetings. Someone in Tokyo raises a valid point about regulatory compliance we hadn’t considered. The US team reconvenes. We loop in Regulatory Affairs. They need two weeks to research.
Fast forward nearly two quarters—yes, SIX MONTHS—and we finally get approval to change the packaging. By then, our competitor has already launched their new design, and honestly, I’ve forgotten why I was so passionate about this change in the first place.
The feedback wasn’t bad. Everyone was professional, thoughtful even. But it was so… distant. So filtered. By the time feedback reached me, it had passed through so many layers that it felt like a game of telephone played across continents.
The Trevean Spice Reality:
Now compare that to last Tuesday at Trevean Spice.
I’m literally pulling sample bags of our new turmeric blend when Alex, our head of operations, walks by. She picks up a bag, looks at it, and says:
“Hey, this label looks great, but I’m worried about the resealable zipper. Our fulfillment partner mentioned these specific ones jam up on their packaging line like 20% of the time. Can we switch to the side-seal version? It’s the same cost.”
I think for maybe ten seconds. “Yeah, you’re right. How fast can we make that change?”
“I can email the supplier right now. We’ll have samples by Friday.”
“Do it.”
Total elapsed time: 90 seconds. Problem identified. Solution proposed. Decision made. Action taken.
That’s startup feedback in its purest form.
Why Everything’s Different When You’re Small
Here’s the thing nobody tells you about startups: You’re never NOT giving feedback.
In that corporate job, feedback was contained in scheduled reviews, formal presentations, carefully worded emails. There were protocols. There were channels. There were people whose entire job was to facilitate feedback (hi, HR!).
At Trevean Spice, we’re eight people in a shared workspace. When I’m frustrated, everyone knows. When something’s working, everyone sees it. When someone’s stuck, we all hear the sighs.
This proximity is simultaneously our superpower and our biggest challenge. There’s no buffer. No filter. No time to carefully craft your message. It’s raw and real and happening constantly.
The question isn’t whether we’re giving feedback—we’re drowning in it. The question is whether that feedback is actually helping us build something or just creating noise.
The Framework That Saved Our Sanity
Let me be real with you: For our first few months, our feedback “system” was basically chaos.
Someone would say, “I feel like we’re not moving fast enough,” and we’d all nod seriously, and then… nothing would change. Or worse, everything would change—we’d pivot our entire strategy based on one frustrated comment made during a stressful week.
We needed structure, but not the kind of corporate structure that would slow us down. We needed something that matched our pace.
Enter what I now call the GAIN framework. It’s not revolutionary, but it works: Goal-oriented, Action-focused, Impact-driven, Next steps.
Let me show you how this actually plays out in real life.
Goal-Oriented: When “We’re Not Aligned” Actually Means Something
The old way (that didn’t work):
Me, stressed during a Monday morning: “I feel like we’re not aligned on the product direction.”
Everyone stares. Someone says, “What do you mean?” I say, “I don’t know, just… feels off.” Meeting ends with vague promises to “sync up more.”
The GAIN way:
Now it sounds like this:
Me: “Our goal this quarter is landing three wholesale accounts by month-end—that’s how we prove our unit economics to investors. But in yesterday’s sales call with that boutique grocery chain, you pitched our subscription boxes while I was talking about bulk wholesale. The buyer asked which business model we’re actually pursuing, and we gave different answers. Before the next call, let’s get on the same page: Are we positioning as wholesale suppliers or direct-to-consumer subscription?”
See the difference?
The feedback is connected to a concrete goal (land wholesale accounts), references a specific situation (yesterday’s call), and ends with an actual question that needs answering.
The magic here is that everyone knows our quarterly goals. They’re on our Notion board. We reference them constantly. So when I say “our goal is landing three wholesale accounts,” nobody needs convincing—we all agreed to that goal two months ago.
The transparency piece:
This only works because we’re obsessive about keeping goals visible and current. In my corporate life, strategy decks got presented in Q1 and then… who knows if they were still relevant by Q3?
At Trevean Spice e, we have a literal whiteboard that says “THIS MONTH’S PRIORITY” in all caps. When it changes—and it does change, because we’re a startup and things move fast—we gather everyone, explain why, and update the board.
Last month, our priority was “ship the cinnamon-cardamom blend.” This month it’s “land three wholesale accounts.” Everyone knows. Nobody’s confused.
Action-Focused: Stop Telling Me How You Feel, Tell Me What You Saw
This one was hard for me to learn because I’m naturally a “feelings” person. I’m an intuitive communicator. In my personal life, that works great. In a startup? It’s a disaster.
The thing that didn’t work:
After a rough week, I told our team: “I feel like communication could be better.”
They all agreed! Everyone nodded. We all committed to “communicating better.”
Nothing changed.
Why? Because “communication could be better” could mean literally anything. More Slack messages? Fewer Slack messages? More meetings? Less meetings? Earlier responses? More detailed responses?
What actually works:
Last month, we had a real issue. Our designer, Jamie, and our marketing lead, David, kept creating conflicting content.
The old me would have said, “You two need to communicate better.”
The new me said this:
“Yesterday, Jamie posted Instagram stories featuring our Morocco blend’s earthy, traditional aesthetic—the terracotta colors, the handwritten origin story. The same day, David sent an email campaign positioning the same blend as ‘modern exotic spice innovation’ with bright, contemporary graphics. A customer replied asking if these were different products. Before we post anything about the Tunisia blend launching next week, can you two sync on the positioning? Let’s decide: Are we ‘preserving tradition’ or ‘modernizing spice culture’? We can’t be both in the same week for the same product.”
Specific behavior: Two pieces of content, posted same day, conflicting messages.
Observable effect: Customer confusion, asking if they’re different products.
No feelings. No vague “we’re not aligned.” Just: This happened, it caused this problem, here’s what we need to do about it.
Why this works when you’re small:
In a big company, you might say “our messaging isn’t consistent across channels” and schedule a three-month brand alignment initiative.
We don’t have three months. We have a Tunisia blend launching next week.
Specificity gives us something we can fix TODAY. Jamie and David literally walked over to the corner, talked for ten minutes, decided we’re going with “preserving tradition,” and updated the Tunisia content. Done.
Impact-Driven: The Art of Not Catastrophizing (It’s Harder Than It Sounds)
Okay, confession time: When you’re bootstrapping a startup with your own savings, every mistake feels existential.
When Jamie missed the design deadline for our rebrand, my internal monologue was: “We’re going to lose the wholesale deal. The investor will back out. We’ll run out of money. I’ll have to move back to my parents’ house. Everyone will know I failed.”
What I almost said: “This is killing us. We can’t afford mistakes like this.”
What I actually said (after taking a deep breath):
“When the packaging designs arrived Thursday afternoon for our Monday printer deadline, our production partner had to rush the setup over the weekend. Because they rushed, they miscalibrated the color settings—the turmeric yellow came out orange. We caught it, but fixing it added $800 to our printing costs and delayed our wholesale sample shipment by three days. The boutique we’re courting needs samples by Friday for their buyer meeting. For next time, can we set a Tuesday EOD deadline for designs? That gives production three full workdays and buffer for issues.”
Facts only:
- Designs came Thursday
- Printer rushed over weekend
- Color calibration error
- Cost: $800 extra
- Delay: 3 days
- Risk: Missing buyer meeting
No drama. No “you’re killing the company.” Just: Here’s what happened, here’s what it cost, here’s how we prevent it.
The flip side: Not minimizing either
I’ve also learned not to downplay real problems.
When our farmer partnership in Kerala fell through because we missed a payment deadline, my instinct was: “It’s fine, we’ll find another supplier.”
But it wasn’t fine. That partnership took four months to establish. The farmer had reserved crop specifically for us. Our “Kerala First Harvest” blend was already marketed. We had pre-orders.
The real impact: “Missing this payment deadline cost us our Kerala farmer partnership. We have 43 pre-orders for the Kerala blend with no product to fulfill. We’ll need to either refund them (losing $1,200 in revenue) or delay shipment by 6 weeks while we source alternative supply. Both options damage trust with early customers. Here’s what I’m going to do differently: Set up auto-pay for farmer partnerships and a calendar alert 5 days before each payment. Can you help me think through how to handle these customer refunds?”
Next Steps: Turning Complaints Into Commitments
This is where most feedback dies in startups. We’re so busy that we have intense conversations, agree something needs to change, and then… sprint back to our desks and forget about it.
The failure mode I see constantly:
“We need to improve our inventory system.”
“Yeah, definitely, let’s do that.”
[Two weeks later, nothing has changed]
The GAIN approach:
Last week, Alex (operations) raised concerns about inventory tracking. Here’s how that conversation actually ended:
Me: “Okay, so here’s what I’m hearing: We need a real inventory system, not just a Google Sheet. Alex, can you research 3 options by Wednesday—specifically focusing on ones that integrate with our Shopify and have mobile scanning? I want to see cost, setup time, and whether they handle lot numbers for freshness tracking. Wednesday afternoon, you and I will review them. Thursday, we’ll make a decision. If we pick something, I want it implemented before our Tunisia blend shipment next week. David, you’re not involved in this decision, but heads up—once we pick a system, you’ll need to scan products at fulfillment. Sound good?”
Accountability: Alex researches
Timeline: Wednesday review, Thursday decision, implemented before Tunisia shipment
Decision rights: Alex and I decide
Communication: David is informed
Success criteria: System handles Shopify integration, mobile scanning, lot numbers
Then—and this is crucial—I put it in our Monday meeting agenda for next week: “Inventory system: Implementation check-in.”
If we didn’t implement it, I’m going to ask why. Not in an accusatory way, but in a “what got in the way, how do we unblock it” way.
The transparency requirement:
This only works if we actually track commitments. We use Notion. It’s public. Everyone can see who committed to what.
When someone misses a commitment, it’s visible. And that visibility creates accountability without me having to be the bad guy.
Last month, I committed to reaching out to five wholesale leads by Friday. Friday came. I’d reached out to two. In our Monday meeting, it was right there: “Wholesale outreach: 2/5 completed.”
I owned it: “I didn’t hit this. Got pulled into fixing the website bug. This week, I’m doing the other three first thing Monday, and I’m blocking my calendar so it actually happens.”
No shame. No excuses. Just: Here’s what happened, here’s the fix.
When Feedback Isn’t Enough: Strategic Disagreements
Here’s where it gets real. Sometimes feedback reveals something deeper than execution issues. Sometimes it reveals that people fundamentally disagree about what we should be building.
This happened to us two months ago.
The surface issue:
David (marketing) kept deprioritizing content for our wholesale pitch deck. We’d agree he’d draft slides, deadline would come, he’d say “didn’t get to it, was working on Instagram content.”
My initial feedback attempt:
“Hey, we agreed wholesale pitch deck was priority. What’s blocking you?”
His response:
“Honestly? I don’t think we should be chasing wholesale. Our brand is built on direct relationships with customers. Wholesale dilutes that. We become just another product on a shelf. I’ve been putting it off because I don’t believe in it.”
Oh.
That’s not a feedback problem. That’s a strategic disagreement.
The corporate approach:
At my old job, this would’ve been escalated. I’d talk to my manager. She’d talk to David’s manager. We’d have a cross-functional meeting. HR might get involved. Six weeks later, we’d have a compromise that nobody’s happy with.
The startup approach:
I said, “Okay, this is a real conversation. Let’s hash it out right now.”
We spent an hour talking. Here’s what I learned:
David wasn’t being lazy or difficult. He genuinely believed wholesale was the wrong strategy. His reasoning: We’d built 500 email subscribers who loved our origin stories and our direct relationship. Wholesale would make us compete on price with mass-market brands.
Fair point.
I shared my reasoning: Our email list is growing 15% monthly, which is great, but at that rate we won’t hit break-even for 18 months. Wholesale gives us volume to cover costs while we build the D2C audience.
Also fair.
The decision:
I said: “Here’s where I land. I hear your concerns, and they’re valid. But I’m the one accountable to our investors, and I’m the one who has to make payroll. We’re doing wholesale. That doesn’t mean we’re abandoning D2C—we’re doing both. If wholesale doesn’t work after six months, we’ll revisit. But for right now, I need you to execute on this even though you’re not convinced. Can you do that?”
He thought for a minute. “Yeah, I can. I still think it’s risky, but I get why you’re making the call. Just promise me we’re not going to abandon what made us special.”
“I promise. And if you ever feel like we’re losing our soul chasing volume, you tell me immediately.”
Why this worked:
- I acknowledged the real disagreement instead of pretending it was about execution
- I made the final call clearly (this is my decision, here’s why)
- I gave context (investor expectations, runway, payroll)
- I invited ongoing feedback (tell me if we’re losing our soul)
- He had the option to leave (unstated, but we both knew—if he couldn’t execute on this, he could quit)
He stayed. Wholesale is working. He’s executing well. We revisit the strategy monthly—not to relitigate the decision, but to check: Is this still working? Are we maintaining our brand identity?
The transparency piece:
After that conversation, I told the whole team: “David and I had a good conversation about wholesale strategy. There was disagreement, which is healthy. We’ve decided to pursue wholesale for the next six months while continuing to build D2C. If anyone else has concerns about our direction, now’s the time. And if strategic questions come up, we’ll address them in our monthly strategy check-ins.”
Nobody else had major concerns. But by being transparent about the disagreement and decision, I sent a message: It’s okay to question strategy. It’s not okay to quietly resist execution.
Building Feedback Into the Rhythm of Work
The biggest difference between corporate and startup feedback? In corporate, feedback is an event. Annual review. Quarterly check-in. Performance improvement plan.
At Trevean Spice, feedback is ambient. It’s happening constantly. So, we need structures that make it productive instead of chaotic.
Our rhythm:
Every morning, 9:15 AM (10 minutes max):
- What did you finish yesterday?
- What are you doing today?
- What’s blocking you?
That last question is gold. “What’s blocking you?” is a lightweight feedback mechanism.
Yesterday, Alex said: “Blocked on sourcing cinnamon sticks—our supplier is out, and I don’t know who else to call.”
I said: “I have a contact in Sri Lanka from my old job. Let me intro you.”
Problem identified and solved in 30 seconds. In a corporate environment, that might’ve been three email threads and a meeting.
Every Friday, 4 PM (30 minutes):
Retrospective. Three questions:
- What went well this week?
- What could be better?
- What’s ONE thing we’ll change next week?
That ONE thing is critical. We used to leave retros with five action items. Nothing changed because everyone’s already swamped. Now we pick ONE thing. Last week it was: “Respond to customer emails within 4 hours.” Everyone can do one thing.
First Monday of each month (2 hours):
Strategy check-in. Questions:
- Are we still pursuing the right goals?
- What have we learned from customers?
- What needs to change?
This is where strategic feedback happens. This is where someone can say, “I think our pricing is wrong” or “I think we should kill the gift box offering” and we actually debate it.
Outside this meeting, we’ve agreed: Unless it’s urgent, strategic questions wait. We can’t relitigate our entire strategy every week.
This structure does something important: It separates tactical feedback (daily standups), process feedback (weekly retros), and strategic feedback (monthly reviews).
In my corporate job, everything was strategic-level serious. Moving a button on the website required the same level of process as changing our go-to-market strategy.
At Trevean Spice, moving a button happens in Slack in five minutes. Changing our go-to-market strategy happens in a planned meeting with prep time.
When Feedback Culture Breaks
Even with good systems, things can go wrong. Here are the red flags I watch for:
Red flag 1: People only complain to me privately
If Jamie keeps texting me about David’s marketing decisions, but she never says anything in our Friday retro, we have a problem.
This happened last month. I finally said, “Jamie, you’ve mentioned this concern to me three times. Either raise it in Friday’s retro where David can respond, or I’m going to assume it’s not actually a problem.”
She raised it. David explained his reasoning. She said, “Oh, that makes sense, I didn’t realize that.” Done.
Red flag 2: I’m getting defensive
The fastest way to kill feedback culture is to ask for feedback and then explain why everyone’s wrong.
I caught myself doing this two weeks ago. Alex suggested we change our subscription pricing. My immediate response: “We researched pricing extensively, that won’t work.”
I literally watched her face close down.
I caught myself: “Wait, sorry. Tell me more about why you think we should change pricing. I’m listening.”
She explained: Three customers this week said they wanted to subscribe but couldn’t justify $45/month. They’d pay $30 for a smaller box.
That’s… actually useful data I didn’t have.
Me being defensive nearly prevented me from learning something important.
Red flag 3: Every decision becomes a debate
This is the flip side. If we debate every tiny decision, we’ll never ship anything.
Last week, we spent 20 minutes debating Instagram caption length. Twenty minutes. For captions that 50 people will see.
I finally said: “David, you own social media. Write the captions however you think is best. If engagement drops, we’ll revisit. But I’m not spending 20 minutes on this.”
The balance: Big decisions deserve debate. Small decisions need an owner who makes the call.
How do you know the difference? I use the “reversible vs. irreversible” test:
- Irreversible: Farmer contracts, pricing strategy, wholesale partnerships → Debate thoroughly
- Reversible: Instagram captions, email subject lines, blog post topics → Empower someone to decide
Anchoring to Vision When Everything’s Chaotic
Here’s the real secret to making feedback work at a startup: You need a North Star.
At Trevean Spice, our vision is: “Connecting home cooks to the origin stories of their food.”
When feedback conflicts arise, we return to this.
Example:
Jamie wanted to add a complex “blend customizer” tool where customers could adjust ratios of spices in our mixes. It would take six weeks to build.
I used the vision test:
“Does this tool connect customers to origin stories? Or does it make the product more complex?”
We discussed. Conclusion: It makes it more complex without deepening the story connection. We’re building it eventually, but it’s not aligned with our current vision priority.
Jamie wasn’t thrilled, but she got it. The vision isn’t “make the most customizable spice company.” It’s “connect people to stories.” The customizer doesn’t serve that.
When vision changes:
Last month, we had real debate about this. David suggested we pivot from “origin stories” to “sustainable sourcing.”
His reasoning: Every customer call mentions sustainability. Nobody asks about origin stories unprompted.
This was important enough to take seriously. We spent our entire monthly strategy meeting on it.
I asked the team: “If we change our vision to focus on sustainability, who’s still in? Be honest.”
Everyone was in. But we landed on something nuanced: “Connecting home cooks to the origin stories and sustainable practices behind their food.”
We updated the vision. We updated our website. We updated our pitch deck.
And I said explicitly: “If this fundamental change doesn’t sit right with anyone, I respect that. This might not be the company you signed up for anymore.”
Everyone stayed. But I needed to give them that out. When vision changes, people deserve the choice to leave.
The Bottom Line
Corporate feedback: Six months, four departments, three time zones, perfect documentation, zero urgency.
Startup feedback: Six minutes, four people, one room, messy notes, total urgency.
Neither is better or worse. They’re optimized for different games.
But if you’re at a startup trying to use corporate feedback systems, you’re going to lose. You’ll have perfect 360-degree reviews while your competitor ships product.
And if you’re at a startup with NO feedback system, you’re also going to lose. You’ll move fast but in random directions, burning out your team and losing your best people.
The GAIN framework—Goal, Action, Impact, Next steps—gives you structure without slowing you down.
But frameworks are just tools. The real work is cultural:
Transparency: Share the constraints, the trade-offs, the reasoning.
Trust: Assume feedback comes from good intent.
Accountability: Track commitments and acknowledge misses.
Alignment: Keep the vision visible and current.
Last week, I asked our team: “What’s the best part of working here?”
Alex said: “I always know what’s happening and why. Even when decisions are hard, I’m never confused about where we’re going.”
That’s it. That’s the whole game.
Not comfort. Not consensus. Not perfect processes.
Clarity. Speed. Shared direction.
And feedback that actually helps us build something worth building.

Leave a comment