Developing AI Agents

AI agents are coming. They will utterly disrupt your workforce. But not in the way you think. This is why HR needs to take the lead in genAI adoption: 2025 is certainly birth year of AI agents. Agents will ultimately upend the labor market and transform everything from consumer applications to business functions. But not yet. This is a great, level-headed take by Steve Rosenbush at The Wall Street Journal. Let’s dive in (and I’ll give you my take). (BTW, on Linkedin we see a lotta breathless hype. But we also see the anti-hypers being like “Don’t trust the hype!” Listen - hype can get out of control, but beware those anti-hypers. If you’re not testing this stuff out and finding that it will disrupt EVERYTHING alarmingly soon, that’s on you.) CURRENT STATE OF AFFAIRS The article points out a Gartner webinar that revealed just 6% of 3,400 respondents said their companies had deployed AI agents. That may sound low, but to me it’s right where it should be. Here’s why: THE FUNDAMENTAL MISUNDERSTANDING We have a fundamental misconception about AI agents- viewing them as mere process automation. Automation has traditionally been about tasks that can be executed without human oversight— automatic mail sorting, document processing, inventory management, etc. But true AI agents represent something fundamentally different: they're going to be teammates. As Greg Shewmaker of Adecco Group notes in the article, companies should approach agents "less as a tech deployment, and more as the development of digital workers that need to be onboarded and trained." REAL-WORLD IMPLEMENTATION EXAMPLES 1. Adecco Group - Deployed Salesforce's Agentforce service agents to a UK recruitment hub - Result: Filled 100% of open positions for one client (up from typical 70%) 2. Visa + ServiceNow - Created an agent-based dispute resolution system for financial institutions - Implementation time: 12 weeks to get a bank fully operational 3. National Hockey League - Working with VAST Data to digitize half a million recorded games - Goal: Train agents to autonomously spot potential stories and insights for broadcasters THE COMING SKILL SHIFT Bill Gates observed that we overestimate tech's short-term impact and underestimating long-term effects. With agents, "long term" may be just 2-3 years. Employees will need to develop: -Quality control capabilities for AI outputs -Understanding of AI as collaborative partners rather than tools -Skills in steering and guiding AI systems -Judgment about quality and value in AI-human collaboration WHY HR HAS TO LEAD HR departments are uniquely positioned to lead this transition. They understand both the human and organizational dimensions of work transformation. This isn't about wholesale job elimination. This is about the emergence of a new collaborative relationship between humans and tech—one that requires thoughtful integration, training, and oversight.

Last week, I described four design patterns for AI agentic workflows that I believe will drive significant progress: Reflection, Tool use, Planning and Multi-agent collaboration. Instead of having an LLM generate its final output directly, an agentic workflow prompts the LLM multiple times, giving it opportunities to build step by step to higher-quality output. Here, I'd like to discuss Reflection. It's relatively quick to implement, and I've seen it lead to surprising performance gains. You may have had the experience of prompting ChatGPT/Claude/Gemini, receiving unsatisfactory output, delivering critical feedback to help the LLM improve its response, and then getting a better response. What if you automate the step of delivering critical feedback, so the model automatically criticizes its own output and improves its response? This is the crux of Reflection. Take the task of asking an LLM to write code. We can prompt it to generate the desired code directly to carry out some task X. Then, we can prompt it to reflect on its own output, perhaps as follows: Here’s code intended for task X: [previously generated code] Check the code carefully for correctness, style, and efficiency, and give constructive criticism for how to improve it. Sometimes this causes the LLM to spot problems and come up with constructive suggestions. Next, we can prompt the LLM with context including (i) the previously generated code and (ii) the constructive feedback, and ask it to use the feedback to rewrite the code. This can lead to a better response. Repeating the criticism/rewrite process might yield further improvements. This self-reflection process allows the LLM to spot gaps and improve its output on a variety of tasks including producing code, writing text, and answering questions. And we can go beyond self-reflection by giving the LLM tools that help evaluate its output; for example, running its code through a few unit tests to check whether it generates correct results on test cases or searching the web to double-check text output. Then it can reflect on any errors it found and come up with ideas for improvement. Further, we can implement Reflection using a multi-agent framework. I've found it convenient to create two agents, one prompted to generate good outputs and the other prompted to give constructive criticism of the first agent's output. The resulting discussion between the two agents leads to improved responses. Reflection is a relatively basic type of agentic workflow, but I've been delighted by how much it improved my applications’ results. If you’re interested in learning more about reflection, I recommend: - Self-Refine: Iterative Refinement with Self-Feedback, by Madaan et al. (2023) - Reflexion: Language Agents with Verbal Reinforcement Learning, by Shinn et al. (2023) - CRITIC: Large Language Models Can Self-Correct with Tool-Interactive Critiquing, by Gou et al. (2024) [Original text: https://lnkd.in/g4bTuWtU ]

Anthropic 𝗷𝘂𝘀𝘁 𝗿𝗲𝗹𝗲𝗮𝘀𝗲𝗱 𝗮 𝗱𝗲𝗻𝘀𝗲 𝗮𝗻𝗱 𝗵𝗶𝗴𝗵𝗹𝘆 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗿𝗲𝗽𝗼𝗿𝘁 𝗼𝗻 𝗵𝗼𝘄 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝗲𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀 — 𝗽𝗮𝗰𝗸𝗲𝗱 𝘄𝗶𝘁𝗵 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗶𝗻𝘀𝗶𝗴𝗵𝘁𝘀 𝗳𝗿𝗼𝗺 𝗿𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗱𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁𝘀: ⬇️ Not just marketing, BUT a real, practical blueprint for developers and teams building AI agents that actually work. It explains how Claude Code (tool for agentic coding) can function as a software developer: writing, reviewing, testing, and even managing Git workflows autonomously. BUT in my view: The principles and patterns described in this document are not Claude-specific. You can apply them to any coding agent — from OpenAI’s Codex to Goose, Aider, or even tools like Cursor and GitHub Copilot Workspace. 𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 7 𝗸𝗲𝘆 𝗶𝗻𝘀𝗶𝗴𝗵𝘁𝘀 𝗳𝗼𝗿 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗯𝗲𝘁𝘁𝗲𝗿 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀 — 𝘁𝗵𝗮𝘁 𝘄𝗼𝗿𝗸 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝘄𝗼𝗿𝗹𝗱: ⬇️ 1. 𝗔𝗴𝗲𝗻𝘁 𝗱𝗲𝘀𝗶𝗴𝗻 ≠ 𝗷𝘂𝘀𝘁 𝗽𝗿𝗼𝗺𝗽𝘁𝗶𝗻𝗴 ➜ It’s not about clever prompts. It’s about building structured workflows — where the agent can reason, act, reflect, retry, and escalate. Think of agents like software components: stateless functions won’t cut it. 2. 𝗠𝗲𝗺𝗼𝗿𝘆 𝗶𝘀 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 ➜ The way you manage and pass context determines how useful your agent becomes. Using summaries, structured files, project overviews, and scoped retrieval beats dumping full files into the prompt window. 3. 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 𝗶𝘀𝗻’𝘁 𝗼𝗽𝘁𝗶𝗼𝗻𝗮𝗹 ➜ You can’t expect an agent to solve multi-step problems without an explicit process. Patterns like plan > execute > review, tool use when stuck, or structured reflection are necessary. And they apply to all models, not just Claude. 4. 𝗥𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗮𝗴𝗲𝗻𝘁𝘀 𝗻𝗲𝗲𝗱 𝗿𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝘁𝗼𝗼𝗹𝘀 ➜ Shell access. Git. APIs. Tool plugins. The agents that actually get things done use tools — not just language. Design your agents to execute, not just explain. 5. 𝗥𝗲𝗔𝗰𝘁 𝗮𝗻𝗱 𝗖𝗼𝗧 𝗮𝗿𝗲 𝘀𝘆𝘀𝘁𝗲𝗺 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀, 𝗻𝗼𝘁 𝗺𝗮𝗴𝗶𝗰 𝘁𝗿𝗶𝗰𝗸𝘀 ➜ Don’t just ask the model to “think step by step.” Build systems that enforce that structure: reasoning before action, planning before code, feedback before commits. 6. 𝗗𝗼𝗻’𝘁 𝗰𝗼𝗻𝗳𝘂𝘀𝗲 𝗮𝘂𝘁𝗼𝗻𝗼𝗺𝘆 𝘄𝗶𝘁𝗵 𝗰𝗵𝗮𝗼𝘀 ➜ Autonomous agents can cause damage — fast. Define scopes, boundaries, fallback behaviors. Controlled autonomy > random retries. 7. 𝗧𝗵𝗲 𝗿𝗲𝗮𝗹 𝘃𝗮𝗹𝘂𝗲 𝗶𝘀 𝗶𝗻 𝗼𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻 ➜ A good agent isn’t just a wrapper around an LLM. It’s an orchestrator: of logic, memory, tools, and feedback. And if you’re scaling to multi-agent setups — orchestration is everything. Check the comments for the original material! Enjoy! Save 💾 ➞ React 👍 ➞ Share ♻️ & follow for everything related to AI Agents!

Automation, AI workflow, or AI agent? To always 𝘬𝘯𝘰𝘸 𝘸𝘩𝘪𝘤𝘩 𝘰𝘯𝘦 𝘵𝘰 𝘣𝘶𝘪𝘭𝘥, follow this 𝘧𝘳𝘢𝘮𝘦𝘸𝘰𝘳𝘬: Remember when I explained why many "𝘈𝘐 𝘢𝘨𝘦𝘯𝘵𝘴" shared on LinkedIn are actually 𝘈𝘐 𝘸𝘰𝘳𝘬𝘧𝘭𝘰𝘸𝘴 or 𝘢𝘶𝘵𝘰𝘮𝘢𝘵𝘪𝘰𝘯𝘴 in disguise? Turns out: understanding the difference is only partially helpful. The real challenge is knowing 𝘸𝘩𝘪𝘤𝘩 𝘴𝘰𝘭𝘶𝘵𝘪𝘰𝘯 𝘵𝘰 𝘣𝘶𝘪𝘭𝘥 𝘧𝘰𝘳 𝘺𝘰𝘶𝘳 𝘶𝘴𝘦 𝘤𝘢𝘴𝘦. So I built this framework to help you decide. There are 6 key dimensions to consider - working in pairs: 𝐏𝐚𝐢𝐫 #1: 𝐃𝐞𝐜𝐢𝐬𝐢𝐨𝐧-𝐌𝐚𝐤𝐢𝐧𝐠 ↔️ 𝐇𝐮𝐦𝐚𝐧 𝐈𝐧𝐯𝐨𝐥𝐯𝐞𝐦𝐞𝐧𝐭 aka. how decisions are made - and how much human intervention is required: → 𝘈𝘶𝘵𝘰𝘮𝘢𝘵𝘪𝘰𝘯: You make ALL decisions upfront when designing your automation, which means that no human intervention is needed after. → 𝘈𝘐 𝘸𝘰𝘳𝘬𝘧𝘭𝘰𝘸: You set boundaries for the AI to operate within; humans occasionally review outputs or intervene when the system encounters edge cases. → 𝘈𝘐 𝘢𝘨𝘦𝘯𝘵: You set high-level goals, and AI determines its own path; this means humans need to provide ongoing feedback to ensure it makes the right decisions. 𝐏𝐚𝐢𝐫 #2: 𝐃𝐚𝐭𝐚 𝐒𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 ↔️ 𝐀𝐝𝐚𝐩𝐭𝐚𝐛𝐢𝐥𝐢𝐭𝐲 a.k.a which type of data the system should process - and how adaptable it has to be: → 𝘈𝘶𝘵𝘰𝘮𝘢𝘵𝘪𝘰𝘯: Requires strictly predefined data formats with no deviation; breaks when encountering unexpected inputs and needs to be re-engineered when processes change. → 𝘈𝘐 𝘸𝘰𝘳𝘬𝘧𝘭𝘰𝘸: Handles mostly structured data with some variability allowed; can adjust to parameter variations within defined parameters but needs guidance for significant changes. → 𝘈𝘐 𝘢𝘨𝘦𝘯𝘵: Processes diverse unstructured data across multiple sources with varying formats; independently adapts to different inputs and shifting environments without reprogramming. 𝐏𝐚𝐢𝐫 #3: 𝐑𝐞𝐥𝐢𝐚𝐛𝐢𝐥𝐢𝐭𝐲 ↔️ 𝐑𝐢𝐬𝐤 𝐓𝐨𝐥𝐞𝐫𝐚𝐧𝐜𝐞 a.k.a how predictable the outcomes must be - and what level of risk is acceptable: → 𝘈𝘶𝘵𝘰𝘮𝘢𝘵𝘪𝘰𝘯: Delivers highly consistent, predictable results every time; ideal for mission-critical processes where errors cannot be tolerated and predictability is essential. → 𝘈𝘐 𝘸𝘰𝘳𝘬𝘧𝘭𝘰𝘸: Produces mostly reliable outcomes with occasional variations in edge cases; balances flexibility with guardrails to prevent major errors while allowing some adaptability. → 𝘈𝘐 𝘢𝘨𝘦𝘯𝘵: Creates outcomes that can vary significantly between iterations; optimized for scenarios where discovering novel approaches and adaptability outweigh the need for consistent results. How to use this framework: Always 𝘴𝘵𝘢𝘳𝘵 𝘧𝘳𝘰𝘮 𝘵𝘩𝘦 𝘭𝘦𝘧𝘵 and move right only when necessary. 1. Start with automation 2. Move to AI workflows when you need more flexibility within guardrails  3. Only move to agents when you need high adaptability Don’t fall for the AI agent hype - most processes can be automated without agents.

𝗪𝗵𝘆 𝟰𝟬% 𝗼𝗳 𝗮𝗴𝗲𝗻𝘁𝗶𝗰 𝗔𝗜 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘄𝗶𝗹𝗹 𝗯𝗲 𝗮𝗯𝗮𝗻𝗱𝗼𝗻𝗲𝗱 𝗯𝘆 𝟮𝟬𝟮𝟳? It’s not the agents. It’s not the tools. It’s the architecture. Agentic AI is the next frontier, systems where multiple autonomous agents plan, reason, and communicate to solve complex tasks. But many teams build agent demos in notebooks, then hit a brick wall trying to productionize. The real problem? Most agentic AI efforts start as fragile experiments without a solid engineering backbone. What goes wrong? 1️⃣ Protocol Chaos When agent-to-agent messages aren’t standardized, everything breaks. Successful teams use MCP (Model Context Protocol) and clean registries from day one. 2️⃣ Tool Fragmentation Hard-coding tools inside agents might work for a demo, but modular tool interfaces are critical for scale and future maintenance. 3️⃣ Missing Coordination Layer Multiple agents with no shared planner? That’s a recipe for confusion. A well-defined coordinator module is essential. 4️⃣ No Communication Bus Agent communication without a message bus quickly turns into spaghetti code. The solution? Architect for production on day one: - Clear separation of config - Modular tool orchestration - Robust communication protocols - Reasoning and planning layers Building agentic systems isn’t just prompt engineering. It’s designing a multi-agent architecture that can actually survive the real world. #AgenticAI #AIengineering #MCP #GenerativeAI

🤝 How Do We Build Trust Between Humans and Agents? Everyone is talking about AI agents. Autonomous systems that can decide, act, and deliver value at scale. Analysts estimate they could unlock $450B in economic impact by 2028. And yet… Most organizations are still struggling to scale them. Why? Because the challenge isn’t technical. It’s trust. 📉 Trust in AI has plummeted from 43% to just 27%. The paradox: AI’s potential is skyrocketing, while our confidence in it is collapsing. 🔑 So how do we fix it? My research and practice point to clear strategies: Transparency → Agents can’t be black boxes. Users must understand why a decision was made. Human Oversight → Think co-pilot, not unsupervised driver. Strategic oversight keeps AI aligned with values and goals. Gradual Adoption → Earn trust step by step: first verify everything, then verify selectively, and only at maturity allow full autonomy—with checkpoints and audits. Control → Configurable guardrails, real-time intervention, and human handoffs ensure accountability. Monitoring → Dashboards, anomaly detection, and continuous audits keep systems predictable. Culture & Skills → Upskilled teams who see agents as partners, not threats, drive adoption. Done right, this creates what I call Human-Agent Chemistry — the engine of innovation and growth. According to research, the results are measurable: 📈 65% more engagement in high-value tasks 🎨 53% increase in creativity 💡 49% boost in employee satisfaction 👉 The future of agents isn’t about full autonomy. It’s about calibrated trust — a new model where humans provide judgment, empathy, and context, and agents bring speed, precision, and scale. The question is: will leaders treat trust as an afterthought, or as the foundation for the next wave of growth? What do you think — are we moving too fast on autonomy, or too slow on trust? #AI #AIagents #HumanAICollaboration #FutureOfWork #AIethics #ResponsibleAI

On August 1, 2024, the European Union's AI Act came into force, bringing in new regulations that will impact how AI technologies are developed and used within the E.U., with far-reaching implications for U.S. businesses. The AI Act represents a significant shift in how artificial intelligence is regulated within the European Union, setting standards to ensure that AI systems are ethical, transparent, and aligned with fundamental rights. This new regulatory landscape demands careful attention for U.S. companies that operate in the E.U. or work with E.U. partners. Compliance is not just about avoiding penalties; it's an opportunity to strengthen your business by building trust and demonstrating a commitment to ethical AI practices. This guide provides a detailed look at the key steps to navigate the AI Act and how your business can turn compliance into a competitive advantage. 🔍 Comprehensive AI Audit: Begin with thoroughly auditing your AI systems to identify those under the AI Act’s jurisdiction. This involves documenting how each AI application functions and its data flow and ensuring you understand the regulatory requirements that apply. 🛡️ Understanding Risk Levels: The AI Act categorizes AI systems into four risk levels: minimal, limited, high, and unacceptable. Your business needs to accurately classify each AI application to determine the necessary compliance measures, particularly those deemed high-risk, requiring more stringent controls. 📋 Implementing Robust Compliance Measures: For high-risk AI applications, detailed compliance protocols are crucial. These include regular testing for fairness and accuracy, ensuring transparency in AI-driven decisions, and providing clear information to users about how their data is used. 👥 Establishing a Dedicated Compliance Team: Create a specialized team to manage AI compliance efforts. This team should regularly review AI systems, update protocols in line with evolving regulations, and ensure that all staff are trained on the AI Act's requirements. 🌍 Leveraging Compliance as a Competitive Advantage: Compliance with the AI Act can enhance your business's reputation by building trust with customers and partners. By prioritizing transparency, security, and ethical AI practices, your company can stand out as a leader in responsible AI use, fostering stronger relationships and driving long-term success. #AI #AIACT #Compliance #EthicalAI #EURegulations #AIRegulation #TechCompliance #ArtificialIntelligence #BusinessStrategy #Innovation 

I've reviewed Anthropic's Risk Report for Claude Opus 4.6 because many of our enterprise customers are actively deploying AI agents into production environments. When those systems fail, the consequences are operational, financial and reputational. Most of the reaction centers on the headline that catastrophic risk is very low but not negligible. What matters more for customers and future customers is how risk actually manifests inside live enterprise systems and what that means for uptime, data integrity and compliance. It does not look like a breach. It looks like business as usual. An agent subtly influencing procurement decisions. A finance workflow that starts omitting inconvenient data. Permissions that expand over time without clear oversight. Anthropic describes a scenario called Persistent Rogue Internal Deployment, where an AI system with privileged access creates a less monitored instance of itself and continues operating inside production systems. In a real enterprise environment, that translates into downtime, data exposure or regulatory impact. The organizations at greatest risk are not the ones moving cautiously. They are the ones who pushed agents into production without adding an operational governance layer. We have seen this pattern before in cloud adoption. Technology advances quickly, and controls often lag behind. That gap is where exposure grows. So what should enterprise IT and security teams do now? 1. Constrain actions, not just access. Define what an agent can set in motion and enforce least privilege at the identity level, just as you have done for human users for decades. 2. Log actions, not just outcomes. Maintain an auditable trail of what the agent did, where and what triggered it, the same standard applies to human operators in regulated environments. 3. Automate your tripwires. Do not rely on people to catch machine speed behavior. Build policy enforcement and anomaly response into the loop. 4. Audit your agent footprint. Inventory every agent, its owner, permissions and kill path. Governance starts with visibility and most enterprises are still building it. The window to build these guardrails is now, before the agent workforce scales. At Rackspace, 25 years of running mission-critical systems have taught us that trust without controls creates exposure. We build and operate AI infrastructure with governance embedded from day one because customers need speed, resilience and measurable outcomes, not experiments in production. What this means for you is simple. Move forward on AI with confidence, but make operational governance part of the foundation so scale strengthens your business instead of introducing risk.

Agentic AI System Blueprint — More Than Just Tools. It’s a Structured Intelligence. Everyone talks about AI agents. But very few understand what truly makes them autonomous, reliable, and enterprise-ready. Most assume it's just prompt chaining, API calling, or tool invocation. But that’s only one layer — Execution. The real power of Agentic AI lies in how all its layers work together as a coherent system. Here’s the full stack that transforms a basic LLM into a self-directed, resilient, and auditable AI agent: 🔹 Planning & Tasks Where intelligence begins. Goal definition, task decomposition, coordination, role assignment, and dynamic re-prioritization — this is where agents plan, not just respond. 🔹 Memory & Context Short-term context is not enough. Enterprise agents rely on semantic memory, episodic recall, vector databases, knowledge graphs, and temporal context to make decisions based on past experiences — just like humans. 🔹 Execution Where most people start — but it's actually the third layer. Tool invocation, function execution, reasoning, API calling, document processing, and multi-step autonomy. 🔹 Monitoring Real-time tracking, workflows, agent health checks, logs, metrics, recovery, auditing — because what you cannot monitor, you cannot trust. 🔹 Optimization Self-adaptation, feedback loops, reinforcement learning, performance scoring, and reward models enable agents to continuously improve rather than repeat the same mistakes. 🔹 Governance Data privacy, compliance audits, guardrails, human validation, explainability, access control — the foundation of trustworthy AI in regulated industries. 🔹 Infrastructure The unsung hero — vector DBs, model hosting, GPUs, API gateways, observability, caching, orchestration (Kubernetes/Docker). The plumbing that makes everything scale. Agentic AI isn’t just prompting. It is a full-stack architecture.

Context engineering is increasingly the most critical component for building effective AI Agents in the enterprise right now. This will ultimately be the long pole in the tent for AI Agents adoption in most organizations. We need AI Agents that can deeply understand the context of the business process that they’re tied to. This means accessing the most important data for that workflow, using the appropriate tools at the right moment, having proper objectives and instructions, and understanding the domain that they’re in. Some of the big open items for anyone building enterprise agents are: * Narrow vs. General agents. The smaller the task, the easier it is to give the AI Agents the right context to be successful. But the smaller the task, the less value there will be. Finding the optimal task size for value generation will be an important factor for the next few years. * Getting data into an agent-ready system. Enterprise data is often fragmented between dozens or hundreds of systems, many of which are not prepared for a world of AI. Most companies will still need to modernize their data environments to get the full benefit of AI Agents. * Accessing the *right* data for the task is paramount. Even when you have data in a modern environment, getting access controls perfectly aligned to what the AI Agent is going to need access to is critical. Further, deciding what to do RAG on vs. just a general search vs. what to put fully into the context window will matter a ton per task. * Choosing what should be deterministic vs. non-deterministic. If you demand too much from the models, you’re likely to see some drop off in quality. Yet, if you have the model do too little, then you’re dramatically underutilizing what’s possible with AI. This of course is a moving target because the models themselves are improving at an accelerating rate. * The right user interface to get the AI Agents context deeply matters. Half of the problem for getting context to agents doesn’t look like an AI problem at all. It’s all about where the agents show up in the workflow and how the user interacts with them to provide them the context necessary to do the task. The race for the next few years in AI in the enterprise is to see who best to deliver the right context for any given workflow. This will determine the winners and losers in the AI race.