Core Cycles
The repeating rhythms that shape how work and decisions flow
Organizations have a rhythm, or more accurately a set of interlocking rhythms.
Some of these are dictated externally by seasonality, by the fiscal year, by earnings calls, or by retail and promotional calendars. Other rhythms follow the natural calendar: years, quarters, months, weeks, and days. And then there are the intentional choices that leadership makes: when to revisit the long-range plan, when to set the annual budget, when to run a mid-year refresh, when to invite headcount requests, when to finalize annual priorities, when to run the company conference, and when to hold offsites.
When these rhythms work well, they complement each other. Revisiting the long-range plan in the spring clarifies direction for the next few years. Quarterly planning becomes a course correction mechanism. The mid-year refresh pressure tests the current plan. Annual planning forces teams to reflect on the year so far.
When they don't align, these rhythms can feel forced. People get bounced between competing cycles, each pulling in a slightly different direction. The work becomes reactive. Teams spend more time preparing for cycles than doing the work that cycles are meant to support.
The purpose of this discovery section is to clarify the major cycles, cadences, and rhythms in the company, and to better understand how they “close,” “open,” and transition into one another.
A simple way to prompt thinking is to finish sentences like:
- “It is the _________ planning season again.”
- “It is the end of the ____________ time to start another ____________.”
- “Every ____________ we close the _________ and open the next __________.”
Cycle Definition Table
| Field | What to Capture | Example |
|---|---|---|
| Cycle Name | What people actually call it. Use the real name, not the idealized version. | "Annual Planning", "Q1 Prioritization", "Mid-Year Refresh", "Weekly Release Window" |
| Start, End, Length | When it begins, when it closes, and the overall duration. | "Starts in August, ends mid-October, runs ~8 weeks" |
| Purpose | Why this cycle exists and what it is meant to accomplish. | "Set constraints and direction for the next fiscal year" |
| Key Inputs | The information or artifacts needed to kick the cycle off. | "Latest LRP slides, rolling roadmap, headcount forecast, revenue targets" |
| Key Outputs | What emerges when the cycle closes. | "Approved annual plan, staffing decisions, finalized OKRs" |
| Who Runs It | The leaders or teams responsible for coordinating it. | "FP&A drives timelines, Strategy sets priorities, Product & Eng provide inputs" |
| Interactions with Other Cycles | Where this cycle overlaps, hands off, or collides with other cycles. | "Starts right after the Mid-Year Refresh, overlaps with budget season, feeds into Q1 planning" |
Example: Core Cycles for a Mid-Sized Company
To make this concrete, here is an example set of core cycles for a theoretical mid-sized company, using real names, realistic timings, and the kinds of overlaps and constraints you will often encounter.
| Cycle Name | Timing | Description | Key Inputs | Key Outputs | Owners | Interactions |
|---|---|---|---|---|---|---|
| Annual Planning | Aug–Oct (~10 weeks) | The company-wide annual reset where constraints, direction, budgets, and top priorities for the next fiscal year are defined. | LRP slides, rolling roadmap, revenue targets, headcount model | Annual plan, finalized OKRs, staffing decisions | Strategy + FP&A | Follows Mid-Year Refresh; overlaps Budget Season; feeds Q1 planning |
| Budget Season | Sep–Nov (~8–10 weeks) | The finance-driven cycle that finalizes spending limits, hiring plans, and vendor allocations. | Annual plan draft, vendor renewals, investment requests | Approved budgets, hiring plan, vendor allocations | FP&A | Overlaps Annual Planning; constrains Q1 prioritization |
| Mid-Year Refresh | Jun–Jul (~4–5 weeks) | A mid-year reality check that tests assumptions, incorporates actual performance, and course-corrects the plan. | YTD results, OKR progress, forecasts | Updated roadmap, revised OKRs | Strategy + CPO + CTO | Feeds Annual Planning; overlaps Q3 shaping |
| Quarterly Prioritization | Last 2–3 weeks of each quarter | Deciding what gets worked on next, aligning bets, sequencing initiatives, and adjusting resourcing. | Initiative proposals, capacity snapshots, dependencies | Quarterly OKRs, initiative slate, sequencing | Product + Engineering Leadership | Shaped by Annual Planning & Mid-Year Refresh; feeds releases |
| Monthly Initiative Review | First week of every month | Teams evaluate progress, identify risks, adjust sequencing, and recalibrate focus. | KPIs, initiative briefs, updated roadmaps | Adjusted priorities, scope changes, dependency calls | VP Product + Product Ops | Feeds Quarterly Prioritization |
| Weekly Release Window | Every Wednesday | A predictable, low-risk deployment cycle for shipping changes to production. | QA signoff, release notes, rollback plan | Production releases, incident monitoring | Platform + SRE | Depends on daily standups; aligns with promo calendar |
| Daily Standups | Every weekday | Day-to-day micro-alignment where teams coordinate tasks, clear blockers, and maintain momentum. | Work board, blockers, dependencies | Daily adjustments and task handoffs | Individual teams | Feeds Weekly and Monthly cycles |
| Long-Range Planning (LRP) | Apr–May (~4–6 weeks) | Leadership defines multi-year strategic direction, investment themes, and capability roadmaps. | Trends, customer insights, portfolio analysis | 3-year investment themes, capability roadmap | Strategy | Feeds Mid-Year Refresh and Annual Planning |
Note: In most organizations, many of these cycles are in flux. Leadership revisits them, teams evolve them, and external pressures force adjustments. That is normal. The goal is not to freeze the cycles in place, but to make them visible so people can work with them intentionally rather than being surprised by them.
You're Done When
- You have a real list of cycles with real names.
- You know when each cycle starts, ends, and why it exists.
- You've documented the inputs, outputs, and owners.
- You understand how cycles connect, collide, or overlap.
- You've mapped the operating rhythm at a high level.