Abstract vs. Teams Manager for Microsoft Teams

• Large teams with dedicated design operations support
• UX managers that want a facilitated workflow for their teams
• Disciplined teams of individual contributors that want to adopt a process in their UI workflow
• Cross-discipline teams that want a central collaboration space for reviewing and critiquing UI artifacts
• If your files are named "FOR-REALS_FINAL_FINAL_FINAL_Super-Important-Project (copy).sketch"
• If you're managing multiple pattern libraries

Incentivized

For different projects in a big organization different teams can be formed and thus their internal tasks assignments can be done there. It is easy to manage, assign tasks to people in a particular project. People or team leads in multiple projects can share different channels thus maintaining different projects. Users should be refrained of creating new teams just for fun purpose etc. to avoid to much chaos.

Incentivized

• Versioning for desginers
• Collaboration between team members

Incentivized

• easy to manage team sites along with members and guest users
• helps managers to track the usage of apps and work done remotely

Incentivized

• Asset exports are not as great as Zeplin and others.
• Filtering within files.

Incentivized

• I feel like the Shifts app could be more advanced to sync with Microsoft Outlook. It would be great to receive notifications in Outlook for Shifts and be able to approve/deny requests and schedule changes there while it's synced with the Outlook calendar.
• It would be nice if the interface allowed further customization such as assigning colors to the separate channels. Some channels within team sites are rather lengthy and it would be great to group them into color groups.
• Another nice feature would be the option to log in as one of your teammates so you can properly set up their Team account before they log in for the first time.

Incentivized

as already explained this software only does branching... the rest is really poor and basic

Incentivized

Abstract has a difficult learning curve. If a feature-branch workflow is new to you, then it will take some getting used to. They make a lot of updates to the interface and these feature releases get ahead of their documentation. They rely heavily on an excellent customer support team and are present on various Slack channels to help design professionals with issues.

Incentivized

Abstract by nature is complex and has to respond to whatever changes in Sketch. So there are frequent issues. Support can be slow to respond and are not always helpful, but they are quick to find and patch the bugs. Overall, it's not the best support, but it hasn't been detrimental.

Incentivized

I purchased and administer Abstract. It was requested by our design department who evaluated it.

Incentivized

As I mentioned before, we switched to Teams from Skype because it was more reliable. We did not experience interruptions in service especially for those departments working remote.

Incentivized

• Single source of truth for the team.
• Could quickly get expensive with corporate accounts.

Incentivized

• A centralized platform for the Operation Manager to handle and see the progress of different projects
• This makes it easy to handle everyone at one place thus reducing time in contacting individuals and taking the feedback on progress
• Knowing of any hurdles or bottlenecks in any project by just clicking on any channel and seeing their discussion. Thus guiding them then and there only.

Incentivized