How to encourage users to create more content?

Question

Imagine a web service where users post notes grouped by tags. Notes are public and the tags are essential, because other users will see notes based on its tags (they can 'follow'). I want users to post as many notes as possible, but I also want them to tag their notes properly.

1. Should I give users two input boxes (one for note text and second one for comma separated tags).
2. Or should I give them just one input box where they can incorporate tags into note text in form of #hashtags (as in Twitter). This would of course include some hints and tutorials for the beginners.

The service is aiming to be as simple as possible. Notes will have limited length and it must be very fast and easy to insert a note.

The question is: is it worth make input process faster by removing input field for tags? Are young people generally able to learn to insert tags using hash sign (#)?

If the question is too abstract I would gladly provide more details.

Answer 1

Choose option 1; users won't guess they can use hashtags. Even if they've been exposed to twitter, they won't assume they can use twitter-like conventions unless they read instructions otherwise - and users never read instructions. What they will spot, however, is an open second field to complete before submission - and there's your opportunity to introduce tagging.

Another thing: users may have trouble grouping content into a set of consistent tags. They don't know the taxonomy, and may not guess the terminology their peers will use. Might I suggest tag autosuggestion, based on keyword detection?

^{download bmml source – Wireframes created with Balsamiq Mockups}

Perhaps after repeated exposure, your application could provide a 'tip' that adding a hashtag automatically adds a topic. This creates a more efficient interaction that users will be bothered to learn because they already have an investment and relationship with the service.

Answer 2

By default, show two boxes. One for the note itself, the other for tags.

As the user enters tags, convert the words in the note to hashtags automatically (if they exist) or insert them at the end of the question text.

Give them the option to hide the second 'tags' box, or just hide it when you notice this user no longer uses it.

You could extend this further with Jimmy's suggestion of automatic tagging - highlight words that you detect as possible keywords and give the user an option to turn them into hashtags.