Really in a project before the "fair" requirements are gathered; or we call the business requirements or requirement gathering in generic, how many times we would commenced with assumptions listing, more often this is a "Fuzzy source", that is not greatly documented or showcased as a engagement model. The assumption listing as bullet points is a straightforward approach, but these "Fuzzy sources" are like UFOs, blips, fuzzy creatures hovering like clouds bursting, blooming and wandering in different spatial times. Emerges in a linear or even radial order that which needs to be easily recorded in simple diagrams.
Connecting diagrammatically is a lucid natural approach to draw the fuzzy objects, and building these natural diagrams are the most essential means to end to start with requirement mapping, which can be naturally understood by other stakeholders as the fuzzy objects relate to their own fuzzy sources. What a natural extrapolating means? What a collaborative effort to clear clouds, rather assumptions. Building such Fuzzy sources are a commendable approach which also naturally creates dialogue - appreciation - translation. In creating a low-cost (resource efficient) fuzzy source is a good starting point when capturing requirements with Client - this often sometimes as in a UX Consultant world, be a rapid prototype to judge a use case or requirement flow or wireflow; a bridge that connects visual linkages to Structures or case docs. Fuzzy sources will stand as dialogues along with the rapid prototypes. Fuzziness is all we start with, appreciatively fuzzy needs to be represented for the onlookers or interested mob, an intertwined model of dialogue plus prototypes on this fuzzy is to be aimed for.