A question to look back and learn

A question to look back and learn

This question comes with a health warning. Its purpose is to explore factors that have influenced (ie. helped and hindered) an outcome so that we can learn. To be most effective, this question needs to be backed by a genuine sense of curiosity. 'How did we get here?' is not code for ‘Who’s fault is this?’ The intention will determine the effectiveness of the question.

If this is your first time in Curly Question of the Week, its promise is simple.

One question, once a week.?

It’s the cognitive kick-starter that takes only five seconds to read but is packed with endless possibilities.?So, make sure that you SUBSCRIBE!

This week's question can help you look back and learn. And if you love it, why not give a thumbs up or share it?

No alt text provided for this image

Already taken this week’s question for a test-drive?

When did you ask it? How did it influence your conversation? Why not inspire others by sharing your experiences in the comments below.

About the Author:

No alt text provided for this image

Learn more at?www.katechristiansen.com.au

#curlythinking?#curlyquestions?#complexproblemsolving?#leadingchange??#disruption?#adaptiveleadership?#adaptiveteams?#momentum?#masterthemoment?#moveforward?#movewhatmatters?#mindset?#mindflow?#motivation

Richard Stockton

Project delivery advisor and recovery expert

2 年

Great question Kate - being heavily involved in project management I have seen the health warning first hand many times. The more leadership turn towards who’s fault it was, the less times this question gets asked. The less the question gets asked the less corrective action is taken. It’s like a silent health risk. If it is not picked up, it grows. This often leads to fractures between business units and technology teams where fear of speaking up results in substandard solutions and eventually technical debt in the environment. Most project recoveries I have participated in have uncovered too little time planning for more granular requirements understanding and more time in solution design. I think a lot of people consider spend in this area as problematic because they don’t see anything tangible quickly enough. But it always results in less spend in delivery and implementation when done right. Excellent start to the week - thanks

要查看或添加评论,请登录

Kate Christiansen的更多文章

社区洞察

其他会员也浏览了