You start with an outline. You bolt literate programming onto it. Then you tell your code blocks they can send input and output to each other via text in the

You start with an outline. You bolt literate programming onto it. Then you tell your code blocks they can send input and output to each other via text in the document. Now you've got an excruciatingly well documented multi-language pipeline. Then you get the source data for all your analyses in real time from [wherever they came from]. Then you render it _beautifully_ with your dependency graph documentation generated from graphviz (which graph data was newly inferred on this very run). My first org-mode killer app, years and years ago was a monthly billing collection and analysis for a backup system I was running. The first pass took me a week to figure out how to collect and analyze. A few iterations later it was literally open the org-mode document and tell it "Do the thing". All my intermediate work was shown, everything was clear and open to inspection, and beautifully typeset. And I could generate it as HTML if they wanted it in a web page. (at the time they wanted PDF). This is one of the ways org-mode is great. There are others. :)