Closed Bug 1033300 Opened 12 years ago Closed 12 years ago

Write 5 emails for NN training

Categories

(Webmaker Graveyard :: Communications, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: laura, Assigned: kelli)

References

Details

(Whiteboard: [training][ttw][july25])

Daily emails on the content (contingent on teaching kits, discussion threads, and CTAs included in Bug 1033244
Blocks: 1033244
No longer blocks: 1033244
Whiteboard: [training][ttw][july25]
Blocks: 1033244
Assignee: nobody → andrea
Status: NEW → ASSIGNED
For now the Net Neutrality e-mails are the most important. It’s SIX emails: Audience: Everyone and their cousins: One general “we’re talking about Net Neutrality this week at webmaker” with a CTA to “participate in the discussion” (leads to training signup??) Audience: Everyone who has signed up to Training one for each day of the training week (line 32 of the below ether pad) This pad: https://teach.etherpad.mozilla.org/drm-nn-training has some bullets and all the stuff we’re doing, and I’m off tomorrow and thursday, so maybe Matt or Michelle can draft?
Summary: Write 5 daily emails for DRM + NN training → Write 6 emails for NN training
Flags: needinfo?(michelle)
Flags: needinfo?(matt)
* Hey Laura. I don't think I'll have time to write these. Sorry.
Flags: needinfo?(matt)
Hard to write the 5 emails now, as we should include information on what has happened during each day, but I've written a general outreach email and the Monday draft. I've started this: https://etherpad.mozilla.org/NetNeutralityEmails I think once more of the content is done these will be easier. @Andrea, can you use the outreach email to get started?
Flags: needinfo?(michelle)
Summary: Write 6 emails for NN training → Write 5 emails for NN training
Hey there. Understanding that we need a much better creation & production process for these kinds of email requests. I've copied Kelli Klein, Digital Campaigns Lead. Kelli is going to be working on improving our processes for emails like this. In lieu of a process now, we need more information. There is a lot of missing information that Kelli and I need in order to attempt copywriting, and I'm not sure we should draft given that we're not that familiar with our usual training correspondence. I want to ask some best-practice questions: - why are we sending 5 emails? do we know that's a good number? Why not 3? - are we sending emails from Blue State Digital? If not, where do the emails get sent from? - We need the following information for every message in the series before anyone can begin to draft: Audience Description (Segment, e.g. "all-time Maker Party participants"): Audience Size (est.): Sequence (e.g. Message #1 of 6): Launch Date: Call to Action (1 only): Sender name:
- 5 emails: 1 for each day. We tested 1 per week and 3 per week already, received feedback that in the context of training, people like to know exactly what they are supposed to do. - BSD, yep - Audience Description: All people who signed up to training Audience Size (est.): currently 3000 but outreach in bug 1033299 is push for more Launch Date: July 28th Call to Action (1 only): tbd (I'm having a hard time making this ONE CTA. I think that using emails as a mechanism for training is not the same as outreach...should discuss in our meeting)
* Laura: what's the status of this one?
Flags: needinfo?(laura)
Kelli and I have chatted, she was aiming to get drafts done this week (but it looks like that might get punted to early next week because the pad is as I left it ;) Drafts started here with grokkable CTAs: https://etherpad.mozilla.org/NetNeutralityEmails
Assignee: andrea → kelli
Flags: needinfo?(laura)
Michelle and I hacked this on Friday.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Great, I think the emails in-training to registrants should be handled by you and training leads (meaning: Emails not going out through BSD to a larger list for marketing purposes). Kelli will be explaining this protocol in more detail, but that's the idea.
You need to log in before you can comment on or make changes to this bug.