[jerf]

There's some sort of PE analog to the Brooks quote I've been working on, but I'm not quite there yet. Something like "Show me your solution and conceal the org chart, and I shall be mystified by your decisions. Show me the org chart and I won't need to see your solutions, they'll be obvious."

It's not quite as determinative, though. See the data and you often really don't need the code, but even understanding the org chart isn't enough. You also need history, and some other stuff.

Still, there is a general analog, in that it's a big danger in this role to think that it's about the produced architecture rather than the structure of the business, which "capturing in data and shared terminology" is a very good starting point for.

[kevinmchugh]

You're getting close to Conway's Law

[jerf]

Well, that's part of what I meant by "it's not quite as determinative". Conway's law constrains solutions but it doesn't determine them; it's not a 100% guidepost the way "letting me see your data" almost does 100% show what the code needs to be, at least at some level of abstraction. I feel like there's some stronger formulation that may more strongly narrow down how the architecture has to look than just the org chart.