Engineering organizations eschew copy and pasting in codebases, but happily embrace it in documentation, planning artifacts, etc.
Why is DRY not a fundamental principal of roadmaps, OKRs, plans, etc. and the CMSes (often @googledocs) on which they are built?
The problem is often exacerbated by bubbling roadmap items, OKRs, etc. up through an org chart.
(e.g. a low-level roadmap item is published in a org-wide high-level summary of key deliverables...
...but updates to low-level item (dates, scope, etc.) are never reflected in summary.)
I am sure there are CMSes out there that try to solve this problem (e.g. wiki includes), but I have never seen them successfully applied.
Ian Brown @igb
(at least not in the companies/orgs I've worked in over the years)

¯\_(ツ)_/¯
View on Twitter ↗
0 1