1. Zopa community strategy

2. 2 distinct Zopa community areas
The Zopa blog
Very clearly part of the Zopa web site
Same look & feel
Space for members to comment, but not start conversations
Positioned as the ‘voice of Zopa’
An opinion / stand
Also individual opinions
Several regular contributors from Zopa
The Zopa discussion boards
Subtly distinct from the main web site
Different graphics / domain
Members can start threads in most forums
Also, private messaging between members
Zopa people participate in, but don’t lead, the conversation

3. Blog usage Continuous growth month on month since launch
Growing number of subscribers to RSS feed
Some posts get heavy comments, most don’t
Spike in KB downloaded was due to upload of research video
Downloaded over 400 times

4. Blog themes Zopa Updates (DN) Team News (TE) Theory (DN) Members (TE)
Changes to the site, upgrades, new bonuses, PR / marketing campaigns
Team News (TE)
Who is doing what, new team members, people who are leaving
Theory (DN)
What is it we’re trying to do? P2P finance beyond Zopa. How the business model might evolve.
Members (TE)
Stories, data, feedback
Cross over with newsletter, but I think that’s fine

5. Blog Requirements
Defined accountabilities for each theme (As per previous page)
Doesn’t imply responsibility for writing 100% of posts, but should take accountability for getting other people to help out if required
Tone of voice / content guidance
But use tone guide with caution - let the individuality come through
Content guide is probably similarly simple
Zopa people to respond to requests for content (or even content suggestions)
i.e. recognise this is an important communications channel!

6. Board requirements
When we think of making a major change, introduce it on the blog, and link to a discussion thread to encourage debate
Zopa employees to respond to questions directly on the board where appropriate
Dave to lead notification of threads where this is needed
Also copy important announcements from the blog here