Every workplace plan carries a picture of the future, even when no one writes that picture down. In the 2017 conversation, Jeff Saunders explained a foresight process for making those assumptions visible and testing them through more than one scenario.
The technology examples and predictions belong to 2017. The planning move does not require treating them as current: name what the team assumes about growth, competition, technology, and work before that assumption quietly guides the budget, space plan, or service model.
Jeff's contribution was not another trend list. It was a method for turning assumptions into something the team can inspect.
A future strategy gets stronger when the assumptions are explicit
Jeff Saunders described the first move as helping teams “make explicit their implicit understandings of the future.” His 2017 process then separated high-impact drivers from uncertainties and used scenarios to test a strategy across different conditions.
That is a better planning discipline than waiting for certainty. A team that surfaces its assumptions can ask harder questions. Which trends are real enough to plan around now? Which uncertainties should produce more than one scenario? Which current strategy would still hold if the environment shifts faster than expected?
Those questions do not predict the future. They expose what the current plan depends on.
Function is not the whole workplace experience
In the 2017 discussion, Jeff also pushed facility thinking past function alone. He argued that a workplace was not only a container for tasks. His framing included belonging, connection, inspiration, and the experience employees had while trying to do useful work.
In Jeff's 2017 framing, focusing only on square footage, desks, or amenities could miss end-user needs such as belonging, connection, choice, and inspiration.
His answer was to study the end user more closely. Not only the building system. The human journey through the day.
Some relationships should stay transactional. Others should not
Another part of the episode was Jeff's distinction between transactional outsourcing and deeper co-sourcing relationships. He described some services as interchangeable market purchases and others as more interdependent relationships with shared information, risk, and reward.
That is a strategic choice, not a procurement habit. If the work is simple and price sensitive, a transactional model may be enough. If the work depends on understanding employees, experience, and multiple touchpoints across physical and digital systems, a shallow vendor relationship can start to limit the result.
A workplace strategy can get stuck here. The organization wants integrated outcomes while managing every provider as if the cheapest substitute could do the same job.
Resource allocation should follow the work, not the old asset pattern
Jeff also challenged fixed assumptions about space and services in 2017. He asked why organizations held underused desks, amenities, and fixed costs when community or shared options might cover some needs more flexibly.
The 2017 example does not make every owned asset a mistake. It provides a review question: why does each major resource support the way this organization expects work to happen?
Take one workplace or service decision and write the future it assumes, the employee need it is meant to support, and the resource it protects. Test that decision across multiple materially different scenarios. The workplace owner can then keep, revise, or defer the choice with the assumptions visible.
The planning choice is practical: leave the assumption hidden, or name it so the team can decide whether the plan survives a different future.
