Skip to content
SponsoredShip your own knowledge site with Vincony
Vinthony

Lessons

Lesson 1 · 12 min · Foundation

Reverse-Engineering Culture from the Problem You Solve

Stop inventing values from scratch and derive them backwards from the problem your team actually exists to solve.

Cultural DNAReverse engineeringProblem-first thinkingBehavioural derivation
Free preview

Lesson 2 · 12 min · Applied

Walking Through Fire Together: Earning Buy-In Early

Engineer one shared adversity moment so identity hardens before you ever need to demand results.

Shared adversityBuy-inEarly winsCollective identity

Lesson 3 · 12 min · Applied

Hiring for Warmth, Obsession, and Championship DNA

Screen for getting on with people, getting stuck in, and obsession with the mission before you screen for raw capability.

Warmth signalMission obsessionTeam fitSelfish detector

Lesson 4 · 12 min · Deep practice

From Command-and-Tell to Explain-and-Enroll

The leadership style that built the team is rarely the style that scales it past the first inflection point.

Style transitionVoluntary commitmentPersuasionSelf-reflection

Lesson 5 · 12 min · Applied

Designing Onboarding That Transmits Culture at Scale

Once your team grows past fifty people, culture stops travelling by osmosis and has to be transmitted on purpose.

Culture transmissionOnboarding designStory-first inductionRemote drift

Lesson 6 · 12 min · Applied

Speaking Last: Surfacing Unfiltered Team Insight

If you speak first, the room converges on your opinion. If you speak last, you get the unvarnished thinking of your whole team.

Senior speaks lastConvergence biasTree of monkeysUnfiltered insight

Lesson 7 · 12 min · Deep practice

Rituals That Hold Under Remote Work and Crisis

Design the small repeated practices that keep the essence of your team intact when offices, leaders, or routines are suddenly stripped away.

Team essenceRitual designCrisis resilienceRemote cohesion

The problem this solves

Most cultures aren't designed; they accrete. Whichever behaviours got the early team through their first hard quarter become the culture, regardless of whether anyone would have chosen them on a calmer day. By the time the founder notices, the culture has become a hiring filter and a hidden ceiling on what the team can build.

This micro-course teaches the deliberate version. Name the DNA before you scale. Sequence the early wins. Build rituals that hold the team together under load. The work isn't glamorous and the payoff is enormous — the kind of team where good people refuse to leave, and the kind of company where the founder isn't the bottleneck.

A taste of the exercise

The preview lesson walks you through writing your culture's three non-negotiables in one short paragraph each, then auditing whether your last five hiring decisions actually reflected them.

Key concepts

Culture DNA
The two or three non-negotiables that shape every hiring, firing, and promotion decision. Written down. Visible to the team.
Sequenced wins
Early shipped outcomes that prove the culture works — not yet at scale, but in the small. Founders who skip this stage build cultures of permanent struggle.
Cohesion rituals
Recurring practices — weekly retros, monthly all-hands, quarterly reviews — that keep the team connected without depending on heroics.
Culture debt
The accumulated cost of behaviours you tolerated past the point you should have addressed them. Compounds faster than financial debt.
Hiring for the culture you want
Not the one you have. Most struggling teams hire to fit the current dysfunction; healthy teams hire toward the next version of themselves.
Public accountability
Leaders modelling the culture in visible ways. The team copies what the leader does, not what the leader says.

Common mistakes

  1. Letting the culture accrete instead of designing it.
  2. Posting values on a wall without anyone enforcing them.
  3. Hiring people you like rather than people who reinforce the culture you want.
  4. Tolerating senior behaviour you wouldn't tolerate from a junior.
  5. Treating culture as a Q4 project rather than a daily one.
  6. Confusing perks with culture.

FAQ

When should I codify the culture?
Earlier than you think. Three to five people is when the culture-by-accretion problem starts; by ten people, retrofitting becomes expensive. Codify in the first six months.
What if my co-founder and I disagree on culture?
Solve it before you hire. Cultural disagreements at the founding-team level cascade through every hire and produce two factions inside a small company. A facilitated weekend usually resolves it.
How do I fire for culture?
Carefully and quickly. Once you decide a high performer is harming the culture, every week you delay costs you trust with the rest of the team. Performance + culture-misfit usually warrants exit.
Do small teams need rituals?
Yes — possibly more than large ones. Five-person teams without weekly retros drift into resentment faster than fifty-person teams with them.