The author's main problem was that he tried to say "employ operational design" and describe at the same time what operational design is.

As to examples, the major headquarters that has been employing this the longest is USSOCOM, and all of those products are quite intentionally unclassified.

The purpose of design is to promote understanding; but perfect understanding that is then locked up in a vault is not of much value. They don't lend themselves to publication very well though, as the design diagrams require a guide to lead one through them; and if a picture tells a 1000 words, a design diagram often tells 1000 stories.

I can't speak for others, but ours work best in small groups with 2-3 of the designers providing a short tag-team brief, followed by a much longer tag-team Q&A.

To simply hang the picture on the web, or to write up an explanation leaves most thinking "what's the big deal," or "I disagree." But most walk out of the tag-team presentations with fresh ideas and perspectives and a deeper understanding of the problem they face, and that is the point of the process.