2690 field guide
The launch spreadsheet is doing more work than it should
How to move from manual status updates to a shared launch record while keeping the tools that already work.
A spreadsheet is often a good first launch plan. It becomes harder to trust when a brand adds more products, channels, agencies, vendors, and approvals. The problem is rarely the spreadsheet itself. It is that a date or offer changes and nobody knows which of the other places now needs updating.
Start with the change that hurt
Pick a recent launch where the team lost time. Follow one change: perhaps a launch moved two days, an offer changed, or an asset was replaced. Where did the decision originate? Who learned about it? Which files or tools still showed the old state? That path shows the seam to fix.
Give the launch one shared record
The record should hold only what the team uses to coordinate: launch date, offer, product, channels, assets, owners, approvals, and current status. Each field needs a clear owner. The record should link to the underlying files instead of trying to replace every specialist tool.
Record decisions, not just checkboxes
A checked box says very little when the date changes. Capture who approved an item, which version they approved, and when. If a dependency changes, make the affected work visible again. This gives the team a useful history and a way to distinguish “done” from “done for the old plan.”
Only then reduce the manual updates
Connect the records and tools that have reliable interfaces. Automate notifications or status changes with clear rules. Keep manual review where a judgment, legal claim, budget decision, or partner commitment is involved. AI may later help summarize open issues or spot missing information, but it should read from the same trusted record as the team.
A good first build might cover one launch type and one channel. Measure the time from a changed decision to an updated plan, the number of stale handoffs, and how often the team has to ask for status. Expand only when that first path works.
Keep exploring
Explore the product-launch workflow or the 2690 Build.