The view of information and pattern recognition.
April 11, 2019
When looking at Idea/Concept refinement, there is an overall flow that could be described as this:
information -> comprehension-> pattern recognition -> simplification -> evaluation
(but a loop, as the evaluation lead to new information)
This loop will occur both during the problem definition phase, as well as the solution definition phase, but seeing as the evaluation phase may change the information to a very large extent, this may lead to a new definition of the problem as well as the solution (as described by Kees and Nigel), i.e. there is an iterative process occurring.
In the article describing the difference between radical and incremental front.end development, they seem to make a difference between the processes in these two situations, describing the radical process as ”probing”, ”learning” and highly driven by ”individuals”, whereas the incremental process is described as ”proficient product portfolio planning”. In other words, the incremental process is assumed to gain nothing or little by having a probing and vast information gathering process. Instead the refinement process is found to best be dealt in-house by the group that is used to this type of pattern recognition in this type of information/data.
If we look at ”co-design”, and the article by Trischler et al, they conclude that codesign and teams with a broader information source, as well as a broader, but still experienced pattern recognition proficiency (i.e. both clients and professionals) result in solutions to more user focused problems, and therefore more unique and relevant solutions, yet feasible solutions.
This is further explained by Sukhov in the article on the importance of comprehension of an idea.
I want to add more to this.
Hang on!