u/Deep-Owl-1890

There's a Harvard study on what predicts long-term business success. The finding is counterintuitive: it's not intelligence, work ethic, or even capital.

It's time horizon...specifically, how far into the future a decision-maker can hold their thinking when they're under pressure.

Founders who build durable businesses think in years and live in weeks. Founders who plateau think in weeks and get buried in days.

Bezos talked about this directly. The decisions that compounded most at Amazon, AWS, Prime, the logistics network, all of them required ignoring short-term costs to build something that would only make sense at a 7-10 year horizon. And they got criticized heavily in the short term for all of it.

The version of this for a $1M-$5M founder isn't as dramatic, but the pattern is the same.

You're making hiring decisions based on who you need right now instead of who you'll need in 18 months. You're building processes for your current size instead of your next size. You're saying yes to revenue opportunities that fit today instead of asking whether they fit where you're going.

And the result is a business that's always slightly behind itself, perpetually catching up, constantly solving problems that a decision made 12 months ago could have prevented.

The trap is that short-term thinking feels responsible. you're being practical. Dealing with what's in front of you. Staying close to the ground. And it is practical, right up until the decisions you didn't make become the constraints you're managing instead.

One thing that helps: once a month, block an hour and ask one question. If this business is 3x the current size in 3 years, what breaks first? That answer is usually where your long-term thinking should be spending its time right now.

That’s it guys but I'd love to know if you think there’s anything more critical for long-term business success?

EDIT: If you found this useful and you're running a business, at some point you probably want it to run without you. That's freedom, not just revenue. I write frameworks like this every Thursday; you can apply right away. free to join here 

There's a Harvard study on what predicts long-term business success. The finding is counterintuitive: it's not intelligence, work ethic, or even capital.

It's time horizon...specifically, how far into the future a decision-maker can hold their thinking when they're under pressure.

Founders who build durable businesses think in years and live in weeks. Founders who plateau think in weeks and get buried in days.

Bezos talked about this directly. The decisions that compounded most at Amazon, AWS, Prime, the logistics network, all of them required ignoring short-term costs to build something that would only make sense at a 7-10 year horizon. And they got criticized heavily in the short term for all of it.

The version of this for a $1M-$5M founder isn't as dramatic, but the pattern is the same.

You're making hiring decisions based on who you need right now instead of who you'll need in 18 months. You're building processes for your current size instead of your next size. You're saying yes to revenue opportunities that fit today instead of asking whether they fit where you're going.

And the result is a business that's always slightly behind itself, perpetually catching up, constantly solving problems that a decision made 12 months ago could have prevented.

The trap is that short-term thinking feels responsible. you're being practical. Dealing with what's in front of you. Staying close to the ground. And it is practical, right up until the decisions you didn't make become the constraints you're managing instead.

One thing that helps: once a month, block an hour and ask one question. If this business is 3x the current size in 3 years, what breaks first? That answer is usually where your long-term thinking should be spending its time right now.

That’s it guys but I'd love to know if you think there’s anything more critical for long-term business success?

EDIT: If you found this useful and you're running a business, at some point you probably want it to run without you. That's freedom, not just revenue. I write frameworks like this every Thursday; you can apply right away. free to join here 

There's a Harvard study on what predicts long-term business success. The finding is counterintuitive: it's not intelligence, work ethic, or even capital.

It's time horizon...specifically, how far into the future a decision-maker can hold their thinking when they're under pressure.

Founders who build durable businesses think in years and live in weeks. Founders who plateau think in weeks and get buried in days.

Bezos talked about this directly. The decisions that compounded most at Amazon, AWS, Prime, the logistics network, all of them required ignoring short-term costs to build something that would only make sense at a 7-10 year horizon. And they got criticized heavily in the short term for all of it.

The version of this for a $1M-$5M founder isn't as dramatic, but the pattern is the same.

You're making hiring decisions based on who you need right now instead of who you'll need in 18 months. You're building processes for your current size instead of your next size. You're saying yes to revenue opportunities that fit today instead of asking whether they fit where you're going.

And the result is a business that's always slightly behind itself, perpetually catching up, constantly solving problems that a decision made 12 months ago could have prevented.

The trap is that short-term thinking feels responsible. you're being practical. Dealing with what's in front of you. Staying close to the ground. And it is practical, right up until the decisions you didn't make become the constraints you're managing instead.

One thing that helps: once a month, block an hour and ask one question. If this business is 3x the current size in 3 years, what breaks first? That answer is usually where your long-term thinking should be spending its time right now.

That’s it guys but I'd love to know if you think there’s anything more critical for long-term business success?

EDIT: If you found this useful and you're running a business, at some point you probably want it to run without you. That's freedom, not just revenue. I write frameworks like this every Thursday; you can apply right away. free to join here 

Lot of talk about how founders are trying to delegate, to people and to AI. I see 3 buckets:

1. Founders who hire their way out. Adding new staff without any documented systems. The chaos just gets more expensive and still routes through them.
2. Founders who try to AI their way out. Buy every tool, open every tab, end up with a graveyard of subscriptions and a business that still lives in their head.
3. Founders who know they're the bottleneck and want to hand work to both people and AI, but have no clue what goes to a human vs a machine.

Most of us started as bucket 1, then sprinted to bucket 2 the second AI got good.

Heres what I do:

I stopped treating people and AI as two different delegation problems and started running one system for all 21 of them.

If a task isnt defined somewhere, it doesnt get delegated. To anyone. Human or agent.

So delegation isnt me re-explaining what I want every time. Its handing off to something that already knows how the work runs.

How it actually works:

1. Every "employee" gets the same 4 things, human or AI

Doesnt matter if it's a person or an agent. Both need:

- A role (what they own)

- Context (what they need to know to make the call I'd make)

- An SOP (how the work runs when I'm not in the room)

- An accountability loop (how I know it actually happened)

Every time I've been burned it's because I skipped the SOP and assumed someone could read my mind.

2. One filter decides who runs it: complexity vs reproducibility

High complexity, low reproducibility goes to a human. Strategy, relationships, judgment calls, the stuff that changes every time.

Low complexity, high reproducibility goes to an agent. Data entry, research, reporting, scheduling, the stuff that looks the same every Tuesday.

For people, I dont manage the person, I manage the system they operate inside. I spend 5 minutes documenting a process, sometimes a quick screen recording, then hand it off and confirm they actually got it. Full accountability. No mystery Drive folder I'm not even sure anyone opened.

For AI, an agent is just an employee you onboard with a document instead of a conversation. It gets context, a clear job, files it can pull from, and specific skills I call on when I need them. I tag it like I'd tag a teammate in Slack, it loads the right context and does the thing. On demand or on a schedule.

3. The system compounds

Every process I write once works forever, for whoever runs it next.

New hire? They read the doc. New agent? It reads the same doc. Six months from now the system knows more about how we operate than it does today, and I didnt have to re-explain a thing.

Why am i telling you this?

Because most founders think the answer is one more hire or one more AI tool.

The ones actually pulling ahead didnt find a better tool. They wrote down how the business runs, then let people AND AI operate inside it.

You have to organize the business first. You cant delegate chaos, not to a person and not to a robot. AI doesnt fix a mess, it just automates it faster.

But once it's built, you stop being the human who explains context fifty times a day. The work finally leaves your desk.

We didnt start with 14 agents. We didnt start with any employees either. I started with one document. The document is the system. The person or the agent is just what reads it.

edit: a few people asked where they can read more about how this system works day to day, I write about this stuff (delegation systems, SOPs, AI agents, getting out of the bottleneck seat) every thursday in modern operators. free to join here

Lot of talk about how founders are trying to delegate, to people and to AI. I see 3 buckets:

1. Founders who hire their way out. Adding new staff without any documented systems. The chaos just gets more expensive and still routes through them.
2. Founders who try to AI their way out. Buy every tool, open every tab, end up with a graveyard of subscriptions and a business that still lives in their head.
3. Founders who know they're the bottleneck and want to hand work to both people and AI, but have no clue what goes to a human vs a machine.

Most of us started as bucket 1, then sprinted to bucket 2 the second AI got good.

Heres what I do:

I stopped treating people and AI as two different delegation problems and started running one system for all 21 of them.

If a task isnt defined somewhere, it doesnt get delegated. To anyone. Human or agent.

So delegation isnt me re-explaining what I want every time. Its handing off to something that already knows how the work runs.

How it actually works:

1. Every "employee" gets the same 4 things, human or AI

Doesnt matter if it's a person or an agent. Both need:

- A role (what they own)

- Context (what they need to know to make the call I'd make)

- An SOP (how the work runs when I'm not in the room)

- An accountability loop (how I know it actually happened)

Every time I've been burned it's because I skipped the SOP and assumed someone could read my mind.

2. One filter decides who runs it: complexity vs reproducibility

High complexity, low reproducibility goes to a human. Strategy, relationships, judgment calls, the stuff that changes every time.

Low complexity, high reproducibility goes to an agent. Data entry, research, reporting, scheduling, the stuff that looks the same every Tuesday.

For people, I dont manage the person, I manage the system they operate inside. I spend 5 minutes documenting a process, sometimes a quick screen recording, then hand it off and confirm they actually got it. Full accountability. No mystery Drive folder I'm not even sure anyone opened.

For AI, an agent is just an employee you onboard with a document instead of a conversation. It gets context, a clear job, files it can pull from, and specific skills I call on when I need them. I tag it like I'd tag a teammate in Slack, it loads the right context and does the thing. On demand or on a schedule.

3. The system compounds

Every process I write once works forever, for whoever runs it next.

New hire? They read the doc. New agent? It reads the same doc. Six months from now the system knows more about how we operate than it does today, and I didnt have to re-explain a thing.

Why am i telling you this?

Because most founders think the answer is one more hire or one more AI tool.

The ones actually pulling ahead didnt find a better tool. They wrote down how the business runs, then let people AND AI operate inside it.

You have to organize the business first. You cant delegate chaos, not to a person and not to a robot. AI doesnt fix a mess, it just automates it faster.

But once it's built, you stop being the human who explains context fifty times a day. The work finally leaves your desk.

We didnt start with 14 agents. We didnt start with any employees either. I started with one document. The document is the system. The person or the agent is just what reads it.

edit: a few people asked where they can read more about how this system works day to day, I write about this stuff (delegation systems, SOPs, AI agents, getting out of the bottleneck seat) every thursday in modern operators. free to join here

I manage a small team of 10, and something clicked for me recently: small businesses or startups have one real advantage over Google, Amazon, or any big company, and it doesn't cost anything to use.

Big tech can offer stock options, free meals, gym memberships, and salaries that make your eyes water. 

What it structurally can't offer is the feeling of being seen. Not when you're employee #4,847. Not when your manager has 40 direct reports. Not when you're a line item on a workforce planning slide.

That's the gap small businesses can fill. You actually know your people's names, their wins, the project that nearly broke them, and the moment they figured it out anyway. You can walk over and say "that mattered" and actually mean it, and they can tell you mean it.

I don't think that's a soft skill. I think it's a retention strategy that a bigger competitor genuinely can't copy at scale.

In my experience, people rarely leave over the next salary bump alone. More often they leave because they quietly stopped feeling like they mattered, and by the time you notice, they've already checked out. 

When someone actually feels seen, they don't just stay, they bring more of themselves to the work without being asked and without a bonus attached.

For most small businesses, the real competition for talent isn't Google or Amazon anyway, it's the agency or SaaS company down the street in your exact niche, offering the same pay band and the same perks. 

You don't need a bigger budget to out-retain them. You need to notice your people before they start wondering if anyone does. A specific "that was great work, and here's why it mattered" does more for retention than a ping pong table ever will, and it's a lot cheaper than hiring and training someone new every quarter. 

I’d love to hear if others here have felt this too?

edit: if you found this helpful, I write about how to run your business without being involved in everything and how to use AI to save 10+ hours a week.

600+ founders are already reading; feel free to join here if you’re interested.

I manage a small team of 10, and something clicked for me recently: small businesses or startups have one real advantage over Google, Amazon, or any big company, and it doesn't cost anything to use.

Big tech can offer stock options, free meals, gym memberships, and salaries that make your eyes water. 

What it structurally can't offer is the feeling of being seen. Not when you're employee #4,847. Not when your manager has 40 direct reports. Not when you're a line item on a workforce planning slide.

That's the gap small businesses can fill. You actually know your people's names, their wins, the project that nearly broke them, and the moment they figured it out anyway. You can walk over and say "that mattered" and actually mean it, and they can tell you mean it.

I don't think that's a soft skill. I think it's a retention strategy that a bigger competitor genuinely can't copy at scale.

In my experience, people rarely leave over the next salary bump alone. More often they leave because they quietly stopped feeling like they mattered, and by the time you notice, they've already checked out. 

When someone actually feels seen, they don't just stay, they bring more of themselves to the work without being asked and without a bonus attached.

For most small businesses, the real competition for talent isn't Google or Amazon anyway, it's the agency or SaaS company down the street in your exact niche, offering the same pay band and the same perks. 

You don't need a bigger budget to out-retain them. You need to notice your people before they start wondering if anyone does. A specific "that was great work, and here's why it mattered" does more for retention than a ping pong table ever will, and it's a lot cheaper than hiring and training someone new every quarter. 

I’d love to hear if others here have felt this too?

edit: if you found this helpful, I write about how to run your business without being involved in everything and how to use AI to save 10+ hours a week.

600+ founders are already reading; feel free to join here if you’re interested.

I manage a small team of 10, and something clicked for me recently: small businesses or startups have one real advantage over Google, Amazon, or any big company, and it doesn't cost anything to use.

Big tech can offer stock options, free meals, gym memberships, and salaries that make your eyes water. 

What it structurally can't offer is the feeling of being seen. Not when you're employee #4,847. Not when your manager has 40 direct reports. Not when you're a line item on a workforce planning slide.

That's the gap small businesses can fill. You actually know your people's names, their wins, the project that nearly broke them, and the moment they figured it out anyway. You can walk over and say "that mattered" and actually mean it, and they can tell you mean it.

I don't think that's a soft skill. I think it's a retention strategy that a bigger competitor genuinely can't copy at scale.

In my experience, people rarely leave over the next salary bump alone. More often they leave because they quietly stopped feeling like they mattered, and by the time you notice, they've already checked out. 

When someone actually feels seen, they don't just stay, they bring more of themselves to the work without being asked and without a bonus attached.

For most small businesses, the real competition for talent isn't Google or Amazon anyway, it's the agency or SaaS company down the street in your exact niche, offering the same pay band and the same perks. 

You don't need a bigger budget to out-retain them. You need to notice your people before they start wondering if anyone does. A specific "that was great work, and here's why it mattered" does more for retention than a ping pong table ever will, and it's a lot cheaper than hiring and training someone new every quarter. 

I’d love to hear if others here have felt this too?

edit: if you found this helpful, I write about how to run your business without being involved in everything and how to use AI to save 10+ hours a week.

600+ founders are already reading; feel free to join here if you’re interested.

That "they'll do for now" hire you brought on because you were desperate to fill the seat? 

They're not just dragging on your metrics quietly in the corner. They're actively scaring off the good people you're gonna want down the line.

Talented people figure out a room fast. Stick them next to someone who's just phoning it in, and within a week they've already decided what you're okay with as a company.

The annoying part is, it's never just one bad hire. It's a domino effect. That one hire quietly resets what "acceptable" looks like. The next person either matches that energy or dips a little lower, because hey, the last one got through fine. 

Fast forward six months and you're confused why solid candidates keep dropping off after the interview.

They're not leaving because of the offer. They already met your team, that's the offer.

Every person you let in isn't just doing their job, they're quietly setting the vibe for everyone who walks in after them.

So genuinely asking, has anyone actually fixed this after the fact? Or is starting over with the team basically the only real fix?

edit: if you found this helpful, I write about how to run your business without being involved in everything and how to use AI to save 10+ hours a week.

600+ founders are already reading; feel free to join here if you’re interested.

Hey everyone,

I wanted to share a workflow adjustment we made recently that saved our team from constant context switching and notification overload.

A few months ago, we realized that our Slack channels were becoming a black hole for basic questions. Team members would ping us for standard procedures, playbooks, or client details. While it’s great to be helpful, it meant constant interruptions and an incredible amount of "noise" throughout the day.

Instead of letting Slack dictate our day, we decided to make Notion our official company OS. We brought all our playbooks, data, and context into one single place.

We set a simple rule for the team: Before asking a question in Slack, ask Notion AI first.

Because everything is indexed in one place, the AI can scan our playbooks, past decisions, and documents to give an accurate answer.

Only if the team member cannot get the answer from Notion AI do they ping us on Slack.

The Results

Reduced noise by 80%: The constant stream of repetitive questions has vanished.

Fewer interruptions: We've reclaimed our focus and can spend more time working on the business instead of managing chats.

Faster onboarding: The team learns faster because they get immediate, context-aware answers.

The magic is that everything the team needs from client guidelines to marketing playbooks is in one place, making our AI system highly reliable.

If you are struggling with Slack overload, I highly recommend building a unified knowledge base and letting your team query the AI before escalating.

I want to be completely honest with you: this isn't a "set it and forget it" system. In the beginning, we noticed that a few questions didn't get answers because the AI lacked the context.

Every time that happens, we treat it as a quick fix: we just update the existing documentation or add a new page if the topic wasn't covered. It takes a little maintenance, but it has been absolutely worth it to cool down Slack and keep the team fully aligned.

If anyone is interested in how we set this up alongside Slack, including our internal Slack communication framework, just let me know in the comments! I didn't want to make this post too long, but I'd be happy to do a deeper dive on that in my next post.

P.S. If you're the founder still in the middle of every decision, still the person the whole company waits on, still telling yourself you'll fix the structure "once things calm down."

I write about building the operational backbone that lets a founder actually step back every Thursday. Was a COO for 20+ years, so this is genuinely my bread and butter. Free to join here

Hey everyone,

I wanted to share a workflow adjustment we made recently that saved our team from constant context switching and notification overload.

A few months ago, we realized that our Slack channels were becoming a black hole for basic questions. Team members would ping us for standard procedures, playbooks, or client details. While it’s great to be helpful, it meant constant interruptions and an incredible amount of "noise" throughout the day.

Instead of letting Slack dictate our day, we decided to make Notion our official company OS. We brought all our playbooks, data, and context into one single place.

We set a simple rule for the team: Before asking a question in Slack, ask Notion AI first.

Because everything is indexed in one place, the AI can scan our playbooks, past decisions, and documents to give an accurate answer.

Only if the team member cannot get the answer from Notion AI do they ping us on Slack.

The Results

Reduced noise by 80%: The constant stream of repetitive questions has vanished.

Fewer interruptions: We've reclaimed our focus and can spend more time working on the business instead of managing chats.

Faster onboarding: The team learns faster because they get immediate, context-aware answers.

The magic is that everything the team needs from client guidelines to marketing playbooks is in one place, making our AI system highly reliable.

If you are struggling with Slack overload, I highly recommend building a unified knowledge base and letting your team query the AI before escalating.

I want to be completely honest with you: this isn't a "set it and forget it" system. In the beginning, we noticed that a few questions didn't get answers because the AI lacked the context.

Every time that happens, we treat it as a quick fix: we just update the existing documentation or add a new page if the topic wasn't covered. It takes a little maintenance, but it has been absolutely worth it to cool down Slack and keep the team fully aligned.

If anyone is interested in how we set this up alongside Slack, including our internal Slack communication framework, just let me know in the comments! I didn't want to make this post too long, but I'd be happy to do a deeper dive on that in my next post.

P.S. If you're the founder still in the middle of every decision, still the person the whole company waits on, still telling yourself you'll fix the structure "once things calm down."

I write about building the operational backbone that lets a founder actually step back every Thursday. Was a COO for 20+ years, so this is genuinely my bread and butter. Free to join here

Hey everyone,

I wanted to share a workflow adjustment we made recently that saved our team from constant context switching and notification overload.

A few months ago, we realized that our Slack channels were becoming a black hole for basic questions. Team members would ping us for standard procedures, playbooks, or client details. While it’s great to be helpful, it meant constant interruptions and an incredible amount of "noise" throughout the day.

Instead of letting Slack dictate our day, we decided to make Notion our official company OS. We brought all our playbooks, data, and context into one single place.

We set a simple rule for the team: Before asking a question in Slack, ask Notion AI first.

Because everything is indexed in one place, the AI can scan our playbooks, past decisions, and documents to give an accurate answer.

Only if the team member cannot get the answer from Notion AI do they ping us on Slack.

The Results

Reduced noise by 80%: The constant stream of repetitive questions has vanished.

Fewer interruptions: We've reclaimed our focus and can spend more time working on the business instead of managing chats.

Faster onboarding: The team learns faster because they get immediate, context-aware answers.

The magic is that everything the team needs from client guidelines to marketing playbooks is in one place, making our AI system highly reliable.

If you are struggling with Slack overload, I highly recommend building a unified knowledge base and letting your team query the AI before escalating.

I want to be completely honest with you: this isn't a "set it and forget it" system. In the beginning, we noticed that a few questions didn't get answers because the AI lacked the context.

Every time that happens, we treat it as a quick fix: we just update the existing documentation or add a new page if the topic wasn't covered. It takes a little maintenance, but it has been absolutely worth it to cool down Slack and keep the team fully aligned.

If anyone is interested in how we set this up alongside Slack, including our internal Slack communication framework, just let me know in the comments! I didn't want to make this post too long, but I'd be happy to do a deeper dive on that in my next post.

P.S. If you're the founder still in the middle of every decision, still the person the whole company waits on, still telling yourself you'll fix the structure "once things calm down."

I write about building the operational backbone that lets a founder actually step back every Thursday. Was a COO for 20+ years, so this is genuinely my bread and butter. Free to join here