Commit b9acc3f9 authored by sajolida's avatar sajolida
Browse files

Restructure blueprint

parent 29d7358d
......@@ -4,37 +4,16 @@
Calendar until the campaign:
- Week 32, Aug 3: summit
- Week 33, Aug 10: team member unavailable
- Week 34, Aug 17: team member unavailable
- Week 35, Aug 24
- Week 36, Aug 31
- Week 37, Sep 7
- Week 38, Sep 14
- Week 35, Aug 24: draft illustrations and text
- Week 36, Aug 31: usability testing
- Week 37, Sep 7: final illustrations and text
- Week 38, Sep 14: sajolida unavailable
- Week 39, Sep 21: sajolida unavailable
- Week 40, Sep 28: sajolida unavailable
- Week 41, Oct 5: sajolida unavailable
- Week 42, Oct 12: launch the campaign
I think that we should do, in this rough order:
Week 31
-------
### Skip any in-person usability tests for now
It's quite time consuming and the Covid situation makes it more
complicated. We can do other things and keep this for next year.
Week 32
-------
### Brainstorm on images with Andrés
Week 33
-------
<h3 id="survey">Survey lapsed donors</h3>
<h1 id="survey">Survey lapsed donors</h1>
Goals:
......@@ -259,19 +238,22 @@ Conclusions:
- Protection from oppressive governments and persecution (18)
- Liberty and freedom of speech (16)
Week 34
-------
<h1 id="donate">Improve /donate ([[!tails_ticket 17697]])</h1>
### Add an image to /donate
Since we won't do usability tests and to avoid a situation à la
[[!tails_ticket 16830]], we will limit our changes to:
And work on how to put the image on the page.
* Things we agree on easily
* Research-based recommendations from experts
* Things we can A/B test during the campaign
Ideas:
At some point we should show the draft images to people. This should
be easy to do remotely with a handful of past donors that we know a
bit better and can ask a favor to. We could also skip this testing
step and fallback on A/B testing during the campaign.
* Add an image.
* Improve "How we spend our money" to tell more about the impact.
* Improve the headline.
### Give some love to /donate/thanks and /donate/canceled
<h1 id="thanks">Rewrite /donate/thanks and /donate/canceled ([[!tails_ticket 17701]])</h1>
These pages look crap and we don't spend time on them because we don't
see them ourselves. But I think that they are critical and low-hanging
......@@ -288,34 +270,13 @@ These are things that are better studied in usability tests but they
are so bad right now that it should be easy to agree on possible
improvements while keeping them cheap.
Weeks 35-38
-----------
### Do non-controversial changes on /donate
Since we won't do usability tests and to avoid a situation à la
[[!tails_ticket 16830]], we will limit our changes to:
* Things we agree on easily
* Research-based recommendations from experts
* Things we can A/B test during the campaign
Ideas:
* Add an image.
* Improve "How we spend our money" to tell more about the impact.
* Improve the headline.
### Plan some A/B testing during the campaign (if needed)
<h1 id="ab">A/B testing during the campaign (if needed)</h1>
Like I did for [[!tails_ticket 16830]], we could do more such things
during the campaign. For example, we could test different images, text,
or controversial changes.
Weeks 42
--------
### Analyze the results of the A/B testing on frequency buttons ([[!tails_ticket 16830]])
<h1 id="buttons">Analyze the results of the A/B testing on frequency buttons ([[!tails_ticket 16830]])</h1>
Compare the conversion rates between Tor Browser, Tails, and mobile.
I'll be analyzing logs when looking at the results of the A/B testing on
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment