zlacker

>>babelf+(OP)
Lot of people critiquing this, but you can't deny the success. I think a lot of the advice is applicable to startups.

1. KPIs, for Beast they are CTR, AVD, AVP, will look different if you are a startup. I am willing to bet he knows his metrics better than >95% of startup founders. Because he is literally hacking/being judged by an algorithm, his KPIs will matter more and can be closely dissected. Startups aren't that easy in that sense, but KPIs still matter.

2. Hiring only A-players. Bloated teams kill startups.

3. Building value > making money

4. Rewarding employees who make value for the business and think like founders/equity owners, not employees.

5. Understanding that some videos only his team can do, and actively exploiting and widening that gap.

The management/communication stuff is mostly about working on set/dealing with physical scale. You need a lot more hands dealing with logistics, which requires hardline communication and management. In startups, the team is usually really lean and technical, so management becomes more straightforward.

I am also getting some bad culture vibes from the PDF and really dislike the writing style. I think it's important not to micromanage to the extent he is--it's necessary, maybe, for his business. Not for startups. Interesting perspective, reminds me of a chef de cuisine in a cutthroat 90s kitchen. The dishes (videos) have to be perfect, they require a lot of prep and a lot of hands, and you have to consistently pump them out.

>>ocean_+Bb
I’m with you on the management vibes - it doesn’t sound like a culture that I’d enjoy.

That’s one of the things I find so interesting about this document: it does feel very honest and unfiltered, and as such it appears to be quite an accurate insight into their culture.

And that’s a culture that works if you want to create massive successful viral YouTube videos targeting their audience.

How much has that specific chosen culture contributed to their enormous success in that market? There’s no way to know that, but my hunch is it contributed quite a bit.

>>simonw+ic
What I find interesting in reading this is that it's not particularly surprising in content. And I don't mean that I expected some hugely toxic culture from a youtube company and found it. I mean that the whole document is largely pretty standard "how to make it in a competitive industry" advice. The tone might be a little unprofessional for folks who are used to big corporate talk, but if you'd leaked internal Microsoft or Google documents to a bunch of long time IBM folks they would have thought the same things I'm sure. The tone might be different, but most of the points seem identical to stuff anyone should be familiar with. "Follow up when you ask someone for something", "Don't commit to giving X if you can't actually get X", "Have a backup plan", "Try to turn a failure into something useful", "Own your mistakes", "Make sure you've exhausted all the avenues for something before you decide it's impossible", "Do the hard work early so you're not cramming it all in at the end", "You are the subject matter expert on your specific project, assume everyone else doesn't know anything". Even the "A,B,C" employee thing is pretty standard stuff folks know intuitively. Fast food is garbage no matter where you go, yet somehow Chick Fil A has lines around the block at lunch time and if there's 3 cars in a Wendy's drive through, you'll go somewhere else. Why? Because Chick Fil A really tries to not have "C" employees (relative to fast food employees in general), and it shows in the customer experience. Two fast food places can have the same quality of food, and the one with the drive through attendant that acknowledges people and responds to phatic phrases, and marks the diet soda cup is going to have more traffic and customer satisfaction than the one where the attendant barely acknowledges you've arrived at the window and leaves you to figure out which was the diet coke when you get home.

>>tpmone+Ys
That's the same impression I got. It's odd seeing the discussion veer off into morality, because most of it seems to be standard and non-problematic advice (IE, understanding what your product is and don't get distracted by focusing on what it's not).

And though the advice isn't particularly novel, it was worth reading since a surprisingly large amount of people don't do these simple things.

>>bnralt+zb1
I read the entire PDF and I felt he was pretty spot on about works and what doesn't in running a business.

This is Hacker News, ostensibly created as a website for hackers and founders.

If you are a hacker and a founder then a ton of this advice is spot on.

For example it's a simple concept but he absolutely nails a key factor by distinguishing between A, B and C employees. A high performing team really can't have more than one or two C's. It moves them out even if they're nice, cool, good people. If the team is run by good humans it does what Mr. Beast does and gives them severance.

I can smell a couple C employees fuming on here and in the Twitter thread. I've had C employees work for me and they were always the ones who lobbied me hardest for being more tolerant of mediocrity. Sorry but you just have to hold the line against the average if you want to succeed, this is dictionary definition level of obvious. To be above average, you have to be above freaking average. Half the world is C's and to win your team needs to not be in that half.

>>safety+Yy1
While I understand the concept of A, B and C employees to the employer from the PoV of the employee there is also management attrition and lack of incentives.

>>loboci+Dbb
This concept of A, B and C employees is just ordinary dose of propaganda. A is a salaried employee who is expected to put in extra time and effort as if their livelihood depends on the success of the company, whereas type C employees poison the mindset by doing what they were hired to do. Bs are Cs with inherent sense of pride in delivering excellence who can be coached to become A.