Msnchris,
Using Team Ownership is good approach for data ownership and easy to maintain if your organization has high turn over percentage and also to avoid hassle in the sharing-record complexity, and if doesn't really care about each individual performance.
Another benefit is by implementing Team Ownership, you can just simply share between team to share to other users across different Business Unit.
It is recommended if your organization doesn't really care about data control security for each individual privacy of the records, because it will automatically 'shared' to other users with sharing same team membership.
I guess so that this is very important feature that CRM added starting from CRM 2011 which was previously unavailable in previous version. Because CRM realizes that it is very possible that one CRM record can be 'owned' by more than just one person and to simplify sharing process to group of users, instead of one by one.
blogs.msdn.com/.../using-teams-to-solve-complex-record-sharing-scenarios.aspx
But, it also has disadvantage if you want to drill down performance by each individual it is not possible. While, using User ownership, you can measure individual KPI + Team Performance as well, one user can be member of many team as well.\
Due to that scenario, according to my opinion, it is okay to implement the Team Ownership if your organization doesn't really care about Salesperson private data, such as Customer and Contact. But, for Opportunity or Case for the sake of individual performance it is recommended to use User ownership instead of Team.
One more thing you need to consider is also Access Team:
community.dynamics.com/.../138504.aspx
blog.customereffective.com/.../exploring-a-new-feature-of-crm-2013-access-teams.html
www.powerobjects.com/.../access-teams-in-dynamics-crm-2013
msdn.microsoft.com/.../dn481569.aspx
And regarding to your Question:
1. Do you agree this is the best approach?
--> I agree if your organization meet that criteria, please refer to my previous explanation, regarding to the Data Control, Security, and Individual Performance.
I myself, from my experience before, I found that in one of my client it is the best way using Team ownership because they don't care about their individual data, and no specific user is assigned to specific customer, they work as a team, regionally, one user can overlap customer coverage as long as they are under same team, so there is no point to keep individual ownership, we implemented Team ownership. Because their sales data is not important for each salesperson, instead, the Account term is only Customer that using their service only, not important who handle this Account.
In other case, I have customer that Team ownership is not the best way because every report in certain time period, the Manager wants to see how many Account has been converted from Prospect to Customer for each individual salesperson. And also in fact they compete each other, even if under same Team or same Region, they don't want let the other salespeople see it unless they share it? So there is no way unless keep the record as Individual Ownership and keep control only until User level.
2. If a user creates a new account or contact how do I assign ownership to the team automatically?
This is not automatically. You need to change it.
How?
Depends..If your rule is kind of 'static' you can use Workflow.
But, if it is too dynamic, I would like to recommend you use custom plugin or custom workflow activity.
Because..remember, one User can be member of Multiple Team, as we know, Workflow (OOB workflow) cannot choose one from a group, from N:N relationship.
But, if you only have few rules, like, if from this BU, then assign to Team A, if from that BU, then assign to Team B. then, this is possible.
One more notable thing here is:
"...I can just move a new person onto the team and they are granted ownership"
If the person doesn't have the role assigned to him, if the records are now owned by Team, he cannot access the record.
See this:
blog.crmguru.co.uk/.../security-roles-and-teams-in-crm-2011-an-inconvenient-half-truth
There is one case also:
community.dynamics.com/.../152402.aspx
Hope this can help you!
Thank you.
