I’ll share with you an interesting reflection found in the book “Prototyping” by Todd Zaki Warfel regarding why we don’t expect prototyping as stage in the process in software development, regardeless the myth of the “return of investment”:
I think the first reason is that in software development, the emphasis is often placed on the development process and not the design process. The industry doesn’t call it “software design”; they call it “software development.“
In software development, design is often an afterthought. The emphasis is on the technology or features—not the design. In architecture and industrial design, however, the emphasis is on design. Form follows function.
Another reason is that software development is seen as a manufacturing process, but architecture and industrial design are seen as a craft.
In the following pages we’re introduced to the concept of Design studio, which is very common in other design fields:
In studio classes, you design or prototype and present to your peers. Your peers critique your work, highlighting the strengths and areas that still need some work.
Prototypes are not just a tool to communicate or to describe ideas, but also a work methodology, a phylosophy where sharing, colaborating and criticizing can speed up the process, prevent future failures and empower peers into trust and success.
It’s not a believe, fortunately I could check it by my own in my short experience, so the answer from my viewpoint is clear:"Yes, the software industry must learn a lot from other fields and design can help to lead that subversion”.