I'm building a product team. Who do I hire first?
You keep making lists. Titles, levels, salary bands. You tell yourself this is hiring work. It is not. It is avoidance dressed as preparation. A team is not a stack of good people. It is a set of problems, divided so each person owns one cleanly. If you cannot say what breaks without a given hire, you are not ready to hire them. Hire now, in confusion, and you'll spend the next year fixing overlap and gaps instead of building. Slow down for one week. Get the shape of the work right. Then go find the people.
You don't have a hiring problem. You have a clarity problem. You're choosing people before you know the work. Stop looking at candidates. Write down the three problems your product must solve this year. The roles will name themselves. Hire for the work, not the title.
What changes unlock by starting
- A short list of real roles, defined by the decisions they own.
- A faster hiring process, because you know exactly what you're testing for.
- Fewer costly mis-hires that come from vague job descriptions.
- A team structure you can explain in one sentence, to anyone.