Snippset Feed

AI agents change more than how quickly a task can be completed. They change how work is divided between people and AI. Instead of directing every individual step, you can delegate a defined piece of work—and focus your attention on the decisions that require human judgment.

From prompting to delegating

With a conventional AI assistant, you ask a question, receive an answer, review it, and decide what to ask next. You manage the individual steps.

An AI agent can work differently. You define an outcome and the boundaries within which it may operate. The agent can then determine an approach, perform several actions, and adapt subsequent steps based on what it discovers.

A typical workflow becomes:

Define the work → Agent executes → Human reviews and decides

What should you delegate?

Not every part of work is equally suitable for delegation:

• Scoping: Keep responsibility for defining the actual problem.
• Research: Agents can gather, compare, and organize evidence.
• Analysis: Agents can identify patterns and inconsistencies; humans determine their significance.
• Delivery: Agents can prepare drafts, while humans review and approve them.

A useful principle is to delegate the legwork while retaining the judgment.

Make the handover explicit

A good handover defines five elements:

1. Goal – What outcome should the work support?
2. Evidence – Which sources, data, and tools may be used?
3. Constraints – What must or must not happen?
4. Checkpoints – When should the agent stop for human review?
5. Output criteria – What should the result contain and look like?

Start with low-risk tasks and evaluate the results before expanding the agent's responsibilities. Above all, verify important evidence and conclusions before they influence decisions or reach a client.

AI agents can carry work forward independently—but accountability remains human.

AI governance isn't about slowing innovation—it's about enabling organizations to use AI safely and responsibly. This course explains how to build a practical governance framework that balances business value with risk, using real-world examples rather than theory alone.

Key takeaways:

• Understand why AI requires different governance than traditional IT systems.
• Build risk-based governance by classifying AI use cases into buckets (lightweight, standard, enhanced, critical).
• Define clear roles, ownership, committees, and decision rights for AI initiatives.
• Apply governance throughout the entire AI lifecycle, from development to retirement.
• Manage third-party AI vendors, document decisions, monitor risks, and measure governance effectiveness.
• Continuously improve governance by learning from established frameworks such as the EU AI Act, ISO/IEC 42001, OECD AI Principles, and the NIST AI Risk Management Framework.

The course is especially valuable for architects, IT leaders, governance professionals, and anyone responsible for introducing AI into an organization while maintaining compliance, transparency, and business agility.

Course: Designing Responsible AI Governance Frameworks (Pluralsight)

Creating an AI agent is only the first step. The real challenge is making sure it gives reliable answers in different situations. A structured process of improving and testing helps you build agents you can trust.

Instead of guessing whether your instructions are good enough, use tools that guide you while you build and verify the results afterward. This reduces trial and error and makes improvements easier.

A practical workflow looks like this:

1. Build: Write clear instructions and provide the knowledge your agent needs.
2. Improve: Review suggestions that highlight unclear instructions, missing information, or opportunities to make your agent more effective.
3. Test: Run realistic scenarios to see how your agent responds to different questions and situations.
4. Repeat: Refine your instructions based on the results and test again until the responses are consistent.

This continuous cycle helps you discover issues early, improve answer quality, and gain confidence before others use your agent.

Whether you are creating your very first AI agent or refining an existing one, combining guided improvements with systematic testing leads to better and more reliable results. Small, regular changes often make a much bigger difference than rewriting everything at once.

The goal is simple: don't just build an AI agent—build one that consistently performs the way you expect.

A read-only editor is useful when users should view a template without changing its main structure. But sometimes, selected areas still need to remain editable—for example, a table where users enter prices, dates, or project details.

TinyMCE can support this approach by combining HTML’s contenteditable attribute with predefined CSS classes.

The main idea

Keep the editor content protected, but assign a special class such as editablecontent to tables that users are allowed to modify. Template authors can select this class directly from the TinyMCE table properties dialog.

The table_class_list option defines which table classes appear in that dialog:

tinymce.init({
  selector: "textarea",
  plugins: "table",
  menubar: "table",
  toolbar: "table",

  table_class_list: [
    { title: "None", value: "" },
    { title: "Editable Table", value: "editablecontent" },
    { title: "Other Table Type", value: "other_table_class" }
  ]
});

When the template author chooses Editable Table, TinyMCE adds the following class to the table:

<table class="editablecontent">

Your application can then detect this class and make only that table editable.

Why use predefined classes?

• Template authors do not need to edit HTML.
• Editable areas are clearly controlled.
• The same class can be reused across many templates.
• Other table options, such as border styles, can be added to the same list.

For larger configurations, TinyMCE also supports nested class menus. This helps organize editable states, visual styles, and other table types into separate groups.

Moving from an AI prototype to a production-ready application requires much more than calling an LLM. This course provides a practical introduction to Microsoft Agent Framework (MAF), Microsoft's open-source framework for building structured, scalable, and maintainable AI agents. Using a hands-on dentist appointment booking system, it demonstrates how to design agents that interact with external tools, maintain conversation history, remember user preferences, and execute complex business processes.

The course covers:

• Agent fundamentals: understanding the agentic loop, prompt design, tools, sessions, memory, context providers, and middleware.
• Building real applications: creating agents that search, retrieve, update, and persist data while supporting multi-turn conversations.
• Workflows and orchestration: when to use agents versus workflows, multi-agent architectures, handoff patterns, human-in-the-loop approvals, checkpointing, and durable execution.
• Production practices: choosing appropriate LLMs, monitoring with Application Insights, testing with DevUI, managing configuration, and deploying agents as Azure AI Foundry Hosted Agents.

A recurring theme throughout the course is that an AI agent is essentially a language model equipped with tools to accomplish a goal. Rather than focusing on a single demo, the instructor teaches reusable design patterns that can be applied to customer support, booking systems, research assistants, and many other enterprise AI solutions. By the end, you'll understand not only how to build intelligent agents, but also how to make them reliable, observable, secure, and ready for production.

Course: Building Agents with Microsoft Agent Framework – Pluralsight

Even if an AI understands your request, it may not present the answer in the format you expect. One of the simplest ways to improve the result is to clearly describe the expected output. Instead of letting the AI decide how to present the information, tell it exactly what you want.

Expected output instructions define the structure, length, and presentation of the response. They help make answers more consistent and reduce the amount of editing afterward.

Useful instructions include:

• Give me five bullet points.
• Keep the answer under 100 words.
• Return the information as a table.
• Provide only a checklist.
• Write a step-by-step guide.
• Do not include an introduction.
• End with a short summary.
• Give only the final answer.
• List the advantages and disadvantages.

You can also combine multiple instructions into one prompt.

Example Prompt

Compare three ways to save money on groceries. Present the result as a table with the columns Method, Benefits, Drawbacks, and Best For. Keep each table cell under 20 words. After the table, add three practical tips for getting started. Do not include a general introduction.

By describing the expected output, you give the AI a clear target. This makes the response easier to read, easier to reuse, and much closer to what you need without additional editing.

With several Microsoft Copilot experiences available, it can be difficult to know which one to use. Each is designed for a specific purpose, so choosing the right one helps you work faster, find better information, and get more accurate results.

A simple way to choose is to think about your goal:

• Need to find something? Use Copilot Search.
• Need a quick answer or help writing? Use Copilot Chat.
• Want AI to help complete your current task? Use Copilot Cowork.
• Need AI to manage a larger task in its own workspace? Use Copilot Scout.
• Researching a topic across many sources? Use Copilot Researcher.
• Working with numbers or business data? Use Copilot Analyst.

Understanding these roles makes it easier to select the right Copilot for the job. Instead of relying on a single AI experience for everything, you can choose the one that best matches your task and get more focused, efficient, and reliable results.

You are ready to publish. The article reads well, the presentation is clear, and your message is complete. But instead of finishing, you keep changing small details. Sound familiar?

This is a common productivity trap: endless polishing. After a certain point, extra edits often make very little difference. They take time and energy without noticeably improving the final result.

A better approach is to know when to stop refining and start sharing your work.

How AI can help

If you use an AI writing assistant such as Microsoft Copilot, let it perform the final review instead of repeatedly reading the document yourself. Ask it to:

• Check for clarity
• Suggest small improvements
• Find grammar or spelling issues
• Highlight sentences that could be easier to understand

This gives you a fresh perspective while helping you avoid unnecessary editing.

Remember the goal

The goal is not a perfect document—it is a document that communicates its message clearly. Once the important ideas are easy to understand and obvious mistakes are fixed, additional changes often provide only small benefits.

Learning to recognize when your work is "good enough" helps you save time, reduce mental fatigue, and spend more energy on creating your next great piece of work instead of endlessly refining the last one.

Have you ever received an AI answer that wasn't quite what you wanted? Often, the problem is not the AI—it is that the prompt did not include enough information. Adding a little more context helps the AI understand your request and produce a more useful response.

Before asking your question, provide the key details the AI needs:

• Goal – What do you want to achieve?
• Audience – Who is the content for?
• Format – Article, email, checklist, table, or another format.
• Tone – Friendly, professional, formal, or simple.
• Source material – Include any notes, text, or information the AI should use.

The more relevant information you provide, the fewer assumptions the AI has to make. This usually leads to more accurate answers and reduces the need for follow-up prompts.

Example Prompt

Write a short article about healthy breakfasts for busy parents. Use simple English and a friendly tone. Organize the article with an introduction, three practical tips, and a short conclusion. Keep it between 200 and 250 words. Use only the information provided below.

This prompt clearly defines the goal, audience, tone, format, length, and source material. Because the expectations are clear from the start, the AI is much more likely to produce the desired result on the first try.