Anchor Moments
Operating rhythm and recorded outcomes
The monthly rhythm consists of beginning-of-month anchor planning, a mid-month progress check, and an end-of-month review. Yoana coordinates; product owners provide briefs and own their product content. May content partly shipped. June DataHub, Flowershow, and Datopian Services content was recorded as shipped; PortalJS videos shipped while demo/article revisions remained open. The July process review outcome is unrecorded. Monthly execution and the continue/adjust decision belong in the operating tracker and the anchor log, rather than separate company project pages.
Previous promise (review outcome unrecorded): Every product has a confirmed anchor moment each month, executed and logged — v1.0 rhythm running through June 2026, reviewed by 2026-07-15.
A monthly marketing operating rhythm that ensures every product (PortalJS Cloud, Flowershow, DataHub, Datopian Services) has one defined focus point per month — the most important thing to communicate. Yoana owns the process; product owners and dev leads are responsible for brief input; content production follows from the anchor.
Channels by product
| Channel | DataHub | PortalJS Cloud | Flowershow | Datopian Services | CKAN |
|---|---|---|---|---|---|
| ✅ | ✅ | — | ✅ | ✅ | |
| Twitter / X | ✅ | — | ✅ | — | ✅ |
| Bluesky | — | — | ✅ | — | ✅ |
| Mastodon | — | — | — | — | ✅ |
| Datopian blog | ✅ | ✅ | — | ✅ | — |
| DataHub blog | ✅ | — | — | — | — |
| PortalJS blog | — | ✅ | — | — | — |
| Flowershow blog | — | — | ✅ | — | — |
| CKAN blog | — | — | — | — | ✅ |
| dev.to | ✅ | — | — | — | ✅ |
| Medium | ✅ | — | — | — | ✅ |
| ✅ | — | ✅ | — | ✅ (soon) | |
| YouTube | — | ✅ | ✅ | — | ✅ |
| Newsletter | — | — | ✅ | ✅ | ✅ |
| CKAN Monthly Live | — | — | — | — | ✅ |
Historical cycle checkpoints
| Milestone / checkpoint | ETA | Expected outcome | Done | Completion date |
|---|---|---|---|---|
| Operating Rhythm v1.0 designed and running | 2026-05-05 | Process defined, calendar invites sent, all POs briefed | ✅ | 2026-05-05 |
| May cycle — all active products | 2026-05-31 | Anchor confirmed and at least one piece of content published per product | [ ] | |
| June cycle — all active products | 2026-06-30 | DataHub ✅, Flowershow ✅, Datopian Services ✅ published. PortalJS 🔄 videos live, demos/article being revised per Rufus's feedback | [ ] | |
| v1.0 review | 2026-07-15 | Decision: process holds as v1.0 or iterated into v1.1 | [ ] |
Why this exists
Without a defined monthly focus per product, content output is reactive, inconsistent, and hard to coordinate across teams. The anchor moment gives everyone — dev leads, product owners, and Yoana — a shared reference point for what matters this month.
Current priority
Confirm the operating rhythm review outcome and current monthly focus in the tracker.
Links
- Process document v1.0: anchor-moments-process-v1.md
- Brief template: anchor-moments-brief-template.md
- Anchor moment log: anchor-moments-log
June 2026 Cycle
DataHub ✅
- Anchor: World Cup 2026 — carbon footprint, prize money, ticket prices (3 new datasets)
- Blog post: The Numbers Behind World Cup 2026
| Content | Channel | Status | Link |
|---|---|---|---|
| Blog post | Datopian blog | ✅ Live | The Numbers Behind World Cup 2026 |
| Blog post | DataHub blog | ✅ Live | Three World Cup Datasets, One |
| Post | LinkedIn (Datopian) | ✅ Done | |
| Thread | Twitter / X | ✅ Done | |
| Post | ✅ Done | ||
| Article | dev.to | ✅ Done | |
| Article | Medium | ✅ Done |
Note: Topic is still trending — worth considering a repeat/resurface push.
PortalJS Cloud 🔄
- Anchor: Civic data portal
| Content | Channel | Status | Notes |
|---|---|---|---|
| Video walkthrough — civic portal (iteration 2) | LinkedIn · YouTube | ✅ Published | William's final adjustments done |
| Video walkthrough — research portal (iteration 2) | LinkedIn · YouTube | ✅ Published | William's final adjustments done |
| Video walkthroughs — civic + research (iteration 1) | — | ⚠️ Not usable | Quality too low — replaced by iteration 2 |
| Blog post — "We looked at civic data portals so you don't have to" | Datopian blog · PortalJS blog | 🔄 In revision | Rufus reviewed the demos and article; both being updated per his feedback |
Status: Videos published early June; Rufus then reviewed the two demos and the article and requested changes. Current work: finalizing both demos to the required quality bar, updating the walkthroughs, and revising the agreed article series. Distribution so far is mainly LinkedIn — dev.to, Medium, and the rest of the social channels (incl. Reddit) are planned once the articles are finalized, since those channels matter most for the (non-promotional) articles.
Flowershow ✅
- Anchor: Publishing content with AI on Flowershow
- Source: Brief from Ola
- Status: Executed — published on Reddit, Bluesky, and the Flowershow newsletter (LinkedIn not activated, per Ola's decision)
Datopian Services ✅
- Anchor: Bhutan data portal
- Status: Executed — 3 LinkedIn posts published (links TBD)
Notes
- Developer involvement cannot be engineered away — content is often technical. The process must be resilient and fast-recovering, not failure-proof.
- Automatable: brief sending, non-response chasing, decision logging, reminders.
- Not automatable: brief completion, the anchor moment decision itself, content production.
- Newsletter initiative sits downstream of this — newsletters use the anchor moment as their primary content signal and should not launch until this rhythm is stable.
