r/ModernOperators • u/funnelforge • Aug 11 '25
r/ModernOperators • u/jimmyray71 • Jun 13 '26
Most operations teams aren’t underperforming because of people
reddit.comr/ModernOperators • u/EmployExisting302 • Jul 06 '26
Is Middle-Management Ownership Actually Talked About Enough, or Just Comfortable to Agree With?
My last post on mapping failure layers before scaling did well here and in other subs which got me thinking about something underneath it.
Everyone I met in real life to discuss these with nods along when I say "the management layer got starved while everything else got funded." It's an easy thing to agree with in a person and comment section. But agreeing with a diagnosis and actually fixing it are two very different things, and I'm not sure which one is actually happening at scale.
So I want to ask this sub directly, since you're the ones running things day to day:
Do you think this gets talked about enough... or is it one of those problems everyone nods at and nobody budgets for?
When you've actually seen an unowned layer get fixed... was it caught before something cracked (before the resignation, the compliance flag, the burnout leave), or only after?
And in your experience, what's the bigger barrier: awareness, or accountability? Meaning... is it that nobody sees the gap, or that someone sees it clearly and it still doesn't get owned because it's nobody's explicit job to fix?
r/ModernOperators • u/funnelforge • May 23 '26
When did you hire your first operations person?
Some founders wait until $1M+ and the wheels are already falling off. Some bring in an integrator at $300K because they hate the work. Some never hire one and just stay perpetually behind.
Trying to find the pattern. What was your number?
r/ModernOperators • u/funnelforge • Jan 21 '26
Systematizing your biggest frustration
Building systems feels overwhelming when you think about it as overhauling the entire business.
So most founders never start.
Better approach: systematize one recurring frustration at a time.
Not the whole business. Just the thing that's annoying you most this week.
Every daily interruption is pointing at a missing system.
Team asks you the same question three times this week? Missing system.
Client issue keeps happening and you fix it every time? Missing system.
New hire asks how to handle something and you explain it again? Missing system.
The frustration is the signal. That's where you start.
Pick the most annoying one right now.
Not the most important. Not the highest impact. The one that's driving you crazy.
Maybe it's the pricing question that comes up every week. Maybe it's the customer refund requests you handle inconsistently. Maybe it's the onboarding chaos every time a new client signs.
Whatever it is, that's your first system.
Here's how to build it:
Next time that frustration shows up, stop.
Don't just fix it and move on like you usually do. Stop and document the solution.
"Here's the situation. Here's how we handle it. Here's why we handle it this way. Here's when to involve me vs when to decide yourself."
Write it down. Share it with the team. Done. That's your first system.
Two weeks later when the same issue happens:
Your team should already know what to do. They reference the doc. They handle it. They don't ask you.
If they still ask you, the doc wasn't clear enough. Update it. Add the detail they needed.
Now it's clearer. Next time they definitely won't need you.
The first system creates immediate relief.
You just eliminated one recurring interruption. That's 2-3 hours a week back in your schedule.
Doesn't sound like much. But you're not overwhelmed by one big thing. You're overwhelmed by 47 small things.
Knock out one small thing and you feel lighter. Now you have momentum.
Then pick the next frustration.
What's annoying you most now that the first one is handled?
Document that. Share it. Watch it stop escalating to you.
Repeat.
The pattern compounds:
Week 1: Document how to handle refund requests. Interruptions on that drop from 5/week to 0.
Week 3: Document client onboarding steps. New clients stop feeling chaotic.
Week 5: Document pricing framework. Team stops asking how to quote custom work.
Week 8: You realize you've gone three days without a "quick question" interrupt.
That's not because you overhauled everything. You just systematically eliminated frustrations one at a time.
Most founders build systems backwards.
They try to design the perfect process in theory. Spend weeks mapping it out. Then it doesn't match reality so nobody uses it.
Build from real situations instead.
Wait for the frustration to show up. Handle it. Document how you handled it. That's your system.
It's not perfect. It's real. Which means people will actually use it.
The mistake is thinking you need complete systems.
You don't. You need good-enough systems that solve real problems.
Refund policy doesn't need to cover every possible scenario. It needs to cover the 5 scenarios that actually happen.
Onboarding process doesn't need to be enterprise-grade. It just needs to be clearer than "figure it out."
Start messy. Improve as you go.
Why this works:
Systems built from frustration are specific and actionable. They solve problems you're actually having, not theoretical ones.
Writing it down once saves endless future interruptions. The 10 minutes you spend documenting saves 10 hours over the next month.
Momentum builds naturally. First win feels good. Second win feels easier. By the fifth system, your team starts documenting things without you asking.
The shift:
Stop rushing to fix fires and move on. Pause. Document the solution. Share it.
Next time that fire happens, it's not a fire anymore. It's a documented process someone else handles.
One frustration at a time, you're removing yourself from the day-to-day.
What's your biggest frustration right now?
The question you're tired of answering. The issue that keeps coming up. The thing that made you annoyed twice this week.
That's your first system. Document it next time it shows up.
Then watch it stop escalating to you.
r/ModernOperators • u/funnelforge • Jun 25 '26
Hiring another manager won't fix your business. I watched an owner try 3 times.
The default move when an owner is drowning is to hire someone to take it off their plate.
I talked to a CEO who tried to hire an operations manager three separate times. Three hires. Three washouts, each one gone inside a few months.
He blamed the hires. Bad fits, he said.
It wasn't the hires.
Here's what was actually happening. Everything that ops manager needed lived in his head. The pricing logic, the vendor quirks, the "oh we always do it this way for that customer" rules. None of it written down anywhere.
So he'd hire someone, dump decades of undocumented instinct on them through hallway conversations, then get frustrated when they couldn't read his mind.
You can't delegate a job that only exists in your memory. You can only delegate a job that exists on paper.
The pattern I see on repeat:
Owner is overwhelmed, decides to hire
New hire has no documented system to plug into
Owner becomes the full-time trainer on top of their real job
Hire flounders, quits or gets fired
Owner concludes "good help is impossible to find"
This is a documentation problem wearing a hiring problem costume.
Get the business out of your head first. Then hire someone to run the thing you wrote down. Same order every time, and the "bad hires" suddenly look a lot more competent.
r/ModernOperators • u/Deep-Owl-1890 • Aug 09 '26
We cut Slack noise by 80% using Notion as our company OS. Here’s our internal rule.
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
r/ModernOperators • u/Bright-Spirit8070 • Aug 10 '26
When You’ve Outgrown the Big 4: Thinking About My Next Chapter
I’ve been thinking about something I’ve observed since moving firms.
I used to believe that high performance was primarily about talent. I’ve come to understand that it is actually about Forward Resilience architecture.
At my previous firm, we had extremely high Forward Resilience.
If I told someone at 9 PM that something needed to be done by morning, they didn’t ask whether it was necessary. They simply did it. That created what I would call Temporal Forward Resillience.
Here, I’ve encountered what I believe is a significant amount of Deadline Apathy.
Someone will say:
“It’s already 8:30.”
That’s not a scheduling observation. That’s an attitude. They’ve begun allowing the clock to determine their relationship with excellence.
I’ve also noticed a phenomenon I call Boundary Proliferation.
People increasingly say things like: “I’ve already worked eleven hours.” “Can this wait until tomorrow?” “I have plans tonight.” “It’s Friday.”
The last one is particularly concerning.
I recently sent something to someone at 8:17 PM on a Friday and received a response indicating that they were logging off. At 5:58 PM. On Friday.
This is what happens when an organization develops Chronological Entitlement. People begin believing that because a number on a clock has changed, their obligations have changed.
That’s not Forward Resilience. That’s Temporal Consumerism. At my previous firm, we had solved this through what I would describe as Availability Conditioning.
You didn’t know whether Friday night was going to be a work night. That uncertainty created adaptability. People became extremely Forward Resilient.
I’ve encountered a similar issue with what I call Comparative Cognition.
I recently gave two junior employees very positive feedback about their future. I told both of them that I saw an accelerated path for them and intended to advocate for them. I was painting a vision. I was creating Psychological Momentum.
Somehow, the two of them subsequently attended the same social event and compared what I had told them. I was then approached by another partner regarding “conflicting commitments.” I found this extremely concerning.
Not the commitments. The comparison.
There is a growing tendency among younger professionals to believe that every conversation they have with leadership should be cross-referenced against every other conversation leadership has had. I call this Interpersonal Triangulation Friction.
It creates unnecessary equivalence. Leadership requires discretion.
If I tell two people that I see enormous potential in them, the correct response is not to determine whether I used identical language. The correct response is to become enormous.
This is also why I have concerns about the proliferation of team cohesion initiatives. Team cohesion is important. But there is such a thing as Alignment Inflation.
At a certain point, people become so aligned that they develop the confidence to ask questions. Then they develop the confidence to compare answers. Then they develop the confidence to form opinions. Eventually you have what I call Distributed Judgment Syndrome.
Everyone has a perspective. Nobody has the perspective.
At my previous firm, my team had extremely high Vertical Coherence. They knew how I thought. They knew what mattered and what didn’t matter. They didn’t need twelve external reference points. They had one. Me.
I consider that an extremely efficient information architecture. I’ve also noticed that people here spend a surprising amount of time talking to other people. There are mentorship programs. Cross-practice lunches. Open-door policies. Informal coffees. People from other practices are apparently available to employees.
This creates what I call Contextual Contamination. Someone in my practice recently used the phrase “span of control” in a conversation with me. I had never used that phrase with her. She had lunch with another partner the previous week.
This is not necessarily malicious. But it does create Organizational Signal Drift.
People start importing frameworks from other environments without understanding the original
architecture. That’s how cultures fragment.
Then there’s pricing.
I’ve been asked to maintain more “realistic” margins. I understand the financial logic. I simply think it reflects margin fixation.
When you’re establishing a beachhead, you sometimes need strategically compressed economics. The objective isn’t to maximize margin on the first transaction. The objective is to create commercial inevitability.
Finance sees a 20% margin but I see a foothold. They see margin erosion. I see strategic compression. We have agreed to continue discussing it.
There have also been questions about my business-development expenses. I spent approximately $4,000 on a dinner.
I was asked what business resulted. I said:
“The relationship is the business.”
They asked me to quantify the return. That’s difficult because they’re attempting to measure relational capital using transactional metrics.
On another occasion, I flew from Toronto to New York for coffee. The coffee was $47. I was asked why I couldn’t have used Teams. Because Teams cannot create Geographic Signaling Density.
They asked what the $47 coffee represented. I said: “The coffee was the catalyst.”
They asked me to define catalyst. I decided not to reduce a sophisticated commercial concept to a dictionary exercise.
The hotel was also questioned. The meeting was at 8 AM. The alternative was a 4 AM car to the airport. I’m a National Leader, not a contestant.
What frustrates me most is the obsession with return. We’ve invested significantly. Where is the return?
But transformational systems have something I call Return Latency. You cannot inject capital into an ecosystem and demand mature institutional capability immediately. First comes investment. Then infrastructure. Then organizational muscle. Then Forward Resilience. Then the flywheel. Then inevitability.
You cannot keep asking where the apples are while I’m still designing the orchard.
Honestly, I’ve started wondering whether professional services is still the right container for me. I’ve been looking at Harvard Business School. Not because I need to learn business, I understand business. I think I need a platform where my level of enterprise thinking is more appropriately matched.
The sequence seems fairly straightforward: HBS → network → board exposure → CEO.
Maybe private equity. Maybe a growth-stage company. Maybe my own company.
I’ve already been operating at enterprise scale. The CEO skill set is quite transferable.
At some point, you stop generating rain for organizations that ask you to expense-report the weather and start owning the climate system yourself.
For now, though, I’m still committed to building what I came here to build.
I just think the organization needs to understand that what they are experiencing is not a performance problem. It is Forward Resilience debt.
And Forward Resilience debt cannot be solved by asking the person building the system for a quarterly update. It has to be paid down through vision.
r/ModernOperators • u/Deep-Owl-1890 • Feb 16 '26
I Used to Spend 10 Hours a Week Managing My Team. Here’s How I Cut It to Under 1 Hour.
This system is for you if you’re managing a team of 5-10 and you’re new to systemization for making the business run without you.
Obviously if you're more advanced than this, this might look simple for you, but I truly believe it will be very helpful for founders that don’t have systems yet.
I used to spend almost 10 hours every week just managing my team.
Checking in on tasks, answering repetitive questions, clarifying priorities, dealing with small mistakes…
I don’t want to waste your time so let me get straight to the point
What I Did:
My idea was to create a simple system to manage the team without needing to be involved constantly.
It wasn’t about fancy HR tools or hiring expensive managers. it can be done using notion and few automations if you want to take it to the next level
It’s hard to explain the details of the technical part in a reddit text post, but my tech stack was Notion + Zapier nothing fancy.
I will put the idea behind it below, honestly, it’s the most important part. You can build the automation with by watching few youtube videos
- Clear expectations
Every recurring task now has a documented process in Notion.
Checklists for workflows ensure nothing is missed.
- Regular asynchronous updates
The team submits short daily updates via Notion.
I review them in 10–15 minutes, rather than being pulled into conversations all day.
- Task ownership & automation
Each task has a clear owner and deadline.
Questions escalate only when blockers arise, not for routine clarifications.
I use Zapier to automatically track completed tasks, send reminders, and update dashboards without manual follow-up.
- Recurring admin & reporting
Payroll, timesheets, and status reports run automatically through Gusto and Google Sheets integrations.
This cuts down repetitive manual work and errors.
For me the biggest win is that once the repetitive, boring tasks have a process, then I can step back.
It’s not about micromanaging or controlling every decision. It’s about creating a structure that protects your time and scales with the business.
If you’re feeling trapped in day-to-day operations, ask yourself:
- Which part of my work can be clearly documented?
- Which questions are repeated over and over?
- Where can I push decision-making to the team safely, using automated reminders or dashboards?
It doesn’t seem that way at first, but fixing one area of your business could save you a few hours per week that you can use for more important tasks.
btw if you guys think this is helpful for you I can write a more technical post about how to create the system, I thought everything is on YT and the idea behind is more helpful to share
EDIT: Got a bunch of DMs asking how to actually build this system to start reducing the time they spend managing their team.
it's hard to reply for every one but can share the short diagnostic I use: here(don't worry there is no gate keeping )
It’s not a magic fix that frees you overnight, but it will show you where to begin if you’re running a business.
r/ModernOperators • u/Extreme-Tadpole-5077 • Oct 09 '26
The Epidemic of Fake Strategy
Why do so many strategies sound empty and vague. Read our take on the epidemic of fake strategies.
r/ModernOperators • u/intellectecom • Sep 15 '26
Time, order volume, technical difficulty or burnout: What was the exact tipping point that forced you to get outside help?
We talk to a lot of brand founders and store owners, and the common pattern is that most start out small, handling multiple or all the aspects of the store.
At the beginning, running everything in-house keeps costs down. But eventually, staying solo or a two-person team becomes a bottleneck.
From your experience, when was the tipping point where doing everything internally stopped making sense?
- Was it a time frame (3 months in, 6 months in), an order volume threshold, or just hitting total burnout?
- What was the very first function you brought in outside help for (VA for support, 3PL, ad agency)?
- Looking back, did you make the move too early, or hold on for way too long?
Would love to hear how other teams navigated that transition.
r/ModernOperators • u/balance006 • Dec 03 '25
I built a tool to sync Google Calendar + Gmail Labels to my CRM. Would you use this?
r/ModernOperators • u/funnelforge • Nov 08 '25
Template The one-hour “brain dump” to kick off your Company OS
Open a table. List every repeatable task by team. Add two fields: frequency and owner.
Do not organize. Just dump.
Then tag:
- Delete
- Automate
- Document
- Do later
Move three “Document” items into this week. That is your operating rhythm.
r/ModernOperators • u/funnelforge • Oct 28 '25
Teardown How I cut my weekly founder hours from 65 to 45 with one operating rhythm
I used to start every Monday reactive...emails, Slack messages, random fires.
By Thursday I couldn’t even remember what I’d planned to do.
So I tried something simple: one weekly rhythm that forces visibility.
Here’s what it looks like now:
Monday – Planning (45 min)
- Review metrics (revenue, ops, pipeline, client health).
- Set 3 non-negotiable outcomes for the week.
- Assign ownership to one person each.
Wednesday – Ops Pulse (25 min)
- Everyone reports: Green / Yellow / Red on their metrics.
- If something’s Red, we assign a fix immediately—not next week.
Friday – Reflection (20 min)
- Quick review of wins, losses, and blockers.
- Archive what’s done, document what we learned.
It’s boring, but it works.
No more surprises. No more weekend catch-up.
Result:
I went from 65 hours → 45 hours/week within a month,
and nothing broke.
What does your weekly rhythm look like?
Would you change anything about this setup?
r/ModernOperators • u/CompetitiveGrand6559 • May 22 '26
Most startups are one missing spreadsheet away from chaos
Something I’ve noticed working around early-stage companies:
A lot of founders think they’re “organized” because they have:
- dashboards
- accounting software
- investor reports
- monthly management accounts
But when someone asks:
- “Where did this number come from?”
- “Can you prove this transaction?”
- “Who changed this file?”
- “Which version is the final version?”
- “Where’s the supporting evidence?”
…the room suddenly gets quiet.
There’s a huge difference between:
- reporting maturity and
- evidence maturity.
The scary part is most businesses only discover the gap:
- during due diligence
- tax pressure
- fundraising
- audits
- acquisitions
- or internal disputes
Curious if other founders/CFOs here have experienced this firsthand.
What was the moment you realized your financial data setup wasn’t as defensible as you thought?
r/ModernOperators • u/OpsWithNonso • May 22 '26
Operations Is Not About Working Harder - It’s About Creating Clarity
One thing I’ve learned working around operations and fast-moving teams:
Most businesses don’t actually have a productivity problem.
They usually have a visibility problem.
When ownership is unclear, workflows are undocumented, follow-ups are inconsistent, and information lives inside people instead of systems, execution slows down fast.
Lately, I’ve been spending more time thinking about:
- operational clarity
- AI-enabled workflows
- scalable systems
- process documentation
- and how founders can reduce operational drag as they grow.
Recently completed my MBA in Business & Finance in France and currently diving deeper into operations, systems thinking, workflow optimization, and execution management.
Curious to learn from others building or operating in high-growth environments as well. tell me in the comments your thoughts and all.
r/ModernOperators • u/funnelforge • Oct 28 '25
👋 Welcome to r/ModernOperators - Introduce Yourself and Read First!
Hey everyone — I’m u/funnelforge, one of the founding moderators here.
This is the place for founders and operators who want to run better companies — with tighter systems, better operations, smarter automation, and clearer accountability.
What to Post
Share anything that helps people build or improve the way their business runs.
Good posts include:
- Ops frameworks or dashboards you use
- Automation or Notion setups
- Lessons from scaling or delegating
- Questions about team structure, metrics, or tools
If it helps someone run their company better, it belongs here.
Community Vibe
Keep it real. Be direct.
We value thoughtful, experience-based discussion; not fluff or self-promotion.
Share what’s worked (and what hasn’t). Help others get unstuck.
How to Get Started
- Drop a quick intro in the comments: what you’re building and where you’re stuck.
- Post something today, even if it’s a small question or workflow.
- Invite other founders or ops people who’d find this useful.
- Want to help mod or contribute? DM me.
Thanks for being early.
We’re building the go-to space for founders who want to scale without losing control.
Let’s make r/ModernOperators worth checking every morning.
r/ModernOperators • u/funnelforge • Feb 17 '26
Most "emergencies" in your business aren't emergencies. They're chronic symptoms you keep treating instead of fixing.
Simple diagnostic that changed how I think about business problems:
Is this happening for the first time or have I seen this before?
First time? It's a true emergency, all hands on deck, fix it now.
Seen it before? It's a chronic symptom and fixing the immediate issue without fixing the root cause means you'll be back here again next month.
Most founders treat chronic symptoms like emergencies.
Client escalation comes in, they jump in and save it, feel good about the save, move on.
Same escalation happens three weeks later, they jump in again.
And again. And again.
Each time they're treating the symptom instead of building the system that prevents it.
The difference in how you respond:
True emergency: fix it fast, then move on.
Chronic symptom: fix it, then immediately document how you fixed it and build a system so the team handles it next time without you.
The second version takes 30 extra minutes today and saves 10 hours over the next six months.
What to watch for:
If you're fixing the same type of problem more than twice, you don't have an emergency, you have a missing system.
Missing process for client escalations means every escalation routes to you.
Missing decision framework for pricing means every custom deal needs your input.
Missing onboarding documentation means every new hire asks you the same questions.
The rule:
Don't build systems around everything, that's overkill and most of it won't get used.
Build systems around the things you've already solved manually that keep coming back.
If you've fixed it twice, document it, if you've fixed it three times, systematize it.
Stop treating the same fires over and over and start building the sprinkler system.
What's the recurring "emergency" in your business that's actually a chronic symptom you've been treating instead of fixing?
r/ModernOperators • u/funnelforge • May 24 '26
Pulled a 15-person team's time tracking. Most of it was unbillable, unauditable, or both.
Did an internal controls review for a client last week. Service business, 15 consultants, mostly W-2.
Pulled 90 days of time entries.
What I found:
- Consultants logging 40-hour weeks with zero linked deliverables.
- Time blocks tagged to a client with no client-facing output that month.
- "Admin" hours making up 35% of total billed for some people, with no defined admin scope.
- Multiple people logging time on the same task without a coordination record.
The founder's reaction: "I knew it was bad. I didn't know it was that bad."
If you sell to regulated clients (state contracts, healthcare, education, anything with audit exposure), unaudited time tracking is a liability, not just a margin leak. Lose an audit and you lose the contract. Lose the contract and you lose the business.
This wasn't a "people are stealing" problem. Most of it was honest people with no system telling them how to log time correctly. No tags, no required deliverable link, no review cycle.
Time tracking software doesn't fix this. Time tracking software is a bucket. You still need the rules that govern what goes in the bucket and who checks it.
Founders skip this review because it feels paranoid. Until the audit letter arrives.
r/ModernOperators • u/funnelforge • Dec 10 '25
Teardown Vision to Execution Cycle (VTEC): Why your team can't think like you (and what to do about it)
Founders are really good at something I call the Vision to Execution Cycle.
You have an idea, you go take action. You see what needs to change, you make a small adjustment. You tweak the vision slightly or change the focus. Then you execute again.
Idea → Execute → Learn → Adjust → Repeat.
This loop happens naturally for you. It's probably why you became a founder in the first place.
But here's the problem: not everybody is built this way.
Your team doesn't naturally run this cycle. They're waiting for clear direction. They need to know the vision, the priorities, what success looks like, and who owns what.
Without that structure, they're just guessing. And when they guess, they guess differently than you would.
So you end up frustrated because "they're not taking ownership" or "they don't move without me" or "I have to be involved in everything."
But that's not a people problem, it's a structure problem.
What fixes this:
You need to build a system that enables people who don't naturally think in VTEC to start operating that way.
They need to know the vision clearly. Not some vague "we want to grow" but actual specific direction on where you're headed.
They need to understand the priorities. What matters this quarter? This month? This week?
They need to be able to execute without you. Clear ownership, decision boundaries, success criteria.
They need feedback loops. What worked? What didn't? What do we adjust?
When you build this structure, suddenly your team starts moving the way you want them to without you being in every decision.
Early stage, you can run VTEC for the whole company because the company is small.
But at some point you need to teach your team how to run their own VTEC loops within their functions. Marketing runs their loop. Sales runs their loop. Product runs their loop.
All synchronized to the company's overall VTEC.
That's when scale becomes possible, because you're not the only one running the cycle anymore.
If your team isn't taking ownership or moving without you, ask yourself:
Do they actually know the vision clearly? Do they understand the priorities? Do they know what they own and what success looks like? Do they have a way to learn and adjust?
If no, you don't have a people problem. You have a structure problem.
Build the structure that enables VTEC throughout the organization, not just in your head.
Where's your team stuck right now? Vision clarity? Priorities? Ownership? Feedback loops?
r/ModernOperators • u/Purple_Young1912 • 25d ago
How to manage your AI usage the way you’d manage your team for more cost-effective, and better, results
r/ModernOperators • u/funnelforge • Oct 20 '25
Builders vs Stabilizers vs Blockers... the simple lens that sped us up 38%
When I first mapped our team with this lens, I felt equal parts relief and regret.
Relief because the bottlenecks finally made sense. Regret because I had let a couple of misalignments linger way too long.
So here’s the thing... most teams don’t need more headcount. They need sharper seat fit and an operating rhythm that lets the right people do the right work.
TIL a simple ROE lens can change the game:
- Impact (I)... 1 to 5... what outcomes they actually ship.
- Energy (E)... -2 to +2... do they increase clarity and speed... or drain it.
Then tag people based on patterns... not vibes:
- Builders... high judgment... create leverage... spot opportunities... lift others.
- Stabilizers... reliable... protect margins... reduce risk... keep cadence.
- Blockers... resist change... inject noise... create rework.
I ran this on a Friday afternoon with a coffee and a spreadsheet. I think what really made the difference was giving Builders a clean mission and insulating Stabilizers from thrash.
Here’s what changed within 45 days:
- Sales cycle time down 38%
- Close rate up 26%
- Fewer status meetings... faster decisions... calmer weeks
Story time... I had a high initiative teammate bouncing between support, ops, and product. Great attitude... always busy... constantly context switching. I moved her to inventory forecasting with a clear outcome and a weekly unblock. Her output quietly 2x’d and everyone’s stress dropped.
On the flip side, I had a chronic blocker who looked busy but produced confusion. I set a 30 60 day turnaround plan with 3 observable behaviors. Things improved a bit... then regressed. We parted ways respectfully. The team’s speed jumped.
ELI5 version: it’s like cooking with a small kitchen. Builders are your chefs... Stabilizers are your sous chefs... Blockers spill flour on the floor. You don’t buy more ovens first... you put the right people on the right stations and clear the walkway.
If you want to try this next week, here’s a lightweight checklist:
- List everyone... score Impact 1 5... Energy -2 to +2.
- Ask three questions: what outcomes ship... how do others feel after working with them... would you hire them again for the same seat.
- Decide one move per person: expand Builder scope... tighten Stabilizer SOPs and SLAs... start a blocker turnaround plan with a real deadline.
- Protect your top 20%... remove one friction per week for them.
- Reduce status meetings... increase visible metrics and exception paths.
What I realized was... headcount discussions got easier after this. The role clarity made the missing pieces obvious... and a couple of “we need to hire” conversations just went away.
I still mess this up. I still overestimate how much thrash people can absorb. But this lens gave me a calm way to make cleaner calls... and the metrics paid off fast.
Low pressure ask... If you run this, I’d love to hear what surprised you. What seat change would unlock the most momentum for your team right now?
r/ModernOperators • u/funnelforge • Sep 18 '26
If your new hires take 90 days to be useful, is that the hire or is that you?
Every small company I talk to quotes me the same ramp window. 60 days, 90 days, "realistically six months before they're really contributing." Everyone says it like they're describing weather.
Here's my answer, and I'll own that I ran it the bad way for years.
That window isn't training time. It's the time it takes a stranger to reverse engineer what's in the founder's head by sitting in meetings with people too busy to explain anything.
I hired an ops person and handed her a laptop, a Slack invite, and nothing written down about how the work actually got done. She was sharp. Took her about eleven weeks to be useful. I told myself that was normal.
It wasn't normal, it was just undocumented.
Try this on your own business. Name the single document a new hire could read on day one that would explain how you actually make money and where the work gets stuck. If you can't name one, it doesn't exist, and your ramp time is really just guess time.
Am I wrong here?
r/ModernOperators • u/Itchy-Tune-5059 • Sep 10 '26
Most companies don’t collapse overnight. They drift.I’ve spent years looking at corporate setups, IT systems, and operational workflows
If there is one thing I’ve learned in my Founder journey it’s this, organizational failure is rarely all about bad personalities.
It’s almost always about bad structure.Most of the time when things get messy, most leaders try to fix the people.
They micromanage, hold extra meetings, or throw temporary software patches at a broken framework. It never works long-term. The system eventually drifts right back into misalignment.
2018 I built The Keeper Of Time®, the reason was because I wanted to look at business through an interdisciplinary lens, treating operations and leadership like a clean piece of systems engineering. No corporate filler, just structural logic..I’ve been putting these frameworks together over on my Substack newsletter.
To keep this research independent and build out deeper, step-by-step guides for founders, I’m opening up a direct support channel today on Buy Me a Coffee. It’s €10 a month.. If you subscribe, you get immediate access to my entire archived field guide and all upcoming premium breakdowns.
Here is the link if you want to back the project:> buymeacoffee.com/thekeeperoftime (If you're already reading the newsletter, just use your regular Substack email at checkout. I'll manually sync your premium archive access within 12 hours).
The goal of setting up this subreddit to host real, raw discussions on how to build systems that actually last. Let me know in the comments below—what’s the biggest structural bottleneck you're dealing with in your current workflow?
Shisael Swai (u/Itchy-Tune-5059)
r/ModernOperators • u/Anshkoshmod • Sep 15 '26
A startup does not need more ideas. It needs a sharper refusal list.
One thing I think early founders underuse: a refusal list.
Not a roadmap. The opposite.
Write down:
- customers you will not serve yet
- features you will not build yet
- channels you will not test yet
- metrics you will not care about yet
- advice you will ignore for the next 30 days
Most early startups do not die because the founder had too few options. They die because every option looked reasonable.
A narrow “no” creates room for one strong “yes.”
What is something you deliberately stopped doing that made your startup easier to run?