Most performance management problems were born as expectation problems nobody wrote down. Most performance problems are expectation problems. Every role should have written expectations at thirty, sixty, and ninety days. Review every two weeks with three questions: what is going well, what is not, what do you need? Write the thirty, sixty, ninety day expectations together, then review them every two weeks.
Letting someone go is a skill you will need
Nobody teaches founders how to fire someone. It is the hardest part of building a team and the part most founders handle worst. The principles: be direct, be kind, be fast. Do not soften the message so much that the person does not understand they are being let go. Do not be so blunt that you destroy their dignity.
The conversation should take ten minutes. State the decision, the reason, and the logistics. Do not debate. Do not offer false hope. Do not blame them. If it is a performance issue, you should have been giving feedback for months, so the decision should not be a surprise. If it is a layoff, say that clearly. The person deserves to know their performance is not the reason. How you handle this conversation defines your culture more than any perk.
Culture is what you tolerate, not what you say
Every company has a culture. The question is whether it is intentional or accidental. Intentional culture comes from the behaviors you reward, the behaviors you tolerate, and the behaviors you punish. If you say you value transparency but punish people for sharing bad news, your actual culture is secrecy.
The test for your real culture: what behavior gets someone promoted, and what behavior gets someone fired? Those two answers define your culture more accurately than any values deck. If the person who hits their number but treats people badly gets promoted, your culture is results-at-any-cost. If the person who misses their number but helps the team gets a second chance, your culture is collaborative. Neither is wrong, but you should know which one you are building.
Your first five hires determine your company's DNA
Your first five hires determine your company's DNA more than any mission statement or values document. Hire for slope, not intercept. Someone who is learning fast will outperform someone who knows it all within eighteen months. The interview question that matters most is not what have you done but what would you do here in the first ninety days with what we have.
Reference checks are underrated. Not the ones the candidate gives you, but the ones you find yourself. Spend thirty minutes on the phone with someone who managed them and was not prepped. Ask one question: would you hire them again, and why? The pause before the answer tells you more than the answer itself. Trust the pause.
Design interviews to test the actual job
Most interviews test interviewing skill, not job skill. The candidate who is charming, well-prepared, and great at answering behavioral questions may be terrible at the actual work. Design interviews that simulate the job: a sales candidate should do a mock discovery call, an engineer should review actual code, a marketer should critique your actual content.
The working session interview is the most predictive format. Give the candidate a real problem from your business, thirty minutes of context, and sixty minutes to work through it with you. You learn how they think, how they handle ambiguity, and how they collaborate. They learn what the job actually involves. Both sides make a better decision.
Onboarding is a product, not an orientation
The first thirty days determine whether a hire succeeds. Not because the work is hard, but because the context is missing. The new hire does not know why decisions were made, who to ask for what, or what done looks like. Onboarding should transfer that context systematically, not leave it to osmosis.
The thirty-day plan: week one is context (product, customers, market, history). Week two is shadowing (watch the person they are replacing or the person they will work closest with). Week three is doing with support (start the actual work with a safety net). Week four is doing independently. At the end of thirty days, they should be able to do their core job without asking for help. If they cannot, the onboarding failed, not the hire.
Frequently asked questions
Where does performance management start?
With written expectations: what the role delivers at thirty, sixty, and ninety days. Most performance problems are expectation problems. You cannot hold someone to a standard you never said out loud.
How often should I give performance feedback?
Every two weeks, with three questions: what is going well, what is not, what do you need? Fifteen minutes. Annual reviews at a startup are where feedback goes to fossilize.
What do I do when someone misses expectations?
Name it early and specifically: what was expected, what happened, what changes by when. Most misses are clarity problems or capacity problems, and both are fixable if you catch them at week three instead of month six.
How do written expectations help the employee?
They make success legible. People relax when they know what good looks like and how they are tracking. Ambiguity feels like freedom for a month and like an ambush at review time.
What is the biggest performance management mistake?
Saving feedback for a formal cycle. By the review, the small miss has compounded into a pattern, and the employee hears months of judgment delivered in one sitting. Frequent small corrections are kinder.