Information flow related aspects should be used for deciding what kinds of user interfaces are needed (for example, what forms, reports and their elements are needed and how forms should be linked and accessible).

Information flow should be assessed above all from application's usage prospective. From an individual user's prospective information flow means the total experience that the user has and combines content, user interface and application's navigation structure usage experience. Content, navigation tools, selection of buttons and fields that the users can interact with and additional features should be presented so that they allow users to experience a coherent flow of information when they use the application.

So, the information should be grouped or distributed on the user interfaces based on information flow.

However, when user interface is developed by following subject matters instead of information flow, it may seem that it is a good idea to group absolutely all the information regarding, for example, organizations in one place and all the information regarding people in another place so that all the fields regarding particular subject matter are displayed together and the application's users interact with the fields they need and skip the rest.

Similarly, it may also seem like a good idea to focus on trying to fit as much information as possible on each row and on every page.

However, in most instances during specific type of application usage processes application's users interact with particular fields that characterize the subject matter, and then need to interact with another, closely related subject matter. Again, organizations and people can be provided as an example. So, the user interface and options available on the user interface should be based on application users needs and help to produce coherent flow of information for the users.