Back to all writings
EssayFeatured

Machine First, Then People

Why strong organizations tend to build systems first, then find people who fit the system, keeping it stable as new people arrive.

Amhar M. ArifinAmhar M. Arifin
7 min read
Categories:essayleadershipbusiness
Machine First, Then People

Machine First, Then People

When employee retention drops dramatically, the spontaneous reaction is almost always the same: loosen deadlines, lower quality standards, give more personal leeway. The common recipe for organizations panicking about losing talent.

Many founders immediately give in. There's a more effective approach, though it sounds counterintuitive.

Ray Dalio, founder of Bridgewater Associates, wrote in Principles: "Don't bend the machine just to keep people. Design the right machine, then hire people who fit inside it."

The focus is on system consistency. Organizations that keep changing their operational principles to accommodate every individual end up having no principles at all: just a collection of clashing personal preferences.

Many founders do the opposite. They recruit people first, then twist culture and processes to be comfortable for each individual. Sounds people-first. The end result is a patchwork culture that's hard to scale.

The Trap: People First, Machine Later

The pattern repeats. You recruit the most impressive candidate available: mature experience, impressive portfolio. A few weeks later they're uncomfortable with meeting transparency. You give in: evaluation meetings become closed. The next hire refuses structured feedback. You give in again: feedback becomes informal and ad hoc.

Three years pass, the organization feels like a patchwork quilt. Standards shift following whoever's most vocal. New people are confused because the rules change depending on who they're talking to.

That arrangement is a collection of individual preferences wearing the costume of a system. While the team has ten people, the founder can still patch inconsistencies. Once the team exceeds fifty, every patch turns into chaos.

Compare with the opposite approach: document the system first. Radical transparency must be enforced. Believability-weighted decision making is mandatory. Five-step problem-solving process must be followed. Then recruit people who can live comfortably within it.

Some top candidates might withdraw from the start. And that's good. They wouldn't have lasted anyway. Better to know before accepting an offer than mutual frustration six months later.

Bridgewater: 30-40% Resign, and That's Intentional

Bridgewater Associates, the hedge fund managing over $160 billion USD, has a reputation: 30-40% of new employees resign within the first 18 months. This fact is actually part of the design.

Ray Dalio built a machine called radical transparency. All meetings are recorded. Feedback is given openly and bluntly. The Dot Collector app provides real-time ratings for every comment. Opinion weight follows track record.

This system is emotionally draining. Your ego is challenged every day. There's no hiding from facts. No politics to pass without contribution. Only those who can separate truth-seeking from feelings survive.

Dalio keeps the machine intact even when people leave. When someone quits because they can't handle it, Bridgewater holds transparency steady and clarifies the rules during onboarding so misalignment shows up quickly.

The result: those who stay are truly aligned. Culture remains consistent even as the organization grows beyond 1,500 people. Decision quality is high because everyone plays by the same guidelines. New employees adapt quickly because the system lives in clear documentation, with no need to reconstruct it from oral history.

Organizations that constantly adjust systems for every dissenting voice might record high employee retention on paper. Culture becomes blurry. Standards shift. Work quality is hard to predict. Scalability becomes a nightmare because there's no reliable map.

Build the machine you believe in. Find people who fit that machine. Try not to bend the machine just for retention numbers.

Implementation Example: From Retention Crisis to Stability

This pattern is visible in many organizations that successfully survived retention crises. Instead of loosening standards, they actually clarified operational systems. The key steps are the same: total audit of operational principles, then document core principles that must be enforced.

Examples of principles that often emerge:

  1. Transparency isn't optional. All evaluation meetings are recorded and accessible to the team.
  2. Feedback weighted by track record. Anyone can criticize, but weight follows track record in that domain.
  3. Decision journal mandatory. Every important decision is recorded: reasoning, data, expected results.
  4. Meetings focus on data. Discussion starts from insights backed by evidence, with wild opinions left at the door.
  5. Value-based pricing. Price sourced from value delivered, with hours worked treated as an internal metric.
  6. Complex tasks require SOPs. No "just remember it".

Principles like these become operational standards: daily work methods enforced consistently, kept alive long after the document is signed.

Effect on Team

When an organization finally documents its operational principles clearly, three responses usually emerge:

  1. Core team breathes a sigh of relief. They've already been working with those standards. Documentation makes expectations explicit.
  2. Some people ask: "Are we this strict?" They need time to adjust.
  3. Some people realize this isn't their path. They choose to move to a more suitable environment.

The last one is actually proof the system works: people who don't fit realize it faster, before both parties experience prolonged frustration.

Organizations that successfully pass this phase usually see a change in team composition: employee retention might drop temporarily. Those who stay are truly aligned. Feedback flows more bluntly. Conflicts about standards drop drastically. New employee onboarding is much faster because the rules are clearly documented.

How to Build a Machine That Attracts the Right Talent

1. Document Core Principles That Must Be Enforced

Write down your ideal working method: how to make decisions, how to give feedback, how to determine priorities, how to measure performance. Make sure these principles are already being practiced with your core team; documentation tidies up what already lives in the team, with no power to install behavior that has yet to take root.

2. Test with Current Team

Share the document with the entire team. Ask them to give concrete examples: when these principles were applied, when they missed. Discuss honestly.

  • If it fits: They feel clarified. They know how to succeed in the organization.
  • If it's heavy: Help them understand the context. Evaluate whether they can adapt or actually need a different environment.
3. Recruit for Alignment Alongside Skills

Include these core principles in the recruitment process from the start. Don't wait for contract negotiation sessions.

Example questions:

  • "We give feedback openly. What's your experience with systems like this?"
  • "Opinions here are weighted by track record. If you're new to a certain domain, your voice has less weight. Do you think that's fair?"
  • "When rushed, we still run the complete decision process. Does this structure help or feel rigid?"

Honesty is what matters here, far more than the surface of "yes" or "no" answers. Better to find misalignment before signatures, with mutual relief, than to suffer for half a year together.

4. Don't Weaken the Machine Under Pressure

The biggest temptation comes when retention numbers drop or clients demand "exceptions." Remember: every exception sends a signal that rules are negotiable.

The system can change if data shows there's a design flaw. What often happens is lack of courage to enforce principles. Consistency is the fuel for long-term trust.

Closing: Clear Machine, Right People

Big organizations rest on a different question than the tired choice between "people-first" and "results-first." The real question is: do you have a crystal-clear machine or a machine that changes following whoever's loudest?

A clear machine protects people. Explicit standards make feedback feel fair. Documented processes speed up onboarding. Clear principles make decisions predictable.

A blurry machine makes everyone anxious. It's unclear if someone's performing well. Feedback feels one-sided. Promotions become political. Culture turns into a survival arena.

Build the machine first. Document core principles that must be enforced. Test with the team. Recruit for alignment. Maintain discipline when pressure comes.

Bridgewater loses 30-40% of new employees. Those who stay are truly aligned. Many other organizations experience similar patterns: employee retention drops temporarily when systems are clarified. The ending is a far more solid and scalable team.

A small team that is genuinely aligned with the machine usually outperforms a large team with half the members in the wrong place.

Machine first, people second. It can sound cold, but this is arguably one of the most respectful approaches for all parties: those who stay know their expectations clearly; those who leave find more suitable environments. Clarity is kindness.

amhar
Loading...