Whether I’m jumping into an existing project or starting a new one, I always want to have on hand the “one and only” document that has all the basic information everyone needs to know. I call this the “canonical” document, as in: the official document, the one that belongs in the canon. If you’ve worked on a complex project you know how messy things can get if we’re not all singing from the same song-sheet. That’s why you need a canonical document but also canonical workstreams, frameworks, nomenclature and visuals. To learn more about Canonical Everything, visit naomi.com. #productivity #productmanagement #product
Your site resources are very helpful! Thanks for sharing 🙏
Project has many facets design, architecture, trade offs , schedule , milestones, progress, people, collaborations to name a few. How does one fit such diverse information in just One Document.? Also a project may have phases that overlap and generations that are multiple year cycles. I totally agree canonical information but don't know how to compress or fit all this in one place. I understand document action vexes big and small. A lot of effort was done at Boeing on this subject. A lot of recent Problems at Boeing were attributed to insufficient or unavailable documents.
See also: https://en.m.wikipedia.org/wiki/Project_charter
Thank you!
дуже цікаво
Engineering + Planning
1ySolves a lot of problems!