Instead of a waterfall style of software development where the development follows the design process, I wonder if anyone has experience with what I am dubbing the 'fountain well' style of product development where the developers rapidly prototype the product to lock in the functionality and then the UX/UI designers refine the look and feel, but in a way that does not impact on the function or business logic of the product/service.
I have seen this process applied where Agile teams are able to decouple the business logic from the implementation framework/platform, and where the visual and interaction design logic is also abstracted away from the implementation details. I am wondering if any developers or designers have applied this approach to product/service design, and whether the project outcome has been successful in terms of meeting project schedule and resources/budget.
I think it is important to make some distinction of this process compared to waterfall and Agile methodologies, in the sense that even though the design and development processes can occur in parallel, the development proceeds the design and after the design implementation there is a minimal amount of effort incurred in refactoring the design to developed product/service.
The question I would like to ask is whether the decoupling of the business process design from the solution architecture design and the user experience design is a different way of product/service development compared to LEAN and AGILE development processes, and therefore should be referred to as a different style of product/service design and development.
I have found a paper on a 'fountain' model of software development, but have read through it because it seems to describe something different even though the terminology is similar.