ThinkWithPrompt by SynotticThinkWithPrompt

Design my company's operating rhythm of meetings and reviews

A weekly, monthly, quarterly, and annual cadence of meetings, reviews, and decisions, each with a clear purpose and owner.

Projects & OperationsFew-ShotStandardMeetingsAnalyzeFill-in Template

The prompt

Help me design the operating rhythm for my company: the recurring meetings, reviews, and planning cycles that run the business. Company size and structure: [HEADCOUNT, teams, locations, remote/hybrid] Current recurring meetings: [LIST with attendees, frequency, and length] What's not working: [e.g. "decisions get reopened", "I find out about problems too late", "too many meetings"] Planning cycle we use: [e.g. OKRs, annual budget, none] Board meeting frequency: [e.g. quarterly] Design a cadence covering: - Weekly: leadership team meeting (metrics, issues, decisions). - Monthly: business or functional reviews. - Quarterly: planning and priority reset, aligned to board meetings. - Annual: strategy and budget. - Company-wide communication: all-hands and written updates. For each forum, give: purpose (one sentence), attendees, length, standing agenda, inputs required beforehand, decisions it owns, and outputs. Then: 1. Show which current meetings to keep, merge, change, or cancel, and the hours saved. 2. Map the calendar: which week of the month or quarter each happens, so the data flows (e.g. month-end close lands before the monthly review). 3. Flag gaps where no forum owns a type of decision. 4. Suggest a 60-day rollout and how I'll know after a quarter whether it's working. Keep it lean: a company of my size should not run a large-company process.

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Projects & Operations prompts

What to fill in

  • HEADCOUNT, teams, locations, remote/hybrid
  • LIST with attendees, frequency, and length
  • e.g. OKRs, annual budget, none
  • e.g. quarterly

How this prompt is built

This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.

Related prompts

Find more prompts like this