Network-Centric Resources


Resources are assets that are drawn on by an individual or groups in order to function more effectively. Network-centric resources are people-powered and participatory resources that support the sharing and dispersal of knowledge in networks and communities. They are developed through sharing ownership, enabling contribution and supporting collaboration. Are you involved in developing a network-centric resource? Get involved!

  • Join the Network-Centric Resources discussion by subscribing to our email list

  • Schedule a free one-hour consultation to discuss your Network-Centric Resource by sending an email to info (at) fabriders.net.

Those of us that are part of the tech and social change sector strive to exchange knowledge and skills in order to improve our ability to change the world for the better. We put a lot of effort into developing resources with the aim of allowing for individuals to use, modify our resources and contribute back. All too often resources and materials are not properly maintained or cared for after their release and there is an expectation that those seen as the beneficiaries will support and sustain the resource. It is assumed that they will see the benefit and value of doing so. Many of us who rely on resources have been frustrated by sudden inaccessibility.  Resource developers are often faced with quick obsolescence. This happens partially because funding only exists to get to launch or because those that initiated and developed the resource took a ‘if we build it, they will come’ approach without a post-launch engagement and modificaiton plan.  It’s all the more exacerbated by a focus on the technology tools that can enable access and sharing of the resource, while forgetting about efforts to engage and encourage human beings.  As a result, we see a lot of wheel reinvention and not building upon the knowledge that  already exists.  Examples of network centric resources would include things like Wikipedia, Tor, and GitHub. Closer to home they would include: LevelUp, School of Data, & Fundamentals for Using Technology.

What we can learn from these examples is that we need to strive to be intentional in the initial design of resources: to follow the main tenets of design methodology, to get users involved early and as equal partners. To be transparent during development and solicit review and feedback. To have clear inroads and encourage contribution. To appreciatethose that do, and guide those that may have something to contribute but don’t know it. To articulate the value of participating. To encourage reuse and modification through outreach and licensing. 


We are proud to have Aspiration as a partner on this project.