Thanks! Definitely just made all of this spreadsheet up so feel free to modify to suit your team specifics. As the generator of the spreadsheet I may have mar

Thanks! Definitely just made all of this spreadsheet up so feel free to modify to suit your team specifics. As the generator of the spreadsheet I may have marked up the spreadsheet for myself as red for stuff I didn't understand but wanted/needed to understand - to reduce team bus factor - in order to show non-technical management what I wanted to spend time on to close the gaps. I also filled out some other team members' column and based on discussions would mark theirs as red. I think the context of a month for yellow was "it would take a month to proactively grok the code (prior to any systems down/bug triage) as a 20% activity on top of other ongoing activities (stand-ups, your existing OKRs, support requests)" - so like 1 day a week dedicated to sitting down to grok Other People's Projects. And now that you mention it - I might have said 2 weeks when I original shared the spreadsheet - so 16 hours to go from yellow->green. Also important is to take snapshots periodically to encourage/reward improvements to making the spreadsheet red -> green. A good work output to demonstrate a red->green transition is 1-2 small feature/bug fixes to a feature and/or a documentation update.