{"id":77729,"date":"2026-07-08T11:20:19","date_gmt":"2026-07-08T18:20:19","guid":{"rendered":"https:\/\/www.atlassian.com\/blog\/?p=77729"},"modified":"2026-09-15T16:56:18","modified_gmt":"2026-09-15T23:56:18","slug":"mercedes-benz-ai-agents-enterprise","status":"publish","type":"post","link":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise","title":{"rendered":"Why AI alone isn’t enough for enterprises (and what Mercedes-Benz did about it)"},"content":{"rendered":"\n

<\/p>\n\n\n\n

The learnings in this blog post are based on the session, \u201cHow Mercedes turns Teamwork Graph into an AI advantage\u201d, presented at Atlassian\u2019s Team ’26 conference. <\/em>You can<\/u><\/em><\/a> check out this session and others on demand.<\/u><\/em><\/a><\/p>\n\n\n\n

<\/p>\n\n\n\n

Foundation models have become astonishingly capable over a very short period. At the beginning of this decade, they could barely look up facts online. Today, they can produce work that would take a human engineer more than an hour, and the pace of improvement has been exponential, especially over the last 18 months.<\/p>\n\n\n\n

And yet, something strange is happening.<\/em><\/p>\n\n\n\n

When you ask individual users whether AI tools have helped them, more than 50% say \u201cyes\u201d, that they’ve actually saved time and effort. But when you zoom out and ask companies<\/em> whether they’ve seen dramatic improvements to their business, 96% report that they have not<\/strong><\/a>. The technology is there, but unlocking the enterprise-level value has been stubbornly difficult.<\/p>\n\n\n\n

Now, Mercedes-Benz\u2019s recent experience proves the harder enterprise challenge is not whether AI can generate output; it’s whether that output can connect to the messy reality of work across tools, teams, data, and decisions.<\/p>\n\n\n\n

The real bottleneck isn’t the model<\/h3>\n\n\n\n

Work inside organizations depends on collaboration, so when enterprise AI treats it like an individual activity, it will always fall short of its promise.<\/p>\n\n\n\n

The average large enterprise runs over <\/strong>367 SaaS applications<\/strong><\/a>, since often multiple teams use their own tools and follow their own rituals. When teams need to collaborate, people find themselves navigating unfamiliar interfaces, reconciling different planning cycles, and chasing down context scattered across a dozen systems. Goals developed in isolation can leave teams rowing in opposite directions, even when everyone has the best intentions.<\/p>\n\n\n\n

With AI entering the picture, this complexity doesn’t automatically decrease. In fact, it can actually increase. <\/strong>How does a coding agent get the context it needs without creating churn for the rest of the team? How does it coordinate with a design agent running on a different platform? Without a shared layer of context, you end up with faster output that still requires extensive review and rework.<\/p>\n\n\n\n

What AI actually needs to deliver enterprise value<\/h3>\n\n\n\n

Mercedes-Benz\u2019s story is a powerful example of what AI can do at an enterprise, organization-wide level instead of just at an individual productivity level. And for AI to work effectively at that organizational level, it requires three things.<\/p>\n\n\n\n

    \n
  1. The richer the context you can provide<\/strong>, the better the result. If you ask an AI tool to help you prepare for a meeting with a specific client, it needs to understand how decisions have been made for similar customers in the past, the current state of the relationship, and your team’s goals.<\/li>\n\n\n\n
  2. AI becomes truly valuable when it doesn’t just answer questions but participates in workflows<\/strong>. Generating a weekly status update, creating a page, notifying stakeholders, or triaging an incoming ticket are all examples of actions that free people to spend their time on higher-value work.<\/li>\n\n\n\n
  3. When AI is taking actions on your behalf, you need to be confident that it honors your organization’s permissions and privacy policies<\/strong>. If a user doesn’t have clearance to see a particular Jira ticket, the AI shouldn’t know it exists either.<\/li>\n<\/ol>\n\n\n\n

    How Mercedes-Benz is applying this to defect management<\/h3>\n\n\n\n

    Quality has always been central to how Mercedes-Benz defines its vehicles, but the key differentiator has shifted from purely hardware characteristics to the software that runs throughout modern cars. The amount of data generated by connected vehicles, test benches, and development environments is enormous, and the challenge is making that data useful in the flow of engineering work.<\/p>\n\n\n\n

    Like many large engineering organizations, Mercedes-Benz found that its engineers needed to use 11 or more tools to accomplish a single task, with over 300 tools in active use across the company. The time spent navigating between systems, transferring context, and remembering workflows was time not spent on what engineers are actually hired to do: build high-quality products and innovate.<\/p>\n\n\n\n

    \n

    \u201cI want to have as many defects filed as possible, because we can focus on the right things. And all the other things, we don’t have to care about, because AI, the graph, Rovo is handling the rest.”<\/p>\n\n\n\n

    \u2013Tobias Langjahr, Product Manager, Mercedes-Benz<\/em><\/p>\n<\/blockquote>\n\n\n\n

    The defect intake process illustrates this clearly. A year ago, when an engineer testing a vehicle detected a problem, the process depended entirely on the engineer’s diligence in documenting it. There was no automatic enrichment. Once filed, a defect manager would review the information provided and try to determine which team should own it, often leading to cycles of back-and-forth before the right group was even identified. When a defect was eventually resolved, the solution and context lived in a silo that other teams couldn’t access or learn from.<\/p>\n\n\n\n

    Connecting the dots across engineering systems<\/h3>\n\n\n\n

    Mercedes-Benz recognized that if they could connect their various data sources through the Teamwork Graph, Atlassian\u2019s living map of how the organization actually works, they could re-imagine the entire defect lifecycle. They brought together requirements data from IBM Doors, code repositories, release management information, physical part and asset data, and telemetry from test vehicles streaming log data to a central data hub.<\/p>\n\n\n\n

    With these sources connected through the Teamwork Graph the entire set of relationships between a defect, the requirement it traces to, the code that implements it, and the vehicle configuration where it was observed becomes traversable.<\/p>\n\n\n\n

    The Norris family of agents<\/h3>\n\n\n\n

    With this connected data layer in place, Mercedes-Benz addressed a practical friction point: the physical act of filing a defect during vehicle testing. An engineer driving at highway speeds on the Autobahn who notices an error message on the display can’t safely stop to file a detailed ticket, so Mercedes-Benz built a suite of AI agents in Rovo (informally called the “Norris family”) to transform their defect management workflow.<\/p>\n\n\n\n

    Defect Norris <\/strong>handles quality assurance at intake. Analyze the Snores<\/strong> reaches out to central data hubs to pull log data and telemetry related to the specific vehicle and event. And the third agent, Main Norris<\/strong>, handles the regulatory and safety context.<\/p>\n\n\n\n

    Making defect filing as easy as speaking<\/h3>\n\n\n\n

    One of the practical friction points Mercedes-Benz addressed is the physical act of filing a defect during vehicle testing. An engineer driving at highway speeds on the Autobahn who notices an error message on the display can’t safely stop to file a detailed ticket.<\/p>\n\n\n\n

    \n

    “If you imagine driving a car, testing something, you’re on a highway or a German Autobahn\u2026 how do you manage to remember what was happening if you detected something that was not working? You have to stop your car basically and note it down because otherwise you cannot remember after you’re back to the office.”<\/p>\n\n\n\n

    \u2013Tobias Langjahr, Product Manager, Mercedes-Benz<\/em><\/p>\n<\/blockquote>\n\n\n\n

    To solve this, Mercedes-Benz built an in-car voice application that allows engineers to describe a defect using natural speech while driving. The app converts speech to text, associates it with the vehicle identification number, and ships it directly to Jira. Defect Norris then takes over, structuring and enriching what started as a simple spoken description into a fully formed defect record with proper metadata, component identification, and linked vehicle data.<\/p>\n\n\n\n

    Results and the road ahead<\/h3>\n\n\n\n

    The impact has been significant. By measuring the lead time from when a defect is detected to when it is fixed, Mercedes-Benz has achieved a 70% reduction compared to its previous approach<\/strong>. They began this work with the development of the new S-Class and established a clear baseline before the new process went live.<\/p>\n\n\n\n

    The philosophy driving this is straightforward: the easier you make it to file defects, the more defects get filed, and that turns out to be a good thing when AI and the graph can automatically handle the heavy lifting of enrichment, duplicate detection, routing, and prioritization. Engineers can focus on the defects that truly require human expertise and innovation while the system handles everything else.<\/p>\n\n\n\n

    Looking ahead, Mercedes-Benz envisions extending this approach well beyond defect management. The broader ambition is a kind of digital twin for engineering work, where AI, powered by the Teamwork Graph, handles 80-90% of routine effort, freeing people to focus on delivering genuine value rather than wandering between tools searching for the right context or the right person to talk to.<\/p>\n\n\n\n

    And while functional safety regulations appropriately limit how much autonomy AI can have in safety-critical automotive systems today, connected data, rich context, and intelligent automation will continue to compress the distance between identifying a problem and resolving it.<\/p>\n\n\n\n

    Co-building with the graph<\/h3>\n\n\n\n

    Mercedes-Benz’s results aren’t a one-off, but rather a preview of what’s possible when AI has the right foundation to work from. The Teamwork Graph is a connected, living map of your organization’s work that gives AI agents the context they need to act with precision, not just speed.<\/p>\n\n\n\n

    While Teamwork Graph captures the most important use cases across industries, almost every organization has its own unique tools and workflows. A home loan company might need to bring data from a specialized testing platform. An aerospace company might want to connect its project management tool. A social media company might need to surface data from a custom sales system.<\/p>\n\n\n\n

    To handle this, the Atlassian platform supports building with the graph directly. It currently offers more than 100 out-of-the-box connectors, and organizations can build their own custom connectors to bring data from proprietary or legacy systems into the graph. Once data is ingested, it becomes searchable and actionable across Atlassian products, and it can power custom agents and applications built on top of the graph.<\/p>\n\n\n\n

    Experience the power of the Teamwork Graph<\/a> for yourself and see your graph preview.<\/p>\n","protected":false},"excerpt":{"rendered":"

    How connected data and AI agents are closing the gap between individual productivity and enterprise-wide transformation.<\/p>\n","protected":false},"author":1376,"featured_media":77730,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"alternative_eyebrow":"","alternative_headline":"","alternative_description":"","alternative_featured_image":0,"rkv_hide_featured_media":false,"rkv_featured_media_url":"","rkv_featured_media_sizes":[],"editor_notices":[],"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[15235],"tags":[15077,14985,15166,15031,15153,15105,15154],"tier":[14936],"apps":[],"coauthors":[12984],"class_list":["post-77729","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-context","tag-ai-agents","tag-ai-at-work","tag-digital-transformation","tag-enterprise-ai","tag-mercedes-benz-ai","tag-teamwork-graph","tag-workplace-productivity","tier-tier-2"],"edit_link":null,"acf":[],"yoast_head":"\nWhy AI alone isn't enough for enterprises (and what Mercedes-Benz did about it) - Inside Atlassian<\/title>\n<meta name=\"description\" content=\"Discover how Mercedes-Benz cut defect resolution time by 70% using AI agents and the Teamwork Graph \u2014 and why connected data beats smarter models alone.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why AI alone isn't enough for enterprises (and what Mercedes-Benz did about it) - Inside Atlassian\" \/>\n<meta property=\"og:description\" content=\"Discover how Mercedes-Benz cut defect resolution time by 70% using AI agents and the Teamwork Graph \u2014 and why connected data beats smarter models alone.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise\" \/>\n<meta property=\"og:site_name\" content=\"Inside Atlassian\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Atlassian\" \/>\n<meta property=\"article:published_time\" content=\"2026-07-08T18:20:19+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-15T23:56:18+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"675\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Ryan Narragon\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Atlassian\" \/>\n<meta name=\"twitter:site\" content=\"@Atlassian\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ryan Narragon\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise\"},\"author\":{\"name\":\"lzneimer\",\"@id\":\"https:\/\/www.atlassian.com\/blog\/#\/schema\/person\/905e0c3376c16f013fafdf1782d38b20\"},\"headline\":\"Why AI alone isn’t enough for enterprises (and what Mercedes-Benz did about it)\",\"datePublished\":\"2026-07-08T18:20:19+00:00\",\"dateModified\":\"2026-09-15T23:56:18+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise\"},\"wordCount\":1633,\"image\":{\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#primaryimage\"},\"thumbnailUrl\":\"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png\",\"keywords\":[\"ai agents\",\"ai at work\",\"digital transformation\",\"enterprise AI\",\"mercedes-benz ai\",\"teamwork graph\",\"workplace productivity\"],\"articleSection\":[\"Context\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise\",\"url\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise\",\"name\":\"Why AI alone isn't enough for enterprises (and what Mercedes-Benz did about it) - Inside Atlassian\",\"isPartOf\":{\"@id\":\"https:\/\/www.atlassian.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#primaryimage\"},\"thumbnailUrl\":\"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png\",\"datePublished\":\"2026-07-08T18:20:19+00:00\",\"dateModified\":\"2026-09-15T23:56:18+00:00\",\"author\":{\"@id\":\"https:\/\/www.atlassian.com\/blog\/#\/schema\/person\/905e0c3376c16f013fafdf1782d38b20\"},\"description\":\"Discover how Mercedes-Benz cut defect resolution time by 70% using AI agents and the Teamwork Graph \u2014 and why connected data beats smarter models alone.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#primaryimage\",\"url\":\"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png\",\"contentUrl\":\"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png\",\"width\":1200,\"height\":675},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.atlassian.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why AI alone isn’t enough for enterprises (and what Mercedes-Benz did about it)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.atlassian.com\/blog\/#website\",\"url\":\"https:\/\/www.atlassian.com\/blog\/\",\"name\":\"Inside Atlassian\",\"description\":\"Research, expert perspectives, and product announcements from Atlassian on how teams can work smarter with AI. Subscribe for monthly insights on the future of teamwork.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.atlassian.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.atlassian.com\/blog\/#\/schema\/person\/905e0c3376c16f013fafdf1782d38b20\",\"name\":\"lzneimer\",\"url\":\"https:\/\/www.atlassian.com\/blog\/author\/lzneimer\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Why AI alone isn't enough for enterprises (and what Mercedes-Benz did about it) - Inside Atlassian","description":"Discover how Mercedes-Benz cut defect resolution time by 70% using AI agents and the Teamwork Graph \u2014 and why connected data beats smarter models alone.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise","og_locale":"en_US","og_type":"article","og_title":"Why AI alone isn't enough for enterprises (and what Mercedes-Benz did about it) - Inside Atlassian","og_description":"Discover how Mercedes-Benz cut defect resolution time by 70% using AI agents and the Teamwork Graph \u2014 and why connected data beats smarter models alone.","og_url":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise","og_site_name":"Inside Atlassian","article_publisher":"https:\/\/www.facebook.com\/Atlassian","article_published_time":"2026-07-08T18:20:19+00:00","article_modified_time":"2026-09-15T23:56:18+00:00","og_image":[{"width":1200,"height":675,"url":"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png","type":"image\/png"}],"author":"Ryan Narragon","twitter_card":"summary_large_image","twitter_creator":"@Atlassian","twitter_site":"@Atlassian","twitter_misc":{"Written by":"Ryan Narragon","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#article","isPartOf":{"@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise"},"author":{"name":"lzneimer","@id":"https:\/\/www.atlassian.com\/blog\/#\/schema\/person\/905e0c3376c16f013fafdf1782d38b20"},"headline":"Why AI alone isn’t enough for enterprises (and what Mercedes-Benz did about it)","datePublished":"2026-07-08T18:20:19+00:00","dateModified":"2026-09-15T23:56:18+00:00","mainEntityOfPage":{"@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise"},"wordCount":1633,"image":{"@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#primaryimage"},"thumbnailUrl":"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png","keywords":["ai agents","ai at work","digital transformation","enterprise AI","mercedes-benz ai","teamwork graph","workplace productivity"],"articleSection":["Context"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise","url":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise","name":"Why AI alone isn't enough for enterprises (and what Mercedes-Benz did about it) - Inside Atlassian","isPartOf":{"@id":"https:\/\/www.atlassian.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#primaryimage"},"image":{"@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#primaryimage"},"thumbnailUrl":"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png","datePublished":"2026-07-08T18:20:19+00:00","dateModified":"2026-09-15T23:56:18+00:00","author":{"@id":"https:\/\/www.atlassian.com\/blog\/#\/schema\/person\/905e0c3376c16f013fafdf1782d38b20"},"description":"Discover how Mercedes-Benz cut defect resolution time by 70% using AI agents and the Teamwork Graph \u2014 and why connected data beats smarter models alone.","breadcrumb":{"@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#primaryimage","url":"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png","contentUrl":"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png","width":1200,"height":675},{"@type":"BreadcrumbList","@id":"https:\/\/www.atlassian.com\/blog\/context\/mercedes-benz-ai-agents-enterprise#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.atlassian.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Why AI alone isn’t enough for enterprises (and what Mercedes-Benz did about it)"}]},{"@type":"WebSite","@id":"https:\/\/www.atlassian.com\/blog\/#website","url":"https:\/\/www.atlassian.com\/blog\/","name":"Inside Atlassian","description":"Research, expert perspectives, and product announcements from Atlassian on how teams can work smarter with AI. Subscribe for monthly insights on the future of teamwork.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.atlassian.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.atlassian.com\/blog\/#\/schema\/person\/905e0c3376c16f013fafdf1782d38b20","name":"lzneimer","url":"https:\/\/www.atlassian.com\/blog\/author\/lzneimer"}]}},"jetpack_featured_media_url":"https:\/\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/07\/mercedes-benz-team-recap-blog.png","jetpack_shortlink":"https:\/\/wp.me\/phdlri-kdH","jetpack-related-posts":[{"id":76328,"url":"https:\/\/www.atlassian.com\/blog\/company-news\/founder-update-team-26","url_meta":{"origin":77729,"position":0},"title":"Atlassian Team ’26: Meet the AI-Native Organization","author":"dkoudsi@atlassian.com","date":"May 6, 2026","format":false,"excerpt":"I'm stoked to be back in Anaheim, California for Team \u201926 with thousands of our customers. Together, we\u2019re facing the most significant reimagining of work in our lifetime\u2014one that has only accelerated since we were last here. This is crazy exciting. We\u2019re seeing a new kind of organization emerge: the\u2026","rel":"","context":"In "Company News"","block_context":{"text":"Company News","link":"https:\/\/www.atlassian.com\/blog\/search?topic[0]=company-news"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/csd-26525-team-26-founder-blog-header-1920x1080%402x-scaled.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/csd-26525-team-26-founder-blog-header-1920x1080%402x-scaled.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/csd-26525-team-26-founder-blog-header-1920x1080%402x-scaled.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/csd-26525-team-26-founder-blog-header-1920x1080%402x-scaled.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/csd-26525-team-26-founder-blog-header-1920x1080%402x-scaled.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/csd-26525-team-26-founder-blog-header-1920x1080%402x-scaled.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":76268,"url":"https:\/\/www.atlassian.com\/blog\/company-news\/teamwork-graph-team-26","url_meta":{"origin":77729,"position":1},"title":"Atlassian Teamwork Graph: The context engine behind your AI\u2014everywhere","author":"dkoudsi@atlassian.com","date":"May 6, 2026","format":false,"excerpt":"Connections. Insights. Workflows. All mapped, all in context.","rel":"","context":"In "Company News"","block_context":{"text":"Company News","link":"https:\/\/www.atlassian.com\/blog\/search?topic[0]=company-news"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/1120-x-545.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/1120-x-545.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/1120-x-545.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/1120-x-545.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/1120-x-545.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/05\/1120-x-545.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":70212,"url":"https:\/\/www.atlassian.com\/blog\/ai-at-work\/unlocking-ai-teammates-with-twc","url_meta":{"origin":77729,"position":2},"title":"Unlocking AI Teammates with Teamwork Collection","author":"Christopher Cheung","date":"July 21, 2025","format":false,"excerpt":"How to unleash smarter collaboration for every team","rel":"","context":"In "AI at Work"","block_context":{"text":"AI at Work","link":"https:\/\/www.atlassian.com\/blog\/search?topic[0]=ai-at-work"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/07\/banner-for-blog.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/07\/banner-for-blog.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/07\/banner-for-blog.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/07\/banner-for-blog.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/07\/banner-for-blog.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/07\/banner-for-blog.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":76115,"url":"https:\/\/www.atlassian.com\/blog\/company-news\/shareholder-letter-q3fy26","url_meta":{"origin":77729,"position":3},"title":"Our Q3 FY26 letter to shareholders","author":"Christopher Cheung","date":"April 30, 2026","format":false,"excerpt":"Prefer a PDF? No worries! Get it\u00a0here \u2601\ufe0f From the CEO Fellow shareholders, I\u2019m thrilled to share our incredible Q3 results. The entire Atlassian team has been laser-focused on execution, and it shows in our numbers. \ud83d\ude80 Total revenue was strong at $1.8B, up 32% y\/y\ud83d\ude80 Cloud revenue surged past\u2026","rel":"","context":"In "Company News"","block_context":{"text":"Company News","link":"https:\/\/www.atlassian.com\/blog\/search?topic[0]=company-news"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/04\/q3-fy26-shareholder-blog-illo-1120-x-545-px-scaled.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/04\/q3-fy26-shareholder-blog-illo-1120-x-545-px-scaled.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/04\/q3-fy26-shareholder-blog-illo-1120-x-545-px-scaled.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/04\/q3-fy26-shareholder-blog-illo-1120-x-545-px-scaled.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/04\/q3-fy26-shareholder-blog-illo-1120-x-545-px-scaled.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/04\/q3-fy26-shareholder-blog-illo-1120-x-545-px-scaled.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":72269,"url":"https:\/\/www.atlassian.com\/blog\/jira-service-management\/supercharging-rovo-with-unito-connectors-in-the-atlassian-marketplace","url_meta":{"origin":77729,"position":4},"title":"Supercharging Rovo: how Unito’s Connectors in the Atlassian Marketplace transform AI intelligence","author":"amacaraeg@atlassian.com","date":"December 2, 2025","format":false,"excerpt":"Bringing enterprise-grade integrations to the Atlassian Teamwork Graph and into the Atlassian Ecosystem as a whole unlocks new possibilities for AI-powered work","rel":"","context":"In \"jira service management\"","block_context":{"text":"jira service management","link":"https:\/\/www.atlassian.com\/blog\/tag\/jira-service-management"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/12\/rovo_twgblog_header_1120x545.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/12\/rovo_twgblog_header_1120x545.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/12\/rovo_twgblog_header_1120x545.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/12\/rovo_twgblog_header_1120x545.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/12\/rovo_twgblog_header_1120x545.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2025\/12\/rovo_twgblog_header_1120x545.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":79454,"url":"https:\/\/www.atlassian.com\/blog\/ai-at-work\/ai-sdlc-transformation-playbook","url_meta":{"origin":77729,"position":5},"title":"The AI SDLC transformation playbook","author":"Martha Fishburne","date":"October 1, 2026","format":false,"excerpt":"Teams across the industry are sprinting to reinvent their software development processes with agentic AI. Yet, navigating the fast-changing landscape of tools and opinions can be daunting for even the most AI-forward organizations.\u00a0 This guide shares Atlassian\u2019s approach and best practices, informed by our own internal AI SDLC transformation and\u2026","rel":"","context":"In "AI at Work"","block_context":{"text":"AI at Work","link":"https:\/\/www.atlassian.com\/blog\/search?topic[0]=ai-at-work"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/09\/blog_email-1120x545px-a-1.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/09\/blog_email-1120x545px-a-1.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/09\/blog_email-1120x545px-a-1.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/09\/blog_email-1120x545px-a-1.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/atlassianblog.wpengine.com\/wp-content\/uploads\/2026\/09\/blog_email-1120x545px-a-1.png?resize=1050%2C600&ssl=1 3x"},"classes":[]}],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/posts\/77729","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/users\/1376"}],"replies":[{"embeddable":true,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/comments?post=77729"}],"version-history":[{"count":1,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/posts\/77729\/revisions"}],"predecessor-version":[{"id":79231,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/posts\/77729\/revisions\/79231"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/media\/77730"}],"wp:attachment":[{"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/media?parent=77729"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/categories?post=77729"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/tags?post=77729"},{"taxonomy":"tier","embeddable":true,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/tier?post=77729"},{"taxonomy":"apps","embeddable":true,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/apps?post=77729"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/atlassianblog.wpengine.com\/wp-json\/wp\/v2\/coauthors?post=77729"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}