Inventory things created by our network

[xmatthewx]

An effective Mozilla network should yield leaders who shape the internet through innovative or impactful "artifacts" that align with Mozilla’s principles and priorities. Artifacts, products, or creations – these include campaigns, software, legislation, reports, think pieces, tools, and curricula released to the world.

Problem

We don't have a comprehensive view of things created by network members that cuts across programs and events. Our members don't have a view of what other members create outside their niche.

Task

Take inventory of 2015. Do this as a prototype for capturing 2016 as it happens. Discuss with staff and network members to explore the relationship between a creation and the network. Does the network know about it or utilize it? Did the network contribute toward its creation?

Goal

This heartbeat: better understand what the network creates and how the network enables that work. Long-term: Amplify the best work of our members. Foster collaboration, prototypes, and innovation created across the network. Contribute toward @adamlofting's network strength indicator.

Deliverable

Report on the findings. Build a simple method to gather, store, and share info about the artifacts.

Driver: @xmatthewx
Consulted: @adamlofting, fellowships, hive cities, etc

[OpenMatt]

Other threads we want to potentially connect:

1. Simon's "Planet MLN" prototype
2. Shared curriculum database

[edrushka]

Curious what you envision for the final "report". Is this something static and printed like Laura DR does? Or something web-based with links to the "things"?

[adamlofting]

If this inventory becomes an artifact in itself, let's put aside some future time to think about promotion and integration into network working practices. I.e. How does the inventory feed the network and vice versa.

[omnignorant]

super interested in this! let me know how I might support. I'm particularly curious about the participation pathways or enabling conditions (resources) that lead to each artifact

[edrushka]

As an easily digestible, public "report", this is an interesting format: https://ca.warbyparker.com/year-in-review-2014 via @benrito

[benrito]

@xmatthewx we're a similar inventory of research + issues, see for instance: https://docs.google.com/spreadsheets/d/1AmAufOHeo7akmfZlzD0e7_tmQBzk6DNVO5pI3fNcNZU/edit#gid=227852233

Can we get together to share notes? Would love to co-develop a single inventory.

[OpenMatt]

@xmatthewx status? [flagged!]

[xmatthewx]

What do Agate, Flexbox Froggy, and Command Line bootcamp have in common? Wouldn't we all like to know?

Good progress on this. I've completed a range of conversations with staff and built a light-weight prototype. I will pull together a summary of observations and recommendations as conversations continue next week.

I'll bump this ticket to next heartbeat with plans to close it and file followup.

[hannahkane]

@xmatthewx - wasn't sure whether to label this with production or program label. (or both!)

[cassiemc]

@xmatthewx Why remove the better-faster label?

[xmatthewx]

Wasn't intentional @cassiemc. In transit now and can't add it back. Nice work on the email update!

[xmatthewx]

This first phase of work is done. It'd be great to get feedback from this group on my observations and recommendations.

Check out the Prototype inventory stream, and see the breadth of things created by peers in the network. Contribute to the WIP precedents deck and help answer the question: How can we best capture, share, and amplify the work by our network?

[xmatthewx]

I invite everyone to capture the story February in the prototype (shout out to @bhuvanshri for the idea), adding anything made by us or members (reports, software, campaigns, etc). Works-in-progress welcome.