Discovering creators' dream features through desire paths

  • 26 January 2023
  • 3 replies
  • 51 views

Userlevel 2
Badge +1

One of the ways our product and design teams have gotten inspiration for new features has been to look at where Goosechase creators’ desired outcomes clash against the edges of what our platform’s current capabilities allow. Similar to how urban planners often observe “Desire Paths” formed by the organic movement patterns of crowds through unpaved areas in order to decide where actual pathways should be paved in the future, I’m interested in finding out what “desire features” creators have been enabling using their own clever workarounds, that have allowed them to “hack” features into Goosechase that we might not even have known creators have wanted to use.

A few examples I’ve heard of in previous conversations with our creators:

  • Permission collection: 

    • Using a text mission worth 0 points in order to get their participants’ permission to use submitted photos or videos for marketing purposes.

  • Points for the fastest submissions: 

    • Including 0-point missions, and using the Dashboard panel to figure out who are the top X fastest submitters who deserve to be awarded bonus points.

  • Gated Missions: 

    • Creating an “unlockable mission” by not including instructions for how to complete it in the mission description directly, but instead printing out the instructions and only giving them to participants who reach a specific physical location to complete another mission first. (Props to @RetChaser for this idea!)

What are the most clever workaround “desire features” you’ve been using? Your tips and tricks might help another creator who wanted to accomplish the same outcome, and might even become something we officially add to Goosechase as a real feature in the future!


3 replies

Userlevel 3
Badge +4

I love the idea of a “Gated Mission”.  When using Goosechase for an alternative assignment, this would be a great way to control the pace or direction of the hunt.  I will have to try this in a professor’s course!

#1 thing needed I believe is more “gating” options for the missions.
#2 would be Multi-threading the automation script so that it was not necessarily a single “file” path for the mission stages.

Userlevel 5
Badge +6

Great input @Tink69. Thanks for sharing. With regards to your second point. Can you elaborate on how you might want to see  “multi-threading the automation script” work? Or do you have an example of a flow chart that might illustrate the journey you’re currently seeing/wishing for?

Reply