SYSTEMS / DAY 02

Your Business Has a Nervous System

By Seçil Sayhan, MSc Clinical Health Psychology & WellbeingUpdated July 2026

The takeaway

your business has a nervous system — and right now every signal runs through one person.

What’s in this article

  1. What your spinal cord knows that your founder brain forgot
  2. Engineers have a name for what you've built
  3. Why working harder makes the wiring worse
  4. The fix is pathways, not effort
  5. "But no one does it the way I would"
  6. What freeing the center is actually for
  7. Frequently asked questions

Touch a hot stove and your hand is moving before the pain ever reaches your brain. That's not a malfunction. Your spinal cord handles the reflex so your brain stays free for the work only it can do — and most growing companies have it backwards.

What your spinal cord knows that your founder brain forgot

Here's the part of the stove story most people miss. The signal from your hand doesn't travel to your brain, get evaluated, and come back as a decision. It can't. By the time pain registers consciously, you'd already be burned. So your body cheats. The reflex arc loops through the spinal cord and fires the muscle directly. The brain finds out afterward.

This isn't your nervous system being lazy or cutting corners. It's the most sophisticated design choice in the whole system. Urgent, predictable responses get pushed to the edge. The center is reserved for what only the center can do — judgment, meaning, the things that need the full picture.

Now look at how decisions move through your company. The refund request, the schedule change, the vendor question, the 'can we approve this' Slack message. Most of those are reflexes. They have a right answer that doesn't require you. But in a lot of growing companies, every one of them travels the long way: out to the edge, all the way back to the founder, wait, then back out again.

A body built that way would never survive a hot stove. Neither does a business. The founder becomes the spinal cord and the brain at once, processing reflexes that should never have reached the center. It feels like diligence. It's actually a wiring problem.

Engineers have a name for what you've built

They call it a single point of failure. One node that, if it stops, the entire system stops with it. A bridge held by a single cable. A data center with one power line. A heart with no backup rhythm.

When the founder is that node, the company can look healthy from the outside. Revenue's up. The team's busy. The calendar's full. None of that tells you whether the system can survive the founder being gone, and that's the only measure that actually matters.

The test is simple and it's uncomfortable. Take a real week off. Not the version where your phone is in your pocket and you're 'just checking.' The genuinely gone version. Come back and look at what's waiting. If there's a pile, and two or three things are on fire, and people held decisions for seven days because only you could make them — you didn't build a business. You built a body where you are the only nerve.

The cruel part is that this shape often comes from doing good work. You answered fast. You cared about quality. You said 'just send it to me, I'll handle it.' Every one of those was a kindness in the moment and a wire you soldered to yourself. Enough of them, and the company can't fire a reflex without you.

Why working harder makes the wiring worse

The instinct, when the pile gets bigger, is to get faster. Wake earlier. Answer quicker. Clear the queue before anyone else is awake. This works for a while, and that's exactly the trap. It works just well enough to keep you from fixing the actual problem.

Speed at the center doesn't reduce the load on the center. It increases dependence on it. The faster you respond, the more reasons people have to route everything to you, because you're the quickest path to an answer. You train the whole organization to bring you reflexes. You become a better spinal cord, which is the wrong promotion.

There's a known pattern in how attention works that makes this worse. Every time you switch from your own deep work to handle someone else's small decision, there's a cost to come back. Research on task-switching shows the return isn't instant — part of your focus stays stuck on the thing you just left. So a day of constant interruptions isn't a full day minus the interruptions. It's a day where you never actually arrived anywhere.

More hustle adds more switches. The repair runs the other direction. You don't need to process the reflexes faster. You need them to stop reaching you at all.

The fix is pathways, not effort

A healthy nervous system doesn't send everything to the brain. Most of what your body does right now — heartbeat, digestion, the constant micro-adjustments that keep you upright — happens with no conscious input at all. That's not the brain losing control. It's the brain refusing to spend itself on what doesn't need it.

Building that into a company is concrete work, not a mindset. Start with one week of honest tracking. Every time someone needs you, write down the decision and one question: did this actually require my judgment, or did it require my permission? The permission ones are your reflexes. They're where the wiring goes first.

For each reflex, you're building a second route. That means three things, stated plainly. A rule, so the answer is knowable without you ('refunds under $200, approve; over, ask'). An owner, one named person who holds it. And a boundary, the edge where it does come back to you. Written down, not implied. The goal isn't to delegate the task once. It's to remove yourself from the path the signal travels, permanently.

Do this for the ten most common decisions and you've changed the shape of the company. The center goes quiet enough to do the work that genuinely needs a center: where this is going, and why.

"But no one does it the way I would"

This is the real objection, and it's usually true. No one will handle it exactly the way you would. The question is whether 'exactly the way you would' is worth what it costs.

Most of the time, you're not protecting quality. You're protecting a preference. The client doesn't need your specific phrasing on the follow-up email — they need a good follow-up email, on time, every time, whether or not you slept. A reflex that fires correctly 95% of the time, without you, beats one that fires perfectly only when you're available and not at all when you're not. A backup heart rhythm that's slightly off is still a heart that doesn't stop.

There's also a version of this that's harder to admit. Being the only one who can do it feels like worth. If the company can run a week without you, what does that say about you? It says you built something that works, which was the entire point. The body doesn't resent the spinal cord for handling reflexes. It uses the freed-up capacity for everything else.

The nuance worth keeping: some decisions genuinely should route to the center. Hiring senior people. Killing a product line. The directional calls. The skill isn't pushing everything to the edge. It's knowing which signals are reflexes and which ones need the whole brain — and stopping the confusion between them.

What freeing the center is actually for

I learned this in my own body before I understood it in companies. A health crisis at sixteen, with real risk, taught me what happens when a system that's supposed to run quietly in the background stops being quiet. When every signal becomes urgent, you can't think. You can only react. The whole organism narrows down to survival, and nothing that requires a future gets built.

A founder living in the reflex pile is in the same state, just slower and more disguised. Reacting all day feels like leading. It isn't. Leadership is the work that needs the full picture and the quiet to see it — where the company is going, what it's actually for, the bets only you can place. None of that gets done in the gaps between approvals.

The point of building pathways was never just to take a clean week off, though you should be able to. It's to get your center back. To free the one node in the system that can do the thing no rule and no reflex ever will: decide what's worth building next.

Your business has a nervous system. Right now, you might be every nerve in it. The work is to become only the part that thinks. If you want to see how we map and rebuild that wiring, it's at marsa.ai/business.

A business where every signal routes through the founder isn't in control — it's one nerve away from collapse.
i wrote the longer version of this — how to find your single points of failure and build the second pathway — over at marsa.ai/business. start with one signal this week.
Explore /business →

Frequently asked questions

How do I know if I'm actually the single point of failure?

Take a genuine week off — phone away, not 'monitoring.' Come back and look at what waited for you. If decisions piled up because only you could make them, and things stalled or broke without your input, you're the single node the system depends on. The cleaner the return, the more pathways you've already built. The bigger the pile, the more signals are still routing through you alone.

Isn't this just delegation with a different name?

Delegation usually means handing off a task while you keep the decision. You still approve, you still get pulled back in. Building a pathway means removing yourself from the path the signal travels at all — a written rule, a named owner, and a clear boundary for when it returns to you. Done right, the decision happens correctly without ever reaching your desk. That's the difference between a faster spinal cord and a system that fires its own reflexes.

Where do I start if everything currently runs through me?

Track one week. Every time someone needs you, write the decision down and ask: did this need my judgment, or just my permission? The permission ones are your reflexes. Take the ten most frequent, and for each write a rule (the answer when no one asks you), assign one owner, and define the boundary where it does still come back to you. Ten decisions rewired changes the shape of the whole company.

What if my team makes worse decisions than I would?

Some will be worse at first. The right comparison isn't your decision versus theirs — it's a decision that happens reliably without you versus one that only happens when you're available. A rule that's right 95% of the time, every time, beats perfection that depends on you never being sick, asleep, or out. Tighten the rules where the misses are costly. Loosen them where they're cheap. The misses are information, not proof the system failed.

Which decisions should still come to me?

The ones that need the full picture. Senior hires, killing or launching a product, major spend, the directional calls about where the company is going and why. Those are brain work, not reflex. The skill isn't pushing everything to the edge — it's separating the reflexes from the judgment calls and stopping the two from getting confused. Most founders are drowning in reflexes and starving the judgment work.

How long does it take to stop being the bottleneck?

There's no clean number, and anyone who gives you one is guessing. What's predictable is the order. You'll feel the quiet first in small, high-frequency decisions — the constant pings — because those are the easiest to write rules for and they free the most attention per hour. The bigger structural dependencies take longer and need more trust built into the team. The signal you're winning isn't an empty inbox. It's that your attention starts returning to the work only the center can do.

About the author

Seçil Sayhan is a behavioral scientist and the founder of MARSA.AI. Trained on both sides of her field — a BA in Business Management, an MSc in Clinical Health Psychology & Wellbeing, a diploma in neuroplasticity, and advanced training in Lifestyle Medicine from Harvard University — she has spent the past decade helping 7,000+ people across 12 countries rewire the systems running their lives. Behavior is one science — whether it moves a person, a market, or a machine. See the full bibliography at marsa.ai/research.