Behaviors/dynamics can be discussed and analyzed as discrete "objects" under your control. Design discussions should often be taking place at the level of the dynamic rather than the level of the functionality. Identify what behavior you want to change first, then piece together the necessary functionality that you believe will enable that... See more
fascinating insights on designing products from the previous head of design at Quora. think of the dynamic, not the functionality, then piece together the necessary functionality.
I believe the primary job of a product designer is to drive behavior , not build functionality. You should be measuring your success in terms of the quality of the resulting behavior, not the quality of your deliverables.