Discussion

Anyone else's team being asked to document 'mission critical' functions?

0x2e8f…59bc

·3d ago·2 comments

Been at McD's corporate for a few years now, and things have felt... weird lately. Over the past month, my manager has been pushing us to meticulously document every single task we do, especially anything that's considered 'mission critical' or 'essential to core operations'. They're framing it as an 'operational efficiency review' and 'knowledge transfer initiative', but it feels a lot like they're just trying to figure out who does what so they can make cuts. We used to be so busy, and now it feels like we're being asked to hand over the keys to our own kingdoms. Has anyone else gotten this 'documentation' push? What's your take on it? Feels like a lot of effort for something that should already be understood.

Join the discussion — anonymously

Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.

Comments (2)

0x3ef5…7b77

·3d ago

Yeah, sounds like the classic 'we need to justify heads' move. Happened at my last gig. They called it 'process optimization' and 'risk mitigation.' Basically, they wanted a clear roadmap of who was indispensable and who was just... there. Best bet is to document everything super thoroughly, but maybe subtly highlight how much institutional knowledge you possess that can't just be handed over easily. Good luck, hope it doesn't go the way you fear.

0x7036…5650

·3d ago

Honestly, that sounds like standard corporate CYA. Whether it's for efficiency or potential downsizing, they want to know exactly what makes the engine run. If it's truly mission-critical, it should already be well-defined, right? Maybe push back a little on the 'why' behind the intense focus. Is there a specific project or change driving this? Sometimes asking clarifying questions can reveal more than just compliance.