this is a good article. but a better analogy is needed. batter is a pre-baked cake. in the development cycle, everything is pre-baked until it is in an operational context: ready for “consumption” or use.
this is especially important if some aspects of code can be reused from one point in construction to another or there is a library component.
this is also quite different from the analogy being drawn here, and one that is especially important for junior designers, devs & stakeholders alike: a list of ingredients is always separate from the final form. if the deliverables, specification & requirements describe the form, they also need to describe what the thing does. the lean process, while difficult to portray to “clients” in some product cycles, can in the hands of a “blended” team (I really hesitate to use that term), help people see the potential of a product, or the explicit & vital, experience far faster than non responsive images strung together in “sequence” as far as can be “predicted” by the designer or product owner.
the “artefact” is invaluable for a wide group of stakeholders, especially where there is a chasm to fill in terms of their understanding. but it needs to be noted that drawing a website is not the same as designing one.