April 7, 2022, by rheger7#4904, julialipton#5331, and angelaa | PST#1461

We audited Juicebox’s onboarding workflow by reviewing the existing content and speaking to existing projects. After discussions with the Juicebox community, we wanted to focus on creating recommendations that would maximize the value of both onboarding calls with and Discord support requests by new projects.

Recommendations:

  1. Treat project set-up as a starting point, not an end state
  2. Offer a starting playbook that won’t constrain projects from adapting over time (and will push them into engaging on Discord)
  3. Provide explanations of the trade-offs in project set-up directly within the workflow
  4. Add more content to the FAQs
  5. Formalize the lessons-learned process

Recommendation 1: Treat project design as a starting point, not an end state

“I think our goal should be to empower people and give them confidence over time.” - Jango

We want to help capture that spirit through content and copy.

Here’s how:

  1. Create a new project launch video that emphasizes that initial project design is for the first funding cycle, not forever
  2. Link to the Gitbook page from the project design workflow
  3. Create marketing copy that emphasizes Juicebox gives projects the chance to grow and adapt over time
  4. We second the proposal by a community member to use the Banny CTA button to direct users to Discord since that’s where the best project growth knowledge lives instead of the current “Design your project” CTA
  5. We also recommend an explicit call to action button on the project design page that directs users to Discord such as “Schedule an onboarding call on Discord”