{"id":237332,"date":"2026-03-05T08:49:57","date_gmt":"2026-03-05T08:49:57","guid":{"rendered":"https:\/\/osmosys.co\/ca\/?p=237332"},"modified":"2026-03-05T08:50:02","modified_gmt":"2026-03-05T08:50:02","slug":"change-management-intelligent-automation","status":"publish","type":"post","link":"https:\/\/osmosys.co\/ca\/change-management-intelligent-automation\/","title":{"rendered":"Change Management for Intelligent Automation: How AI + Workflows Actually Stick"},"content":{"rendered":"<div id=\"bsf_rt_marker\"><\/div>\n<p>That\u2019s not an automation problem. It\u2019s a <a href=\"https:\/\/osmosys.co\/blog\/people-centric-modernization-change-management\/\"><strong>change management<\/strong> <\/a>problem.<\/p>\n\n\n\n<p>Intelligent automation (AI + workflows + RPA) can reduce repetitive effort and improve consistency. But it only pays off when people trust the outputs, know how exceptions are handled, and can see what\u2019s changing in their day-to-day work.<\/p>\n\n\n\n<p>Prosci\u2019s research is blunt: projects with <strong>excellent change management<\/strong> are far more likely to meet objectives than those with poor change practices.<\/p>\n\n\n\n<p>This post explains what intelligent automation is in practical terms, how it maps to Microsoft tools (especially <strong>Power Automate<\/strong>), and the adoption plan that helps it become \u201cthe way work happens\u201d across ANZ, the US, and Canada.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What \u201cintelligent automation\u201d means <\/h2>\n\n\n\n<p>Traditional automation is great at structured work:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If X happens, do Y.<\/li>\n\n\n\n<li>Move data from A to B.<\/li>\n\n\n\n<li>Route approvals.<\/li>\n\n\n\n<li>Create records, notify users, update status.<\/li>\n<\/ul>\n\n\n\n<p>Intelligent automation adds AI for the parts that are messy:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reading unstructured documents (invoices, claims, emails)<\/li>\n\n\n\n<li>Classifying requests (support tickets, case triage)<\/li>\n\n\n\n<li>Extracting fields from forms<\/li>\n\n\n\n<li>Detecting anomalies that need review<\/li>\n<\/ul>\n\n\n\n<p>In other words: <strong>automation runs the process; AI handles the ambiguity.<\/strong> The result is a workflow that can operate at scale while still escalating edge cases to humans.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Where Microsoft fits: the practical toolkit<\/h2>\n\n\n\n<p>If you\u2019re modernizing in the Microsoft ecosystem, intelligent automation is usually built from a few building blocks:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Power Automate for workflow orchestration<\/h3>\n\n\n\n<p>Power Automate is the orchestration layer: triggers, approvals, routing, notifications, system updates, and connector-based integrations. Microsoft positions it as covering digital process automation plus robotic process automation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2) AI Builder for document and prediction steps<\/h3>\n\n\n\n<p>AI Builder lets you embed \u201cintelligence\u201d into workflows (for example: extract data from documents and pass results downstream). Microsoft\u2019s docs show how document processing models are used directly inside Power Automate flows.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3) RPA (desktop flows) for legacy gaps<\/h3>\n\n\n\n<p>When an old desktop app or a non-API system blocks automation, RPA can bridge the gap. This is often where governance is most important (credentials, access, and auditability).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4) Dynamics 365 and Dataverse as the system of record<\/h3>\n\n\n\n<p>Many teams start by automating \u201caround\u201d CRM\/ERP: case routing, lead assignment, service workflows, or customer communications, then expand into cross-system processes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A real example of intelligent automation value <\/h2>\n\n\n\n<p>It\u2019s easier to get buy-in when leaders can point to outcomes.<\/p>\n\n\n\n<p>In a Microsoft customer story, CareSource reported reduced documentation time (75%) and savings tied to automation initiatives, alongside productivity improvements.<\/p>\n\n\n\n<p>Two important takeaways for your rollout:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The story is not \u201cwe implemented AI.\u201d It\u2019s \u201cwe removed time from a specific task.\u201d<\/li>\n\n\n\n<li>People adopt when they see the workflow makes their day more predictable, not more risky.<\/li>\n<\/ol>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" data-src=\"https:\/\/osmosys.co\/wp-content\/uploads\/2026\/03\/2.png\" alt=\"intelligent automation workflow diagram showing AI Builder document extraction, human review, and audit trail\" class=\"wp-image-239720 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">The change management spine: a rollout pattern that scales<\/h2>\n\n\n\n<p>Most automation programs stall for one of three reasons:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>People don\u2019t trust the outputs<\/li>\n\n\n\n<li>Exceptions aren\u2019t handled cleanly<\/li>\n\n\n\n<li>Ownership is unclear (who fixes what when it breaks)<\/li>\n<\/ul>\n\n\n\n<p>Use this <strong>change management<\/strong> pattern for intelligent automation rollouts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Pick one process with measurable friction<\/h3>\n\n\n\n<p>Choose a process that is:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>High volume<\/li>\n\n\n\n<li>Rules-based with known exceptions<\/li>\n\n\n\n<li>Painful enough that teams want it fixed<\/li>\n<\/ul>\n\n\n\n<p>Good starting candidates:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Document intake (claims, onboarding, compliance evidence)<\/li>\n\n\n\n<li>Ticket triage and routing<\/li>\n\n\n\n<li>Case updates and customer notifications<\/li>\n\n\n\n<li>Approval workflows with repeated back-and-forth<\/li>\n<\/ul>\n\n\n\n<p>Define success in business terms (not tool terms):<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Shorter cycle time<\/li>\n\n\n\n<li>Fewer handoffs<\/li>\n\n\n\n<li>Lower rework<\/li>\n\n\n\n<li>Better audit trail<\/li>\n\n\n\n<li>Fewer \u201cwhere is this at?\u201d escalations<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Map the workflow as \u201chappy path + exceptions\u201d<\/h3>\n\n\n\n<p>Most failures happen in exceptions, not the main route.<\/p>\n\n\n\n<p>Document:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Happy path (80% of cases)<\/li>\n\n\n\n<li>Top 5 exception types (missing fields, low confidence extraction, mismatched identifiers, duplicate records, policy exceptions)<\/li>\n\n\n\n<li>Human decision points (what must be reviewed, by whom, and within what SLA)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Add AI only where it removes real manual judgment<\/h3>\n\n\n\n<p>Good AI inserts:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Extract key-value pairs from documents<\/li>\n\n\n\n<li>Classify email intent into a known set of categories<\/li>\n\n\n\n<li>Identify missing data and request it automatically<\/li>\n<\/ul>\n\n\n\n<p>Avoid AI inserts where:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The decision needs a policy interpretation<\/li>\n\n\n\n<li>The consequences are high without human review<\/li>\n\n\n\n<li>Data quality is inconsistent and unmonitored<\/li>\n<\/ul>\n\n\n\n<p>Microsoft\u2019s AI Builder guidance emphasizes embedding intelligence into automated processes (and it\u2019s often most effective when the AI step is narrow and well-defined).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Build \u201chuman-in-the-loop\u201d into the first release<\/h3>\n\n\n\n<p>Your first version should include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confidence thresholds (route low-confidence results for review)<\/li>\n\n\n\n<li>Approval gates (who can override, who is notified)<\/li>\n\n\n\n<li>Clear audit trail (what the AI extracted, what the human changed, what got posted)<\/li>\n<\/ul>\n\n\n\n<p>This is not \u201cslowing it down.\u201d It\u2019s how you earn adoption.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Treat go-live as an adoption milestone, not a finish line<\/h3>\n\n\n\n<p>A practical adoption plan includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A short \u201cday-in-the-life\u201d training (what changes for users)<\/li>\n\n\n\n<li>Role-based playbooks (operators vs approvers vs admins)<\/li>\n\n\n\n<li>Hypercare window (fast responses to early failures)<\/li>\n\n\n\n<li>Weekly feedback loop (exceptions, false positives, missed automations)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Governance and risk controls you should not skip<\/h2>\n\n\n\n<p>Intelligent automation often touches personal data (customers, employees), credentials, and operational decisions. Governance needs to exist before scale.<\/p>\n\n\n\n<p>Minimum controls:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Environment strategy:<\/strong> separate dev\/test\/prod<\/li>\n\n\n\n<li><strong>DLP policies:<\/strong> control which connectors can be used together (to reduce accidental data exposure)<\/li>\n\n\n\n<li><strong>Access model:<\/strong> least privilege, shared service accounts controlled by IT, clear break-glass procedures<\/li>\n\n\n\n<li><strong>Auditability:<\/strong> logs, run history, exception reasons, and approval trails<\/li>\n\n\n\n<li><strong>Model lifecycle:<\/strong> who updates AI models, how you test changes, how you monitor drift<\/li>\n<\/ul>\n\n\n\n<p>For responsible AI principles, Microsoft publishes its AI principles and approach (fairness, reliability\/safety, privacy\/security, inclusiveness, transparency, accountability). Use these as governance anchors when AI is part of the workflow.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Success metrics: what to measure <\/h2>\n\n\n\n<p>Track outcomes at three levels:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Workflow performance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cycle time (start \u2192 completion)<\/li>\n\n\n\n<li>Exception rate (how often humans must intervene)<\/li>\n\n\n\n<li>Rework rate (how often outputs are corrected)<\/li>\n\n\n\n<li>SLA compliance (especially for approvals)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Adoption health<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>% of work items processed via the new workflow vs manual path<\/li>\n\n\n\n<li>Top reasons people bypass automation<\/li>\n\n\n\n<li>Training completion and confidence (simple pulse checks)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Risk and control health<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incidents tied to incorrect routing\/extraction<\/li>\n\n\n\n<li>Audit trail completeness<\/li>\n\n\n\n<li>Security events or policy violations related to connectors and access<\/li>\n<\/ul>\n\n\n\n<p>This measurement discipline is part of <strong>change management<\/strong>: it tells you whether behavior has actually changed, not just whether a flow ran.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">ANZ, US, Canada: the regional lens you should build in early<\/h2>\n\n\n\n<p>Intelligent automation isn\u2019t only a technical project. The buyer concerns differ by region, and your rollout needs to reflect that.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">ANZ (Australia \/ NZ)<\/h3>\n\n\n\n<p>For privacy, Australian organizations commonly anchor to the <strong>Australian Privacy Principles (APPs)<\/strong> under the Privacy Act framework. When automation touches personal information, you need clarity on what data is collected, where it moves, and who can access it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Canada<\/h3>\n\n\n\n<p>Canada\u2019s federal private-sector privacy law context is often discussed through <strong>PIPEDA<\/strong> guidance from the Office of the Privacy Commissioner of Canada. From an implementation perspective: document data handling, consent assumptions, retention, and access controls, especially when workflows span multiple systems.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">US<\/h3>\n\n\n\n<p>In the US, expectations vary by sector, but many governance conversations reference frameworks such as <strong>NIST\u2019s AI Risk Management Framework<\/strong> for managing AI-related risks in a practical, voluntary way. This can be a useful structure for \u201cwhat could go wrong and how do we control it\u201d without turning a project into a compliance exercise.<\/p>\n\n\n\n<p>Note: This is not legal advice. Treat it as implementation guidance; confirm obligations with your compliance\/legal team.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Example architecture: intelligent document intake (invoice\/claim\/onboarding)<\/h2>\n\n\n\n<p>A common pattern that works well in Power Automate:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Trigger:<\/strong> Document received (email, portal upload, SharePoint, D365 attachment)<\/li>\n\n\n\n<li><strong>AI step:<\/strong> Extract fields using AI Builder document processing<\/li>\n\n\n\n<li><strong>Validation:<\/strong> Check confidence thresholds + mandatory fields<\/li>\n\n\n\n<li><strong>Routing:<\/strong>\n<ul class=\"wp-block-list\">\n<li>High confidence \u2192 auto-create\/update record in Dataverse\/Dynamics 365<\/li>\n\n\n\n<li>Low confidence \u2192 send to reviewer with extracted fields pre-filled<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Exception handling:<\/strong> If mismatched identifiers or duplicates, route to queue<\/li>\n\n\n\n<li><strong>Audit trail:<\/strong> Store extraction result, reviewer edits, timestamps, and final status<\/li>\n\n\n\n<li><strong>Notifications:<\/strong> Update requester\/customer with status and next steps<\/li>\n<\/ol>\n\n\n\n<p>This balances speed with control, which is often what makes adoption possible.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Implementation checklist (copy into your project plan)<\/h2>\n\n\n\n<p>Use this before you scale beyond a pilot:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Identify a process owner (business) and a platform owner (IT)<\/li>\n\n\n\n<li>Map the workflow with exceptions and escalation paths<\/li>\n\n\n\n<li>Define what must be reviewed by a human (policy, high impact decisions)<\/li>\n\n\n\n<li>Set confidence thresholds for AI extraction\/classification<\/li>\n\n\n\n<li>Create dev\/test\/prod environments and deployment approach<\/li>\n\n\n\n<li>Apply DLP policies and connector standards<\/li>\n\n\n\n<li>Define identity and access model (least privilege; managed accounts)<\/li>\n\n\n\n<li>Design monitoring: failures, exception volumes, and bypass reasons<\/li>\n\n\n\n<li>Run role-based training (operators, approvers, admins)<\/li>\n\n\n\n<li>Launch with hypercare and a weekly improvement cadence<\/li>\n<\/ul>\n\n\n\n<p>If you want <strong>change management<\/strong> to work, the checklist must include ownership, training, and feedback loops, not only build tasks.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1772694062881\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What is intelligent automation in simple terms?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>It\u2019s the combination of workflow automation (routing, approvals, integration) with AI steps (document understanding, classification, extraction) so processes can handle real-world variability without constant manual effort.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1772694070210\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Where does Power Automate fit in intelligent automation?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Power Automate orchestrates the end-to-end workflow: triggers, conditions, approvals, system updates, and integrations. AI Builder can be inserted inside flows for document processing and other intelligence steps.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1772694086002\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Why does change management matter for automation projects?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Because adoption is behavioral. If users don\u2019t trust outputs, don\u2019t understand exceptions, or don\u2019t know who owns issues, they will bypass the automation, regardless of how good the tech is. Prosci research links stronger change practices with better project outcomes.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1772694093811\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What\u2019s the safest way to start with AI in workflows?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Start narrow: one process, one AI task (like extracting fields), human review for low-confidence results, and an audit trail. Then expand only after you see stable performance and adoption.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1772694100145\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">How do privacy and governance affect intelligent automation?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Automation often moves personal or sensitive data across systems. Governance should cover access control, logging, connector policies, and responsible AI principles, adapted to your regional obligations and internal risk posture.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n<h3 class=\"wp-block-heading\">Closing: build the workflow, but also build the habit<\/h3>\n\n\n\n<p>Intelligent automation can reduce repetitive effort and make operations more consistent. But the difference between a pilot and a platform is <strong>change management<\/strong>: ownership, exception handling, training, trust, and measurement.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/osmosys.co\/book-a-demo-2\/\"><img decoding=\"async\" data-src=\"https:\/\/osmosys.co\/wp-content\/uploads\/2026\/03\/3.png\" alt=\"Power Automate intelligent automation architecture with governance controls, exception handling, and adoption steps\" class=\"wp-image-239721 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/a><\/figure>\n\n\n\n<p><br><a href=\"https:\/\/osmosys.co\/book-a-demo-2\/\">If you\u2019re evaluating intelligent automation in Power Automate, Osmosys can help you pick a pilot process, design governance, and deliver an adoption-ready rollout (not just a working flow). Talk to us about an Intelligent Automation Pilot Blueprint: process shortlist, architecture, controls, and a 30-day adoption plan.<\/a><\/p>\n\n\n\n<div class=\"wp-block-group alignfull has-contrast-color has-text-color is-vertical is-content-justification-center is-layout-flex wp-container-core-group-is-layout-f1198d31 wp-block-group-is-layout-flex\" style=\"min-height:40vh;margin-top:0;margin-bottom:0;padding-top:var(--wp--preset--spacing--60);padding-right:var(--wp--preset--spacing--50);padding-bottom:var(--wp--preset--spacing--60);padding-left:var(--wp--preset--spacing--50)\">\n<figure class=\"wp-block-image size-large is-resized\"><img decoding=\"async\" data-src=\"https:\/\/osmosys.co\/wp-content\/uploads\/2026\/03\/Osmosys-Logo-pictorial-1080x867.png\" alt=\"\" class=\"wp-image-239723 lazyload\" style=\"--smush-placeholder-width: 1080px; --smush-placeholder-aspect-ratio: 1080\/867;width:80px;height:auto\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/figure>\n\n\n\n<p class=\"has-text-align-center has-medium-font-size\">Osmosys Software Solutions<\/p>\n\n\n\n<ul class=\"wp-block-social-links has-normal-icon-size is-style-logos-only is-nowrap is-layout-flex wp-container-core-social-links-is-layout-53bee8aa wp-block-social-links-is-layout-flex\"><li class=\"wp-social-link wp-social-link-linkedin  wp-block-social-link\"><a href=\"https:\/\/in.linkedin.com\/company\/osmosys_2\" class=\"wp-block-social-link-anchor\" target=\"_blank\" rel=\"noopener\"><svg width=\"24\" height=\"24\" viewBox=\"0 0 24 24\" version=\"1.1\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" aria-hidden=\"true\" focusable=\"false\"><path d=\"M19.7,3H4.3C3.582,3,3,3.582,3,4.3v15.4C3,20.418,3.582,21,4.3,21h15.4c0.718,0,1.3-0.582,1.3-1.3V4.3 C21,3.582,20.418,3,19.7,3z M8.339,18.338H5.667v-8.59h2.672V18.338z M7.004,8.574c-0.857,0-1.549-0.694-1.549-1.548 c0-0.855,0.691-1.548,1.549-1.548c0.854,0,1.547,0.694,1.547,1.548C8.551,7.881,7.858,8.574,7.004,8.574z M18.339,18.338h-2.669 v-4.177c0-0.996-0.017-2.278-1.387-2.278c-1.389,0-1.601,1.086-1.601,2.206v4.249h-2.667v-8.59h2.559v1.174h0.037 c0.356-0.675,1.227-1.387,2.526-1.387c2.703,0,3.203,1.779,3.203,4.092V18.338z\"><\/path><\/svg><span class=\"wp-block-social-link-label screen-reader-text\">LinkedIn<\/span><\/a><\/li>\n\n<li class=\"wp-social-link wp-social-link-facebook  wp-block-social-link\"><a href=\"https:\/\/www.facebook.com\/OsmosysSoftwareSolutions\/\" class=\"wp-block-social-link-anchor\" target=\"_blank\" rel=\"noopener\"><svg width=\"24\" height=\"24\" viewBox=\"0 0 24 24\" version=\"1.1\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" aria-hidden=\"true\" focusable=\"false\"><path d=\"M12 2C6.5 2 2 6.5 2 12c0 5 3.7 9.1 8.4 9.9v-7H7.9V12h2.5V9.8c0-2.5 1.5-3.9 3.8-3.9 1.1 0 2.2.2 2.2.2v2.5h-1.3c-1.2 0-1.6.8-1.6 1.6V12h2.8l-.4 2.9h-2.3v7C18.3 21.1 22 17 22 12c0-5.5-4.5-10-10-10z\"><\/path><\/svg><span class=\"wp-block-social-link-label screen-reader-text\">Facebook<\/span><\/a><\/li>\n\n<li class=\"wp-social-link wp-social-link-instagram  wp-block-social-link\"><a href=\"https:\/\/www.instagram.com\/osmosysindia\/\" class=\"wp-block-social-link-anchor\" target=\"_blank\" rel=\"noopener\"><svg width=\"24\" height=\"24\" viewBox=\"0 0 24 24\" version=\"1.1\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" aria-hidden=\"true\" focusable=\"false\"><path d=\"M12,4.622c2.403,0,2.688,0.009,3.637,0.052c0.877,0.04,1.354,0.187,1.671,0.31c0.42,0.163,0.72,0.358,1.035,0.673 c0.315,0.315,0.51,0.615,0.673,1.035c0.123,0.317,0.27,0.794,0.31,1.671c0.043,0.949,0.052,1.234,0.052,3.637 s-0.009,2.688-0.052,3.637c-0.04,0.877-0.187,1.354-0.31,1.671c-0.163,0.42-0.358,0.72-0.673,1.035 c-0.315,0.315-0.615,0.51-1.035,0.673c-0.317,0.123-0.794,0.27-1.671,0.31c-0.949,0.043-1.233,0.052-3.637,0.052 s-2.688-0.009-3.637-0.052c-0.877-0.04-1.354-0.187-1.671-0.31c-0.42-0.163-0.72-0.358-1.035-0.673 c-0.315-0.315-0.51-0.615-0.673-1.035c-0.123-0.317-0.27-0.794-0.31-1.671C4.631,14.688,4.622,14.403,4.622,12 s0.009-2.688,0.052-3.637c0.04-0.877,0.187-1.354,0.31-1.671c0.163-0.42,0.358-0.72,0.673-1.035 c0.315-0.315,0.615-0.51,1.035-0.673c0.317-0.123,0.794-0.27,1.671-0.31C9.312,4.631,9.597,4.622,12,4.622 M12,3 C9.556,3,9.249,3.01,8.289,3.054C7.331,3.098,6.677,3.25,6.105,3.472C5.513,3.702,5.011,4.01,4.511,4.511 c-0.5,0.5-0.808,1.002-1.038,1.594C3.25,6.677,3.098,7.331,3.054,8.289C3.01,9.249,3,9.556,3,12c0,2.444,0.01,2.751,0.054,3.711 c0.044,0.958,0.196,1.612,0.418,2.185c0.23,0.592,0.538,1.094,1.038,1.594c0.5,0.5,1.002,0.808,1.594,1.038 c0.572,0.222,1.227,0.375,2.185,0.418C9.249,20.99,9.556,21,12,21s2.751-0.01,3.711-0.054c0.958-0.044,1.612-0.196,2.185-0.418 c0.592-0.23,1.094-0.538,1.594-1.038c0.5-0.5,0.808-1.002,1.038-1.594c0.222-0.572,0.375-1.227,0.418-2.185 C20.99,14.751,21,14.444,21,12s-0.01-2.751-0.054-3.711c-0.044-0.958-0.196-1.612-0.418-2.185c-0.23-0.592-0.538-1.094-1.038-1.594 c-0.5-0.5-1.002-0.808-1.594-1.038c-0.572-0.222-1.227-0.375-2.185-0.418C14.751,3.01,14.444,3,12,3L12,3z M12,7.378 c-2.552,0-4.622,2.069-4.622,4.622S9.448,16.622,12,16.622s4.622-2.069,4.622-4.622S14.552,7.378,12,7.378z M12,15 c-1.657,0-3-1.343-3-3s1.343-3,3-3s3,1.343,3,3S13.657,15,12,15z M16.804,6.116c-0.596,0-1.08,0.484-1.08,1.08 s0.484,1.08,1.08,1.08c0.596,0,1.08-0.484,1.08-1.08S17.401,6.116,16.804,6.116z\"><\/path><\/svg><span class=\"wp-block-social-link-label screen-reader-text\">Instagram<\/span><\/a><\/li>\n\n<li class=\"wp-social-link wp-social-link-youtube  wp-block-social-link\"><a href=\"https:\/\/www.youtube.com\/user\/OsmosysOfficial\" class=\"wp-block-social-link-anchor\" target=\"_blank\" rel=\"noopener\"><svg width=\"24\" height=\"24\" viewBox=\"0 0 24 24\" version=\"1.1\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" aria-hidden=\"true\" focusable=\"false\"><path d=\"M21.8,8.001c0,0-0.195-1.378-0.795-1.985c-0.76-0.797-1.613-0.801-2.004-0.847c-2.799-0.202-6.997-0.202-6.997-0.202 h-0.009c0,0-4.198,0-6.997,0.202C4.608,5.216,3.756,5.22,2.995,6.016C2.395,6.623,2.2,8.001,2.2,8.001S2,9.62,2,11.238v1.517 c0,1.618,0.2,3.237,0.2,3.237s0.195,1.378,0.795,1.985c0.761,0.797,1.76,0.771,2.205,0.855c1.6,0.153,6.8,0.201,6.8,0.201 s4.203-0.006,7.001-0.209c0.391-0.047,1.243-0.051,2.004-0.847c0.6-0.607,0.795-1.985,0.795-1.985s0.2-1.618,0.2-3.237v-1.517 C22,9.62,21.8,8.001,21.8,8.001z M9.935,14.594l-0.001-5.62l5.404,2.82L9.935,14.594z\"><\/path><\/svg><span class=\"wp-block-social-link-label screen-reader-text\">YouTube<\/span><\/a><\/li><\/ul>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>That\u2019s not an automation problem. It\u2019s a change management problem. Intelligent automation (AI + workflows + RPA) can reduce repetitive effort and improve consistency. But it only pays off when people trust the outputs, know how exceptions are handled, and can see what\u2019s changing in their day-to-day work. Prosci\u2019s research is blunt: projects with excellent [&hellip;]<\/p>\n","protected":false},"author":44,"featured_media":237335,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","_lmt_disableupdate":"","_lmt_disable":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[74,63],"tags":[57,175,66,117],"class_list":["post-237332","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai","category-power-apps","tag-ai","tag-automation","tag-dynamics-365","tag-power-apps"],"modified_by":"mounika","jetpack_featured_media_url":"https:\/\/osmosys.co\/ca\/wp-content\/uploads\/sites\/5\/2026\/03\/1.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts\/237332","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/users\/44"}],"replies":[{"embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/comments?post=237332"}],"version-history":[{"count":2,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts\/237332\/revisions"}],"predecessor-version":[{"id":237336,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts\/237332\/revisions\/237336"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/media\/237335"}],"wp:attachment":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/media?parent=237332"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/categories?post=237332"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/tags?post=237332"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}