Think you have nothing to do with Stop Online Piracy Act (SOPA) and Protect Intellectual Property Act (PIPA)? Well, think again.
The whole SOPA/PIPA saga has implications beyond US politics and beyond the use of information in the internet. It also contains valuable lessons for intranet managers who need to craft information and data protection policies in the organisation.
SOPA & PIPA – Explained Visually
Being a non-US citizen, I honestly couldn’t care less about the massive online protest against SOPA and PIPA. Heck, I don’t even know what they are. That’s until Wikipedia was voluntarily shut down for 24 hours on 18 January 2012.
[update: as of 20 January 2012, the two bills were withdrawn]
The Wikipedia blackout leaves me with no choice but to find out what’s the big fuss all about. It’s not easy. Wikipedia “simply” told me to contact the senate now (I’m not in the US). And everybody in Twitter and in other online media were just parroting each other and said that SOPA/PIPA is going to censor internet, inhibit innovation, and kill the start ups.
I thought: “Wow. Can two US-based regulations create so much ripple-effect in the internet?”. And “why people are against good-intention policies (they are meant to deter piracy, aren’t they)?” To me, something was lost in translation (no pun intended). Thankfully this video helps to shed some light.
I found another visual explanation that is equally good in explaining the technicalities of SOPA and PIPA.
Basically the problem with SOPA/PIPA is its vague language. And the worse part is, they are killing the “messengers” – not the pirates. As a result, the weak languages in the two bills can be exploited and lead to internet censorship, while the pirates go scot-free. In other words, SOPA/PIPA doesn’t address the problem that they intend to.
4 Lessons Learnt for Intranet Managers
One direct implication of SOPA/PIPA being shelved for intranet is this: you can still download online information from internet, copy-and-paste it to Microsoft word, and share it in the corporate intranet. Yes, I know many of you are doing this stuff (Pheww! what a relief). But trust me, you should make use of pull technology, i.e. RSS feeds.
The SOPA/PIPA saga, including the campaign against it, has some valuable lessons beyond the use of information in the organisation. It also tells us how to promote open culture, how to craft great information policies and how to implement it in the organisation.
Here are the key takeaways:
1. Use Internet Publishing Model: Publish and then filter. Intranet has to encourage information sharing. Thus, make it easy for people to publish information in the internet. Filtering should take place after publishing, not before. This will encourage openness, and reduce effort required to filter information.
2. Don’t kill the messenger. The punishment has to be directed to those who abuse the shared information. Normally, it is understood that people aren’t allowed to share corporate information to outsiders. So people who share corporate information in the intranet shouldn’t be held responsible if another person leak the information to the outsiders.
3. Get diverse opinions before rolling the policy out. SOPA/PIPA was supported by Rupert Murdoch and Hollywood, but criticised by many internet entrepreneurs like Google founders, Jimmy Wales, etc. Worse, the policy makers don’t have answer for the critics. You don’t want this to happen on your intranet policy. Get staff’s opinions from different departments/ranks, and make sure you plug any flaw in the policy.
4. Run campaign to promote your policy. Remember I mention earlier that Wikipedia blackout made me aware of SOPA/PIPA saga? You have to run great PR campaign to bring the newly-minted policies to people’s attention. Informing people via email will not be sufficient. How about getting the top management to share their views? Or how about showing how many people support your policy, like how Google does it. (of course, for this to happen, you have to make it easy for people to show their support. See how Mozilla does it.)
What do you think about SOPA/PIPA saga? How are you going to learn from it to create better intranet information policies? Share your thoughts.
Further readings:
Topolsky, J. (19 January 2012). SOPA and PIPA: The wrong tools to combat online piracy. The Washington Post.
Condon, S. (18 January 2012). SOPA, PIPA: What you need to know. CBS News.

