zlacker

[return to "How to succeed in MrBeast production (Leaked PDF)"]
1. doix+Nr1[view] [source] 2024-09-16 12:09:25
>>babelf+(OP)
There are lot of comments here disliking MrBeast and what not, but some of the advice can definitely apply to all organizations.

> Your goal here is to make the best YOUTUBE videos possible. That’s the number one goal of this production company. It’s not to make the best produced videos. Not to make the funniest videos. Not to make the best looking videos. Not the highest quality videos.. It’s to make the best YOUTUBE videos possible.

Replace "youtube videos" with whatever the company is trying to achieve. I see it all the time in large organizations, where different teams forget what the goal of the company is and instead get hyperfocused on their teams KPI's to the detriment of the company as a whole.

Lawyers finding problems and trying to stop things from happening instead of finding solutions. Security blocking things and not suggesting alternatives. IT blocking this or that instead of trying solve problems, etc.

◧◩
2. kspace+pt1[view] [source] 2024-09-16 12:21:37
>>doix+Nr1
>Lawyers finding problems and trying to stop things from happening instead of finding solutions.

Sounds like they're doing their jobs, which is to protect your future selves from your current selves. Sure, finding solutions is great, but faulting them from finding problems and slowing things down until solutions are found is odd.

Yes, security or IT does sometime have to act as a reality check in an organization that has over-hired over-zealous but under-experienced go-getters who want to "move fast and break things". They are a vital counterweight that makes ambition productive, instead of allowing it to wreck the organization's reputation.

◧◩◪
3. JohnMa+p22[view] [source] 2024-09-16 16:05:04
>>kspace+pt1
See this all the time - for example, zealous dev "if I had production DB read/write I could get things done so much faster."

Sure, but the production DB has an incredible amount of PII and we are audited out the wazoo, but even if that weren't the case and it was totally fine, all it takes is you being careless with your credentials one time and the company's hosed or we have a massive breach, or some rogue employee encrypts the data with ransomware. So, yes, it would make you faster, and no, you can't have it. It's insane how often I have this type of conversation and insane how often I am the bad guy in it.

◧◩◪◨
4. doix+0c4[view] [source] 2024-09-17 08:55:14
>>JohnMa+p22
In your example, I am not saying you need to give the dev access to prod. But you should be working with the dev to figure out why he needs access to prod and figuring out what needs to happen to make the end goal happen. Getting read/write access to prod isn't the end goal, the dev is trying to accomplish something and they see direct access to prod as the solution.

My point wasn't that lawyers/security/IT/whatever shouldn't do their job. It's that their perspective should be focused on helping the company achieve whatever it's trying to do.

[go to top]