I would recommend using tasks for most actionable items. The do not even have to have a project tied to them. If you are in a meeting just open up the most relevant discussion group in social and you can assign tasks on the fly that stay in context of the conversation and topic. When the resource goes to their task list, they will see BOTH these ad hoc tasks and projectized tasks in one view.
Requests I would use for items that go through an approval process and may become tasks or be rejected. These could be change requests, new project requests, feature requests, etc.