What is the Root of Knowledge?

Jonaton Pie ~ Stakkholtsgja Canyon, Iceland
Jonaton Pie ~ Stakkholtsgja Canyon, Iceland

I've been thinking a lot about what makes people want to create, invent, innovate, learn.  So many of my colleagues and friends are innately curious and I know that, for me, learning is an addiction.  So, appropriately, I was reading one of my favorite philosophers/theologians and found this:

““Wonder rather than doubt is the root of knowledge. Doubt comes in the wake of knowledge as a state of vacillation between two contrary or contradictory views; ... the business of doubt is one of auditing the mind’s accounts about reality ... “”

— Abraham Heschel, "Man is Not Alone," pg 11

We certainly learn through doubting - we gain knowledge and insight by doubting, questioning, and even doubting our doubts.  But at the root of it all, what gets us to doubt in the first place, is our ability to wonder, to ponder, to think.  

How much more would we learn if we could wonder as we did when we were 4 or 5 or 8 years old? What can we try to truly wonder about this week? I'm curious!

Look for What's Working!

img-2.jpg

May - when spring really starts for many of us in the 'north'.  So, just a short blog - more of a request.  

This week, instead of looking at what's not working all the time, try 2 times, just 2, to find what's working, why it's working and how you can make that happen more.  Try this at work, at home, wherever you want - but please, try it - just twice, that's not asking a lot....

“Find what’s working & why! #BrightSpots”

Let me know how it goes! Feel free to share!

Pre-Natals vs. Post-Mortems

So often, when a project or product doesn't go well or fails, organizations do "post-mortems" - they go over what went wrong, why, sometimes rushing to blame people first instead of looking at processes.  

What if we started doing pre-natals instead of post-mortems? What if our cross-functional teams, at various steps in project or product development, examined why, what and how they were doing, what was working and why, what wasn't and why, and discussed all the things that could go wrong from that point on and why they could go wrong and how they could mitigate or eliminate those risks?  Then they could prioritize all that based on probability and possibility, make sure they are on top of those and do this regularly throughout development.

This isn't a fail-safe, but chances are a lot of problems could be caught, corrected and learned from before they happen and the more you do pre-natals, the better you'd get! 

Worth a shot isn't it?