Hey Lyft folks, any thought to experimenting with the usability of the graph data in Cartography (as shown) vs putting the same data in a DSM? https://en.m.wiki

Hey Lyft folks, any thought to experimenting with the usability of the graph data in Cartography (as shown) vs putting the same data in a DSM? https://en.m.wikipedia.org/wiki/Design_structure_matrix https://en.m.wikipedia.org/wiki/Design_structure_matrix I can imagine buckets or nested buckets as rows, policies, groups or users as columns, just as one way of viewing it. Alternative graphing tools such as Sourcetrail for source code also come to mind, as a way to merge policy source code with a graph view, for example.