
AIネイティブ企業が他社と違う7つのこと
7 Things AI-Native Companies Do Differently

AIネイティブ企業が他社と違う7つのこと
The AI Daily Brief: Artificial Intelligence News and Analysis
要約
NLWが、Stripe、Shopify、Uber、Rampなど先進企業が公開したエージェント運用事例から、AIネイティブ組織に共通する7つの実践を整理した回。共有コンテキスト、全部門への展開、シグナル起点の業務開始、オーケストレーター型の構成、検証、リスクに応じた人間の責任、組織共通の仕組みが挙がる。後半では「エージェントはチームメイト」という見方が実態に合わなくなり、オンデマンドのコンサル会社に近いと論じている。
この回のポイント
- ●最も重要な実践は、従業員が見られる情報をエージェントにも見せるコンテキスト共有で、Odessia、Ramp、Uber、Shopifyが事例として挙がった。コンテキスト層の管理が必要で、古くなると性能が落ちる。
- ●エンジニアリング以外の全部門にエージェントを置き、業務は人間のプロンプトではなく顧客メッセージや請求書、障害アラートなどのシグナルで自動的に始まる。
- ●常設エージェントを多数抱えるのではなく、オーケストレーターが必要に応じてサブエージェントを起動する構成が主流になりつつある。Anthropicのリサーチシステムは単一エージェントを社内評価で約90%上回ったという。
- ●成果物の検証が新たなボトルネックとなり、Shopifyは発見した人とは別のモデルで検証する。同時にリスクに応じて人間のレビューを割り当て、最終責任者を必ず明確にする。
- ●組織全体で共通のスキルライブラリや公開チャンネルでの運用を整え、指標もコード行数ではなく差し戻し頻度などで測る。
- ●役割ごとに固定されたエージェント名簿という発想は崩れつつあり、Harvard Business Reviewの研究ではAIチームメイト扱いだと確認が甘くなる傾向も示された。
章立て
導入:チームメイト観への疑問
エージェントをチームメイトとみなす見方が実態に合わないという問題提起と、本回で扱う内容の紹介。
実践1:全体像を渡すコンテキスト
Odessia、Ramp、Uber、Shopifyの例を挙げ、エージェントに従業員と同等以上の情報を与える重要性と、その管理の難しさを説明する。
実践2・3:全部門展開とシグナル起点
エンジニア以外の部門でのエージェント活用と、人のプロンプトではなくトリガーで仕事が始まる仕組みを紹介する。
実践4:オーケストレーター構成
主エージェントが必要に応じてサブエージェントを起動する構成とその利点を、AnthropicやRampの例で示す。
実践5・6:検証と人間の責任
別のエージェントによる検証と、リスクに応じたレビュー設計、責任者の明確化を取り上げる。
実践7:組織共通の仕組み
共有スキルライブラリや公開チャンネル運用、自己改善の仕組み、測るべき指標について述べる。
チームメイト観が合わない理由
固定名簿ではなく動的な規模のエージェント群が有効だと論じ、オンデマンドのコンサル会社という比喩を提示する。
HBR研究と個人エージェントとの関係
AIチームメイト扱いで検証が甘くなる研究と、個人向けエージェントがオーケストレーターとして位置づけられる可能性を述べる。
解説記事
AI関連ポッドキャスト「The AI Daily Brief」の司会NLWが、Stripe、Shopify、Uber、Rampといった先進企業が公開したエージェント運用の事例を読み込み、AIネイティブ企業に共通する7つの実践をまとめた回である。さらに、2026年前半に盛り上がった「エージェントはチームメイト」という考え方が実態に合わなくなっているという見方も示した。
前提:エンジニアリング事例が中心
NLWは、紹介する事例の多くがソフトウェア開発由来だと断っている。コードにはテストがあり、完了の定義が明確なので、エージェント活用が先行したという説明だ。一方で、エンジニアの今の動きは他部門の3〜6か月後を映すとも述べ、参考にする価値を強調している。全体の要点は「会社そのものがシステムになる」ことだという。
7つの実践(前半)
1つ目はコンテキストの共有である。モデル性能ではなく、モデルが触れられる情報と仕組みが限界になっているという認識が背景にある。OpenAIに買収されたOdessiaのFrancis Davidsonは、会議録、Slack、メール、ドライブなどにMCPやCLIでアクセスさせる方針を「content maxing」と呼び、意思決定ごとに共有文書も残していた。Rampは日次パイプラインでSlackやNotionなどを永続メモリに取り込み、Uberは30以上の社内システムを結ぶコンテキストグラフを作った。ただしコンテキスト層自体の管理が必要で、Rampの分析エージェントは情報が古くなると悪化するという。Hebbiaでは、将来を不安視する従業員が雇用保障のために知識を抱え込む問題も報告された。
2つ目は、エンジニアリングだけでなく全部門にエージェントを置くことだ。Anthropicの成長マーケティングは1人のチームで、エージェントを使い数百の広告を数分で書けるとされる。3つ目は、プロンプトではなくシグナルで仕事が始まることだ。顧客メッセージ、請求書、更新期限、運用アラートなどが起点になり、Uberではエージェントのセッションの多くが、コードレビューやCIの自己修復、オンコールの一次対応を中心に、別のエージェントから開始されるという。
4つ目は、常設エージェントを並べるのではなく、オーケストレーターが必要に応じてサブエージェントを呼ぶ構成である。Anthropicのリサーチシステムでは、リードエージェントが並列にサブエージェントを動かし、社内評価で単一エージェントを約90%上回った。要約と重要な文脈はオーケストレーターが持ち、各ワーカーには絞った指示とまっさらな状態を渡す。
7つの実践(後半)
5つ目は検証である。ボトルネックは作ることから確認することに移ったとNLWは述べる。Shopifyのセキュリティシステムは、すべての発見を「証明すべき主張」として扱い、悪用するテストを書けなければ却下か格下げし、発見したモデルとは別のモデルで確認する。RunLayerでは修正後にスクリーンショット付きでプルリクエストを出し、別エージェントが敵対的にレビューし、出荷後はQAエージェントが壊しにかかる。
6つ目は、リスクに応じた人間のレビューと説明責任だ。すべてを見るのでも何も見ないのでもなく、事前に人が必要な領域を決める。Uberではエージェント間の呼び出しが特定の担当者まで遡れ、Stripeではマージは必ず人間が行い、RunLayerでは低リスクの変更は自動マージされる。Snapはエージェント投資の半分超をガードレールに充てているという。
7つ目は、組織全体での一貫性である。Rampは350の共有ワークフロー、Uberは3,600のスキルを持ち、1日3万回以上実行される。Shopifyのコーディングエージェントは公開Slackチャンネルでしか動かず、全セッションが検索可能な記録になる。Warpではスコアリング用エージェントが実行結果を採点し、別のエージェントが改善案をプルリクエストで出す。指標はコード行数やPR数ではなく、差し戻し頻度のような質に近いものを見るべきだとされた。
なぜ「チームメイト」ではないのか
NLWは、エージェントをチームメイトとみる発想は、チャット窓から自律的に働くAIへ移る過渡期の比喩としては有用だったと認める。しかし固定の名簿、役割、永続的なアイデンティティを前提にしがちで、実際には仕事量に応じて増減する動的なエージェント群が主流になりつつあるという。個人の記憶より会社全体のコンテキストが重要になる。Anthropicの指針として、プランナー、コーダー、テスターなど職能で分けると受け渡しが伝言ゲームになり、役割別の実験では協調に労力が割かれたとも紹介された。NLWはこれをbitter lessonの一種とみて、人間の管理手法を模倣するよりエージェント自身に組織化させる方がよいと論じる。Everyも各人に代理エージェントを持たせる実験を経て、交点に立つ少数のエージェントが必要に応じて拡張する形に移ったという。NLW自身も、OpenClawでの階層的な構成から、リポジトリという共有コンテキストにエージェント群を差し込む使い方へ変えた。
より適した比喩として挙げたのがオンデマンドのコンサル会社だ。目標を渡し、コーディネーターが人員を割り当て、証拠付きの成果物が返り、自分が承認して責任を負う。終了後に担当者は去るが、成果と記録は残る。
加えて、5月のHarvard Business Reviewの研究では、誤りを仕込んだ文書をマネージャーに確認させたところ、AIチームメイトが書いたとされた場合に確認が甘くなり、AIを従業員として扱う企業では精査が約16%下がったと紹介された。NLWは単一の研究であり、早期の結果だと留保している。個人向けエージェントとの関係については、それらは個人の文脈を握る「超オーケストレーター」であり、両者は必ずしも対立しないと述べた。
まとめ
日本企業でも、エージェント導入を人格を持つデジタル社員として進めるか、共有コンテキストと検証・責任の設計として進めるかは重要な分岐点になる。本回の示唆は、名前付きエージェントを増やすより、情報基盤の整備、トリガー設計、検証層、責任者の明確化に投資すべきだという点にある。特にコンテキストの陳腐化や知識の抱え込みという文化面の課題は、日本の組織でも無縁ではない。なお事例の多くは企業側の自己報告であり、効果の数字は番組内の紹介にとどまる点には留意したい。
文字起こし(英語・自動生成)
People have been excited about the idea of agents as teammates for a lot of 2026, going all the way back to the OpenClaw explosion. I myself had an entire team of OpenClaws, some researchers, some writers, a bunch of different coordinators for projects, and a chief of staff that sat above them all. Increasingly, though, I am getting more and more convinced that agents as teammates is, in fact, the wrong mental model. Or at least, it doesn't at all reflect how the most sophisticated users are using agents in practice. Today we're going to get into that, but also look at more broadly, seven things that AI native organizations are really doing, and why so many of them come back to how they manage context. The AI Daily Brief is a daily podcast and video about the most important news and discussions in AI. All right, friends, quick announcements before we dive in. First of all, thank you to today's sponsors, KPMG, Robots and Pencils, Cdata and Blitzy. To get an ad-free version of the show, go to patreon.com slash AIDailyBrief,
or you can subscribe on Apple Podcasts. And if you want to learn more about sponsoring the show, send us a note at sponsors at AIDailyBrief.ai. One more last call to register for the AI Champions Bootcamp. It's the first time that we're running this program. It is six live sessions with Nuflar. It kicks off tomorrow and will transform you not only into an agent user, but into someone who can help agents propagate across your entire organization. You can find info about that at BeSuper.ai. At this point, we have all been drowning in China's spy and chip export control scandals for way more time than I think anybody wants. And so for this week's Long Read Sunday slash Big Think episode, I really wanted to do something that was once again much more practical. And as you might imagine, one of the things that I am constantly watching for is companies reporting how they're actually using AI. I think one of the great things that we all struggle with is that there's so little information relative to the speed at which things changes about how these new capabilities are actually finding their way into existing systems.
You hear a lot of companies aspire to be AI native, but what does that actually mean? Well, luckily, over the past few months, at least a handful of the most aggressive AI adopters have started publishing exactly how they run agents in production. These are companies like Stripe, Shopify, Uber, Ramp, Cloudflare, as well as smaller AI native companies and startups as well. Individual operators, of course, are posting their setups on X on a much more frequent basis. Now, you read enough of these things, and a picture starts to become clear of what, at least at the moment, the closest to AI native organizations have in common. Today, we're going to look at seven of those practices. Practices which, theoretically, you could put in place as soon as you're done listening to this. And then we're going to spend time on one thing that I might imagine many of you to expect to be on the list, but it isn't, which is the concept of agents as teammates. I've been getting increasingly convinced that the agent as teammate mental model is an incorrect one. And I'm starting to see some evidence for other people finding something similar as well. Now, one important caveat up front is that, as you might guess,
a lot of the examples that we'll discuss today come from the world of software engineering. That's not only because code got there first, it's because of why code got there first. It has tests, verifiability, done has a clear definition. And in some cases, applying these things to other areas outside of coding and software engineering won't be as clear. Still, I've always said that one of the best ways to actually see into the future of your own organization or your own AI practices is to go watch what the engineers are doing today to give you a sense of what you might be doing in three to six months. So let's get into these seven practices and then talk about why agent organization seems increasingly less like a team of co-workers and more like hiring consulting firms on demand. So let's start with these seven practices for getting useful work out of agents. And if you had to give it a TLDR, The idea is that the company becomes a system. The first practice, which will come as a surprise to exactly zero of you, is about context. Context which has lurked around as the important unspoken issue for basically the entire history of AI. As we all know so well, especially for significant, meaningful knowledge work, the limit tends
not to be the model, and it hasn't been for some time. It's the context in information and systems that the model has access to. So the first practice of the most advanced AI native organizations is to give agents the whole picture, to give them everything an employee can see, or in some cases, even more than a single employee, because agents are working so cross-functionally. One example, which by the way, was one of the inspirations for this piece as a whole, came from the blog post by Francis Davidson after OpenAI acquired his company, Odessia. This is a company that was less than a year old, and people were really excited to see Francis spell out a ton of his different practices. Now, when it comes to this idea of giving agents everything an employee can see, Davidson called the approach content maxing. And what it means is that agents get MCP or CLI access to everything, every meeting recording, Slack, email, drive, and every tool the company uses. Now, one thing that I thought was really notable, it is another stealable idea that many of us might not be doing, is that Odessia also wrote clean shared documents for every decision.
Agents keep that knowledge base up to date, but it provides a track record of not just the decisions but what went into them and how they were decided. Ramp has something similar. A daily pipeline pulls Slack, Notion, Linear, and Calendar into persistent memory so agent sessions never have to start cold. Uber built a context graph for more than 30 internal systems and at Shopify, agents work inside a mono repo effectively. They have one repository that holds the code plus skills conventions runbooks and instruction files that are written for agents Now one of the key catches in giving agents this amount of rich context holding aside of course any security concerns which I am blissfully breezing over right here is that this context layer is in and of itself something that has to be managed. RAMP's analyst agent, for example, they found gets absolutely worse when its context layer gets out of date or is neglected. One additional fascinating challenge that George Svalka of Hebbia found was that this actually has some political issues to it as well. Basically, employees who are unsure about their future are starting to hoard context as job security.
If you know what your value is, why would you hand it to the agent? Now, that is, of course, a cultural problem much more than a technical one, and one that I think leaders are going to have to deal with head on. Practice number two, put agents in every function, not just engineering. Being AI native does not mean having an engineering team who is AI native. It means being AI native across the organization. Odessia, again, put agents across strategy, partnerships, product design, marketing, support, legal and finance, and the different groups share back in the way that they use agents to understand how that might differ from other groups as well. Over in Anthropic, their growth marketing team is, or at least has been in the past, a single person. They've built a robust set of workflows that leverage agents to do things like reading CSVs of hundreds of ads that are running, flagging the underperformers, sub-agents for writing headlines and descriptions, and the net result is that they can write hundreds of new ads in minutes. OpenAI's enterprise signals research found examples like Basis running customer onboarding with agents, Clay running account management with a workspace and sub-agent for every account, and Exa using agents to run developer ecosystem growth.
I recently did my episode about how I use agentic video pipelines, which is another example of agents outside engineering. With practice number three, the description gets a little more abstract, but I think what it is will become clear. The idea is that a signal, not a prompt, starts to work. In other words, in non-AI native companies, AI isn't doing something unless someone explicitly tells them to do it. In the more AI native companies, the work starts without anyone telling it to do it because it's based on some trigger that when it happens doesn't require a human transfer that trigger to a prompt. The types of signals or triggers include things like a customer message, an invoice, a renewal, some sort of operational alert. At RunLayer, they find that work comes in from customer calls, custom Slack channels, builds failing, Slack mentions, and pins people drop right in the live product. In Uber, most of their agent sessions are now started by other agents around things like code review, self-healing CI, and on-call triage. And if you want to think about this outside of engineering, just try to think about which events in your business should start work on their own.
A churn signal, a renewal coming due, an invoice arriving. The question changes here from what should I ask the AI to do to which things happen that should start work automatically. Practice number four starts to get into some of what we'll talk about in the team member section. But the point of this one is that increasingly, teams are not interacting with a whole bunch of standing agents. There is one main or orchestrator agent that can figure out what's needed and can spin up or call in other sub-agents as whatever challenge it's dealing with requires. Anthropics research system is one of the clearest public examples. A lead agent plans the work and then spins up sub-agents in parallel. Each one gets its own task, its own context, and its own output format, and doesn't even know the others exist. The number scales to the job. One agent for a simple fact check, ten or more for a hard problem. This approach to agents beat a single agent by about 90% on Anthropics internal research evaluations. ORP has an orchestrator whose only job is to route work but not do the work itself. For each job, it picks which agent or agents, which models, and which slice of context the agents get.
RAMP has a coding agent that they call Inspect. That's a good example of how this is coming into the shared or team agent domain. And one of the key reasons for this again comes back to context windows. Rather than having to maintain comprehensive context across a large number of different agents, the orchestrator keeps the summaries in the key context, and each worker gets a narrow instruction and a clean slate and theoretically just what they need. Practice number five, having agents check each other's work and show proof. At this point, I think it's pretty clear that the bottleneck across pretty much all types of knowledge work has moved from producing the work to verifying it and or just making sure it doesn't suck. AI native organizations are not only viewing verification as its own important job, but are also designing specific systems for that step and that layer. They don't view the agent's job as being done when it produces whatever it was supposed to produce. So a couple of examples that have been published. Shopify has a security system that treats every finding as a claim that has to be proven. If it can't write a test that actually exploits the bug, the finding is rejected or downgraded.
And the model that checks the finding is different from the model that found it. At run layer, an agent fixes any problems and opens a pull request with before and after screenshots or a recorded walkthrough. A second agent then reviews that adversarially. And then even after it ships, a QA agent tries to break it in production. So to sum up, we've got one, check the work. And two, use a different agent that produced the work to be the one who checks the work. A new study from KPMG in the University of Texas at Austin found that when people work with AI, similar skills don't guarantee similar outcomes. Researchers studied more than 500 early career professionals and found that the best performers consistently amplified the value of AI by guiding, evaluating, and refining its outputs. These top performers, called AI amplifiers, weren't defined by what they knew alone, but by how they worked with AI. Learn more about what separates AI amplifiers from everyone else at kpmg slash us slash AI amplifiers The best teams don have a single star carrying everyone else They know their own strengths and each other weaknesses and play to both
That's the team Robots and Pencils has built on purpose. Nobody there is grinding through busy work to pad a headcount number. People come for the hard problems and they stay because everyone around them is leveling up at the same time. In a market full of companies that are just trying to hire fast, that's worth a look. Check out robotsandpencils.com slash careers. This episode is brought to you by Cdata. Token spend is climbing, security is holding agents back, and companies rolling out AI initiatives might not know how it's truly being used. The root cause, AI is cut off from the systems and context your business runs on. That's why Cdata built Connect AI Gateway, one control point between your AI and your systems. Connect AI Gateway is not just another static model router. Prompts get intelligently routed to the right model, with exactly the tools and data it needs governed down to the record. The result? Accurate answers at a fraction of the token cost with a context engine that learns your business with every interaction. Built on the connectivity layer powering Palantir, Google, Salesforce, and hundreds more. Give it a try and start your free trial at cdata.ai.
That's C as in connect, data.ai. Every AI coding tool on the market does the same thing first. It starts writing code. Blitzy does the opposite. Before writing a single line, Blitzy spends days reverse engineering your entire code base. Thousands of agents ingest millions of lines, mapping every dependency, every undocumented constraint, every architectural decision made over the last decade. The result is a dynamic knowledge graph that understands your software the way a principal engineer would after 30 years in the building. Other tools guess at context with grep searches and markdown files. Blitzy never guesses. It builds true understanding first, then delivers over 80% of entire software epics autonomously. Validated, end-to-end tested, production-grade pull requests. That's why Fortune 500 engineering teams trust Blitzy with the code bases that matter most. See for yourself at Blitzy.com. That's B-L-I-T-Z-Y dot com. Practice number six, scaling human review to the level of risk involved and keeping someone, a person, accountable.
The point is that AI native companies neither review everything nor do they review nothing. They try to decide ahead of time what types of things are going to need a human, and they always know which human owns the result. Whenever there's an agent-to-agent handoff at Uber, they retain a chain of responsibility that traces back to a specific person. Every time one agent calls another, the call carries a record of the whole chain, so even a long agent-to-agent handoff traces back to that responsible person. At Stripe, while agents are writing the code, it's humans who merge it. Every merge has a human reviewer. At RunLayer, they do it a little bit differently. Small, low-risk changes merge on their own, and humans step in when asked. Ramp is actually selling something similar for finance, offering finance agents that approve low-risk expenses on their own or recommend a decision with their reasoning. Each customer gets to decide how much those agents can do alone and where they have to stop. Interestingly, Snap says they put more than half of their agent investment into guardrails rather than the agents themselves. The seventh practice is about the consistency of the system across the organization.
Most companies, even who are working very hard to use AI well, still tend to have wild variations in how different people use AI. Basically, everyone is using AI in their own way, or maybe at least different departments are using AI in their own way. The more AI native the organization, the more there tends to be a single system that's dynamic enough to adapt and allow everyone to improve it while still working within the same system. And there are a couple of hallmarks of this. Ramp and Uber, for example, both have shared skills libraries that make workflows reusable across the whole organization. Ramp has 350 shared workflows in one library with a tool that recommends skills based on your role. Uber's library, meanwhile, has 3,600 skills that runs over 30,000 times a day. Another way to build this sort of shared system comes from Shopify. Its coding agent only works in public Slack channels, never through DMs, which means that every session is a transcript that anyone can search and learn from. These AI-native companies are also figuring out novel, interesting ways to help the systems improve themselves. For example, at warp, scoring agents grade finished runs,
and another agent proposes improvements to the system as pull requests the team reviews. Basically, they're using some of their agentic power to examine the agentic system in an ongoing way. One caveat or caution within this is to make sure to measure the right thing. Shopify, for example, does not count lines of AI code or pull requests. It focuses instead on things like how often changes get reverted. So these are seven practices that tend to be hallmarks of AI native organizations. And again, as I said at the beginning, the one that isn't in here, at least not in the way that we were talking about it a few months ago, was agent teammates. Now, I don't want to be overly pedantic or semantic about this, but I do think that exploring why the way we work with agents has evolved a little bit differently than many of us thought is useful, even if it risks either A, overstating the case, or B, trying to ascribe a single reality when lots of different individuals and lots of different companies are going to have different experiences. I do think it's fair to say that many folks thought that agents as teammates would be
the defining feature of AI native companies, that every person would have their digital representation, or that there would be specific agents that have specific roles that are maintained and persistent, and that you anthropomorphize through names and things like that. Now, what this did get right is that it helped us shift our thinking from AI as a chat window that we could ask for help for work that we do to something that could go out and do work on its own AI as teammates was a useful mental model to help people make the transition from assisted AI to agentic AI But there are a few different reasons why it didn't exactly play out that way. One is that a teammate model tends to assume some fixed roster. When we're just using the analogy of agent as digital version of the people that work for you, that means a set number of agents, each with a role they own, and an identity that lasts. Instead, what we've seen is a move towards dynamically sized fleets of agents that can scale up or scale down based on the work at hand. So what that means is, instead of a fixed roster, you have capacity that follows the job.
Instead of a persistent identity, you get fresh context for every task. Instead of a single enduring role, models and workers can change. And instead of personal memory, the most important thing is actually company-wide knowledge, company context. In fact, interestingly, Anthropic's guidance on multi-agent systems has found that splitting agents by job function, like planner, coder, tester, reviewer, tends to backfire. Each handoff becomes a game of telephone. In one experiment, agents split by role, spent more effort coordinating with each other than actually doing the work. I think a little bit of this is a version of the bitter lesson. It's very natural for humans to assume that the right way to organize agents is to approximate the things that we've learned about managing people, when in fact, what's better is to just let them figure out how to organize themselves, because those structures might look very different than what works best for us. I think that these games of telephone and effort coordinating are the chief example of that. Another example of this shift came from Every, who did a bunch of experimentation towards the beginning of the year with each person having their own proxy agent, and then realized
that didn't make sense at all. It made much more sense to have a smaller number of agents that lived at the intersection and could expand themselves through sub-agents as was required. And every week that goes on, you see more examples of this shift popping up as well. I've certainly experienced it. At the beginning of the year when I was messing around with OpenClaw, I had a research agent, actually multiple different research agents based on different projects. I also had a coordinator agent. I also had agents who were responsible for keeping track of different projects, and then a chief of staff agent that sat on top of them. Now my behavior is pretty much not like that at all. Within CloudCode and Codex, I have projects that are basically organized around their shared context in the form of repositories, and then agents get spun up to do specific things with them, which in a session of Codex or Cloud Code is actually more akin to spinning up a new orchestration agent, given how many sub-agents they might spin up to do whatever work you've given them. There's not a persistent named anthropomorphized agent. There's a persistent bundle of context that I can drop any set of agents into at any given time. Although it's not perfect, I think in some ways, a better analogy than teammates is something
like on-demand consulting firms. Think about how an engagement works. You bring a goal. That's a prompt or a signal. The engagement lead or coordinator staffs it. That's an orchestrator. You never manage the staff, and you may never even meet them. The deliverable comes back with evidence. You sign off and you own the result internally. And when the engagement ends, the agents and people who did the work are gone, but the work and the records of the work stay. And theoretically, if you've done that well, the firm's methodology can get better every time. So not totally perfect, but I think directionally closer if we are plumbing for analogies that help people wrap their heads around how to use these new systems. Interestingly, a study published in the Harvard Business Review in May found some actual downsides to treating agents as teammates as well. The study looked at researchers working with BCG. Managers reviewed the same documents with errors planted in them. The only difference was the label on who wrote them. an AI tool, a human colleague named Alex, or an AI team member named Alex3. When the work came from an AI teammate, Alex3, managers checked it less carefully.
And the clearest effect was that companies that said they already treat AI as employees, where scrutiny dropped about 16%. One manager describing an agent named Kevin pointed out that a problem was when Kevin, aka the AI team member, makes a mistake, Kevin literally can't be accountable. It's always important to not overstate this. It was one study. It happened very early on in the adoption of agents. And to be clear, if you are finding success in your company using the teammate analogy, far be it for me to suggest that you shouldn't be doing so. One last note, you might be wondering if it is true that the agent teammate paradigm, the named agent paradigm, isn't really how things are playing out. How does that interact with the personal agent paradigm where Meta and ChatGPT are having you name your muse or dot? doesn't that somehow fit in contrast to that, especially because those products are doing well? I don't necessarily think it does, for the simple reason that comes back to the idea that focusing your interactions on the orchestrator is where you need to focus. Effectively, these personal agents are like the er-orchestrators.
They have, theoretically, all of the context about everything in our lives, and so are going to be in the best position to orchestrate whatever agents and sub-agents we need to do anything, while leaving us to still only interact with one point of contact. Now, I think it's still too early to know if these two trend lines will fully merge or if they just represent different parts of the AI experience, but I don't think that they're as mutually exclusive as they might seem at first. Anyways, guys, based on a close reading of lots and lots of recent shares, that is seven things AI native companies do. And that is going to do it for today's AI Daily Brief. I appreciate you listening or watching as always, and until next time, peace! Thank you.
番組の概要欄(原文)
<p>What do AI-native companies actually do differently? Drawing on examples from Stripe, Shopify, Uber, Ramp, and others, NLW breaks down seven practices that turn agents into useful systems—from shared company context and automatically triggered work to verification and human accountability. Plus, why the “AI teammate” model may be giving way to something more effective: flexible groups of agents organized around the work, rather than a fixed roster of digital coworkers.</p><p><strong>Check out How We Got Here Ep. 3 - How Gambling on Everything From Our Phones Became Normal </strong></p><p><a href="https://open.spotify.com/episode/4OHJ8GCtbEoAcSHsDT2Byr?si=B7qP-oAGS6SNRoPEGXGC7A">https://open.spotify.com/episode/4OHJ8GCtbEoAcSHsDT2Byr?si=B7qP-oAGS6SNRoPEGXGC7A</a></p><p><a href="https://podcasts.apple.com/us/podcast/how-gambling-on-everything-from-our-phones-became-normal/id6822359990?i=1000800740286">https://podcasts.apple.com/us/podcast/how-gambling-on-everything-from-our-phones-became-normal/id6822359990?i=1000800740286</a></p><p><strong>Learn More about the AI Champions Program: </strong><a href="https://www.besuper.ai/champions">https://www.besuper.ai/champions</a></p><p><strong>Brought to you by:</strong></p><p><strong>KPMG</strong> – New KPMG and UT Austin research shows what separates “AI Amplifiers” from everyone else. Learn more at <a href="https://kpmg.com/us/en/articles/2026/ai-redefining-career-success-empower-your-talent-thrive.html?utm_source=the_ai_daily_brief&utm_medium=native&utm_content=podcast&utm_campaign=701dV00000aMKrPQAW&cid=701dV00000aMKrPQAW">kpmg.com/us/AIamplifiers</a></p><p><strong>Granola</strong> - The AI notepad for people in back-to-back meetings. Try it free <a href="http://granola.ai/brief">granola.ai/brief</a> </p><p><strong>CData - </strong>The gateway that makes AI more accurate, for less - <a href="https://www.cdata.com/ai/">https://cdata.ai/</a></p><p><strong>Harbor - </strong>Invest in the AI ecosystem. <a href="https://www.harborcapital.com/aidaily">https://www.harborcapital.com/aidaily</a></p><p><strong>Section</strong> - Section turns AI investment into workforce transformation and ROI - <a href="https://www.sectionai.com/">https://www.sectionai.com/</a></p><p><strong>Blitzy - </strong>Want to accelerate enterprise software development velocity by 5x? <a href="https://blitzy.com/">https://blitzy.com/</a></p><p><strong>Robots & Pencils</strong> - Cloud-native AI solutions that power results <a href="https://robotsandpencils.com/">https://robotsandpencils.com/</a></p><p>The AI Daily Brief helps you understand the most important news and discussions in AI. </p><p><strong>Newsletter: </strong><a href="https://aidailybrief.beehiiv.com/">https://aidailybrief.beehiiv.com/</a></p><p><strong>Interested in sponsoring the show? </strong>sponsors@aidailybrief.ai</p><p><br></p><p> </p>
出典・この記事について
- 番組
- The AI Daily Brief: Artificial Intelligence News and Analysis(Nathaniel Whittemore)
- 元の回
- 7 Things AI-Native Companies Do Differently
- 配信日
- 要約作成日
- 公式サイト
- aidailybrief.ai
この要約・解説記事は、元の音声を文字起こしした内容をもとに AI(Claude)が日本語で作成したものです。 固有名詞や数値に誤りを含む場合があるため、正確な内容は元の音声でご確認ください。制作方法について
関連エピソード

ワシントンがAIの主導権を握る:ジェンセン・ファン退任の余波
The AI Daily Brief: Artificial Intelligence News and Analysis

【ライブ】パッチは間に合うか?AIが脆弱性を見つける速度が人間の対応を超えつつある
The Neuron: AI Explained

エンタープライズAIはなぜROIを出せないのか|DevRev CTO Ahmed Bashir
Eye On A.I.

暴走するAIボット群が示す「制御喪失」の現実(マックス・テグマーク氏)
Future of Life Institute Podcast

エージェント検索はページを探すのではなく、答えを組み立てる
The Stack Overflow Podcast

私たちのパッケージはすべて奪われた:AIエージェント時代のサプライチェーン攻撃とSocketの対策(Changelog Interviews #690)
Changelog Master Feed