We'd love your feedback on Atlassian Teams!

[#1]

Hi non-profit community 👋

My name is April and I'm a Product Manager on the Atlassian Teams team (see What is Atlassian Teams?). I'd love to hear some feedback from you!

Currently, Atlassian Teams is in its early stages. We're in the midst of product adoption and adding a Teams field to Jira. Before we add more features, I'd like to learn more about the following:

1. How are we using Teams and why do we use them?

2. I'd like to hear about your understanding of team visibility: (1) who can see what teams? (2) who can access what teams? (3) do you work in an organisation where users are from a diff email domain?

3. Do you have confidential teams or teams that you make that you hide from other users?

3. Are there any features of improvements that can be made that you'd like? 

The ultimate goal is to get your feedback and ensure we're spending the time on the right things.

Please comment below to get the discussion started! Let me know if you have any suggestions, thoughts, or concerns.

Prefer a 1:1? Feel free to reach out to me via:

Email: achi@atlassian.com

Calendly: April chi - Book a call (or let me know and I can open up more times)

[Jimi Wikman]

Hi April,
here are some quick thoughts from me regarding Teams :)

As of now I am advising my clients to ignore Teams and the reason for that is that Teams, as it exist today, have no value for work. What I mean by that is that I can not use Teams in any of the products, which makes it a separate tool, which kind of remind me of Yammer.

I like the idea of Teams, but for it to be really useful it must become a core functionality across all Atlassian products. It must be something you can use to assign with, search for and tie into functionalities like Advanced Roadmaps. It must also be something that app developers can tie into.

Right now we have many versions on "Teams" in multiple products and apps and it just makes things messy and confusing.

Once you have that, I would want to see features that are team related, like schedules for team meetings, availability for each team member with vacations and sick days (that also impact every planning tool) and the ability to connect a Confluence space for anything we need to document for the team.

Teams can be one of the best features Atlassian has implemented, but it needs to be front and center and not a feature on the side that no one uses.

I believe you have a raw diamond in Teams April and I look forward to seeing you shape it into the amazing gem I think we all know it can be!

[April Chi]

Hi @Jimi Wikman ,

Thanks for the great response. You have some really good points there. I agree there's a lot of growth potential and we're working towards product adoption starting with the ability to associate Teams in Jira issues. 

I'm running a 1 hour paid research study to learn about how we can make Atlassian Teams better. Would you be willing to join? If so, it'd be great if you could fill in this brief survey and I'll be in contact :)

From the sounds of it and based on your profile, you're regularly helping customers with Atlassian products - it'd be great to hear more around your thoughts on Teams. 

Regards,

April

[Jimi Wikman]

@April Chithank you for that offer, I will see if time lets up in a few weeks as I am closing a project right now :)