In Audience Ops’ first year, we’ve grown from a team of 1 to 17—6 full-time employees and 11 part-timers who we still very much consider team members in every sense of the word.
As you might imagine, there’s one personal entrepreneurial skill I’ve been forced to focus on this year:
It’s been several years since I started managing teammates in one form or another. But now that I have several “levels” of team management under my belt, I feel it’s a good time to write my guide to what I’ve learned.
Today’s article is my answer to one of the top questions I hear from readers. It typically goes something like this:
“How did you go from working solo to managing a team and when did you hire and manage your first employee?”
I’ll cut straight to my answer:
There is no quick answer.
Hiring your first employee is one small step in a multi-level progression you’ll take from being a solo-preneur doing everything yourself to a manager-preneur, building a team to execute your entrepreneurial vision.
This guide assumes you’re taking a similar path to the one I’ve taken: You started as a freelancer / consultant, perhaps built up your consultancy, then transitioned to a product business. At every step, you find the need to bring on help and talent, often wondering how to take those next steps in growing a team.
I believe most of what it takes to be a great manager can only be self-taught. Meaning, what works for one person won’t necessarily work for another. You must figure out and embrace your own personal style at every level of managing a team.
That’s not to say you shouldn’t learn from great (and horrible) managers you’ve come in contact with. I certainly have drawn lessons from some of my former managers when I was employed. Some were excellent, highly efficient, and they facilitated some of my and my teammate’s best work. Others, were, well… not that. And it showed in both my and my team’s output. There are always bits and pieces to take away from experiences like these and apply in your own business, as I have.
This guide on becoming a manager is built on my experience as a manager. I broke it into 6 distinct “levels”:
You may not experience every one of these levels in the same order I did, but if you’re self-funded and building your business organically as I have, chances are you’ll see a similar progression.
For each level, I’ll describe what it looks like. I’ll offer some prerequisites—things that should be established before this level of management comes into play. And I’ll cover the essential skills you’ll develop while managing at each level.
Ready? Let’s dig in.
I call this Level “0”, not “1” because this level typically happens before you have a product business. I started my self-employed career as a freelance web designer, and I built my consultancy for several years before I transitioned to product businesses.
It was during my freelance/consultancy days that I cut my teeth on my very first managerial experience: I brought in project-based sub-contractors to help me execute parts of my client work. This served as an excellent preview of what it’s like to manage a team, and it helped me learn basic but essential skills in owning a project that has multiple people delivering assets.
The great thing about starting with sub-contractors—especially when you’re consulting—is a lot of the big question marks are answered for you right from the start: You know exactly how much you can budget and exactly what you need from a sub-contractor. These are short-term engagements with a defined start and finish, which allows you to get a taste for managing without a long-term commitment.
This next level is really the first level of management once you’ve launched a product or a productized service business.
I call this an “Assistant” role, but I don’t necessarily mean this is their literal job title. By “assistant”, I’m refering to anyone who takes on tasks that you’ve been doing yourself for a while, and have defined a trainable process for someone to take over. An assistant-type role doesn’t necessarily bring skills or talents that you wouldn’t have been able to produce yourself. But they do relieve you of day-to-day “busy work”, which can open up new bandwidth for you to push new things forward.
Examples of a part-time assistant role would be tier-1 customer support, an administrative virtual assistant, a bookkeeper, perhaps a quality assurance checker.
Don’t let the “low level” of this role fool you. If your business isn’t truly ready to have someone in this role, it will turn into a huge waste of time and money, resulting in a big setback for your business (and you personally, as a manager). It took me two failed VA hires to realize the problem wasn’t the people I hired, it was the fact that my business didn’t have the repeatable need for an ongoing assistant.
As you move up the management food chain and your business grows, there should come a point when you seek to bring on creative people to your team.
Again, I don’t mean “Creative” in a literal job-description sense. I’m referring to any teammate who produces new assets for your business. Examples might include designers (produces visual assets), developers (produces code & functionality), writer (produces content), marketing (produces leads), sales (produces customers).
A creative person can still serve in a part-time capacity. If your need is only temporary (for example, you’re launching a bi-annual redesign of your website), then this isn’t much different than the sub-contractor hire I touched on earlier. But most product businesses develop an ongoing need for creative work, such as a designer or front-end developer. The ongoing position is more along the lines of what I’m focusing on here.
At this level, you reach a scary decision:
Do you hire more part-time employees to cover the growing demands of the workload, or do you convert your part-time contractors into full-time employees?
Hiring more part-timers is the easier, simpler option. You’ve successfully done it before, so why not just double down and hire more people this way? Technically, this can cover your workload needs. But it might result in an over-grown team. Too many people, all who’s focus is split in many directions. Plus, it’s common for part-time contractors/freelancers to suddenly take other gigs and leave you in a constant hiring mode.
For the long-term health and your own personal sanity as a manager, you’re better off with a few full-time employees than many part-time freelancers. But committing to your first full-time employee is scary! I know it. Although I’ve had full-time teammates in years past, this year was the first time I brought on full-time W2 workers here in the US. Something about that step felt bigger, more complex, and came with more responsibility than any other hire I’ve made before. Some of this is natural entrepreneurial nerves, but some is reality.
As your team grows in size, there comes a point when you can’t possibly manage everyone and everything yourself. You have to develop a management structure.
The conventional wisdom on how many direct reports a manager should have ranges anywhere from 6 to 10 to 15. I think it really depends on the type of company and your personal style. For example, according to Business Insider, when Tim Cook took over as CEO of Apple, the number of direct reports to the CEO increased from 9 to 17.
If you’re running a small, lean startup, and if you’re using the productized service model like I am, then there’s another factor to take into account here: Which management duties do you want to have?
Even if your team is still relatively small, there might be daily or weekly tasks such as checking in on progress or keeping clients in the loop, which you don’t really want to (and shouldn’t be) handling yourself. For example, in my business, Audience Ops, I’ve built a group of Project Managers to oversee our day-to-day production line of content, which frees me up to focus on improving our processes and building new things.
Another question that comes into play at this level is deciding whether to promote someone into a management role or to bring someone new directly into a management position. I have found it can work (and not work) in both scenarios. Your super talented developer might not make a great CTO. Your rainmaker sales person might not be as effective in a sales management position. Someone with strong communication and organizational skills will probably excel in a management role, so it might be best to hire someone directly when this need arises.
I’d lump one more type of hire in this level: Creative Lead. While some of your creative asset-producers may not be best suited for a promotion into management, they might be better suited to become a creative lead. Think creative director, product owner, lead developer, etc. This person works on the mission-critical components and helps drive strategic and creative decisions.
I was fascinated to read Rand Fishkin’s dual-track system for employee advancement at Moz, where some can take the “Individual Contributor” track and others can take the “People Wrangler” track.
Managing business partners and “C-Level” executives at a large company. I’ll be honest, I don’t have a lot to say at this level because I don’t have a ton of experience here.
Although I tend to work best as the sole founder/owner of my business, I have worked in partnerships before and I do still take on side project collaborations with partners. So I can speak a bit about working with and managing partners.
I think there are two key tips to making it work:
First, you must recognize you’re on equal footing. Even if, technically, your ownership shares may not be equal, you must treat your partners, and your relationship, with an “equal” level of authority. In other words, unlike managing employees under you, where you generally have the final say on things, partners should share that final say. Not all decisions will be yours and you have to be OK with that.
My second tip here is to make sure you and your partners compliment one another in terms of the skills and experience you bring to the table. There are very few successful partnerships between two highly technical programmers. More often it’s a programmer and a designer, or a biz dev marketing person and a CTO, or a similar matching. No matter how well you may work together, too much overlap won’t do anyone (or your business) any good.
I’ll conclude with this: Don’t let “Becoming a Manager” prevent you from starting a business that’s bigger than yourself.
Managing people can actually be truly rewarding and enjoyable—Yes, even if you come from a technical/creative background like I do.
I write and talk a lot about “learning by doing” and growing as an entrepreneur. There’s no area where this rings true more than when it comes to managing people and growing as a manager. And like most things, the way forward is to take it one level at a time.