How to Create a Useful Not-Now List for a Growing Team

Growing teams generate more sensible ideas than they can pursue. When every proposal remains half-alive, priorities blur and people keep revisiting the same debate. A not-now list gives worthwhile ideas a respectful place to wait. It is different from a backlog with implied commitments and different from a graveyard nobody reviews. Used well, it protects current work while preserving context for later decisions.

Give the list a clear purpose

Define what belongs on the list. A good candidate is relevant to the team’s goals but not important enough to displace current commitments. Ideas that clearly conflict with strategy should be declined, not parked. Urgent risks should enter the active decision process. The not-now list is for plausible options whose timing or evidence is not yet right.

Tell the team what placement means: the idea is recorded, not approved. That distinction prevents contributors from treating the list as a promise. Readers may also want to visit Search-Zero. The label matters less than a shared definition.

Keep the list visible in an existing workspace. A separate application creates another place to forget. Give one person responsibility for maintaining the format, but allow anyone to propose an item.

Save enough context for a future decision

A title alone rarely survives the passage of time. “Improve onboarding” will mean something different to each reader several months later. Capture the customer or operational problem, the expected benefit, the evidence available now, and the reason the team is waiting.

Each entry should answer a few compact questions:

• What problem or opportunity prompted the idea?
• Who is affected, and how do we know?
• Why is this not the right time?
• What event or evidence should reopen it?
• Who can provide context if it returns?

Add links to useful notes rather than copying every discussion. Avoid detailed plans for work that may never happen. The purpose is to preserve decision context, not to perform the project in advance.

Set triggers instead of hopeful dates

Arbitrary review dates can fill meetings with stale items. Whenever possible, attach a meaningful trigger: completion of a related launch, repeated customer requests, a change in capacity, new evidence, or the expiration of a temporary constraint. A calendar review can still catch items without natural triggers, but it should be occasional and brief.

When a trigger occurs, reassess the idea against current priorities. Do not assume an old proposal is still the best response to the problem. You can also visit Go And Grow Online for more reading.

Items also need an exit. If the underlying problem disappears, the strategy changes, or the evidence remains weak after repeated review, close the item with a short reason. An archive preserves the history without crowding the active view.

Use the list to improve conversations

The list should make it easier to say “not now” with honesty. Explain which current commitment the new idea would compete with and what could cause reconsideration. This respects the contributor while keeping the team focused. Do not use the list to avoid difficult refusals or to create the appearance that every suggestion will eventually happen.

Review patterns across the entries. Many similar ideas may point to a recurring customer problem. Repeated deferrals caused by the same missing skill or approval may reveal a capability constraint. For a related read on this site, see How to Build Honest Client Relationships in a.

Keep the ritual light. A short review by the relevant decision makers is better than reading the entire list aloud to everyone. Share which items moved, closed, or stayed parked and why. That feedback builds confidence that the list is maintained rather than performative.

A useful not-now list reduces the emotional pressure to act on every good idea immediately. It lets the team finish what it has started, retains the reasoning behind deferred opportunities, and creates a disciplined route back when conditions change. The value lies not in the number of stored ideas, but in clearer choices about attention.

Be thoughtful about who can see and edit the list. Broad visibility can improve trust, while unrestricted editing can erase reasons or create duplicate entries. A simple contribution form with a maintained review view often balances participation and order. When an item is revived, link the new active work back to its original record. That connection shows which trigger occurred and lets the team evaluate whether its earlier decision to wait was sound.