This proposal will restructure our approach and visibility as an organisation. We believe we need to be more open about our work. We need your help and feedback on how to do this.
Why change?
What would more visibility look like?
Benefits?
What are we proposing?
Option 1 - low visibility - no change to current strategy
This is what we are at now! This option means NO change to our current level of visibility. There is no such thing as passive support for the ‘low visibility’ approach. If this is your choice then it's your responsibility contribute so that we are sustainable.
Option 2 - medium visibility - taking it to the next step
Our Community Guidelines would be changed to allow members to talk openly about Red Files online and offline. This means we can network and inform others about us on a public level and direct people on how to find us. There will continue to be no mention of a database, ugly mugs or screening information.
Option 3 - high visibility - leading the conversation
Red Files has its own social media presence and identity. This involves creating a social media policy that dictates how we conduct ourselves online. We would have direct control over the conversation on how we function and what we do. It will take the responsibility of networking off our members shoulder and we can reach out to more workers. This can help us with sponsors, funding and support.
Good news is we have a fallout plan if things go awry! If either the mid/high visibility approach doesn’t go as planned then we migrate the entire site to a new place on the internet with a new name.
This is similar to re-branding, all current memberships and members would stay the same and have access to the new site under a new name, but Red Files would disappear from the internet and people would not be able to find us again.
If the idea of increasing visibility makes you uneasy, take a moment to consider the number of safeguards and securities in place within Red Files.
Below are just some of the known features. There are also a lot of back-end features (that we don’t share) to keep us protected. We wouldn’t be confident about taking a step forward if we didn’t believe we have enough security in place.