important

Prioritizing Urgent, Important, Unimportant, and Not Urgent

Dividing workflow into the quadrants of urgent, not urgent, important, and unimportant trends this time of year. Assuming this approach, the central question is, how might I focus most of my work on important projects? 

For me, this mindset does not embrace the human dimension. When we travel, we might select an itinerary that includes transportation, lodging, restaurant reservations, meetings, cultural visits, and free time. Not much of it will feel urgent if appropriately scheduled. Some moments will be important, and some will be unimportant or not urgent. But one missed transportation connection or meeting, and instantaneously, the urgent task of getting back on schedule dominates. The itinerary that avoided urgent defaults to that mindset after a disruption.

What we are likely to encounter is serendipity. A chance encounter with an individual who offers an opportunity to engage in a future project. An epiphany when engaging with a work of art or geographic location that reshapes the dimensions of our internal map. An unforecasted weather pattern that has us stepping off a plane wearing a parka in tropical heat or a t-shirt during an arctic blast. Suddenly, the unscripted moments become areas of focus. These unanticipated events shift our internal question: how might I get back on schedule and closer to my planned reality?

If we start by asking our essential question, then force ranking our time allocation into quadrants is less relevant. For example, if I commence an engagement by asking, how might I deliver remarkable service and insights to inspire those doing the work that matters? This mindset widens the scope of what is relevant to my work. During ‘unimportant’ times, I might encounter a way of presenting an idea that improves how I serve the client. I might reread a blog post that reframes a discussion during ‘not urgent’ time. And when the itinerary is shifted, requiring travel in the opposite direction to get back on track, it supports the essential question, allowing me to model retesting an idea before it is ready to launch.

What is/are your essential question(s) that might break quadrant-dependent scheduling?