Senior roles in early stages

Freshness Warning
This blog post is over 15 years old. It's possible that the information you read below isn't current and the links no longer work.

In the early stages of a company, should you be hiring senior people or more junior individuals? Who should the first few non-founder hires be?

Ed Sim worries that early-stage startups with no product and no customers are too focused on creating an impressive-looking senior team. He says, "I have major concerns when I see SVP of this and SVP of that and I wonder to myself who is going to do all the work if everyone is a Senior VP."

Feedburner’s Dick Costolo disagrees. There’s a lot of good reasons to bring on senior people early—if they’re going to be able to get their hands dirty and do the early-stage work.

He says,

You as entrepreneur are less likely to have to play grown-up and deal with the management issues that can frequently pop-up among a largely junior staff. It’s critical in the first 12-18 months to run as fast as possible, and by bringing in experienced players that can hit the ground running, you give yourself an opportunity to get a lot accomplished quickly.

The additional advantage of this is that you’ll have an easier time finding junior people when you’re in your high growth phase. The senior people will already be on board and can stop into management and mentor roles.

Sim further suggests that if you hire senior people early on, you might have the wrong people. What if that VP of Marketing has scads of experience in marketing consumer products, but you decide to shift to enterprise software?

Costolo suggests making sure you hire flexible snior people, not specialists. Hire people with experience in multiple organizational roles, or at least people with general management experience. Hire a CTO and you’ll have trouble when you need someone to run the sales staff while you’re traveling to your first trade show. Hire a VP of Sales and you might have trouble getting payroll filled when your finance guy is out.

Costolo suggests...

You want your more experienced early hires to be as much like stem cells as possible….able to take on differing roles in the organism depending on where they’re needed if the business or market or hiring experience shifts from expectations.

Recently Written

Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.
Tyranny of Outcomes (Aug 19)
An extreme focus on outcomes can have an undesired effect on product teams.
The Trap of The Sales-Led Product (Dec 10)
It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7)
One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16)
When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27)
An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24)
Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2023 Adam Kalsey.