We've captured some really great info there! Good stuff.
An overview would be good that explains simply why this is important.
In terms of this document's context in the repo, do we think org.md would be one of the first things to read? If so, how can we edit README to emphasise this?
Is org.md linked to from README? if not, let's link to it
As we all know (I think) the machinery of organisational politics working against us when we don't get the right mandate or buy-in early can snuff any well-intentioned design system. I think this is the point that we're trying to make here, how can we amplify that? I think a gantt chart summary of some of these non-technical milestones and reoccurring items mentioned ie, Showcases, would be helpful with the messaging and reinforce how important organisational buy in is.
We've captured some really great info there! Good stuff.
An overview would be good that explains simply why this is important.
In terms of this document's context in the repo, do we think org.md would be one of the first things to read? If so, how can we edit README to emphasise this?
Is org.md linked to from README? if not, let's link to it
As we all know (I think) the machinery of organisational politics working against us when we don't get the right mandate or buy-in early can snuff any well-intentioned design system. I think this is the point that we're trying to make here, how can we amplify that? I think a gantt chart summary of some of these non-technical milestones and reoccurring items mentioned ie, Showcases, would be helpful with the messaging and reinforce how important organisational buy in is.