Establishing Teams by Object

[dwilliams]

I'm curious how other companies are handling their object teams. My original thinking and our current direction is that teams can be established using team templates based on a product category.

For most objects, using a team template works great. Unfortunately, they do not work very well for bulk item objects and documents.

What process have you found works best for establishing the object teams? Do you strictly use the context teams or team templates? Do you modify these teams by object to ensure you have the correct roles and members?

Thanks for your advice,
Dax

[MikeLockwood]

Why do you use teams at all for Documents and Parts?

[dwilliams]

Hi Mike,

We use teams to determine the responsible roles for the object (Change administrator, Purchasing Manager, Engineer, etc). These roles get specific tasks in our processes such as analyzing a problem or determining a changeover date based on inventory levels.
We also use teams for notification purposes. Rather than notifying a static list of people regarding a change, we only notify the people on the object team.

How do you manage object specific tasks and notifications?


From: Lockwood,Mike,IRVINE,R&D [

[MikeLockwood]

We may be a bit behind on this. We currently only have teams in use only for a few Roles on change objects. These are pulled from Org-level Team Templates.

In general for change, we have the creator select all participants on the first workflow assignment.