“Here are a few questions I reflect on:
– Am I excited to be doing what I’m doing or am I in aimless motion?
– Are the trade-offs between work and my relationships well-balanced?
– How can I speed up the process from where I am to where I want to go?
– What big opportunities am I not pursuing that I potentially could?
– What’s a small thing that will produce a disproportionate impact?
– What could probably go wrong in the next 6 months of my life?”
Zat Rana on here on Business Insider.
The link above provides some insights into the way some of the world’s greatest innovators have tackled the challenges that lay before them. It espouses the benefits of Reflective Thinking versus the current mindset of Doing Thinking, as discussed here earlier.
If you were to follow Zat Rana’s suggestion of allocating two hours a week to reflective thinking, what are the seed questions you could ask? Would the list above work as a starting point? Perhaps something more specific to your situation?
Here are a few other possibilities:
- Do I know what (my) OSS will look like in 5 years
- Am I satisfied that (my) OSS is actually helping outside operations
- What tangents could (my) OSS take to improve the world
- Where does complexity stem from that impacts (my) OSS
- Which areas can I pare back with negligible impact
- What is the OSS moonshot that changes the landscape forever
- What is my lead domino(es) (ie What’s a small thing that will produce a disproportionate impact?)
- Have I thought about what might impact business continuity
- How can I impact the bigger bodies (eg CSPs, vendors, standards bodies) around me