Go Big, Or Go…Startup

big Fish Little Fish

Image source unknown

A common career advice question I get all the time is what the tradeoffs are between going to a startup vs. going to a big company. There are many things to consider and lots of “it depends” when it comes to where you are in your career, where you live etc., but when it comes to the general aspects of a startup vs. mature company, most of the situations don’t vary that much. I’ve done both, several times, so here’s a perspective on the tradeoffs based on my own experiences.

Startup vs. Mature Company

Screen Shot 2018-10-15 at 10.54.03 AM

(c) 2018 Julia B Austin

Putting aside for a moment industry and how you feel about the products the company is building (both of which are very important!), most of the differences between a startup vs. a mature company are pretty obvious. In a mature company, you will likely have more role models to learn from and stronger teams to collaborate with, a clear direction and a mature board. The role you consider may have a narrow scope, but could offer deeper learning and of course great benefits, compensation, etc.. You’ll also get exposure to what good (or bad) looks like at scale and possibly a nice brand for your resume.

Startups can offer a chance to do “all the things” which can be either a blessing or a curse depending on your interests. You may miss out on having peers to collaborate with, have to look outside of your company for mentors and role models or have limited budget to get stuff done, but you may get high value equity in exchange for lower than market-level pay. If you want to dig more into deciding which startup to join, I suggest Jeff Bussgang’s book Entering Startupland which goes deep on the different roles at startups and how to get your foot in the door.

Leadership

One thing often overlooked when considering a new job is the leadership of the company. Serial entrepreneurs will have a very different approach than someone who has limited real-world experience and mature company executive teams can be world class or “legacy” leaders who can’t move with the times. There are many tradeoffs when factoring in leadership into the decision process of startup vs. a mature company.

Screen Shot 2018-10-15 at 10.55.10 AM

(c) 2018 Julia B Austin

Startup founded by serial entrepreneurs: This can often be the best case scenario if you want to learn from those who have “seen the movie before”. They likely had no issue raising money and were selective on who their investors were and who sits on their board. They will know how to get the flywheel moving incited by past mistakes OR failures.

“When I started my fifth company I knew exactly how I wanted to build the team. So, on day one I hired a head of recruiting to get things off to a strong start. I also knew market adoption would be critical to fundraising so focused on growth very early on – before we even had a product!” – David Cancel, CEO & Co-Founder Drift

Serial entrepreneurs may also try to overcorrect in areas where they failed the first time, such as over analyzing or delaying decisions, being too conservative on cash flow or focusing too much on scalability too early in the product development process. If you’re interviewing with a serial entrepreneur, it’s always good to ask what lessons they learned in their last startup and how they’re bringing those lessons into their new venture.

“I joined Drift in part because I wanted to learn from the experience of the co-founders. They’ve seen it before so they anticipate issues, they know when (and how) to hire experts to level up the team, and they know what’s “normal” for a hypergrowth company. It’s the best of both worlds: you get the rollercoaster startup experience with some of the more measured leadership and strategic characteristics of a bigger company.” – Maggie Crowley, Product Manager Drift

Industry veterans doing their first startup: Founders coming from mature companies with no startup experience can have big company confidence, be great at hiring and leading teams, but lack scrappiness to get a Minimum Viable Product (MVP) out the door and work towards product market fit.

“At our first startup after a series of roles at large enterprise software companies, we tried to force a big company perspective on how we did employee feedback and reviews. We were too structured with this initially and quickly cut back to a more loose feedback and review process with our team.” Izzy Azeri & Dan Belcher, Co-Founders Mabl

They may also be too used to having teams of people and systems in place to cover the more mundane duties of running a company and don’t want to get their hands dirty. On the flip side, they often know how to implement those processes and know the people to hire to run them so once the flywheel is moving and cash is in-hand, they can get momentum quickly.

“Earlier in my career, I hired a small team within a large corporation that was scrappy and had entrepreneurial mentality. At my startup, I quickly realized the benefit of once having a corporation behind me when things weren’t working out. The impact of a bad decision or process was much greater with no safety net.” – Karen Young, CEO & Founder Oui Shave

Startup with limited leadership experience: Working with a skilled group of founders leading teams for the first time can be tons of fun. If you bring some experience to the table, it can be very gratifying to not only work from the ground up, but also work alongside these founders as they grow. However, it can be frustrating if you find yourself figuring out things on your own because there’s no one in the company to mentor you. These situations can be very rewarding if you’re patient and you can always get outside mentors and advisors if they’re not available at this type of startup.

“When we started, we got a lot of advice like: stay focused, don’t expand too quickly, be careful that experienced hires match your culture.  All good advice, but we discovered there’s no real substitute for learning the hard way. The lesson just doesn’t sink in until you feel the pain of doing it wrong.” Wombi Rose, CEO & Co-Founder LovePop

Mature company with inexperienced leadership: If they made it this far, they are either wicked smart, lucky or both! More likely they also have surrounded themselves with strong, experienced leaders, investors and/or board members. You can learn a lot from joining a company like this, but they are very, very rare! When companies scale too fast, they can also suffer from having people in roles that have outgrown their experience. Read more about the impact of Hypergrowth situations written by my friend at Reboot, Khalid Halim, for First Round.

Mature companies with experienced leadership: These organizations have all the standard things you’d expect. Probably more politics and process than you’d ever find at a startup, but the benefit of exposure to great role models and best practices can be invaluable. Sometimes, these bigger companies can also expose you to the “dark side” of leadership and processes which are also great learnings on what not to do in your next job or company you may start yourself.

Which comes first in your journey?

For those doing early career path planning and knowing they want to do both a startup and a mature company at some point, there’s always the question of which should come first. Hiring managers at early stage companies can get “spooked” when they see someone with too much time (5+ years) at mature companies; questioning whether the candidate will be able to transition to startup life. Not that it’s impossible, but it’s something to consider. For these candidates, I suggest highlighting any scrappy “ground zero” work they may have done at their companies to demonstrate they can handle ambiguity and take risks. I am also a huge (and very biased) fan of people who’ve joined companies early and scaled with them. They have learned a TON from those experiences and can often start scrappy, but know how to operate at scale. Win-win.

Conversely, someone with a lot of startup experience may have a hard time adjusting to mature company. A hiring manager at a mature company may question whether a candidate with only startup experience can handle a slower pace or won’t know how to navigate a complex organizational structure that requires political and communication savvy. You may have to sacrifice title and maybe some salary to get a foot into larger institutions who may view your past role, which may have been very senior at a startup, to being pretty junior if those around you have decades more experience. However, I always find those with startup experience can be invaluable to a team that needs to be shaken up, take more risks or explore new ground. Often, those who sacrifice title and pay when they joined, make it up fast as they move up the chain in a larger organization.

There’s no right or wrong place to start. A lot depends on how you define your skills and how willing and patient you are in either case to adjust. Much can depend on who hires you and their management philosophy. I’ve seen some people bounce between both types of situations over and over, some that just can’t handle startup life, and others who have startups in their DNA and should just stick with that world 🙂

“At a startup, every job matters and you can see almost daily that you are creating something that wasn’t there before. You have the ability to learn quickly and have a fast feedback loop to let you know how you’re doing. It’s very different working at an established company vs a startup, but you can learn a lot at both – you’ll just learn very different things.” – Rebecca Liebman, CEO & Co-Founder LearnLux

Questions To Ask

Regardless of whether you are a seasoned veteran or fresh out of school, as you ponder whether you want to join a startup or a mature company here are some final things to consider:

  • What tools do you want to add to your toolbox? Will the role allow you to hone skills you already have or add new ones?
  • Who do you want to learn from, and how do you want to learn? You can learn from experienced colleagues and mentors, but having bad role models can also teach you a lot about what not to do. Similarly, if you are an experienced hire coming into a company started by inexperienced founders, you may want to learn by mentoring or teaching these young leaders. Taking the skills you’ve developed over your career and applying them to a new situation in itself can be a very enlightening experience.
  • Who do you want to work with? How important is the size and culture of the team you’ll work with? Remember, you’ll probably spend more waking hours of the day with these people than anyone else in your life – regardless of the size and nature of the company you join.
  • What do you value? At the end of the day, love what you do and decide what role will allow you to maintain the integrity of who you are and who you aspire to be!

Do you have other tips on how to decide whether to join a startup vs. a mature company? Please share in the comments!

Mastering The Team Meeting

No matter how much we hate going to meetings, there’s a generally accepted best practice that teams should meet with their manager as a group on a regular cadence. More often than not, I hear leaders and/or their staff dreading their team meeting. Instead of these meetings being the least favorite time suck of the week, wouldn’t it be great if these were the meetings we looked forward to? That we felt it was time well spent with our colleagues and added value to our roles in some meaningful way?

There’s no reason you have to suffer or make your teams suffer through another tortuous hour or more. A while back, I shared protips on Mastering the 1:1. Now, herewith my tips on Mastering the team meeting…

Meeting Purpose: Set a clear purpose for your team meeting. What do you want your team to get out of the time spent together? Do you want them to stay informed about larger topics in the organization? Get to know each other and their respective work better? Whether you are rebooting a long standing meeting or you are a new leader of a team gearing up for your first routine meeting, talk with your team members about what they want out of the session. This time is much more about their needs than yours, so align the purpose with their needs. A fun way to get this dialogue going is to ask each team member to complete this sentence: “My favorite meeting of the week is my manager’s team meeting because……” What would they say?

Agenda: I am a firm believer that if a meeting is important enough to have, it should have a time-boxed agenda and always be followed up with notes and action items (“AIs”). Protips on setting the agenda:

  1. As the team leader, you should solicit 1-2 “hot” topics per meeting from your team. I recommend you do this no more and no less than 48 hours before it is scheduled so ideas are timely and content is fresh. Topics should not be tactical – that’s what stand-ups and 1:1s are for. Instead, focus on strategic discussions and information sharing. On the latter, do not make it a status reporting meeting. Information sharing could be a product demo, or draft of a presentation someone is preparing for a conference or a preview of a big announcement to solicit feedback before it goes out.
  2. Always send the agenda for the meeting 24 hours in advance. This sets expectations and ensures no surprises and attendees are well prepared.
  3. Prepping for the meeting should take less than 15 minutes. Solicit agenda items – prepare agenda – communicate agenda. Long slide decks and spreadsheets created just FOR the meeting is a total waste of time. If those materials already exist and can add value to the discussion, then owners of said content should A) share these materials ahead of the meeting for pre-reading and B) bring said materials with them and be prepared to share them at the meeting.
  4. Lead by example for your team and read all materials sent in advance before the meeting. If you have not read them, no one else will and again, you’re wasting people’s time. If you’re prepared, everyone else will be prepared.
  5. Finally, always carve out 10 minutes at the end of the agenda to take a pulse on your team. My method is “share thumbs at one”. Three, two, one and on one have everyone in the meeting give a thumbs up, down or sideways. I do a quick read of the room and video screens to gauge if we’re trending in a particular direction and, if so, take time to discuss. People feeling really up? Share why! People feeling down? How can we work together to make things better? This simple, transparent, way of sharing how the team is feeling is a great way for you to lead and for them to support each other. I also find doing this at the end vs. the start of a meeting tends to be a better read because no one is bringing the stress from a prior meeting into their pulse check.

Meeting Engagement: No one wants to listen to a monologue at the team meeting and no one wants to be in a meeting with other people who are checked out. Several protips to avoid this:

  1. Ask 1-2 members of your team to take the lead on the hot topics in each meeting. They do not need to be the experts on the topic, just the topic leader. This includes having them facilitate getting pre-reads to team members ahead of the meeting. The more they have ownership in a topic, the more engaged they’ll be.
  2. The team’s leader should not speak more than ⅓ of the time throughout the meeting. Other than updating your team about broad company topics, your job is to facilitate the discussion and LISTEN. If you’re a bad facilitator (not every leader’s strong suit), then appoint or bring someone in to facilitate. I’ve seen everything from EAs and HR leaders to program managers serve as facilitators of meetings – they keep the meeting on topic, on time and pay attention to the room. I don’t recommend one of your team members be the facilitator – they are there as an engaged participant, only.
  3. READ THE ROOM. Are people reading their email, checked out on a remote phone or video line or rolling their eyes at each other (visibly or under the table on their cells via text…)? Pay attention to what’s happening in the meeting and pause if you see this kind of behavior. If you’re losing people, you’re wasting everyone’s time and you’re costing the company money. (do the math, the average team meeting can cost a company thousands of dollars every week!). Tell people to put their phones or laptops away if they are checked out. Ask people called in remotely if they have anything to add to the conversation. Pull them in. If the topic is falling flat, be direct and ask why or solicit suggestions on how to make it more engaging. E.g., budget discussions are rarely engaging so even a simple “bare with me as we get through this” can go a long way.
  4. Have fun! It’s great to start a meeting with a funny anecdote or personal story to wake up the room. Maybe someone on your team has a good customer story or had someone on their team get a “win” worth sharing. Perhaps you have a fun personal story to share that shows your human side. Keep it light where you can, but serious during some of the tougher topics (budget, staffing, etc.). This fortifies the culture of your team both inside and outside of the meeting.

Tactical Stuff: When you meet and who goes to the meeting is just as important as the agenda and the content. Protips:

  1. Timing: Got a distributed team in multiple timezones? Find a time that’s mutually convenient for all team members. Do you find the meetings always run over? Schedule it for an extra 30 minutes and if it ends early, everyone gets time back – you’re a hero. Does the team have family responsibilities in the morning or after work? Don’t schedule the meeting such that it disrupts their lives outside of work (if it can be avoided). I also generally discourage team meetings on Mondays (frequent holidays/long weekends means rescheduling or skipping too often) and Fridays (long weekends and if hard topics, no time to debrief/process offline before the weekend).
  2. Decision making: If a meeting has >8 people attending, it is an “information sharing” meeting. Less than that, and decisions can be made at the meeting. If you have a team greater than 8 people, tee up decision topics for discussion and, unless it’s a layup, take the actual decision off line. Otherwise, there are “too many cooks”.
  3. Assign and rotate a note taker at every meeting. You and/or the facilitator cannot read the room and take notes at the same time. Further, by rotating the role across your team, you foster engagement and get fresh perspectives on the meetings each time. Notes should be distributed no later than 24 hours after the meeting while things are fresh. Always call out AIs with owners and deadlines in the notes.
  4. Guests: An agenda should always build in intros for guests and should be time-boxed for cameos. For example, if the head of HR is a guest at your meeting to talk through the next review cycle with your team, the team should know that person will be there and why. Further, unless there’s scheduling trickiness, have guests come at the start or end of the meeting so as not to disrupt the meeting with people coming and going throughout. My personal preference is guests at the start. Then we get into our regular routine.

Most important, don’t set it and forget it. If you do change things up, be clear on why you’re doing it and give it time to settle. Starting or overhauling your meeting process won’t necessarily show positive results the very next meeting and changing it too often will not only cause unrest with your team, but can create distrust if the rules of engagement keep changing. Have at least 4-6 meetings for a new routine to set in and then evaluate whether the changes are effective and adjust as needed. Solicit feedback from your team regularly too – after all, it’s their meeting!

Do you run a kick ass team meeting? Or, do you have ideas on how to improve the team meetings you attend? Share your protips in the comments!