Onboarding, Culture, and Managing a Small Team

Founders often treat a signed offer as the finish line. It is the starting line. A great hire dropped into chaos, with no onboarding, no clear goals, and no feedback, will underperform and may quietly quit within months, and you will blame the hire when the failure was the environment.

Lesson 1 got the right people in the door. This lesson is about what turns them into productive, committed contributors:

• Onboarding: the first weeks that set someone up to succeed or flounder.
• Direction: clear goals and expectations so effort points the right way.
• Management: the one-on-ones and feedback that keep people growing and aligned.
• Culture: the shared behaviors that hold a team together as it grows.

These are not soft extras; they are where the return on a hire is realized or lost. A useful frame from Gallup's research: in their State of the American Manager work, Gallup found that managers account for around 70 percent of the variance in team engagement. For a founder, that is a direct message, how you manage is the single biggest lever on whether your team is engaged and productive. The people practices in this lesson are that lever.

Onboarding is the deliberate process of getting a new hire productive and connected. Done well it accelerates their ramp and cements their decision to join; done badly it wastes the first months and raises the odds they leave. A simple, powerful structure is the 30-60-90 day plan.

• First 30 days, learn: access and tools ready on day one; meet the team; understand the product, customers, and how things work. The goal is context, not output.
• Days 30 to 60, contribute: start owning real tasks with support, applying what they learned. First meaningful wins build confidence.
• Days 60 to 90, own: operate independently on their core responsibilities, working toward the outcomes from their scorecard.

Two founder-specific points. First, prepare before day one: nothing says "we are disorganized" like a new hire with no laptop, no logins, and no plan, and first impressions of the company cut both ways. Second, connect the plan to the scorecard from Lesson 1: the outcomes you hired for become the 90-day targets, so the new hire knows exactly what success looks like. Structured onboarding is not bureaucracy at small scale; it is the difference between a hire who ramps in weeks and one who drifts for a quarter.

The most common cause of underperformance is not laziness or lack of skill; it is ambiguity. People cannot hit a target they cannot see. A founder's job is to make the target unmistakable and keep it visible.

Good goal-setting for a small team has a few properties:

• Outcome-focused, not activity-focused. Define the result you want ("land 10 qualified demos this month"), not a list of tasks, so people can use judgment about how to get there.
• Measurable and time-bound. A goal you cannot tell you have hit is a wish. Numbers and dates remove argument.
• Few and prioritized. Three clear priorities beat ten vague ones; when everything is important, nothing is.
• Shared and written. Written goals both people agreed to prevent the "I thought you meant" gap.

Many teams use a lightweight framework like OKRs (objectives and key results) to do this, but the framework matters less than the discipline: everyone should be able to say what they are responsible for and how success is measured. This connects directly to management, you cannot give useful feedback, or hold anyone accountable, against goals that were never made clear. Clarity up front is what makes everything downstream, feedback, reviews, even a fair exit, possible and fair.

If goals set the direction, the one-on-one is the engine that keeps people on it. A one-on-one is a regular, private conversation between you and each person who reports to you, typically 30 minutes weekly or biweekly. It is the highest-leverage management habit a founder has, and the easiest to skip when busy.

A good one-on-one is the report's meeting, not a status update. Status can go in a document; the one-on-one is for what a document cannot surface: blockers, concerns, growth, morale, and the early signals of a problem while it is still small. Ask, then listen: what is in your way, what do you need from me, how are you feeling about the work.

Feedback is the other half. Two rules make it work:

• Be timely and specific. Feedback right after the event, about a concrete behavior, lands; a vague comment three months later at a review does not. Praise good work specifically and often, not only correct problems.
• Address issues early and directly. The founder instinct to avoid an awkward conversation lets small problems grow into big ones. Kind, clear, early feedback is a gift; silence followed by a blow-up is not.

These habits are cheap and compounding: they catch problems early, help people grow, and build the trust that keeps good people engaged.

Founders often think of culture as ping-pong tables, snacks, and a values poster. Real culture is none of that. Culture is the behavior you model, reward, and tolerate. It is how people actually act when a deadline slips, how disagreements are handled, whether commitments are kept, how customers are treated. Perks are amenities; culture is behavior.

Three facts make this urgent for a founder:

• You set it, whether you mean to or not. In a small company, the founder's own behavior is the culture. What you do under pressure teaches far more than any stated value. If you say "customer first" and then cut corners when rushed, the real value learned is "corners are fine when rushed."
• The worst behavior you tolerate becomes the standard. Keeping a brilliant but toxic performer signals that results excuse how people are treated. What you permit, you promote.
• It forms early and sets hard. The first 10 hires effectively are the culture; they carry and amplify it as you grow. Culture is far easier to shape at 5 people than to fix at 50.

The practical takeaway: decide the handful of behaviors you actually want (how you treat customers, each other, mistakes), then model them relentlessly, hire for them, and address violations quickly, especially in high performers. Culture is built by consistent action, not declared on a wall.

Every founder hits the same wall: the company cannot grow past what you personally can do, but letting go feels like losing control or quality. Delegation is the skill that breaks the wall, and it is more than dumping tasks.

Real delegation means handing over an outcome and the authority to achieve it, not just a to-do list. "Own our customer support and keep satisfaction above this bar" gives someone a goal and room to decide how; "do these ten support tickets exactly this way" just makes you a bottleneck with extra steps.

A workable approach:

• Delegate outcomes, not micro-steps. Define the result and the guardrails, then let the person choose the method.
• Match trust to track record. New or high-stakes work needs closer support; a proven person on familiar work needs room, not oversight.
• Accept a different "how." They will do it differently, and often that is fine or better. Reserve intervention for outcomes that are actually off track, not for style.
• Delegate the work you are worst-positioned to keep. Free your time for what only the founder can do, direction, key relationships, the biggest decisions.

Delegation done well is not abdication; you stay accountable for outcomes and support through one-on-ones. But it is the only way both the company and your people grow, people stretch into responsibility, and you escape being the ceiling on everything.

For a while, the founder manages everyone directly, and that is correct; a flat team of a handful of people needs no hierarchy. But growth eventually forces the question of adding a layer of management.

Watch for the signals that you have outgrown flat:

• You have too many direct reports to give each a real one-on-one and timely feedback (for many founders this strains somewhere around 7 to 10 people).
• Coordination is breaking down, work falls between people, priorities collide, things slip through gaps.
• You are the bottleneck, decisions and approvals pile up waiting for you.

When you add managers, two cautions matter. First, a great individual contributor is not automatically a great manager, the skills are different (coaching, delegating, giving feedback), so promote for management ability and support the transition, do not just reward your best doer with a team they may struggle to lead. Second, do not add layers too early: hierarchy adds distance and overhead, so introduce it when coordination genuinely demands it, not to hand out titles. Recall the Gallup finding that managers drive most of the variance in engagement, once you have managers, whom you choose and how you develop them becomes one of the most consequential people decisions you make.

After a hire signs, structured onboarding builds context, clear goals point effort, and regular one-on-ones and feedback keep people aligned and growing; the founder's modeled behavior sets the culture around it all, and as the team grows, managers extend that system.