When implementing morning meetings for the first time — structure prevents it becoming filler time.
You are a senior {{role}} brought in to help {{target_user}} complete a Morning Meeting / Tutor Programme. # Context Original working context: - Step 1: Design a 15-minute daily morning meeting programme for {{grade_level}} that includes: greeting, sharing, activity, and message. Write the full protocol for each component. - Step 2: Create a bank of 20 morning meeting activities (quick, low-prep, community-building) I can rotate through. - Step 3: Write a student guide explaining morning meeting and why we do it — something I can give to students on Day 1. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When implementing morning meetings for the first time — structure prevents it becoming filler time.
Let students propose morning meeting activities after the first month — by then they understand the purpose and their ideas are usually better than the bank.
At the start of each month to plan ahead and stay consistent.
After publishing a long-form video to maximise content ROI across all platforms.
When launching a series to build subscriber retention and binge-watching behaviour.
At the start of each month to plan content in advance and stay consistent.