This document discusses the pros and cons of building a community from scratch versus joining an existing community. It notes that building a community from scratch means starting with no users but gives full ownership and control, while joining an existing community avoids starting from zero but means less control. The document provides tips for deciding which approach to take such as considering resources, goals, and competitors. It then gives best practices for nurturing and growing a community.
3. Created in early 2005 with the launch of Yahoo!’s first Search APIs Over 30 APIs and web services offered today Over 250k API keys issued Key resources: Documentation Developer language centers Message boards/forums User interface patterns Code samples and developer kits Blog & video
4.
5. Pros Ownership of UGC Overall control of usability is yours Manage the message Traffic to your site increases Knowledge base onsite
Tell Duzins story Why I chose to join communities, instead of creating one
On last point: (think short and long term) Site creation, security protocols, take time Effectively creating a new product More difficult to enlist outside moderation
YDN Offsite content consists of: Marketing, Communication, Light Discussion, Fan building Onsite “”: Deeper conversation, Technical deep dives, Evergreen content, Permanent resources
Customer Service emails should talk like real people "At the tone, please record your message. When you have finished recording, you may hang up, or press 1 for more options. To leave a callback number, press 5. To send a fax, press 7. (Beep)”
For our audience, especially, typical marketing doesn’t work. They are extremely web savvy, and carry that internet chip on on their shoulders, so they’re typically skeptical of all marketing. Real voice has to happen. No BS.
Your customers are your knowledge base They help each other They warn of potential problems
While we do encourage community members to help other community members, we spend a great deal of time cultivating fans internally (ie employees) to help us cover all the major community areas. And, we never launch a community area without internal owners.
Very different ‘communities’ on Facebook, Twitter, and on your own site. Deliver content specific to that audience when you do any messaging.
Facebook you can be heavier on the communication, but people tend to passively ‘like’ rather than converse. For our audience, we rarely see debate on FB. On Twitter, heated debates can quickly become trends. People subscribe to searches on popular technologies. Different content for different audiences.
On Twitter especially. Depending on your audience, livetweeting can annoy. Know if people follow your company on their phone. If so, be careful of how often you tweet.
@s don’t go to all of your followers. .@s can solve that, but only use them if it’s important that all your followers see the info. Hashtags are great, but too many is annoying. Don’t spam hashtag. Always take the time to attribute to a service user if possible, rather than merely naming the person. RT often, but only excellent content. Don’t auto-DM followers. Don’t discuss private matters in a public forum.
Community is not easy Real work Real effort Real relationship Real loyalty Questions?