Let me tell you about the moment I realized I’d burned two weeks of my team’s time with a single sentence.
We were heads-down on the core bet for Trevean Spice—getting NFC-enabled packaging to actually work. Clear goal. Clear timeline. Whole team aligned.
Or so I thought.
Then I had lunch with a friend who runs a boutique grocery store. Somewhere between the appetizers and the check, she mentioned that holiday gift boxes were her biggest sellers in Q4. “You should totally do a gift set,” she said. “People love that stuff.”
Good intel. Filed it away. Mentioned it at our next team call: “Something to think about—gift boxes could be huge for the holidays.”
That was it. No action item. No timeline. Just a stray thought I wanted to share.
Fast forward two weeks.
I’m asking my co-founder about the NFC adhesive tests we were supposed to run. She looks confused. “I thought we were pivoting to gift packaging—I’ve been researching box suppliers and bundle pricing.”
Ten days of her time. Gone.
And here’s the part that really stung: our designer had also heard my comment. He’d started mocking up gift box layouts instead of finishing the label designs we actually needed.
Nobody made a conscious decision to change the plan. I never told anyone to stop working on NFC. But I also never said “keep going.” I’d assumed the context was obvious.
It wasn’t.
“You have enough ideas to destroy Amazon”
A few months ago, Jeff Bezos told a story at Italian Tech Week that stopped me cold.
In Amazon’s early years, one of his executives—Jeff Wilke, a manufacturing guy who’d eventually run Amazon Worldwide Consumer—pulled him aside with a warning most founders never want to hear.
“Jeff, you have enough ideas to destroy Amazon.”
Bezos described himself as someone who could stand in front of a whiteboard and generate a hundred ideas in half an hour. He thought this was his superpower.
Wilke saw it differently.
“This was such a shocking idea for me,” Bezos admitted.
When he asked what Wilke meant, the answer was blunt: “You have to release the work at the right rate so that the organization can accept it. Every time you release an idea, you’re creating a backlog, a queue, work in process. It’s adding no value, and in fact, it’s creating a distraction.”
That reframe changed how Bezos led Amazon. He started keeping lists of ideas. He started holding ideas back until the organization was ready. He learned that even brilliant ideas become liabilities if you release them faster than your team can absorb.
Here’s the thing that hit me: Bezos had thousands of employees when he learned this lesson.
I have three people working on Trevean Spice.
The math is even more brutal at our scale.
Context decays faster than you think.
In a bigger company, if you mention something once and don’t follow up, it gets buried. There’s so much noise—Slack channels, all-hands meetings, project trackers—that one stray comment fades into the background.
In a five-person startup? There is no background.
Everything you say lands.
I tested this accidentally a few weeks ago. On a Tuesday, I mentioned to my co-founder that I’d been thinking about offering single-origin spices alongside our blends. Just thinking out loud. Didn’t even frame it as a possibility—more like “I wonder if…”
On Friday—three days later—she sent me a spreadsheet comparing sourcing costs for twelve single-origin options.
Three days. That’s how fast “just thinking” becomes “active project” when you’re one of three people setting direction.
The problem isn’t that small teams don’t listen. The problem is they’re listening too well.
Your enthusiasm, your offhand remarks, your “hmm, that’s interesting” reactions—that’s all the data they have about what matters. So when you express interest in something new, you’re not just sharing information. You’re adjusting the priority stack.
And unless you explicitly clarify, your team will fill in the gaps with their best guess.
The trap I keep almost falling into
Here’s where I get myself in trouble over and over: I genuinely love ideas.
Put me in a room with a whiteboard—or honestly, just hand me a napkin and a pen at dinner—and I’ll sketch out possibilities for hours. Subscription boxes. AR experiences showing where our spices come from. A custom blend creator where customers can mix their own. Restaurant partnerships. Farmers’ market booths. A podcast interviewing spice farmers.
Every single one of these is a legitimately good idea. I could make a case for any of them.
And every single one of them would destroy Trevean Spice right now if I actually pursued it.
Because here’s the uncomfortable truth I keep having to relearn: we haven’t even proven the core bet yet.
The whole point of Trevean Spice is that NFC-enabled packaging creates a different kind of customer experience. Tap your phone, get origin stories, freshness data, recipes tailored to what you bought. That’s the thing that makes us different from the ten thousand other spice companies out there.
If I can’t prove that works—if customers don’t actually care about tapping their spice jars—then nothing else matters. Not the subscription boxes. Not the AR experiences. Not the podcast.
But man, those other ideas are fun to think about. And every time I mention one out loud, I’m implicitly telling my team to start thinking about it too.
Sound familiar?
The real tradeoff (and why it’s harder than it sounds)
Here’s the tension every early-stage founder faces:
You need to stay open to new opportunities. The whole point of being a startup is that you’re learning fast and adapting. If you’re completely closed off to new information, you’ll miss the pivot that saves you.
But you also need to maintain focus on existing commitments. Nothing ships if everyone’s chasing the latest shiny object.
The mistake—the one I keep making—is thinking you can hold both without active management.
If you never share new ideas, your team feels like they’re executing in a vacuum. They don’t know what you’re learning. They can’t help you think through possibilities. You become the bottleneck for every strategic insight.
If you share every interesting signal, you create noise. Your team can’t tell the difference between “this is the new direction” and “this is a random thought I had in the shower.” Every idea you mention becomes a task in their mental queue—and if they can’t absorb it, it doesn’t just sit there. It creates a distraction that degrades everything else.
There’s a third option. It took me embarrassingly long to figure it out.
The option I didn’t know I had: Hold it back
Here’s what I’ve started doing, and it felt weird at first.
When I have a new idea—a good one, the kind that makes me want to grab a whiteboard—I don’t mention it to my team anymore.
Instead, I write it down and let it sit.
I have a note on my phone called “Ideas I’m Not Sharing Yet.” (Creative, I know.) It’s got maybe forty items in it right now. Some of them are three months old. Most of them I’ve completely forgotten about until I scroll past them.
That’s the point.
If an idea is still interesting to me a month later, I revisit it. Still interesting at three months? Maybe it deserves real consideration. If it survives six months of sitting in a note while I’m focused on other things—while I’m actually doing the hard work of proving NFC packaging matters—then it’s probably real.
Most ideas don’t survive this test.
The gift box thing? I added it to my list back in October. By December, I’d realized that gift boxes are a completely different business—seasonal, retail-dependent, with low margins on packaging, and totally disconnected from our technology story. It was a good idea for a different company. Not for us. Not this year.
But I only figured that out because I didn’t unleash it on my team the moment I heard it.
I wrote about this a few weeks ago—the “12-Month Focus Test” and the “Not This Year” list. Turns out that list isn’t just a planning tool. It’s where ideas go to germinate instead of fragmenting my team’s attention.
Bezos figured this out, too. He started “keeping ideas to myself until the organization was ready for the ideas.”
That’s not withholding information. That’s respecting your team’s finite capacity to absorb and execute.
When you do share, add the sentence that feels redundant
Okay, but sometimes you do need to share something. You’ve had a conversation that genuinely affects the plan. You’ve learned something the team needs to know.
Here’s what I’ve started adding—a sentence that initially felt completely unnecessary:
“This doesn’t change what we’re working on right now.”
I know. Obvious, right? Of course,e we’re still focused on NFC—I just mentioned one interesting thing!
But here’s what I discovered: the sentence that feels redundant to you is the one that prevents drift for your team.
Last week, I got an email from a retail buyer at a specialty grocery chain. Actual interest. Real opportunity. The old me would have immediately shared this with the team as exciting news.
The new me paused. Thought about the downstream effects. Then sent this message:
“Got an interesting email from a buyer at [chain]. They want to talk about carrying our products. I’m going to take the call to learn what they’re looking for, but this doesn’t change our focus—we’re still proving DTC before we think about retail. Just wanted you to know it’s on my radar.”
See the difference?
Same information. Completely different signals about what the team should do with it.
The call I take, I hold. The learning I get, I keep to myself until it’s actually relevant. My team stays focused on NFC and our Shopify launch. Nobody starts researching retail pricing or wholesale packaging.
Five seconds of clarification. Weeks of focus preserved.
The meeting that feels like a waste is the one you need
There’s another version of this problem, and I see it in myself constantly.
When you’re staring at a mountain of work—when the NFC adhesive tests are overdue, and the website copy isn’t done, and you’re supposed to be writing this blog post—the weekly sync feels like an interruption.
You know what everyone’s doing. They know what they’re doing. Why spend thirty minutes rehearsing the obvious?
I’ll tell you why: because it’s not obvious.
Two weeks ago, I almost skipped our Thursday call. We’d had a brutal week. Everyone seemed heads-down and productive. I figured we could skip it and get an extra hour of real work done.
I kept it anyway, mostly out of guilt.
Fifteen minutes in, I discovered that my co-founder thought our launch target was March. I thought it was February. We’d both been operating on our own assumptions for three weeks without realizing we had different dates in our heads.
If I’d skipped that sync, we’d have had a very unpleasant conversation sometime in mid-February when I started asking about launch readiness, and she looked at me like I was crazy.
The sync isn’t about status updates. It’s a recalibration checkpoint. It’s where you catch the fact that two people are working toward different goals before that gap becomes two weeks of rework.
The meeting that feels redundant is the one preventing expensive surprises.
The math that finally changed my behavior
Here’s the calculation that made this real for me:
- A fifteen-minute conversation to clarify that the gift box idea isn’t a priority: fifteen minutes
- A misalignment that runs unchecked for two weeks: two weeks of work, plus the emotional hit when someone realizes they’ve been building the wrong thing, plus the trust repair, plus the re-planning
I lost ten days to one sentence about gift boxes.
I almost lost three weeks to a one-month discrepancy in launch dates.
The math is brutal. And yet I keep underinvesting in communication because it doesn’t feel like “real work.” There’s no artifact at the end. No code committed. No supplier locked in. No label designed.
But here’s what I finally understand: keeping a small team aligned is the work.
Not overhead. Not a distraction from execution. The actual infrastructure that makes execution possible.
Without it, everything you build rests on assumptions that expired three days ago.
What I actually do now
Alright, here’s the system I’ve landed on. Nothing fancy—just a few questions I run through before I open my mouth.
When I have a new idea:
First question: Does this deserve the next twelve months of Trevean Spice’s life?
If yes—actually, truly yes—then it’s a real priority conversation. I bring it to the team, explain what it means, and explicitly state what’s changing and what’s not.
If no (which is almost always the case), second question: Is this interesting enough to revisit later?
If yes, it goes in my “Ideas I’m Not Sharing Yet” note. I write it down, date it, and let it sit. If it still matters in three months, we can talk then.
If no, I let it go. Not every interesting thought deserves to be remembered.
When I do need to share something:
I force myself to finish this sentence out loud: “This is interesting, and here’s what it doesn’t change about what we’re working on right now.”
That sentence takes five seconds. The unfiltered approach cost me two weeks and a chunk of team trust I had to rebuild.
Once a week:
I look at two things: our actual priorities (to make sure I’m working on them) and my “Ideas I’m Not Sharing Yet” list (to make sure nothing in there has become urgent enough to surface).
If anyone is interested, this is how I automatically add and sort my ideas by Idea Date in Excel.
Ten minutes. Most valuable ten minutes of my week.
Your team isn’t waiting for you to have better ideas. They’re waiting to know which ideas actually matter.
And the only way they can know is if you tell them—repeatedly, explicitly, even when it feels unnecessary.
Or sometimes, by not telling them at all. By trusting that the idea still nagging you in three months will find its moment—and the one that fades probably wasn’t worth the distraction anyway.
Here’s the question I ask myself now before I share anything: What am I implicitly telling my team to stop doing?
If you can’t answer that, you’re about to find out the hard way.