What I might do is to first, study how designs are justified and argued for, second, to analyse this logic of design, and third, to see what implications this might have for how we publish designs, present design proposals.
Designs always come with an argument. In professional practice, you almost always say “here is our design, and here’s why you should invest resources to produce it”. In academia, you say a subtly different thing, “here is our design, here’s what makes it new and unique, here’s what it’s good and bad at, why you might want to make something similar, etcetera”. It’s much less a proposal than a set of claims in academic work.
Come to think of it, I’d be curious what the answers would be if you simply asked engineering designers at universities the question “why do you publish your work?”, “Apart from being cited and adding to your list of publications, what would you like the effect of your publications to be?”, “What function does it serve to publish designs?”
Then again, do we really publish designs? Or is it that we publish about our designs? Yes, the basic principles and construction methods are usually described in a paper, but it’s far from the design information in patent applications, let alone from open source software.