{"id":1843,"date":"2026-10-09T15:15:00","date_gmt":"2026-10-09T15:15:00","guid":{"rendered":"https:\/\/bizdom.app\/?p=1843"},"modified":"2026-10-09T15:15:00","modified_gmt":"2026-10-09T15:15:00","slug":"approval-window-winery-decision-tempo","status":"publish","type":"post","link":"https:\/\/bizdom.app\/en\/legacy-innovator\/approval-window-winery-decision-tempo\/","title":{"rendered":"The proposal nobody rejected and nobody scheduled"},"content":{"rendered":"

Most stalled modernization at a heritage winery was never rejected \u2014 it was never scheduled to be decided.<\/strong> The Approval Window is a short recurring meeting with a fixed three-part agenda, where every item carries a decision date and a stated default so silence still produces a choice somebody made. Top-quartile wineries grew DTC revenue 22% last year while the median was flat and the bottom quartile fell 13% (Silicon Valley Bank, DTC Wine Report 2026).<\/p>\n

Go back to something on last year’s plan that never happened, ideally something you still believe in. An entry program for younger buyers, a reworked allocation flow, a change to how the release is offered. Now try to find the moment it was refused. At most heritage estates, there is no such moment. There is a conversation in March that went well, a follow-up in April that got a “let me think about it,” a founder traveling in May, and a plan that quietly stopped being mentioned.<\/p>\n

Nothing was decided. That is the finding, and it is different from the one everybody assumes. The blocker at an estate in generational transition is rarely a no. It is the absence of a scheduled moment at which a yes could be given, which means your rate of change is set by whoever on the family side is hardest to get hold of.<\/p>\n

The Approval Window<\/h2>\n

The Approval Window is a recurring, short, scheduled meeting with a fixed agenda and one unusual rule attached to every item on it. It is the least sophisticated idea in this series, and it recovers more time than either of the other two. Three components.<\/p>\n

Component 1: One standing window, same three items<\/h3>\n

Put it on the calendar as a recurring commitment with the founder or the family principal: thirty minutes, every two weeks or every month, whichever survives contact with harvest.<\/p>\n

The agenda never changes, and its fixity is the point. What shipped since last time. What it did. What needs a decision today. Three sections, in that order, and the order matters: you open with things that already happened and their results, which is the only reliable way to make the third section feel routine rather than adversarial.<\/p>\n

Keep it short deliberately. A thirty-minute standing commitment survives a busy season; a two-hour strategy session gets canceled in September and never returns. The value here is entirely in recurrence, not in depth, because what you are buying is a known date rather than a longer conversation.<\/p>\n

Component 2: Every item carries a decision date and a stated default<\/h3>\n

This is the component that does the work, and it is one sentence per item: if no decision is made by this date, this is what happens.<\/p>\n

Write the default as the lower-risk option and write it in advance. For a proposed change, the default is usually that it does not ship this cycle and returns at the next window. For a change already running as a pilot, the default is usually that it stops. The specific default matters less than its existence, because the function is to convert silence into a choice somebody made rather than a delay nobody owns.<\/p>\n

Say plainly why you are doing it, because a default can be read as a squeeze if it arrives unexplained. The reason is that a proposal sitting unanswered is currently being read as a refusal by your team and as a not-yet by the founder, and those two readings diverge quietly for a quarter before anyone notices. A stated default ends that divergence without requiring anyone to be more decisive than they want to be.<\/p>\n

There is a version of this that fails, and it is worth naming so you can avoid it. If every item you bring carries the same default, namely that it ships unless somebody stops it, you have not built a mechanism; you have built a dare, and it will be read that way inside two cycles. Vary the default by what the item actually risks. The ones that should default to shipping are reversible operational items that are in the room for visibility rather than for permission. The ones that should default to waiting are anything a buyer reads as identity. Getting that distinction right is what earns the device its credibility, and the credibility is the whole asset.<\/p>\n

Component 3: Bring them in a batch<\/h3>\n

Ten changes arriving separately over six weeks are ten interruptions, and each one gets its own small negotiation, often with a different amount of attention and a different mood behind it.<\/p>\n

The same ten, presented together, become a program. The founder can see proportion: eight timing and sequence changes, two that touch a surface a buyer reads as identity. That proportion is itself reassuring, and it is invisible when the items are delivered one at a time. Batching also lets you show the trade explicitly, which is the conversation you actually want: here is what we are not touching, and here is what we would like to move.<\/p>\n

This is where the previous two systems pay off. The register tells you which items are even in scope, and the reversibility test tells you which of them belong in this room at all. Without those, the batch is just a longer list.<\/p>\n

What Changes When the Calendar Does<\/h2>\n

The first effect is measurable within a quarter, and it is simply that decisions happen. Not more approvals, necessarily; decisions, including refusals, which are considerably more useful than silence because a refusal can be worked with.<\/p>\n

The second is competitive, and it is worth being precise about the evidence. Top-quartile wineries grew DTC revenue 22% last year, while the median was flat and the bottom quartile fell 13%, across roughly 450 wineries (Silicon Valley Bank, DTC Wine Report 2026). That spread opened inside the same channel, the same contraction, and the same conditions. It is not a channel difference. It is an operator difference, and the most mundane input to being on the right side of it is how long your estate takes to decide something.<\/p>\n

There is also a smaller effect on your own reporting, and it arrives before either of those. A window produces a list, and that list is the answer to a question you are asked at every quarterly review and have never had in a defensible form: what did we actually change this quarter, and who agreed to each one.<\/p>\n

The third effect is about what delay costs on the acquisition side, which is the line a Legacy Innovator is usually measured on. The generational opening is real: 45% of 21- to 28-year-olds say they are interested in drinking more wine, and Millennials are now the largest share of wine drinkers (BMO Wine Market Report 2026). That is an opportunity with a clock on it, and the entry program that slips two quarters is not neutral in the meantime. It is two quarters of a cohort forming habits somewhere else.<\/p>\n

The Objection You Will Hear Internally<\/h2>\n

Somebody will say the founder will not commit to a recurring meeting, and that trying to schedule them is how you get quietly written off.<\/p>\n

Do not ask for a meeting, then. Ask for a slot inside something that already exists: the production review, the monthly numbers call, whatever the family already sits in. Ten minutes at the end of an existing commitment beats thirty minutes in a new one, and the agenda works at either length. The recurrence is the requirement, not the room.<\/p>\n

The second objection will come from you, if you are honest, and it is that defaults feel like an ultimatum dressed as a process. They would be, if the defaults were aggressive. Write them conservatively for the first two cycles and let the mechanism prove itself as a way of protecting people from deciding by accident. Once the founder has seen a default protect a decision they would have made anyway, the device stops being read as pressure.<\/p>\n

This Month’s Action<\/h2>\n

Find the recurring meeting that already exists and ask for the last ten minutes of it, once a month, with the three-part agenda.<\/p>\n

Then take one stalled item, the one you most believe in, and write it up in four lines: what it is, what it would touch, what happens if we do nothing, and the date by which a decision is needed. Bring that one item to the next window. One item with a date, decided, is a better demonstration of the process than any description of it.<\/p>\n

P.S.<\/strong> The three ideas this week share a shape. Each takes something that currently happens by memory, by instinct, or by chance, and gives it a written form: what is permanent, what can be undone, and when the rest gets decided. Monday’s email puts them together and shows what a heritage estate looks like when all three are running.<\/p>\n\n

\n
See how a standing approval window sets your DTC tempo<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

A stated default turns an unanswered proposal into a choice.<\/p>\n","protected":false},"author":1,"featured_media":1839,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[46],"tags":[],"class_list":["post-1843","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-legacy-innovator"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t