What does it mean to build web services that DoTheRightThing™? A panel about product design decisions and the tradeoffs made in designing social software. We'll discuss understanding user expectations, incentivizing behavior, the impact of default settings, and handling privacy. Avoid becoming the next [company name redacted].
Questions Answered:
What does it mean to develop "respectful" software?
Hey, why does it matter? Why is it worth building respectful software to begin with?
What particular tradeoffs in this area have each of the panelists had to manage on their respective websites?
Aren't growth/adoption hindered by these practices? How can we accelerate growth without being spammy?
How can we encourage our members to share more, without subverting their expectations of privacy?
Opt-in versus opt-out? When is each appropriate?
Horror stories: What are some particularly heinous stories about the consequences of when people got it wrong?
What are the general "anti best practices" for respectful social software? -- Things a respectful website should never do.
How can you "institutionalize" practices in your organization that will lead to building respectful software?
How has increased integration between different web services complicated everything?
Level:
Intermediate
Category:
Case Study, Community / Online Community, Design Thinking, Social Networking, User Experience