Not dramatically. I don’t announce it. I just quietly stop.

The posting slows down. The follow-through gets softer. “I’ll get back to that next week” turns into next month, and eventually the thing just... disappears.

And when I look back, it almost always happens at the exact same point: after I’ve done enough work to expect a result, but before I’ve gotten any proof that the work is actually doing anything.

Every time.

The pattern, once I actually looked at it

I started noticing it because it kept repeating across completely different projects, which is usually how you know something is actually about you and not about the project (shocking revelation!)

There was an earlier version of my Etsy shop that I worked on for months. I made the products. I built the listings. I wrote the SEO descriptions. I did all the things you’re supposed to do.

And when the sales didn’t come quickly enough, I quietly stopped.

Same with content. I’d post consistently for a few weeks, watch the numbers barely move, and decide that was enough information to know it wasn’t working.

No traction felt like proof of failure instead of what it actually was: a normal, boring, unremarkable early stage.

There’s a version of this story I could probably write about almost every meaningful thing I’ve tried to build.

I do the work.

I don’t see quick proof.

And some quiet voice tells me the absence of proof is the proof.

That I’m wasting my time. That nobody wants this. That this one isn’t going to be different.

It never really occurred to me in those moments that the proof might just not have arrived yet.

“No proof yet” always felt exactly like “no.”

Why “no proof yet” gets read as “no”

I think this is an operations-brain problem as much as anything else.

In my day job, everything has an answer, there are no mysteries (I say this to my team all the time). There’s a metric, there’s a target, there’s a trend line. You can usually tell within days or weeks whether something is moving in the right direction or if something is broken.

I’m used to systems that give you feedback fast.

But building something of your own doesn’t necessarily run on that timeline.

There’s no dashboard for is this Substack going to matter?

There’s no trend line for is this shop eventually going to become real income?

The proof, when it comes, often comes much later than feels reasonable and almost never on the timeline you decided it should.

So I’ve been applying a fast-feedback instinct to a slow-feedback process.

And then I’ve been doing something even worse:

Treating the absence of data like negative data.

No sales yet = nobody wants it.

No subscriber growth = nobody cares.

No traction = bad idea.

But nothing has happened yet and this isn’t working are not the same sentence.

I’m realizing I’ve spent a lot of time treating them like they are.

Everything you want is on the other side of consistency

This sentence has been living rent-free in my head for a week.

And I haven’t been able to stop thinking about it. Hence the article.

Because I think consistency is the exact part I’ve underestimated.

Starting something? I can do that.

Getting excited about an idea? Very good at that.

Building the plan, making the thing, setting everything up, imagining what it could become?

Absolutely.

But continuing to do it after the excitement wears off and before the results arrive?

That’s where it gets harder.

Consistency isn’t particularly exciting in that part.

It’s posting again when the last thing barely got seen.

It’s making another product when the first one hasn’t sold.

It’s writing another article when you have no idea whether anyone is going to read it.

It’s continuing to show up when absolutely nothing is reassuring you that showing up is worth it.

And to be clear, I don’t think consistency means blindly doing the same thing forever.

Sometimes an idea really isn’t working. Sometimes the strategy needs to change. Sometimes the data actually does tell you to stop.

But that’s not historically where I’ve quit.

Those are two very different things.

The gap isn’t a red flag

What I’m trying to internalize now is that the gap I keep quitting in, the one between doing the work and seeing the proof, isn’t necessarily a warning.

It’s just the gap.

It’s supposed to be there.

Every single thing I’ve ever built that eventually worked had some version of that same quiet, proof-less stretch.

I just don’t remember those parts as clearly.

I remember the result.

The projects that I abandoned are different. I quit while I was still inside the gap, which means I never actually found out what was waiting on the other side of it.

That’s a hard thing to hold onto while you’re in it, because the gap doesn’t feel like not yet.

It feels exactly like no.

I don’t know if I can change that feeling.

But I can recognize it now.

And instead of asking myself:

Is this working?

I’m trying to ask:

Have I actually been consistent long enough to know?

A very small piece of proof

This Substack is actually a tiny, real-time experiment in doing this differently.

This is my fourth article. I’m not even a month in. (9/1 - Happy 1 Month!)

And for most of that month, I’ve experienced exactly the kind of silence I’m describing.

Then this past week, five new people subscribed because of a a few notes I almost didn’t bother posting.

Five people isn’t a viral moment.

It isn’t proof that I’ve “made it.”

But that’s almost what makes it more meaningful.

The prior notes didn’t suddenly perform because I found some secret formula.

I just kept posting. I kept testing. I kept learning.

And eventually something landed.

Maybe this is the middle

I don’t know if I’ve finally broken this pattern.

I’m probably going to have to choose not to quit a hundred more times before I can say that.

But now I know where the pattern lives.

It lives in the quiet part.

The part after the excitement wears off.

After you’ve done the work.

Before anyone notices.

Before the sales come.

Before the numbers move.

Before you have anything reassuring you that you’re not wasting your time.

That’s the part I’ve always mistaken for the end.

So if you’re in that gap right now, with a business, a newsletter, a career move, a project, or something else you’re trying to build, maybe don’t ask yourself whether it’s working yet.

Ask yourself whether you’ve actually given it enough time to answer.

Because maybe everything you want isn’t waiting on the other side of some huge breakthrough.

Maybe it’s just on the other side of consistency.

Until Next Sunday,

That’s how long I’ve led teams in operations.

Ten years of performance reviews, engagement surveys, exit interviews (the rare ones), and stay interviews (the much more common ones).

And across almost every metric that’s supposed to tell you whether you’re a good manager, I score well.

Low turnover. High satisfaction scores. People who transfer onto my team, not away from it.

By the numbers, I’m a good manager.

I am not, however, a great one.

And it took me a long time to understand why, because the thing holding me back was one of the things I was most proud of.

The story I told myself

For years, I thought my teams stayed because I cared about people.

I set clear expectations. I advocated for them when they weren’t in the room. I made myself available. I tried very hard to never be the kind of boss who left someone drowning while I watched from shore.

All of that is true.

But it wasn’t the whole story.

The fuller story is this:

I hold onto things I should hand off.

Not tasks. I delegate tasks constantly.

I’m talking about ownership.

The kind where someone else gets to make the call, potentially make the wrong call, deal with what happens next, and become better because of it.

That part is much harder for me.

And I wish I could tell you it comes from some noble place.

It doesn’t.

I’m good at my job. I’ve been doing this long enough that I can usually look at something and see three ways it could go sideways before they happen.

So I help.

Or at least, that’s what I’ve always called it.

Someone brings me a plan and I start asking questions.

Have you thought about this?

What if we did it this way instead?

Do you think we should account for this?

They sound like questions.

Sometimes they are.

But sometimes, “Have you thought about doing it this way instead?” isn’t really a question.

It’s a redirect wearing a question mark.

And because I deliver it warmly, because I’m not demanding or dismissive, because the whole conversation feels collaborative, the person walks away feeling coached rather than overridden.

For a long time, I walked away thinking the same thing.

I was helping.

Except multiply that interaction by ten years and hundreds of tiny decisions and you can accidentally build a team that’s incredibly good at working with you.

And not nearly as practiced at working without you.

That one stung.

The problem with being the person who always catches it

Here’s the really uncomfortable part.

This behavior gets rewarded.

People feel supported because I’m involved.

They don’t feel abandoned because I don’t let them get too far down the wrong road.

Projects run smoothly because I’m constantly scanning ahead for the potholes.

Stress stays low.

Confusion stays low.

Turnover stays low.

The numbers look great.

And somewhere along the way, I started treating those numbers as proof that my management style was working exactly as intended.

But there’s another number I’ve never had on a dashboard:

How many decisions did someone learn to make without me?

Because every time I remove the friction, I also remove an opportunity to build judgment.

Every time I give someone “guidance” that’s really my preferred answer, I’m teaching them how I would solve the problem.

I’m not necessarily teaching them how to solve it.

Those can look exactly the same when you’re trying to get through Q4.

They look very different when you’re trying to build the next leader.

Then I caught myself doing it when no one else was around

I didn’t fully recognize this pattern at work.

I recognized it while building something of my own outside of it.

Suddenly, there was nobody else to over-guide.

Nobody’s plan to redirect.

Nobody to ask my question-that-isn’t-really-a-question.

Just me.

And somehow, the same instinct was still there.

I’d redo something I’d already finished because the first version wasn’t quite right.

I’d hold something back because I could think of three more things I wanted to fix first.

I’d spend time solving edge cases for something that hadn’t even been given the chance to succeed or fail yet.

And eventually I had this uncomfortable realization:

At work, mine looks like over-involvement.

On my own, it looks like an inability to ship.

Same root. Different costume.

And that’s when I finally understood what I had been doing with my teams.

I wasn’t holding onto ownership because I didn’t trust them.

I was holding onto it because handing someone ownership means accepting that they may produce an outcome I wouldn’t have produced.

Maybe their deck looks different.

Maybe their process isn’t as clean or operationally-efficient.

Maybe they make a decision I wouldn’t have made.

Maybe something small actually does go wrong.

And then I have to resist the urge to say:

I knew that was going to happen.

That’s the muscle I hadn’t built.

Not delegation.

Tolerance.

So I’m trying something different

I wish this were the part where I told you I figured it out and now I delegate beautifully.

I don’t.

I’m catching myself in real time.

But I’m starting with three things.

I’m separating “guidance” from “the answer.”

Before I weigh in, I’m trying to ask myself: Am I pointing out a risk they genuinely haven’t considered, or am I uncomfortable because they’re doing this differently than I would?

Those are two very different things.

And only one of them requires me to intervene.

I’m letting small things go sideways.

Not things with meaningful consequences. I’m still responsible for the work and for my team.

But there are plenty of low-stakes moments where learning something the harder way costs almost nothing.

Sometimes my intervention would save ten minutes.

Maybe those ten minutes aren’t worth stealing the lesson.

I’m tracking ownership, not just output.

Did the work get done?

Great.

But I’m trying to ask another question now:

Could this person make that decision without me next time?

Because if the answer is always no, I don’t think I get to call the output alone a success.

The part I’m still working out

I don’t have a tidy ending for this one.

I’m mid-pattern, not past it.

What I know is that for years, some of the things that made me feel like a good manager were also making it harder for me to see where I needed to grow.

My availability felt like support.

My intervention felt like coaching.

My ability to anticipate problems felt like leadership.

And sometimes, they were all of those things.

Sometimes they weren’t.

That’s the part I’m learning to distinguish.

Because maybe the goal isn’t to build a team that never falls.

Maybe it’s to build one that doesn’t need you standing behind them with your hands out, ready to catch them every time they wobble.

So now I’m looking at those good numbers a little differently.

Low turnover matters.

Engagement matters.

People wanting to work for you matters.

But I’m asking myself one more question:

Are the good numbers telling me people are growing or just that I’ve gotten really good at catching them before they have to?

I don’t know that I’ll fully answer that this year.

But I’m done pretending the good scores were the whole story.

Until next Sunday,

That part was hard enough.

But it was move-out day that really taught me what audacity means.

He showed up with a “friend” to help him carry boxes. Except the friend wasn’t a friend. She was the girlfriend he’d already been living with.

That’s audacity.

The bad kind.

The kind that takes something from someone and does it right in front of them like it’s nothing.

For a long time after that, I flinched at the word. Audacity felt like a synonym for cruelty, for people who do whatever they want without much thought for who they hurt.

And honestly, most of us are raised to think of it that way.

We’re taught to be polite. To ask permission. To wait our turn. To earn things before we claim them. Especially women.

So audacity reads like a character flaw.

Audacious people are the ones who overstep. Who don’t ask. Who assume they’re allowed when the rest of us were taught not to assume anything.

But here’s what I’ve come to believe since:

At its core, it’s the willingness to act without waiting for permission.

What determines whether that’s admirable or awful is what you’re being audacious about and who pays the price for it.

My ex used his audacity to take. To rewrite the rules of our life together without telling me and then make me watch him do it, boxes and all.

His audacity had a cost, and someone else had to absorb it.

Me.

It took me a long time to stop associating the word itself with that day.

But there’s another version.

Audacity turned into fuel instead of a weapon.

It’s leaving the job everyone tells you is smart to keep because it comes with a title and a salary and a 401(k) match.

It’s starting the business before you feel “ready,” before you have perfect product photos or a polished brand or any proof it’ll work.

It’s hitting publish on a newsletter with your real name attached to it, with no guarantee anyone will read it and no guarantee it won’t feel like shouting into an empty room for a while.

That’s audacity spent on yourself instead of taken from someone else.

Nobody wakes up robbed because you decided to bet on yourself.

I’ve needed that kind of audacity more than I expected these last couple of years.

I’ve needed it to imagine a career that doesn’t follow the one safe track I thought I was supposed to stay on. To start things before I had a perfect plan. To write under my own name instead of hiding behind an anonymous account “just in case.”

None of those decisions came with permission.

I just made them.

And that’s the part that took me a while to sit with.

Audacity is a tool, like ambition or confidence or speed. Neutral until you point it at something.

So maybe the question isn’t should I be audacious?

Maybe it’s:

What am I being audacious for?

And who’s on the other end of it?

Am I taking, or am I building?

Is someone else absorbing the cost of my boldness, or am I the one putting my own skin in the game?

Because I don’t think most of us struggle with being too audacious.

I think we struggle with the opposite.

We wait for a green light nobody is ever going to hand us.

We wait to feel ready, which is a feeling that conveniently never quite arrives.

We wait for permission that was never actually required in the first place.

I catch myself doing it all the time.

Before I hit publish. Before I say out loud that I’m building something beyond my job title. Before I claim something I want before I have enough evidence to prove I’m entitled to want it.

There’s still a version of me that wants to ask first.

To run it by someone.

To get the nod of approval before I let myself take up that much space.

And every time, I have to remind myself:

Nobody is going to tap me on the shoulder and say, you’re allowed now.

That moment doesn’t come.

You start.

And sometimes the starting is the permission.

I’ve also had to get honest about the difference between caution and cowardice dressed up as caution.

Caution says, let me think this through so I don’t hurt someone.

Cowardice dressed as caution says, let me wait until it’s safe.

But what it often really means is:

Let me wait until I can’t be blamed if it doesn’t work.

Those aren’t the same thing, even though they can feel almost identical from the inside.

The first is wisdom.

The second has a cost too. It’s just quieter.

Nobody notices the newsletter you didn’t send.

The business you didn’t start.

The opportunity you didn’t ask for.

The thing you wanted but talked yourself out of wanting because wanting it too openly felt a little too audacious.

I don’t think the goal is to become reckless. I’ve seen firsthand what audacity looks like when there’s no regard for who absorbs the fallout.

The goal is to get honest about which kind of permission you’re actually waiting for.

The kind that protects someone else?

That’s worth respecting.

The kind that’s really just fear wearing a more acceptable name?

Maybe that’s the permission you stop waiting for.

So I’ll leave you with the question I’ve been asking myself:

Where are you waiting for permission you don’t actually need?

Reply and tell me one place in your life where you’re being too careful, too polite, or too willing to wait.

Maybe it’s time to have a little audacity.

Until next Sunday,

The employee who’s been with your company for 10 years may be making less than the person who starts next Monday.

They know your systems.
They train new hires.
They solve problems before leadership even knows they exist.

And yet they’re often paid below market, not because they’re less valuable, but because they stayed.

The longer I’ve worked inside large organizations, the more I’ve realized this isn’t an exception. It’s often how compensation systems are designed to work.

External hiring budgets flex to match the market in real time. Internal raises rarely do. They move on an annual cycle, capped by percentages that have little to do with what the role is actually worth today.

If I had five minutes with a room full of executives, here’s what I’d ask them to consider.

Every company talks about wanting loyal employees.

People who stay. People who know the business inside and out. People who carry institutional knowledge no process document could ever fully capture.

But loyalty has a cost, and most companies aren’t paying it.

They’re simply not printing the bill.

The bill arrives later, in the form of a resignation letter from someone who finally realized the raise they’d receive by leaving is larger than five years of annual merit increases combined.

By the time that resignation lands on your desk, the decision has already been made.

No counteroffer fixes what should have been addressed two years earlier.

Every time this happens, you’re teaching your highest performers that loyalty produces a lower return than leaving.

The market rate isn’t just for new hires.

It’s the real value of the role.

When a company hires someone into a role at a higher salary than the tenured employee already doing it, they aren’t necessarily saying the new hire is more valuable.

They’re unintentionally admitting what the role is actually worth.

The problem isn’t that the market suddenly changed.

The problem is that the employee who stayed never benefited from it.

Instead, they have to interview elsewhere, secure another offer, and effectively threaten to leave before anyone is willing to acknowledge the gap.

That’s an expensive way to discover what someone has always been worth.

It’s also a strange incentive system.

The smartest companies treat retention like recruiting.

Recruiting gets the budget.

Retention gets what’s left over.

The companies getting this right understand that compensation isn’t only about attracting talent. It’s about keeping the people who already know how to create value.

That means conducting regular market reviews, not simply for compliance, but as a retention strategy.

It means having honest conversations with long-tenured employees about where they stand against today’s market instead of hoping they never look.

And it means treating internal compensation decisions with the same urgency as external hiring decisions.

Because from the employee’s perspective, they’re exactly the same decision.

One just comes with a familiar parking spot.

What this really costs when companies get it wrong

The cost isn’t the resignation itself.

It’s the six months of productivity lost while someone new gets hired, onboarded, and learns what the previous employee already knew.

It’s paying a higher salary to replace someone you could have retained for less.

It’s the institutional knowledge that quietly disappears and never fully returns, regardless of how many documents get written during the transition.

But perhaps the biggest cost is the message everyone else receives.

The people who stay are watching what happens to the people who leave.

They notice who receives significant raises after accepting another offer.

They notice when new hires come in above existing salaries.

And they draw the same conclusion:

That signal spreads much faster than leadership usually realizes.

A different version of loyalty

Companies spend millions trying to attract great talent.

Sometimes the smartest investment isn’t finding someone new.

It’s making sure the people who’ve already helped build your business don’t have to leave before you recognize what they were worth.

The organizations that understand this don’t just retain employees.

They build trust.

And trust creates the kind of loyalty that isn’t based on comfort or fear of change.

It’s based on knowing that staying is still the smartest decision.

The best companies don't ask employees to prove they're worth more. They make sure employees never have to.

That’s the version of leadership worth building.
Next Sunday, I’ll share what loyalty looks like from the builder’s side of the desk.

If this resonated, share it with a leader who's building the kind of company people don't want to leave.

Share

Until next Sunday,

Subscribe now

For most of my career, I’ve built things that didn’t belong to me.

I’ve launched products. Built ecommerce experiences. Led teams. Solved operational problems. Sat in conference rooms making decisions that impacted millions of dollars in revenue.

It has been rewarding work.

But when the day ended, none of it had my name on it.

Over the last few months, something started to change.

A friend asked me to help launch his handyman business from scratch. Another reached out about ecommerce consulting. I found myself sketching website wireframes at night, redesigning business cards, writing marketing copy, and obsessing over how a small business earns trust before it ever earns a customer.

I realized I wasn’t just helping businesses.

I was remembering what I love.

I love building.

Not just companies.

Ideas.

Systems.

Brands.

People.

Momentum.

Somewhere along the way, I started believing that the only meaningful work happened inside large organizations with big budgets and impressive titles.

But lately I’ve been discovering something different.

Some of the most interesting problems don’t exist inside Fortune 500 companies.

They exist at a kitchen table where someone is trying to figure out how to get their first ten customers.

Or in a local business trying to compete against companies ten times its size.

Or in the blank page that appears when someone says, “I have an idea, but I don’t know where to start.”

That’s the work that energizes me.

This newsletter is where I’m going to document it.

Not from the perspective of someone who has everything figured out.

But from the perspective of someone who’s actively building.

Some weeks I’ll write about helping a small business grow.

Some weeks I’ll share lessons from corporate leadership that translate surprisingly well to small companies.

Other weeks, it’ll be AI workflows, marketing experiments, systems I’m testing, books I’m reading, or mistakes I’m trying not to repeat.

If it helps someone build something a little better, it’s worth writing.

I’m also writing this for a more personal reason.

For years, I kept waiting until I felt “ready” to put my work out into the world.

Ready to create content.

Ready to consult.

Ready to write.

Ready to build something with my own name attached to it.

I’ve learned that “ready” is usually just another word for “later.”

So this is me choosing now.

Not because I have all the answers.

Because I finally have the courage to ask better questions in public.

My hope is that, years from now, this becomes a record of everything I built, everything that failed, everything that surprised me, and everything that taught me something worth sharing.

If this resonated with you, I'd love to know what you're building. Leave a comment or simply reply to this email. I read every one.

Welcome.

I’m glad you’re here.

Until next Sunday,