Planning

Decomposing Light and Decomposing Planning

What might we learn from the decomposing light demonstration? Our perspectives change when we eliminate certain inputs from our environment. Nonprofit organizations that hold a planning retreat but decide not to include all staff members or to refrain from inviting the advisory council are effectively narrowing the range of ideas that will be illuminated. We do not have to invite everyone to every session, but when we are deliberately seeking a generative mindset, it might be valuable to pair people who do not meet in typical sessions.

How might our willingness to seek out weak ties actually strengthen the process?

Screenshot

Vanishing Point

We can map out our route until we cannot. There is a moment at which our planned itinerary contains a gap or uncertainty. It may appear that we are traveling a continuous path, but serendipity and detours will appear, even in the most detailed schedule of events. How might we expect the unexpected and embrace the elements of our plan that fall into place?

Who Is It For?

Two Starbucks, located across the street from each other, appear like poor business planning; until we recognize that the stores exist in an urban design that prioritizes automobiles. If ease of pedestrian travel were a preference, perhaps one store would be sufficient.

How might we understand ‘who it is for’ before we begin our design and implementation phase? Starbucks does not exist to serve vehicles, but it does serve people. That said, it inhabits an environment that has amplified the needs of motorized travel; therefore, its design model accommodates those arriving in vehicles.

What if we Postpone Buying for the Future

When we launch a new idea or product, it is our most recent (and hopefully best) version. It is the current model. When we purchase a new vehicle, software, or product, we receive what is currently in production. We cannot purchase and immediately use the coming model.

How might we embrace where we are and what we have? How might we not always be evluating our version versus the next itteration? How might we avoid prioritizing buying for the future when our needs might change?