All necessary options should be visible, intuitive, and accessible … think one degree of separation.
Kevin Bacon was not too far off the mark: there really are no more than six degrees of separation between you and just about anything you’d care to be in touch with—even in a software product. However, that is not to say that everything needs to coexist in the same screen real-estate. Immediate goals naturally lead to secondary, related goals. It is entirely possible to map out how goals cascade into one another. Within this view of an application, smart decisions about how to create interface flows can be made. In Agile software development, this might reflect a necessary concept of a “genealogical” map of story relationships. (For the layperson, a story translates into a contained, feature-requirement in product development—these are typically small, self-contained, and able to be described in a sentence). A recent story exercise we went through on the Product team yielded 43 stories within the first two days. It might make perfect sense to show how these stories are interrelated in some kind of a family tree. These series of relationships will most certainly positively-affected decisions about how to create software-level, graphical user interface navigation and paths between objectives.
Kevin Bacon was not too far off the mark: there really are no more than six degrees of separation between you and just about anything you’d care to be in touch with—even in a software product. However, that is not to say that everything needs to coexist in the same screen real-estate. Immediate goals naturally lead to secondary, related goals. It is entirely possible to map out how goals cascade into one another. Within this view of an application, smart decisions about how to create interface flows can be made. In Agile software development, this might reflect a necessary concept of a “genealogical” map of story relationships. (For the layperson, a story translates into a contained, feature-requirement in product development—these are typically small, self-contained, and able to be described in a sentence). A recent story exercise we went through on the Product team yielded 43 stories within the first two days. It might make perfect sense to show how these stories are interrelated in some kind of a family tree. These series of relationships will most certainly positively-affected decisions about how to create software-level, graphical user interface navigation and paths between objectives.
No comments:
Post a Comment