Related Posts
The king 👑

Another bull trap
Additional Posts in Tech Strategy & Product
Facebook (Meta) Product Management (IC5) or Google Cloud Marketing S&O/ Annual Planning (L6) role if I want to eventually be working on Product Strategy for consumer tech?
Heard it hard to pivot from Google S&O to Product Strategy even with 20% projects internally…
Facebook (Meta) | Google
AWS vs Amazon PM roles?
New to Fishbowl?
unlock all discussions on Fishbowl.




Transition tip #1 - don’t burn bridges. Do the recorded sessions. You are getting paid, correct?
Indeed - whether or not the session is recorded, it still counts as a KT.
Why is that such a problem to do? I don’t think this is an unreasonable request.
That’s normal. I agree with what most folks have commented. See it as a privilege to help, not everyone who leave an organization is presented with such tasks.
Consider how this may be presented as a positive in interviews for your next position. In a cross-functional role you want to be seen as someone who shares useful knowledge across the company rather than gate-keeping info, and who operates on the basis of good faith rather than self-protection. Even if your current work environment has been characterized by negative political gamesmanship, you can act in contrast to that and start acting in preparation for how you want your next environment to be, and in line with who you want to be.
It also helps you organize and remember all the great things you did in this role and prepares you to discuss it in future interviews.
I have my team create videos for each project, using Loom and just going over the code that they’ve written and giving a demo of it working. Often it’ll be one engineer, showing another engineer the ins and outs of their part of the stack/product. Having another person to show it to gives clarity because that other person can ask questions.
Since we have this as an ongoing task, there’s no need to do five full hours at the end of someone’s job.
Shorter videos about specific modules are preferred for obvious reasons. Like someone else said, nobody wants to go through five hours of video to find nuggets of information.
We put links to these videos in the product documentation for internal use, and the retrospective in JIRA.
Again, just look at this as prep for your interviews and brushing up your resume. I’m sure you did some great things at this company, and they’re paying you to go back and recap, which is a good exercise to do for yourself.
Just simply say "I'll agree to the transfer sessions, but don't record me", as is your right.
This is a moronic comment. Do not do this OP. I’d honestly just terminate you on the spot if I had this happen.
Your knowledge is yours. You have every right not to be recorded.
Out of curiosity, what is your discomfort with being recorded? Perhaps further context about that would allow for better responses.
This is a right thing to do irrespective of why or how you are leaving. It shows that you have opportunity to share your knowledge with someone else in the organisation. Yes, your knowledge is your knowledge but this is a good way to handover and be glad.you are leaving well without burning that bridge.
This is like having meetings/sessions with anyone taking over from you and allowing them record those sessions for their own reference when you are gone. This is a good and right thing to do.
I would allow the recording and do it.
That being said, I find this propensity to record everything is a relatively new development in companies. It's as useless as watching YouTube videos to learn something versus having good notes or a reference manual.
Who is going to wade through 5+ hours of recordings to find some nugget of info? No, instead it will be ignored anyway. The transcription is more useful, but requires everyone be on a separate dial in so the recording system can distinguish who is talking.
I recently attended a meeting and execs were shocked to learn that having everyone in a face to face meeting dialed into Teams doesn't "recognize" voices - I had to squelch the urge to laugh out loud while asking, "How would that work, exactly?"
There’s no reason not to have it be recorded. They need it for reference after you leave unless you intend to hand over a robust KT packet. You’re making it unnecessarily difficult.
When I took my current role, it had been unfilled for months, and I learned the product by watching all my predecessor’s presentations and demos. I made a written knowledge base as I went. Everyone thought I was a genius, but I just watched the videos.
The recording is there to preserve the knowledge, not to monitor you. Although I don’t agree that watching a video is the BEST way for your successors to learn, it at least keeps the info technically available, and I would be critical of a manager who didn’t ask you to do it.
If it’s any consolation, very few people watch these because it’s too much effort to find the exact content they need. Keep a post-it on your monitor to remind yourself you’re being recorded so you don’t say something awkward in a sidebar.
If you are in one party consent State, he can record you anyways. More context is appreciated. I’ll personally be happy to provide KT recorded, alternative might be to redact a comprehensive document.
Lool
Why do you care if it's recorded? Do you not record meetings ever?
Do as your told.
Don’t burn bridges.