You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue follows the discussion that emerged in the thread I brought about managing tension.
I realize that for as long as I can remember, I have felt that tensions are not in their proper place. #429 (comment) #429 (comment)
Tensions can be dealt with quickly in one step, or they can last over time and be the subject of many steps, including projects, actions, governance changes, strategies, etc.
And Tension is a different concept than a Project. A Project is defined by an expected specific outcome, whereas Tension is a gap between the actual expression of your Role’s Purpose and Accountabilities to your vision of their ideal potential.
Managing a project requires defining Next-Actions.
The management of a Tension - i.e. trying to enact your vision by taking steps to reduce or resolve those Tensions - can be much broader and is driven by a vision that is not necessarily attainable. The objective here is more the creative energy given by sensing the Tension itself as a gap you want to reduce, which allows to move things towards the vision, more than the result itself. Moreover, from experience, the vision of a Tension may evolve overtime as I take steps to reduce it, as it matures.
IMO, it is therefore appropriate to manage Tensions just as one manages a project and make Tension parallel to Project./Next Action.
See pull request 12dbac1
The text was updated successfully, but these errors were encountered:
This issue follows the discussion that emerged in the thread I brought about managing tension.
I realize that for as long as I can remember, I have felt that tensions are not in their proper place.
#429 (comment)
#429 (comment)
Tensions can be dealt with quickly in one step, or they can last over time and be the subject of many steps, including projects, actions, governance changes, strategies, etc.
And Tension is a different concept than a Project. A Project is defined by an expected specific outcome, whereas Tension is a gap between the actual expression of your Role’s Purpose and Accountabilities to your vision of their ideal potential.
Managing a project requires defining Next-Actions.
The management of a Tension - i.e. trying to enact your vision by taking steps to reduce or resolve those Tensions - can be much broader and is driven by a vision that is not necessarily attainable. The objective here is more the creative energy given by sensing the Tension itself as a gap you want to reduce, which allows to move things towards the vision, more than the result itself. Moreover, from experience, the vision of a Tension may evolve overtime as I take steps to reduce it, as it matures.
IMO, it is therefore appropriate to manage Tensions just as one manages a project and make Tension parallel to Project./Next Action.
See pull request 12dbac1
The text was updated successfully, but these errors were encountered: