Files for the StoryEngine guide at https://storyengine.io/guide
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
CODE OF CONDUCT.md
CONTRIBUTING.md
LICENSE
README.md
RESOURCES REQUIRED.md
roadmap.md

README.md

Welcome to the StoryEngine Repo!

StoryEngine a narrative-based methodology used to listen to, support, and create with the people who matter most to an organization or a cause. It can be used to do research, to monitor or evaluate a program, to generate learning, or facilitate grant reporting. StoryEngine is based on in-depth interviews that gets transformed into stories. These stories are assets for communications, advocacy, data collection, and more. Together these stories create a large dataset that can be analyzed to surface insights and learning that inform decision-making. Check out our StoryEngine repository!

Table of contents

Code of Conduct

Learn more

Who might use StoryEngine?

Where are we now?

Want to contribute?

I want to use StoryEngine!

Code of conduct

This project and everyone participating is governed by the StoryEngine Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to github@loup.design.

Learn more

Resources required

Roadmap

StoryEngine Guide

Website

Who might use StoryEngine?

StoryEngine can generate value across an organization — as well as for the participants. User profiles (some tested, others in development) are listed below. Note that StoryEngine can serve multiple people and purposes at the same time. For example, the process of collecting the data needed for an assessment can provide valuable assets for leadership, fundraising, and advocacy teams — with the added bonus of potentially getting different parts of the organization onto the same page.

User profiles

  • Leaders with organizational development, learning, and innovation agendas
  • Participants / Interviewees — people the organization serves, including partners, volunteers, and members
  • Network- / member-driven organizations, including associations
  • Designers of programs, services, products, and experiences
  • Evaluation, assessment, and learning and insights teams
  • Grant writers and development teams
  • Communications professionals, including advocacy, marketing, and public relations
  • Funders and grant managers
  • Conference organizers and attendees
  • Recruiting and onboarding / human resources teams

For more detail on each of these use cases, read the Introduction to the StoryEngine Guide.

Where are we now?

StoryEngine was developed by Loup for the Mozilla Foundation. The pilot phase is now complete, as well as the initial documentation for others to use and adapt. Mozilla has institutionalized key StoryEngine practices and narratives will be shared via Mozilla Pulse. Loup will continue to steward StoryEngine’s development and is currently using it with other organizations. See the Learning and History chapter in the StoryEngine Guide to learn more.

Want to contribute?

We're thrilled to have your help, thank you! If you’d like to contribute to advancing the StoryEngine methodology, please see our contributor's guide.

Join the StoryEngine conversation. Have a question? Discuss ideas? Join our StoryEngine Slack Workspace to communicate about all things StoryEngine with us.

Want to use StoryEngine?

Welcome! We're happy you're here. Next step: read the StoryEngine Guide. Please submit any questions via GitHub issues so they can be properly documented.

The obligatory disclaimer...

All information regarding StoryEngine is provided to the best of Loup’s knowledge and is believed to be accurate. Your use and application of the suggested methods and recommended products are beyond our control (duh!). There is no warranty regarding the accuracy of any given data or statements. Loup specifically disclaims any responsibility or liability relating to the use of any of the methods and products recommended and shall, under no circumstances whatsoever, be liable for any special, incidental, or consequential damages which may arise from such use.