4. Member Experience of Efforts

Looking for something specific? Skip ahead:

When creating a new effort, it helps to experience an effort from your supporters' points of view. If you'd like, you can interact with a live, demo effort: https://demo.controlshiftlabs.com/efforts/ban-fracking/near/new or this article will take you through the screens that your members will see.

Please keep in mind that depending on how you configure your new effort, some of these screens may not be available for supporters interacting with the effort. Nevertheless, there are three main ways a supporter might interact with the effort: as a recruited leader (of an admin-created, leaderless petition), as a campaign creator, and as a signer.

As a recruited leader

When the effort has admin-created, leaderless petitions, and the settings are configured to allow members to lead these petitions, then a user may be recruited to become a local leader. These users will begin on the effort's landing page. NOTE: To recruit local leaders, users MUST start from the effort's landing page. Users sent to the effort's hub page will not be able to enter the recruitment series.

This is the workflow for members recruited to lead a local campaign:

Summary:

1. Users begin on the effort's landing page, where they enter a search query.

   

2. The closest petition is shown on the search results page.The text included on this page is customizable in the effort's leadership settings. If they click the What will I need to do? link, they can view a quick summary of expectations. The user will then click the I'll be a leader button.

   

3. The user is brought to the first page of the recruitment series, which thanks them for agreeing to be a leader. The text included on this page is customizable in the effort's leadership settings. When they click to Commit as a Leader, they'll be associated with the petition/decision maker.

   
   
   

4. The user is then asked to review/edit the text of the campaign. (This is an optional step configured in the Leadership settings.) They'll then click Save.

   
   
   

5. After editing the text of the campaign, the user is asked to review the petition text. (This review screen will not be shown if the user is not asked to edit the text of the campaign.)  They'll then click Next.

   
   
   

6. The user will then see the training page. On this page, org admins can include requirements for campaign leaders, tips to be successful, means of getting in touch with org staff, etc. The user will then click I'm ready, let's go!

   
   
   

7. The user will then be brought to the campaign's signature page. They're now listed as the campaign leader and have access to all of the campaign creator's tools.

As a campaign creator

Depending on the effort's configuration, it may be possible for users to add their own decision makers to an effort and create their own campaigns. These users will begin on the effort's landing page. NOTE: To create their own campaigns, users MUST start from the effort's landing page. Users sent to the effort's hub page will not be able to enter the recruitment/campaign creation series.

This is the workflow for members recruited to create a local campaign:

Summary:

1. Users begin on the effort's landing page, where they enter a search query.

   

2. If there is no matching campaign, they'll be asked to create a campaign for that location.The text included on this page is customizable in the effort's leadership settings. If they click the What will I need to do? link, they can view a quick summary of expectations. From here, they'll click the I'll be a leader button.
   

   

3. If there is a close campaign, they'll be shown information about that campaign. Below the results box, they can click the Start a new campaign link.
   

   

4. The user is brought to the first page of the recruitment series, which thanks them for agreeing to be a leader. The text included on this page is customizable in the effort's leadership settings. When they click to Commit as a Leader, they'll be associated with the petition/decision maker.
   

   

    

5. The user is then asked to enter information about their new decision maker. The information collected here will vary by effort. They'll then click Save.
   

   

6. The user will be asked to review/edit the text of the campaign. Then, they'll click Save.
   

   

7. The user will be brought the the campaign review screen. They'll then click Next.

   

8. The user will then see the training page. On this page, org admins can include requirements for campaign leaders, tips to be successful, means of getting in touch with org staff, etc. The user will then click I'm ready, let's go!
   

   

9. The user will then be brought to the campaign's signature page. They're now listed as the campaign leader and have access to all of the campaign creator's tools.

As a signer (through the landing page)

Users can always sign the campaigns in an effort. Signers can use the effort's landing or hub pages to find their closest campaign.

This is the workflow for a user signing a campaign after going through the landing page:

Summary:

1. Users begin on the effort's landing page, where they enter a search query.

   

2. They're shown their closest campaign and click the Sign the Petition button.

   

3. Users are brought to the petition's signature page where they sign the petition.

As a signer through the hub page

Users can always sign the campaigns in an effort. Signers can use the effort's landing or hub pages to find their closest campaign.

This is the workflow for a user signing a campaign after going through the hub page:

1. Users begin on the effort's hub page, where they enter a search query.

   

2. They're shown the closest campaigns and click the title of the campaign they want to sign.

   

3. Users are brought to the petition's signature page where they sign the petition.

Next we'll look at efforts' settings.