Capstone Brief: Design an Enablement Plan
Plan four weeks of hands-on training for a real team, built on the skills from this track.
Objective
By the end of this lesson, you can scope a four-week enablement plan for a real team and know exactly what you will hand in.
The project
You will design a four-week enablement plan for a real team. The team can be your workplace, a nonprofit, a small business, a faith group, or a youth program you help with. If you do not have one, The Cook Up will match you with a practice team or a detailed made-up case.
The plan covers at least two of the four skill areas from this track:
- Growth & Performance Marketing
- Content, Social & Brand Systems
- Data & Analytics for Marketers
- AI & Automation for Go-to-Market
Every week of your plan pairs learning with shipping. The team practices on its real tasks and produces something it will keep using.
Capstone
Capstone brief
- A real small business, nonprofit, or youth program team (or a practice case from The Cook Up)
- The team has a real gap in marketing, content, data, or automation work. Design a four-week enablement plan that helps them close it and keep going without you.
Deliverables
- A one-page needs check: the team's real tasks, a skill map, and whether training is the right fix
- A four-week plan: one session per week, each with a learn goal and a ship goal
- One session guide, written so another trainer could run it
- One reusable tool for the team: a message map, metric dictionary, test card, or SOP with rollback plan
- A judgment and privacy page: what the team should not train, automate, or collect, and why
- A 2-minute walkthrough (live or recorded with captions)
| Criterion | Meets the standard when |
|---|---|
| Judgment | Names at least one task or tool the team should not train or automate, and explains why. Says whether training is the right fix at all. |
| Real work | Every session uses the team's real tasks and ends with something shipped |
| Handoff | The plan shows how the team will run the work without the trainer by week 4 |
| Measurement | Checks behavior or results, not only whether people liked it |
| Privacy and equity | No private or minors' data in tools; considers who could be left out |
| Clarity | Plain language a new team member can follow; captions and alt text where needed |
Step 1: Run the needs check
Before you plan anything, find out what the team actually needs.
- Ask three to five team members about their real week. Which tasks are slow, repeated, or stressful?
- Build a simple skill map for the roles you see.
- Ask the judgment question from Module 1: "If everyone had this skill tomorrow, would the problem go away?"
If the honest answer is no, your plan can say so. A plan that fixes ownership or time first, and trains second, is a strong plan.
Step 2: Draft the four weeks
Use this shape. Change it to fit the team.
| Week | Learn goal | Ship goal |
|---|---|---|
| 1 | The team's main goal and shared definitions | A metric dictionary or message map |
| 2 | The first skill area | One real piece of work using the new skill |
| 3 | The second skill area | One test, workflow, or small automation |
| 4 | Running it without you | The team leads its own weekly review |
Step 3: Use AI with care
You may use AI to help draft your plan. Use the Prompt Lab below, then check and rewrite every line in your own words. Do not paste team members' names, private numbers, or anything about minors.
Prompt Lab
Draft a first outline of a four-week enablement plan you will then check and rewrite.
Your prompt
Act as an experienced trainer who designs hands-on programs for small teams.
Scope check
0 of 6 doneGo deeper: Training & Advising: Building Teams That Can Actually Execute
Discussion
Ask. Answer. Build together.
Loading…