Moving Beyond Case-by-Case Without Going Corporate

Over the past few years, remote work has become the norm for many startups; whether fully remote, hybrid, or flexible by design. At the same time, a growing number of large organizations and public institutions are now pushing employees back to the office.

This shift has created confusion for many founders. Some are questioning whether they should follow suit. Others are trying to strike a balance, adjusting expectations as they go. In many cases, remote work decisions are being made on a “case-by-case” basis with the intention of staying flexible while avoiding heavy rules.

It usually starts with good intentions. But over time, this approach tends to create more problems than it solves.

Often, the issue isn’t whether work happens remotely or in the office, but rather the lack of clarity around how decisions are made.

The return-to-office push and why startups feel the pressure

When large employers and governments announce return-to-office mandates, it sends a strong signal. Even if their realities are very different, startups feel the ripple effects.

Founders start asking:

• Are we too flexible?
• Will remote work hurt performance or collaboration?
• Are we sending the wrong signal as leaders?

The mistake many startups make is assuming that what works for large organizations should automatically apply to them. In reality, the reasons driving return-to-office decisions in large, complex institutions (such as real estate commitments, political pressure, or uniformity at scale) are often very different from the realities of early-stage companies.

For startups, the challenge is not choosing sides in the remote-versus-office debate. It’s deciding how to manage flexibility in a way that is fair, clear, and sustainable.

It’s also important to remember that, for many startups, remote work isn’t just a policy choice:  it’s a strategic advantage. Flexibility allows startups to attract top talent they might not otherwise be able to compete for, especially when compensation budgets are tighter. In many cases, startups also don’t have offices at all, or choose not to because of the cost. 

Remote work isn’t a trend to reverse, it’s often a core part of how startups operate and grow.

Why “case-by-case” decisions feel right … at first

Managing remote work informally can feel like the most human and pragmatic approach, especially in small teams.

• Everyone knows each other
• Needs feel unique
• Trust feels personal
• Formal policies seem unnecessary or “too corporate”

In early stages, decisions are often made based on context, relationships, or intuition. For a while, this works. Until it doesn’t.

As teams grow, informal decision-making becomes harder to justify, harder to explain, and harder to apply consistently.

___________

Where “case-by-case” remote work starts to break down

1. Perceived unfairness

Even when decisions are made in good faith, employees compare. When some people are allowed more flexibility than others without clear criteria, questions naturally arise:

• Why is this allowed for them but not for me?
• Is this about performance, seniority, or personal preference?

This becomes especially sensitive when employees see headlines about return-to-office mandates elsewhere. Without a clear framework, decisions start to feel arbitrary rather than intentional.

2. Pressure on managers

When there’s no policy, managers become the policy.

They are expected to:

• Make judgment calls without guidance
• Explain and defend decisions repeatedly
• Navigate emotional reactions

For first-time managers, this is particularly challenging. Over time, this leads to inconsistency, discomfort, and decision fatigue.

3. Difficulty scaling

What works for five people rarely works for twenty-five.

“case-by-case” decisions don’t scale because:

• New hires don’t know what to expect
• Some managers interpret flexibility differently
• Leadership keeps revisiting the same conversations

Instead of being a strategic choice, remote work becomes a recurring source of friction.

4. Misalignment and risk

Without clear rules, remote work can quietly affect:

• Availability and responsiveness
• Collaboration norms
• Performance expectations
• Team cohesion

When expectations aren’t explicit, people fill the gaps with assumptions; and those assumptions rarely align across a growing team.

___________

What startups actually need in a remote work policy

A remote work policy doesn’t need to be long, rigid, or legalistic. It also doesn’t need to mirror what large organizations are doing.  What startups really need is shared clarity.

1. Clear eligibility criteria

Not everyone needs to be treated identically. But everyone should understand the rules.

A simple policy should clarify:

• Whether remote work is available to all roles
• Differences between remote, hybrid, and in-office expectations
• Any conditions related to performance, role, or business needs

Clarity provides a baseline, even when exceptions exist.

2. Expectations around availability

Remote work often fails not because of where people work, but because expectations are left unspoken.

A good policy addresses:

• Core working hours
• Response time expectations
• Meeting norms
• Time zone considerations

This is especially important when teams are distributed and leadership visibility is reduced.

4. A shared reference point

A policy creates a common language. Instead of saying, “It depends,” leaders can say: “Here’s how we approach remote work as a company.”

That alone reduces uncertainty and tension.

_____________

What startups don’t need

❌ Overly detailed rules

• Policies that attempt to anticipate every scenario quickly become outdated and ignored. 
• Remote work policies should guide decisions; not replace judgment.

❌ Copying large organizations

• Startups don’t need to replicate return-to-office mandates designed for thousands of employees. 
• Their strength lies in adaptability, not uniformity.

❌ Silence

• Avoiding the topic altogether leaves room for assumptions; especially when external messaging around remote work is noisy and contradictory.

__________

The real purpose of a remote work policy

At its core, a remote work policy is not about location.

It’s about:

• Fairness
• Trust
• Consistency
• Clear expectations

In a context where remote work norms are shifting and debated publicly, clarity becomes even more important.

Final thought

Remote work doesn’t fail because startups are too flexible. It fails because flexibility isn’t clearly defined.

As larger organizations push employees back to the office, startups don’t need to follow blindly. They need to be intentional.

Moving away from “case-by-case” decisions toward a simple, thoughtful remote work policy is one of the most effective ways to reduce friction, support managers, and strengthen trust, without becoming “too corporate.”

Structure, when done right, is not the opposite of flexibility.  It’s what allows flexibility to last.