Atlassian originally pitched the name “Architected for Atlassian (A4A)”, and we (the community) pushed back hard (RFC-124). Atlassian went back to the drawing board and pitched the name "Enterprise Ready" (RFC-133). That was better, but still had lots of problems, and we pushed back again. So, Atlassian went back to the drawing board again.
Final result: “Atlassian Enterprise Certified”.
Reviewing some of the objections that were raised across the two RFCs, I think Atlassian addressed many (but not all) of them. For example:
- Don’t imply too much about an app’s technical architecture → Done. Dropped “Architected”.
- Make it a certification instead of a statement of general readiness → Done. Replaced “Ready” with “Certified”.
- Make it clear the certification is Atlassian’s → Done. Put “Atlassian” back in the name.
- Don’t frame the program around “Enterprise” → Still there…
Not saying I love “Atlassian Enterprise Certified”, but we came a long way from “Architected for Atlassian”.
All of that is to say I think there is clear evidence that Atlassian considered our feedback and made substantial changes in response.
I do, however, agree with the criticism about the tagline. The phrase “common enterprise needs for compliance, security, reliability, privacy, accessibility, and responsible AI use” is overly broad and not fully supported by the actual certification requirements.