Closed xmatthewx closed 8 years ago
Theory: if we investigate and optimize the experience of members who might share with our network, we can increase visibility across programs and thereby increase collaboration, innovation, and impact.
This is cool thinking, design team should see this. @lovegushwa @sabrinang @kristinashu @vazquez @flukeout @natalieworth
Looking further at the prototype it'd be cool to understand how you intend to use it. Is it for external use? Internal only? The UI is off-brand atm so we could definitely do a stricter design review, but this falls into that tricky category of 'how finished do we want prototypes to look'. We may not be there yet!
@xmatthewx is this a stream or do you imagine some curation (something like a web magazine for example?).
suggestions: make it "small" for this heartbeat; more about spec-ing and info-gathering than production at this point.
@cassiemc - In the next heartbeat, I hope to build 2+ new prototypes. They are disposable, and strive to test programmatic and UX concerns, so I'm not too concerned about brand at this stage – although those are Mozilla colors :smile:. I'll test Foxlight in the next round.
It'd be great to have a designer for p2
-ish input with design thinking.
@lovegushwa - too early to say how this will manifest, but my thinking: we need a stream that captures most of the things, with minimal barriers to entry. From that, we curate interesting, strategic bits, and tell the deeper story. Those two things might live in one space, or curation might appear elsewhere on an org blog.
additional thought: if it's indeed fun/interesting, would be good to surface some of that feed inside of the hub-specific websites, to help people find out about fun things happening across the network. So maybe e.g. the weblit hub shows a view of the feed that is 90% tagged weblit, and 10% "other".
On Fri, Feb 26, 2016 at 9:43 AM matthew w notifications@github.com wrote:
@lovegushwa https://github.com/lovegushwa - too early to say how this will manifest, but my thinking: we need a stream that captures most of the things, with minimal barriers to entry. From that, we curate interesting, strategic bits, and tell the deeper story. Those two things might live in one space, or curation might appear elsewhere on an org blog.
— Reply to this email directly or view it on GitHub https://github.com/MozillaFoundation/plan/issues/746#issuecomment-189387420 .
@xmatthewx While I appreciate the mobile-first approach, I doubt many of the projects that will be featured will actually work & render properly on a mobile device. While that may change over time, it might be interesting to...
I think @flukeout just volunteered himself. P2 though!
Without wanting to take this thread down a rabbit hole, I was wondering this morning if there's a name for this project that sounds more immediately like a magazine / gallery / feed of things to explore? It's probably my bias, but I think of Network Health KPIs when I hear see pulse
. This is definitely a P3 question though :wink:
Slow, but steady progress to connect this work with parallel research efforts and internal comms. Some small additions to the prototype. Rolling to next heartbeat to continue.
Closing this meta ticket. Will file something more specific in a future heartbeat.
RASCI
R: @xmatthewx A: @davidascher S: C: program managers, comms team, etc I:
Overview
Staff and network members create things (reports, software, tools, ...) that they might share with the network if their motivations align with our incentives and potential outcomes.
How do we foster a comprehensive view of these things created? How do we capture these things to tell our collective story? How do we amplify the best of our network's impact?
Next steps
Links