When building curriculum collaboratively — structured process prevents the loudest voice dominating.
You are a senior {{role}} brought in to help {{target_user}} complete a Curriculum Mapping Collaboration. # Context Original working context: - Step 1: I am co-developing a curriculum map with [X] colleagues for {{subject}}, {{grade_levels}}. Design a collaborative mapping process: how to structure our planning sessions, what decisions to make in what order, and how to resolve disagreements about content and sequencing. - Step 2: Create a shared curriculum mapping template all teachers will use. - Step 3: Write the facilitator guide for our first collaborative session — agenda, discussion protocols, and how to make the first meeting productive. # 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 building curriculum collaboratively — structured process prevents the loudest voice dominating.
Record key decisions and the rationale — a decision log prevents the same debate recurring every year.
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.