The idea is new. The workload is not.

A new podcast. A better campaign. A fresh way to reach customers. Each sounds promising in the meeting where someone proposes it. The trouble starts when the person responsible returns to a calendar already full of work that nobody has agreed to stop.

In this ChatGTM conversation, Andrew Davis challenges the familiar request to think outside the box. Beck and Chad explore the practical problem underneath it: an imaginative solution still has to work with the people, time and resources available. Borrowing an idea from a better-funded competitor does not bring that competitor’s budget along with it.

Davis makes the case for defining the box more carefully. Useful constraints give people something concrete to solve. Without them, a team can spend a remarkably productive afternoon inventing work it has no capacity to do. The question becomes less about how many possibilities everyone can name and more about which possibility they can actually carry through.

Make room before asking for more

Davis describes four constraints: eliminate the unnecessary, define a clear singular outcome, further limit the options, and raise the stakes. The first deserves attention before the excitement of a new initiative takes over. He recommends removing at least two things when adding something new.

That is a management decision, not an instruction to an overloaded employee to become more efficient. Even work that is no longer moving can occupy someone’s attention if they still believe they are responsible for it. Giving permission to stop matters as much as assigning the next project.

The conversation uses a podcast launch to make the point tangible. An initial goal might be one lead in the first month. The equipment might be limited to an iPhone. A launch date creates a boundary, while the chance to take ownership of the podcast gives the employee a reason to care. These are examples of how to frame a project, not a claim that any particular podcast produced that result.

For a hospitality or technology team, the useful application is to name the work being retired in the same conversation that approves the new work. A project brief that lists only additions has left out an important part of the assignment.

A smaller assignment can produce a better answer

An open-ended request to improve marketing gives a team almost nowhere to begin. Davis’s examples narrow the problem: a specific result, a limited number of people, an available channel and a deadline. The limitations force choices that a broad ambition can postpone indefinitely.

He also distinguishes a constraint from an excuse. A lack of equipment might suggest using the phone already in someone’s pocket. A lack of time should prompt a discussion about what can stop. Procrastination may point to unclear stakes. The point is to make the obstacle specific enough to work on.

When the discussion turns to restaurants, Davis offers a thought experiment about focusing on the guest experience with existing people and resources rather than simply adding advertising. He explicitly acknowledges that he does not know the industry well enough to prescribe the answer. It is a prompt for exploration, not evidence that an advertising pause will preserve traffic.

Our practical reading is to begin with a bounded experiment and a clear measure. Pick one guest experience the team can improve, decide what success would look like, and protect the capacity to try it. That application is ours; the episode does not provide a tested restaurant playbook.

More content still needs a reason to exist

AI enters the conversation as another way to think about constraints. It may help clarify a problem or explore options. Davis is careful about the limits of his own experience, saying he has not yet tested giving the tool this framework. The discussion is exploratory, rather than a demonstration of a proven AI workflow.

The distinction matters for teams suddenly able to produce much more material. Output is easy to count. Whether someone has a reason to pay attention is a harder question. Davis considers who would pass a piece of content along and what they would say about it. He presents that as a question he is still working through, not a formula he has solved.

He also separates curiosity from disappointment. Creating tension can draw someone into a story, but the payoff has to justify the attention. A clever opening that leads nowhere may win a click while teaching the audience to distrust the next one.

Give the next idea a fair chance

The conversation leaves room for play and practice. Childhood boredom, improvised projects and the repeated development of a keynote all appear in the discussion. Creative work does not arrive fully formed just because someone has announced a brainstorming session.

For the next initiative, start with a short set of decisions: what stops, what one outcome matters, which resources are available, and why the result matters to the person doing the work. Those decisions will not guarantee a brilliant idea. They give a useful idea somewhere to go.

A team does not always need permission to think bigger. Sometimes it needs permission to finish something smaller, without carrying every previous assignment into the room.

Hear the full conversation