Thanks Adrian + co.
So why a standard or common set?
We have observed that there are only a few documents in a project that help connect a project story and its members together. Sometimes these documents are hidden from view and difficult to understand.
So what if there were a standard or common set to get the project started? These can fit the specifics of the project over time, but the intention is to help connect a project together around its goals, customers, data and designs.
This may help provide a well understood story and speak to some the points already suggested.
It also implies a lead role in introducing the artefacts and guiding the project on how to populate them and how they should connect or speak to each other.
It seems not only organisations are in silos, but so are team members and the documents/deliverables they produce. This is not even talking to how well or not well designed or usable or useful these artefacts are to begin with as communication pieces and the language inside (inviting or divisional)
So how would we find simple ways to address this?