Sharing Twitter within Strawberrysoup
Twitter has become a really useful tool for us. We communicate with people that are interested in our business, our thoughts and things we like. If we see something that we feel will benefit our customers or community, we share it on Twitter.
Since we started using the platform, we have used it as a way of connecting with people, rather than wanted to attract thousands of followers. Our success criteria is the quality of responses we get from our followers, rather than the quantity of followers.
Last month, we made the decision to share our Twitter account internally and give each member of our team access via CoTweet. This was a reasonably easy decision to make and was made due to the following reasons:
Traditionally, I updated our Twitter account with anything that I found interesting. Due to the nature of my role, this led to most of our tweets being related to business and design subjects which is fine, but perhaps a little limiting.
With a team of 11, we all have different skills and interests. This should therefore result in a wide range of different subjects being covered including coding, project management, marketing as well as many others – thus making us more interesting to more people.
Time and holidays
As Strawberrysoup has grown, my responsibilities have increased and I am finding it increasingly difficult to spend time reading my RSS feed, researching links, reviewing and sharing content via Twitter. By sharing the account with our team, this responsibility can be shared. If someone sees something they like, they can post it to Twitter.
Everyone needs a holiday and I am no exception. I recently went to San Francisco for 2 weeks and was a little concerned that nothing would get tweeted for 2 weeks and our followers would think that we had disappeared. By sharing our account, I was confident that we would continue to interact with our community and share useful/interesting links that we had found.
It’s the same principle for replies. If someone tweets us, I know that someone in the team will reply to them so they don’t need to wait for 8 hours until I am available or have Internet access.
I look up to successful companies like @MediaTemple and @CampaignMonitor. These companies have great reputations but their Twitter accounts are generally used to support their customer based. They have however found that it works really effectively. We feel that if it works for them, it’s probably worth trying it out for us too.
In summary, we are looking forward to see how our team contributes ( and would find it interesting to hear your thoughts via comments or tweets.