Give Your New Hire a Decision to Make by Friday

A new hire starts on Monday. By the following Friday she has met the whole team, read the wiki, sat in on four customer calls, and filled out a 30-60-90 day plan with headings like "Learn the product" and "Build relationships." Nobody can tell you yet whether she's good at the job. Neither can she.

That's the normal shape of a startup onboarding, and it's backwards. The first two weeks are usually built to make the new hire feel oriented and the manager feel thorough. Neither of those things tells you what you actually need to know: how this person thinks when something is ambiguous and the clock is running.

Familiarity isn't evidence

Reading the onboarding doc, shadowing calls, meeting stakeholders — all of this produces a person who is comfortable. It doesn't produce a person who has shown you anything. You can be extremely familiar with a codebase, a pricing page, or a support queue and still be bad at the job that uses them. Comfort and competence are different axes, and startups routinely optimize the wrong one in week one because it's easier to schedule than it is to risk.

The cost shows up three or four weeks later, when the manager finally has a real signal and it's bad. Now you're having a "this isn't working" conversation in month two instead of a small correction in week one, and the new hire has had a month to build habits around a version of the job that was never actually tested.

The fix: a real decision, small enough to fail safely

Here's the rule of thumb: by the end of the first week, a new hire should have made one real decision, with real consequences, that you did not make for them.

Not a task list item checked off. Not a document they contributed a paragraph to. A decision — something where they had to weigh options, pick one, and own the outcome.

Suppose you hire a growth marketer. The conventional plan has her spend week one reading past campaign retros and shadowing the current lifecycle emails. Instead, hand her the next lifecycle email in the queue on day two. Tell her the goal, the audience, the send date, and nothing else. Let her decide the subject line, the call to action, the send time. Ship it. By Friday you have open rate, click rate, and — more importantly — a conversation about why she made the choices she made.

Compare what you learn from that to what you learn from a week of shadowing. Shadowing tells you she can follow along. The email tells you how she reasons under a small amount of real risk. That's the thing you're actually trying to find out when you hire someone.

What makes a good week-one decision

Not every task qualifies. A good first decision has four properties:

• Reversible. If it goes wrong, you can undo it by Monday. Nobody should be onboarded into a decision that locks in a contract, a hire, or a public commitment.
• Bounded. One variable at a time. The email example works because the copy and timing are variables, but the audience and the goal are fixed. Too many open questions and you're not testing judgment, you're testing whether they can read your mind about scope.
• Visible. The outcome should be measurable within days, not quarters. If you can't tell whether the decision worked until next quarter's numbers come in, it's not a week-one decision, it's a bet you're making on faith.
• Actually theirs. This is the one startups get wrong most often. If the manager has already decided the answer and is handing over the task as busywork with a predetermined outcome, the new hire will sense it. Nothing erodes trust in the first week faster than being asked to "decide" something that was never actually undecided.

If a task doesn't have all four properties, it's either too big for week one or it's not really a decision — it's a chore dressed up as one.

The debrief matters more than the outcome

When the decision plays out, resist the urge to grade only the result. A bad open rate on the first email doesn't mean a bad hire. A good open rate doesn't automatically mean a great one either — she might have gotten lucky, or copied last quarter's winning subject line without knowing why it won.

Sit down and walk through the reasoning. Ask her to explain the choice she made and what she'd do differently with another week of data. What you're listening for is whether her reasoning holds up on its own terms, independent of whether the coin landed heads or tails. A new hire who says "I picked that subject line because our best-performing sends last quarter used a question format, and I wanted to test whether that holds for this segment" has told you more about her judgment than three weeks of shadowing ever could — even if the email underperformed.

The comparison that actually matters

By week three, you want to be able to compare two kinds of new hires. One is still "getting oriented": has opinions about the product, has met everyone, hasn't made a call that mattered yet. The other has already made and defended three or four small decisions, some of which worked and some of which didn't, and you already have a read on how she thinks.

The second person is ahead, even if she's made mistakes, because you and she both know something true about how she operates. The first person is comfortable, and comfort is not information. If your onboarding plan for the next hire is mostly reading, meetings, and shadowing, ask what decision you're deferring — and whether you're deferring it because it's genuinely too soon, or because it's easier not to find out yet.