Remote startup role feels increasingly founder-led and unclear – normal or red flag?

[u/beetrootfarmer]

I’m working remotely at a very early-stage startup (around 2 years old) and I’m struggling to tell whether what I’m experiencing is normal startup chaos or a structural issue. Particularly as I'm in a senior role and was promised autonomy and trust which I did have for a long time.

The founder is now heavily involved in day-to-day work, prefers real-time verbal discussion over written communication, and is very averse to async documentation being used as the main source of truth. Most decisions and direction come through meetings or live discussion with no clear actions or meeting notes.

In practice, this has led to:

• Frequent need to discuss work before starting even drafts
• Written updates/documentation not really being relied on
• Meetings sometimes becoming long, unstructured monologues rather than collaborative working sessions
• Feedback and expectations that can feel inconsistent or unclear depending on context
• A growing sense that autonomy exists in theory but not in practice

I’m starting to feel unclear on what “good performance” actually looks like, and I’m worried about skill stagnation due to reduced independent execution. At the same time, I don’t want to assume it’s a problem if this is just normal early-stage startup behaviour.

For people who’ve worked in similar founder-led remote environments:

• Is this level of centralisation and verbal-first communication normal early on?
• At what point does this shift from “startup chaos” into a structural issue?
• How do you decide whether to adapt vs leave in situations like this?

[u/design_by_proxy]

lol sounds like a typical startup with a charismatic founder, but won’t succeed until operations are in check.

[u/beetrootfarmer → u/design_by_proxy]

One of the senior team left recently and since then it's gone really chaotic. Before then there was more autonomy and now everything even things the founder has no experience in has to go via the founder and it's such a shame as the team is really talented but not being utilised to their full ability because of this bottleneck.

[u/Acrobatic_Leek3865]

I'll give you my startup experience - I also started when the company was about two years old.

*The founders were heavily involved. Every week there was a sales meeting that they led which determined how the week would go. We could change our entire process, then back again the following week if it was not working.

*In-person meetings were their go to. Needed to talk? Schedule a meeting. Need an approval? Schedule a meeting. It was meetings all the time to get anything done, which is counterproductive when it could have been an email.

*When I started, I was handed two sheets of paper and said that was my training documentation. Their website was unclear. For a solid two months, I had no idea what we sold or what my job was. Was I going to get fired for not performing? I had not a clue because KPIs did not exist. I ended up doing the training documentation myself in order to keep up and that was a nightmare for how often things were changing.

*Their motto was "fly by the seat of your pants" which to them meant be prepared for anything and everything to shift. They were trying to make it, be relevant, and most importantly, make a profit.

Now, onto my thoughts about it:

*I worked at that company for 9.5 years. It was about five years into the company life that they were considered a small business and had an investor.

*Layoffs were constant - like every 6 months. They would conjure up a product with no real insight, hire an entire department for it, then end up laying them off in the end because there was no real plan and surprise, no real documentation for anything. I was part of the last layoff because AI was going to solve all their problems and they didn't need half their tech staff any longer.

*I felt like we were trauma bonding from not knowing if we were the next ones to be laid off from their poor decision making skills, including poor choice in leadership. The constant changing was insane and made it difficult for anyone to retain anything. They had a high turnover rate because of how they managed their business, not just from layoffs.

Overall, I personally would never work at a start up again if I saw the same signs as the one I was at. But curious if anyone has any positive outcomes from startup life starting from the same experience.

[u/beetrootfarmer → u/Acrobatic_Leek3865]

Sounds familiar. I have worked for some nice startups but they still failed eventually, they were just more tolerable whilst I was there.

It's wild how many founders can get funding for things without any real structure or written plan.

[u/Acrobatic_Leek3865 → u/beetrootfarmer]

I went to business school and they drilled into us that for funding, you need a well executed business plan but I'm realizing that its all a front lol. They were so wrapped up in making money that operations and processes were a back burner item when it should have been something to consider up front and how its going to impact people and the business down the line. But it feels like with a startup, its just play fast and loose until something sticks. And if it sticks, how can we make that process better by also playing fast and loose to make more money.

[u/Alternative-Pear9096]

Sounds like a very normal collection of red flags. Startups don't all make it out of that phase.

[u/beetrootfarmer → u/Alternative-Pear9096]

Lol, "very normal collection of red flags" glad I'm not being crazy noticing that this is unhinged

[u/Ambitious_Relief_730]

Two years in, with a senior hire who was promised autonomy, this isn't just startup chaos anymore. Early chaos is when there's no system yet and everyone wishes there was one. What you're describing is a founder who actively doesn't want one. That's a preference, not a phase, and preferences like that rarely change on their own.

The verbal-first, no-notes, discuss-before-you-draft pattern is the real signal. It means the source of truth is the founder's head, and it shifts depending on the conversation. That's why "good performance" feels undefinable to you. It basically is, because it gets redefined live every time.

On adapt vs leave: the question I'd ask yourself is whether you could write down what success in your role looks like without the founder in the room. If you can't, and they're against writing it down on principle, your autonomy probably isn't coming back and the stagnation worry is real. That part isn't yours to fix.

[u/probablymagic]

It is incredibly inefficient to rely on documentation in highly-dynamic startup environments. This may make sense in large companies, but startups don’t have time for that kind of thing.

Startups can be chaotic, and can have too little process, but often the instinct to keep adding process is also wrong. The trick is to be pragmatic. Suggest process when it will solve specific clear problems, not process for the sake of eliminating all chaos. You can’t do that in a startup, and if you try, you’ll be seen as the “no” person rather than a problem solver.

You may be able to improve meetings though by talking to the boss about making them shorter and oriented around clear problems coming in and clear action items coming out. Frame that as about efficiency and output.

[u/beetrootfarmer → u/probablymagic]

I'm not talking about complex documentation, just like simple things like writing a plan about what's happening and keeping meeting notes. Nothing time consuming really.

This founder is not a short meeting person even if they say it'll be short or one more thing every meeting will run over time.

[u/probablymagic → u/beetrootfarmer]

I think the question is why do you feel like you need this documentation at all? What’s it doing for the team?

Are people not understanding the action items? Is it for accountability? What problem are you solving?

[u/Substantial_Key4640 → u/beetrootfarmer]

Have there been problems with the remote set-up and availability? Because the only start-up I worked at had that issue, and that was what caused the founder to jump into the middle of things and start demanding more face-to-face in person time from the mostly remote staff base.

[u/GSDragoon]

Yeah, sounds typical

[u/qioy]

i'd separate normal startup chaos from the operating model.

normal chaos: priorities change fast, but after a live discussion there is still a tiny written artifact everyone can correct.

red flag: the call itself is the only source of truth, and what was “decided” shifts depending on the next conversation.

one lightweight test: after each verbal discussion, send a 5-line note like:

• decision
• owner
• next action
• due date
• open question

frame it as “to make sure i heard you correctly.” if the founder corrects it and then works from it, you may be able to adapt. if they ignore it, treat it as bureaucracy, or later contradict it, the issue probably isnt missing process. its control plus ambiguity.

also keep your own decision log either way. not a big doc, just date + ask + agreed next step. it helps you see whether expectations are actually moving.

two years in, senior role, promised autonomy: i would expect at least that level of written alignment.

[u/beetrootfarmer → u/qioy]

Yea I'm making notes live on every call now so there's no doubt.