Most strategy documents are undated in the only way that matters. They carry the day they were presented and a finish line somewhere out in front, and nothing in between that anybody could be late for. The plan that came out of a global pharmaceutical company's digital strategy group had exactly two dates in it, both measured in days, and they were the only firm numbers anywhere in a document that covered three annual stages of technology, content and process work.
A usable draft of the strategic guidance, for the global commercial function, within thirty days. Final publication, to that function and to every market, within sixty. Everything else on the page was a priority, a layer or an outcome statement. The clock was the commitment.
The wording of the two dates is not symmetrical, and the asymmetry is the tell. The thirty-day figure is hedged: an estimate of when a usable draft would be available. The sixty-day figure carries no hedge at all. The internal working artefact was estimated. The promise to the markets was committed. Read together, they set a rule the authors clearly understood: the draft may slip a little, the publication may not.
The challenge
The group that wrote this document owned almost nothing it could point at. The governance model around it named six functions, and the split was clean. One designed new services and supported the work of making them more effective. One held the customer relationships and generated demand for marketing excellence. One sourced, reused and maintained the content assets. One ran business services and reporting at group and platform level. One built and evolved the content platforms. The strategy group's own line was to set strategic direction and issue guidance to regions, markets and brands.
That is a function whose entire output is a document. It does not ship a platform, so it cannot borrow a platform's release date. Its delivery date and its document's publication date are the same date, and a document without one is a function without a delivery.
The distribution plan made the deadline sharper rather than softer. The guidance had three routes out: published to the markets, fed into each market's own digital priority-setting, and taken up by the commercial and IT functions, with the strategy group holding representation at the steering forum on top. None of those is a shared drive. All three are somebody else's planning cycle, and planning cycles do not wait for a document to be finished properly. Arrive after the market has set its priorities and the guidance is a comment on decisions already made.
So the clock was not a productivity gesture. It was the difference between guidance that lands inside a decision and guidance that arrives as an opinion about one.
The approach
Put a date on a strategy document and it starts refusing content. Three effects are visible in this one.
The last year of the plan is thinner than the first, and deliberately so. The first year carries four key priorities and five named outcomes, specified down to the level of an interim campaign management solution across key digital channels and a plan for sourcing non-branded external content. The second carries four scale priorities and three outcomes. The third carries one priority, a single sentence about integrating the scaled platforms and partnering with the commercial function to operate localised experiences at scale, and three outcome lines, one of which repeats the second year's content outcome word for word. A document written against a deadline cannot manufacture detail about a year it cannot yet see, so it stops trying. The alternative, filling the far column with plausible sentences, is the thing that makes most three-year plans unfalsifiable.
Second, the layers keep the specificity honest where it does exist. Every year is resolved across technology, content and process, so no capability is allowed to advance on technology alone. The most checkable claim in the plan comes out of that discipline: the integrated operating model for the shared campaign and analytics capabilities is a second-year outcome, a full year before the platforms themselves are integrated. Process integration sequenced deliberately ahead of technical integration is a statement someone can be held to. It is also the sequencing most enterprise data programmes reverse, which is why they end up with a joined-up platform serving two organisations that still disagree about who owns the request.
Third, and this is the part that follows directly from the clock, the question the group could not settle inside the window is published as a question. The final page asks its own audience what other guidance the commercial and IT functions would need in order to be successful, and what format would work best. Format is treated as a first-order strategic question, not a production detail. A document with no deadline would have answered that quietly, badly, and in passing, because there would have been no cost to guessing. A document due in sixty days has to either settle it or say out loud that it is unsettled.
The same standard shows up in the guidance backlog itself. Fourteen named assets were listed, covering search, media, social, mobile, email, design and craft standards, campaign management, branded content, content-marketing training, sales-force digital aids and supplier selection. They were grouped not by topic but by state and priority: one group headed completed assets and assets to be reformatted, a second headed agency and priority assets, with a highest-priority box drawn around three of those. The second label in that first pair is the interesting one. It exists to hold content which already exists and is not yet usable. An organisation that will publish a category called "exists but not yet usable" is an organisation that has agreed what usable means.
The Platform work we do starts in the same place. State belongs on the record next to the asset, so the difference between held and usable is a field a pipeline can read rather than a judgement somebody makes again each time.
The outcome
What the source records is a commitment and a route, not a result. Two dates, three distribution paths, a governance seat, a backlog with declared states, and an open question to the room. It does not record whether the draft landed on day thirty or the publication on day sixty, and this piece will not pretend otherwise. Every number here is a plan.
The plan is still worth taking seriously, because of one further detail. The analytics capability in the governance model sits across all six functions rather than beside them, and it is given two mandates. The first is the usual one: insight at group, region and market level, with dashboards, measures, tracking against targets, and campaign effectiveness. The second is unusual. Analytics is also chartered to support conformance to the strategy and course correction, explicitly including whether the content is being used, which means measuring whether the published guidance was actually taken up. The same organisation that promised a usable draft asked somebody to prove afterwards that it got used. That closes the loop the deadline opens.
The document that occupies this slot today is the data and model readiness plan, and it is usually written without a clock. It describes the pipelines, the feature store, the lineage the auditors will want and the deployment path a model will take to production, and it takes long enough to write that the estate it describes has moved by the time it is circulated. Our Consult engagements start by asking for the two dates, in that order: when is a usable draft available to the function that has to act on it, and when is it published to everyone. What survives that question is a shorter document with clearer holes in it, which is the correct shape.
The same applies to the guidance most organisations are now trying to write about where language-model pilots may and may not be used. That guidance is worth very little at month nine and quite a lot at week four, because the pilots are already running. Ship the usable draft, name the format question as open, and let the people who have to follow it tell you what they need.
A deadline on a strategy document is not a project management preference. It is an editorial instrument. It decides what the document is allowed to claim, and it converts every unresolved question from a quiet deferral into a written one.