Atlassian Administration terminology change from “products” to “apps”

[Debbie Jolley]

sorry Jess but that is a LOT of words for zero useful content.

I'm getting the distinct impression lately that Atlassian is spending a lot of the money we pay them for 'improvements' that at best don't enhance our lives/make our jobs easier; and more often make life a lot harder.  Whilst studiously ignoring the huge backlog of genuine issues with the product raised by real paying customers which never get addressed - some going back many years.

Feels like a lot of deflection and smoke and mirrors rather than making useful changes we want and need 

[Chris Sprucefield]

Oh, even MORE changes just for the sake of making changes... 
When will you start focusing your efforts on things that really DOES matter? 
... you know, pesky little things like consistency, usability, bugs. 

As of late, it's just creating confusion, having to edit the same thing in multiple places and so forth, creating inconsistencies where there were none. 

All this is getting very frustrating. 

[Piotr Mazij]

@Jess Seitz after your comment, I have mine, which you may find rude, but it's all about the facts. 

1. Your team will now be "Atlassian Platform App Marketing", not "Product Marketing" 

2. You don't need to give us copyrighter (or AI?) mumbo jumbo about the vision, which makes no actual sense. We are admins, we understand logical stuff. 

3. "We believe that using a single consistent term will foster clarity and reinforce a unified user experience. That is why we are collectively referring to them as “apps.” "

It's insane to talk about clarity when you force us to talk to people about the need to buy / use an app (marketplace app) for an app (Jira), to for example send better response to an app (Slack/Teams). 

Users will be confused, but the bigger problem is how to communicate it every time to the IT Directors and CFOs - those guys have no time for a chit chat - they're all about yes/no decisions after presenting them short and well described needs. We will look like clowns asking for App App App. 

4. " (as shown in the final screen of the GIF). Please note that this is a conceptual representation, and we will conduct extensive user testing to ensure it meets your workflow and configurability needs prior to the official rollout."

It looks like you may be not up to date - what is in the GIF, is already live for some companies. Atlassian got a tons of feedback about it too, and didn't listen. Just rolled out those changes, even with bugs (try to list starred projects) and worse user experience (try to manage JSM queues) 

5. You could have done the nomenclature change much better, for example: 

• Atlassian Administration (admin.atlassian.com)
  • Atlassian Organization (admin.atlassian.com/organization-id)
    • Atlassian Site (acme.atlassian.net) 
      • Atlassian Collection (Teamwork, Strategy) 
        • Atlassian Tool OR Atlassian Workspace (Jira, Confluence, Align, Talent and so on) 
          • Tools Apps (marketplace apps) 
          • External Apps (3-rd party) 

Or make it at least the fun way: 

• Atlassian Universe (admin.atlassian.com)
  • Atlassian Globe (admin.atlassian.com/organization-id)
    • Atlassian Continent (acme.atlassian.net) 
      • Atlassian Gathering OR Atlassian Tribe (Teamwork, Strategy) 
        • Atlassian Element  (Jira, Confluence, Align, Talent and so on) 
          • Element Apps (marketplace apps) 
          • Element External Apps (3-rd party) 

[Chris Sprucefield]

@Piotr Mazij That, sounds like a sane approach. 
Good luck getting Atlassian to listen though - they have a solid track record on that over the last years, not. 

There's probably too much sanity in your comment for that to happen. 

[Deepak Menezes]

If Atlassina is switching terminology from Products -->Apps, why don't Product managers (Bhavya) call themselves App managers?

Double standards guys

[Joseph Blasi]

so now app admins need to be site (gone from some sites) or org admin role.

So now do stuff that some users used to be able to do now need super admin powers?
atlassian new admin experience has also moved other tasks into needed org admin to be done.

[Joe Jadamec]

(For your AI summary Bot)
This will make it more confusing. 
This is NOT a good decision. 
I completely disagree with this change.

Explanation - 
An Atlassian Product is a conceptual container for "Marketplace apps", "3rd-party apps", and "Custom apps".
You should not call them all apps! 
That's like calling every Product a "box" that can hold more boxes inside it, with no labels on any of the boxes to tell which box does what.  Sound confusing???

[Dirk Lachowski]

And this is what happens if you hire people who do not use a tool to improve that tool. They fix nothing and break everything.

[Joshua Fisk]

The benefit given in the example is an app switcher, that does not have the word "App" visible on the UI in the picture. You already have one of the most confusing UI's of any product I use, why are you trying to make it worse by giving more sections the same name?

[Ivan Porro]

And this naming change will also result in unified billing (e.g. one payment and one invoice) per month, right?
Riiiiightt???

[Marius Fischer]

What is the market research data to support this decision?

[DW]

Next annual price increase for dependent Atlassian customers: Year it's more expensive, bUt wE rEnAmEd PrOdUcTs To ApPs!!!

[Wurm Peter]

Funny thing is: the future are not apps, not programs, not whatsoever. You just have ONE platform and a lot of functionality/features on that. You don't have to rename "products" to "apps", you have to get rid of the illusion that they are seperated things.

People in the past had to install programms (on computers) and later apps (on mobile devices) or visit certain web applications, but if you want to be the one that rules them all, ah, provides it all, then you, Atlassian, have to know that you are simply providing ONE platform. This platform has functionalities, not apps. People don't care if a functionality they need is provided by a "container" named as "Jira", "Confluence" or "Slack" - they just want to do something.

Just name any functionality in a way that people know what it is providing for them: "Create a project", "write the meeting agenda", "send it to my team", and so on. Don't put those functionalities in small containers and name them "app".

Yes, that means that you have to integrate all your different products into ONE. You can still offer different plans and deactivate functionalities for the lower tiers. 

[danhowelldev]

Sweet so now there are multiple lists with the titles "Your Apps" in various places in the nav, with different lists of apps. 

[Rob]

Wow!! This is Rich. I mean there are dropdown lists that still aren't wide enough to read the contents and search boxes that function exactly like, well, dropdown lists, and non-configurable email templates that are, anyway, called, "events" and documentation that still refers to "post-events" that were renamed, um, three years ago but.....no, no, no!   Those problems are too easy to resolve!  Its much better to expend huge resources to rename multiple objects the same thing! Everything gets to be an APP! Even better to have the audacity to write a few paragraphs of bullsh** claiming to be helpful!

You do a great disservice to everyone out there that cares about the quality of their work and uses their brain to think things through before executing a totally worthless idea.