Building trust as the foundation of happy, motivated teams

Executive overview

Employees today can take their skills anywhere — the balance of power has shifted. Companies that rely on surveillance and rigid policies lose the best people to those that don't.

The antidote is radical trust: treating employees as partners, not hired guns. This means flexible schedules, transparent financials, and results-based accountability instead of hours-based policing.

Trust is not naivety. It converts the management question from "are they working?" to "what are they producing?" — and bad actors become visible faster, not slower.

Trust isn't a perk — it's the structural reason high performers stay and give discretionary effort.

Flexible work policies in practice

• Drop fixed hours; ask employees to set schedules that work for them, their team, and customers — in that order.
• Flexible vacation ≠ unlimited vacation. Give a rough anchor (e.g. "most people take ~3 weeks") and let individuals calibrate.
• Coordinate vacation at the team level, not through manager approval — the manager rarely knows the team's sprint status.
• Flexible schedules generate reciprocal flexibility: people who own their hours will work evenings and weekends when the situation requires it.
• One-size-fits-all policies punish everyone to guard against the minority who would abuse them.

Transparency as a trust mechanism

• Share financials, strategy, and bad news with employees the same way you'd share with co-founders.
• Employees who see the numbers become more business-literate and stop defaulting to "just add headcount."
• When bad news is hidden and later surfaces, trust is broken — often worse than the original problem.
• People don't need to love your answer; they need to know you're listening and not keeping secrets.
• Anonymous feedback tools (e.g. Suggestion Ox) create psychological safety for candid input before full trust is established.
• Transparency at the leadership level is also accountability: leaders who must present financials can't hide problems either.

Results-based management

• Measure outputs, not presence. A senior developer's output is bug-free, shippable code — not hours at a desk.
• In a results-focused culture, poor performers can't hide behind visible busyness; underperformance surfaces fast.
• In a surveillance culture, people can look productive for months without producing anything.
• Don't confuse effort with output. "I'm working really hard" is irrelevant — what was produced?

Giving hard feedback

• Trust flows both ways: employees must trust that managers will be candid, not blindside them in annual reviews.
• Performance feedback should happen continuously in 1:1s — never as a surprise.
• If managers can't say the hard things, the trust framework breaks down regardless of other policies.
• A useful 1:1 technique: require employees to name three complaints per session, including one about you. It normalises critique and primes the manager to reciprocate honestly.
• Book recommendation: Crucial Conversations — helps managers develop the skill of raising difficult topics without damaging relationships.

Scaling trust across a growing company

• Trust looks different at 2, 10, 50, and 5,000 people — but remains possible at every stage.
• Large companies are collections of smaller teams; each team can operate with a trust-first culture even if the company-wide manifestation differs.
• As you add managers, hire and train people who are 100% bought into this model — most people default to what was modelled to them in traditional companies.
• Policies built for the lowest common denominator penalise everyone. Calibrate the penalty for getting it wrong: a rogue long vacation costs far less than a culture of distrust.

Who this works for

• High performers don't need policing — they want to produce because output drives their career and their pride in craft.
• Most employees are not bad actors. Designing systems assuming they are destroys morale and drives away the best people.
• "Great" is not the bar — "solidly good with good intentions" is enough for the model to work.
• Bad apples exist in every company regardless of management style; the question is whether your policies punish everyone else to catch them.