Want to create interactive content? It’s easy in Genially!

Get started free

202X calendar

J

Created on March 10, 2026

Start designing with a free template

Discover more than 1500 professional designs like these:

3D Corporate Reporting

Corporate CV

Interactive Onboarding Guide

Success Story

Higher Education Teaching Microsite

Modern microsite mobile

Basic Shapes Microsite

Transcript

202X

weeks 1-4

Next

13

12

11

10

Cycle begins; Product working in Discovery, Delivery and Optimisation mode

20

19

18

17

16

27

26

25

24

23

Core operating rhythm (example)
202X

weeks 5-8

Back

Cycle continues

13

12

11

10

20

19

18

17

16

Cooldown period

27

26

25

24

23

New cycle begins
Core operating rhythm (example)

The Cycle (8 weeks: 6 execution + 2 cooldown)

During execution (weeks 1 - 6):

  • Cross-functional teams own delivery against acceptance criteria
  • Instrumentation is part of Definition of Done for all shipped work
  • Only critical risks escalated to Product Ops
In parallel:
  • Discovery PMs shape problems; Optimisation PMs define success metrics
  • Final pitch preparation for the next Betting Table

Product Unblock (weekly, as needed)

  • Support for blocked bets or unclear platform behaviour
  • Agenda is set in advance, so answers can be prepared where possible async

The Cycle (8 weeks: 6 execution + 2 cooldown)

During execution (weeks 1 - 6):

  • Cross-functional teams own delivery against acceptance criteria
  • Instrumentation is part of Definition of Done for all shipped work
  • Only critical risks escalated to Product Ops
In parallel:
  • Discovery PMs shape problems; Optimisation PMs define success metrics
  • Final pitch preparation for the next Betting Table

The Cycle (8 weeks: 6 execution + 2 cooldown)

During execution (weeks 1 - 6):

  • Cross-functional teams own delivery against acceptance criteria
  • Instrumentation is part of Definition of Done for all shipped work
  • Only critical risks escalated to Product Ops
In parallel:
  • Discovery PMs shape problems; Optimisation PMs define success metrics
  • Final pitch preparation for the next Betting Table

Product Unblock (weekly, as needed)

  • Support for blocked bets or unclear platform behaviour
  • Agenda is set in advance, so answers can be prepared where possible async

Activities during Cooldown:

  • The Betting Table (first week)
    • Pitches reviewed in advance
    • Decisions measured against OKRs, appetite, and readiness
  • Per-bet retrospectives
  • Internal and external docs updates
  • Instrumentation health check; degraded data quality flagged

Cross-mode retro (~quarterly)

  • Hosted every other cooldown
  • Focused on cross-mode interaction health

Product Operating Meeting (ad-hoc)

  • Convened when needed for:
    • proposed changes to our product operating model
    • retros on implemented decisions