Always Be Testing.
That’s a baked-in mantra around the Spike office. Because email is life and death to us we test everything we can. From subject lines to senders names to copy and offers we’re constantly testing for what works.
To make sure our emails go out on time and have no mistakes we have a tried and tested process. This is passed on to new developers and looked at from time to time to see if it can be done better.
Here’s the Spike Step by Step Guide for email testing.
After building the email make sure you have the following ready:
- Email to be tested
- Updated brief
- Asana Link
- Any additional notes from the client that is important to take note of during testing
- Notify the team that an email is ready to be tested.
- Make sure that all the required information is available for the team for testing
For Tester/Rest of the Team
- Make sure that all information needed for testing is ready and up to date
- Click the link for Asana, make sure it’s the right task to log the time to
- When you start the timer, make sure you update the task name and add “- Test” (Check Note 1 for example) and the task is set to “Test”
- Start the test – Check spelling, design, links, tag and alt-texts
- Note changes and send it on Slack – Remember to tag the developer.
Note: There might be a couple of back-and-forths between the team, the developer and then the client – so make to leave ample time for testing.
- Once final changes have been made, send the final copy to the client
- Apply changes, if there are any
- Once approved, schedule the email on GreenArrow, Mailchimp or other platform
- Notify the team that the email has been scheduled, including Campaign Name, List or Segment it will be sent to and time of sending
And there you have it. The complete guide to how Spike makes sure emails are sent how they’re meant to look to whom they’re meant to go to at the right time.
If you’d like us to look at your testing process Contact Us.