Your search for returned 100 results.

Many companies have the technology, but not the organizational structure to make AI truly effective. Its the combination of both layers that creates real business impact. Table of Contents

Goals instead of steering logic: the four promises of AIAI Implementation Strategy: the Governance and Execution Framework Between Goals and ImpactTwo pillars: AIready Organization & AIready ITOperational Effectiveness: three central action areas of the AIReady OrganizationConclusion: AI Transformation as a management taskWorkshops The majority of companies (94% in 2026, according to research institute Resoucera) are already investing in artificial intelligence (AI) today: AI tools are being rolled out, copilots activated, and pilot projects launched. Business units are experimenting with productive use cases. A logical and welcome indeed necessary development.

Yet the proof of sustainable value creation often remains incomplete. Why? The short answer: the issue is less about the absence of powerful systems and more about the lack of an organizational foundation.

Too often, AI is still treated as a purely IT-driven topic or as a loose collection of use cases. And this creates systemic side effects: pilots improve local subprocesses without touching endtoend value creation. Results remain contextbound and cannot be replicated because interfaces, roles, and governance are missing. Return on investment (ROI) becomes a matter of interpretation due to poorly defined target states and measurement logic. Daytoday operations experience friction: some employees benefit in isolated instances, while others face additional effort or uncertainty; the workforce polarizes between enthusiasm and skepticism.

Where goals are unclear, responsibilities diffuse, and decision paths not consistently aligned with the value chain, impact evaporates in the transition from pilot to production. These organizations simply arent designed to reliably translate AI into value creation. They are AI-busy, not AI-effective: plenty of AI activity, but structurally anchored impact is missing.

The key insight: the experimental phase is right and important but it does not replace the deliberate design of the systemic prerequisites needed to shift AI from a prototyping mode into reliable production. The task now is to build a robust level of AI-readiness. Companies associate different expectations with AI depending on their starting point, strategy, and market environment. Typically, they pursue one or several of four dominant objectives seen in practice:

Efficiency gains: automation, cost reduction, productivity improvements.Service orientation: faster response times, personalization, consistent quality.Innovative capacity: new products, new business models, revenue growth, accelerated cycles.Cultural development: stronger data orientation, learning capability, openness to change.

These expectations are understandable goals, but they do not provide a robust steering logic for a scalable AI transformation. Without a solid AI strategy and its implementation and thus the creation of a unifying framework they remain fragmented ambitions that may generate local impact but fail to scale across the organization. Impact is created where strategic ambitions are translated into a robust logic for execution. Organizations still develop carefully crafted AI strategy papers yet the path to execution often remains unclear. Whats needed is an AI implementation strategy. It serves as the connecting element between strategic objectives and operational value creation, defining the governance and delivery framework that transforms AI initiatives from isolated pilot projects into a repeatable, measurable, and scalable valuecreation process.

An implementation strategy is not a detailed methodology at first, but rather an overarching operating and governance logic. It specifies how strategic goals are translated into concrete prioritization criteria, decisionmaking routines, role models, and steering mechanisms. Specific programs, initiatives, and methods are derived from this foundation and can be designed differently depending on the organization.

The starting point is a structured analysis of goals, the current state, and existing capabilities. Strategic objectives are refined and translated into measurable impact goals. At the same time, the organizations technological, organizational, and cultural prerequisites are assessed to identify both strengths and development needs. Based on this, a target picture for AI emerges one that clearly describes in which value streams and business areas AI should generate impact and what priorities follow from that.

Building on this, the implementation operating model is defined. The implementation strategy translates the target picture into a viable setup of program and project structures, governance bodies, roles, decision logics, and steering mechanisms. It determines how initiatives are prioritized, funded, and managed; how progress and impact are measured; and how technical, datarelated, and organizational guardrails interact. Organizational realities are consciously considered so that the setup matches the companys actual capacity and maturity.

A central element is the learning and scaling mechanism. It ensures that AI initiatives do not remain isolated, but are systematically transformed into repeatable patterns. Insights from pilots flow into standards, architectural components, governance rules, training formats, and operational processes. Over time, this creates an organization in which AI is not run as a project, but as a sustained capability.

The AI implementation strategy therefore creates strategic coherence, aligns resources with prioritized fields of impact, and establishes a consistent model for governance and decisionmaking. Its effectiveness lies in proportionality: it defines exactly the guardrails and routines needed to enable speed while ensuring quality, safety, and longterm sustainability. AI readiness can be understood as the target state that an AI implementation strategy works toward. AI readiness, as a catalyst for achieving one or several of the objectives mentioned above, is not measured by the number of tools in place but by an organizations ability to systematically translate AI into value creation. To do so, AI must be viewed strategically and not as a task or responsibility owned solely by IT. This leads to two central pillars that must be stabilized: both the technical conditions (such as data quality, infrastructure, and compliance) and the organizational and cultural factors (e.g., clear accountabilities, skills, adoption, and strategic direction) must work together.

AIReady Technology: Data & TechnologyIn many companies, the technological foundation is present but only partially robust: cloud infrastructures exist, but data quality and availability are often inconsistent; models are powerful, but not embedded into productiongrade operating processes; AI tools are available, but integration, security, and compliance are only partially resolved. Technology, therefore, is necessary but rarely sufficient.AIReady Organization: Strategy, Governance & OrganizationOrganizationally, a different pattern emerges: prioritization often follows opportunity rather than clear value streams; roles and responsibilities are insufficiently defined; and governance remains ad hoc. AI solutions frequently fail at process boundaries because interfaces, role models, and operating processes are not designed to be resilient meaning even solid technology fails to generate impact. Only clear accountabilities, stable processes, and consistent decisionmaking logic create the conditions for scalable value creation.

What we observe: Many companies begin their AI journey through the technological pillar they invest in platforms, data quality, and initial use cases and are often relatively well positioned there. The true barrier to impact, however, tends to emerge within the organization: without clear accountabilities, governance, operating processes, and prioritization logic, technology cannot be translated into scalable value creation. This is precisely why, in the following sections, we deliberately focus on the pillar AIready Organization and examine its mechanisms and levers for impact. For shaping the AIready Organization pillar, three central action areas can be identified. Their level of maturity determines an organizations actual ability to scale AI. They form the operational layer that reveals whether an implementation strategy holds up in daytoday practice and whether AI can be reliably transformed from isolated initiatives into a repeatable valuecreation mechanism.

These three action areas relate to the design of valuecreation processes, the definition of roles and operating models, and the way leadership and collaboration are organized. Only their interaction creates the organizational conditions that make AI effective within the company.

Action Area 1: Process & Value Creation

The first lever lies in consistently aligning AI with real value streams. AI generates value not through isolated suboptimizations, but where it accelerates, stabilizes, and simplifies endtoend processes. Problem definition, data usage, model development, and operational decisionmaking must be viewed as a connected value stream. The focus shifts away from individual use cases toward processlevel units of impact. What matters is not the technological elegance of a solution, but its measurable contribution to value creation for example through shorter lead times, lower error rates, higher forecast accuracy, or more stable service levels. Impact emerges only when AI outputs are firmly embedded in decisions and workflows rather than provided as optional recommendations alongside the process.

Action Area 2: Organization & Roles

The second action area concerns the organizational foundation. Without clear responsibilities and operating models, AI remains an experimentation system. Roles such as Data/AI Product Owners, Service Owners, Data Stewards, or AI Governance Leads define accountability across the entire lifecycle from ideation and development to operations, evolution, or retirement of a solution. They ensure that decisions are made, quality standards are upheld, and responsibilities remain transparent. Formalized decisionmaking logic clarifies who decides what, when, and on the basis of which data and how conflicts are resolved. Governance acts not as a bureaucratic obstacle, but as a proportional guardrail for quality, security, ethics, and compliance. This turns AI into a stable operational capability rather than a sequence of isolated projects.

Action Area 3: Leadership & Collaboration

The third lever is leadership and collaboration. Introducing AI is less a technical challenge and more an organizational and cultural leadership task. Leaders who understand AI as a valuecreation system set clear priorities, articulate expectations for its use, and provide orientation within a changing work environment. Psychological safety is essential: employees must be able to experiment and learn in order to confidently integrate AI into their daily routines. Skill development is not treated as a onetime training initiative but as a continuous component of the operating model. Clear communication and decisionmaking routines enable teams to share experiences, abstract patterns, and anchor learning structurally. In this way, AI becomes not only technically feasible but also organizationally and socially rooted. The path toward building the foundation for AI scaling within organizations is not an isolated IT initiative, but a management task with a systemic character. Impact emerges where technology and data are connected with processes, roles, governance, and leadership in such a way that AI usage becomes not only possible, but expected and rewarding.

Many companies have AI initiatives. Few have an organization that can make AI effective on a lasting basis. Those who build this organizational capability turn technological potential into real value creation. Get in touch with us!

Learn more

Traditional structures in project management offices (PMOs) focused on individual projects and transformation initiatives are increasingly reaching their limits. Not because methods are lacking, but because operational complexity is crowding out true steering and governance work. AI is shifting this balance increasing efficiency and, more importantly, strengthening steering effectiveness itself. Table of Contents

Effectiveness, not Efficiency, drives ImpactWhere AI delivers tangible value in the PMOSteering remains a human responsibilityHow AI atrengthens the PMOs steering capabilityNew requirements for Project ManagersHow companies can get startedChallenges on the path to an AI-driven PMOConclusion: Effectiveness Over Efficiency Although projects play a key role in delivering transformations, their success rate remains sobering: only 48 percent achieve their stated goals. The challenges facing PMOs have been growing for years driven by agility, which fundamentally changes planning and steering logics, and by sustainability requirements, which broaden the definition of project success. Expanding project landscapes, growing data volumes, and shorter decision cycles add further pressure. Artificial intelligence can address these challenges by reshaping the way operational project steering is performed.

At the same time, it is becoming increasingly clear that project managers and PMOs need greater foresight to identify risks and issues early and take corrective action before time, budget, or scope are jeopardized. In many organizations, a substantial share of PMO capacity is consumed by operational tasks: consolidating data, producing reports, preparing variance analyses, and setting up status meetings. These insights often emerge only after the relevant decision has already been made or a risk has long become visible. Transparency exists but frequently too late to intervene effectively. This is typically not a question of capability, but a structural challenge. When AI is discussed in the PMO context, the debate usually revolves around efficiency: faster reports, automated status updates, and less manual data maintenance. That is not wrong, but it does not go far enough. The real question is not whether the PMO becomes faster, but whether it can intervene earlier. Whether risks become visible before they escalate. Whether resource bottlenecks are identified before they put schedules at risk. Whether decisions are made on a more robust foundation, rather than on whatever could be compiled by the next status report. This is where the real lever of AI lies. Not automation for its own sake, but automation as a prerequisite for enabling PMO teams to perform their core role: steering, prioritizing, and making informed decisions. The potential becomes most evident where processes are structured, repeatable, and data-driven, and where a large share of operational effort is currently required.

In reporting, AI automates the consolidation and preparation of project data. What previously took hours becomes continuously available. The focus shifts from creation to interpretation, from the question What happened? to What does it mean, and what should we do?In resource management, AI identifies patterns in historical data, detects bottlenecks at an early stage, and enables more realistic forecasts. Capacity decisions become more robust and less dependent on the experience of individual contributors.In cost and budget control, AI highlights deviation trends before they appear in the next reporting cycle. Scenarios can be simulated, risks assessed, and countermeasures defined before budget overruns occur.In scheduling, dependencies across projects become more transparent, delays are detected earlier, and timelines are adjusted dynamically instead of being documented after the fact.

According to estimates, up to 80 percent of operational project management tasks could be supported or automated by AI by 2030. This does not just change individual processes, but fundamentally reshapes the role and responsibility profile of the PMO. The more strongly tasks are shaped by context, experience, and interpersonal interaction, the more important the human role remains. Resolving stakeholder conflicts, setting priorities under uncertainty, and taking responsibility for decisions are core elements of effective project steering that AI cannot (yet) replace. The greatest value therefore lies not in full automation, but in purposeful collaboration: AI prepares, humans decide. The time gained is invested in value-creating activities such as interpreting results, understanding cause-and-effect relationships within the project context, and making strategic decisions. With the automation of operational tasks, the identity of the PMO begins to shift. Less reporting, more steering. Less data maintenance, more contextualization. As a result, the PMO expands its role toward a more forward-looking approach to governance. Risks are addressed earlier, dependencies become transparent sooner, and decisions are made on a more solid foundation. This is what Campana & Schott defines as the PMO of the future: an evolution that combines classic project governance with data-driven steering, AI support, and targeted change management. The goal is to reduce operational complexity while sustainably strengthening decision-making capability. With the use of AI, the role of project managers is evolving as well. Operational tasks such as reporting, data maintenance, or status inquiries are increasingly supported or taken over by AI. The time and attention gained are redirected toward capabilities that cannot be automated: interpersonal communication, stakeholder management, and navigating uncertainty. In addition, a new core competency is emerging: the ability to confidently work with AI outputs to interpret them, challenge them, and place them in the appropriate project context. AI provides recommendations, but responsibility for decisions remains with people. Getting started does not begin with selecting tools, but with an honest assessment of the current situation. Where do the greatest operational efforts arise today? Where does manual data work slow down effective steering? Experience shows that the areas with the highest AI impact are reporting, resource planning, and cost forecasting, as they are structured, repeatable, and data-driven. Pilot projects provide the foundation for gaining experience and iteratively refining the approach. Scaling follows only once clear value has been demonstrated. Critical success factors include a reliable data foundation, close collaboration between business units and IT, and clear governance for data protection, transparency, and accountability.

Finally, organizational culture plays a decisive role. AI adoption succeeds where willingness to learn and experiment is part of everyday practice. This calls for an honest assessment of maturity: many organizations aspire to use AI but are not yet ready culturally, technically, or organizationally. At the same time, implementing AI in the PMO is not a self-running exercise. Issues such as data quality, the traceability of results, and the handling of sensitive information present organizations with new challenges. Potential biases in training data must also be taken into account: AI systems learn from data that may overrepresent certain perspectives and contexts while systematically excluding others. In project management, this can lead to recommendations that fail to adequately reflect cultural or organizational specifics. Those who adopt AI outputs uncritically may also inherit their blind spots. In addition, technical and organizational integration runs deeper than it may appear at first glance. Introducing AI into the PMO means more than adding individual tools to existing systems. It involves infrastructure, data storage, and computing capacity, as well as the targeted enablement of employees. This makes it all the more important to define clear responsibilities and ensure that AI outputs are critically assessed and used responsibly. AI does not just make the PMO more efficient it makes it more effective by reclaiming the space that operational complexity occupies today. Organizations that deliberately shape this transformation gain one thing above all else: time and attention for the tasks that truly make a difference communication, sense-making, and decision-making. And ultimately, for project success.

Campana & Schott supports organizations in approaching this transformation in a structured and pragmatic way, combining a thorough analysis of existing PMO processes with concrete use cases and a realistic roadmap. Sie mchten wissen, wo KI in Ihrem PMO den grten Mehrwert schafft? 

Nehmen Sie gerne Kontakt mit uns auf. 

Learn more

The first productive use of an AI platform within an organization often begins in a straightforward way. Licenses are procured, employees are trained, features are activated, and initial successes become visible through simple use cases that make day-to-day work easier. In this introductory phase, usage is deliberately focused on basic, clearly defined scenarios. AI platforms such as Microsoft Copilot and Foundry leverage existing information, enrich it with context, and support users in handling routine tasks. Table of Contents

From Helper to RiskFrom Risk to ControlEnabling Successful IntegrationA strong AI platform requires strong IT Service Management As usage increases, however, organizations begin to realize that AI is more than just a tool embedded in individual applications. The AI platform evolves into a permanently available service whose outputs actively shape workflows. In a growing number of companies, AI agents are autonomously taking over entire process steps. To do so, they require their own permissions to access data and resources.

The necessary shift in perspective is therefore clear: AI may start in Outlook, but its sphere of impact extends far beyond that. To effectively support the use of AI as a service, service management comes into play. It provides the service with a structured framework of specialized organizational capabilities and processes designed to optimize service quality and the customer experience across the entire lifecycle. This ensures that the service is aligned with both business and employee requirements and delivers the greatest possible value to the organization. In day-to-day operations, it quickly becomes apparent how demanding ongoing operations can be. Organizations face the following challenges: With the increasing integration of AI mechanisms such as M365 Copilot, new operational requirements are emerging. Processes become more dependent on data, role models, and continuous development. IT Service Management (ITSM) provides the structured framework needed to manage this dynamic and make AI platforms reliably usable. It ensures that the required IT services are delivered effectively, in a standardized and demand-oriented manner, thereby offsetting the operational uncertainty that arises when deploying AI-enabled services.

An effective organization, supported by the right tools and end-to-end process orchestration, creates the stability required for AI-dependent workflows. As a result, fluctuations in technical behavior, shifting dependencies, or unclear responsibilities no longer pose a risk but instead become transparent and controllable. What matters most is integration into the existing service environment and the companys value chains. Only then can the impact of AI platforms on business processes be reliably assessed and actively managed.

From an operational perspective, ITSM ensures that typical uncertainties in dealing with AI no longer arise in an unstructured way but are addressed systematically. Proactive monitoring allows irregularities to be identified early, before they affect process quality. Rapid incident resolution, detailed root cause analysis, and controlled implementation of changes prevent unexpected results, variable outputs, or technical deviations from spreading unchecked across the organization. At the same time, application availability increases and downtime is deliberately reduced.

In parallel, ITSM creates the necessary transparency around dependencies and risks. By documenting how components are interconnected, what impact changes can have, or where error chains may propagate, complex AI relationships become operationally manageable. What is often perceived in everyday work as difficult-to-explain behavior is thus placed on a clear, traceable foundation.

Another key aspect is the clear assignment of responsibilities. Clearly defined roles and established escalation paths enable faster decision-making and more targeted incident resolution. This is a critical factor when AI services are used concurrently across different areas and multiple underlying causes may be at play.

When ITSM is integrated early into AI application use cases and new operating models, it creates a holistic approach that leads to optimized processes, higher productivity, and increased overall efficiency. In this way, an innovative tool becomes a reliable, manageable component of enterprise operations. The use of AI platforms such as Copilot or Foundry within an organizationand thus the integration of these services into an existing IT and service organizationraises a number of fundamental questions:

How does the AI platform fit into the existing IT and service organization as a service or application?Which functional and non-functional requirements apply in connection with the AI platform?Which processes need to be adapted?How is the technical and organizational integration implemented?How is the IT service operated reliably and continuously improved?How should the user experience and interaction with the services ideally be designed?

These questions can be addressed through a structured, ITSM-based approachone that spans from initial needs assessment to continuous improvement and step by step integrates AI services into the organizations existing operating model. Without a clearly structured operating and service management model, AI services remain vulnerable to fluctuations, inconsistencies, and unclear responsibilities. Only when governance, processes, and technical foundations are properly aligned can AI services reliably realize their full potential. ITSM provides the foundation on which a stable, secure, and scalable AI service can be operated and managed.

Campana & Schott supports organizations in getting started with a structured maturity assessment. The focus is on seamlessly integrating the use of the AI platform into existing ITSM processes and tool landscapes in order to ensure governance, transparency, and long-term operational stabilitywhile delivering the best possible user experience. Sie mchten wissen, wo KI in Ihrem PMO den grten Mehrwert schafft? 

Nehmen Sie gerne Kontakt mit uns auf. 

Learn more

Copilot Wave 3 has been rolling out for several weeks now. It is becoming increasingly clear that this is less about individual new features and more about a new way of working. We summarize the key developments and provide initial perspectives. Table of Contents

From Tasks to WorkflowsWhats hanging on the Technology sideCowork: Automating End-to-End WorkflowsWork IQ: Context as the FoundationAgent 365: Governance, Control, and OversightLicensing: Which features are included in which plansConclusion Copilot is already in daily use at many companies. In many cases, it has significantly increased the personal productivity of individual employees. Initial use cases at the process levelmostly within individual business unitsare also demonstrating measurable value.

At the same time, usage often remains limited to individual tasks. Many organizations fail to move beyond initial pilot applications to broader scaling. One key reason for this: Copilot is used, but rarely thought of as an end-to-end platform. This is exactly where Microsoft steps in with Wave 3.

Wave 3 is not a new product or a single feature, but rather a new stage in Copilots evolution. The focus is on automation, contextual understanding, and agents. What matters less is any individual capability and more the shift in how it is used: away from ad hoc support toward workflows that are more deeply embedded in daily work. Copilot thus definitively becomes a process platform. Agents and automated workflows are not a new concept in the Microsoft ecosystem. Even before Wave 3, they could be created and used through tools such as Copilot Studio. In practice, however, this usage was often limited to employees with the appropriate expertise. The tool requires an understanding of processes, logic, and structure and was therefore primarily used in specialized roles.

With Wave 3, the concept itself changes less than the way it is accessed. Copilot no longer operates only in response to individual queries, but directly within applications. In Word, Excel, PowerPoint, or Outlook, it no longer supports just individual steps, but carries out complete work assignments.

The difference lies less in new features than in the mode of interaction. Instead of formulating individual prompts, employees increasingly describe the desired outcome. Copilot independently derives a multi-step workflow from this description, asks follow-up questions if needed, and executes the necessary steps.

An example illustrates the shift: rather than creating a presentation slide by slide, a complete work assignment can be definedfor example, Create a presentation deck for a product launch based on existing materials, structure the content by target groups, visualize the key messages, and follow the corporate design.Copilot analyzes the existing content, develops a structure, creates the slides, adds visual elements, and iteratively refines the result. The workflow does not emerge step by step through individual instructions, but is executed as an integrated whole.

With capabilities such as Cowork, this approach goes even further. Here, not only content within a single application can be created, but entire cross-application workflows can be delegated.

The decisive shift, therefore, is not the creation of new possibilities for specialists, but the deep integration of AI into the everyday work of virtually every employee. Agents that were previously used in isolated scenarios increasingly become a natural part of daily collaboration. This shift in usage does not happen in isolation, but is enabled by several technological building blocks. Cowork, in the context of Copilot Wave 3, is both a concrete capability and an expression of a changed way of working. While Copilot previously reacted primarily to individual requests, Cowork enables the structured delegation of entire workflows.

The key difference lies in the nature of the collaboration. AI is no longer guided step by step, but integrated like a colleague. Humans define the goal, boundaries, and desired outcome. Cowork independently develops a workflow from this, asks follow-up questions if needed, and carries out the necessary steps.

The underlying principle can be summarized in three points: Cowork is particularly well suited for two scenarios: Mit der Automatisierung operativer Aufgaben verschiebt sich die Identitt des PMO. Weniger Berichtswesen, mehr Steuerung. Weniger Datenpflege, mehr Einordnung. Das PMO erweitert damit seine Rolle um eine strker vorausschauende Steuerung. Risiken werden frher adressiert, Abhngigkeiten frher transparent gemacht, Entscheidungen auf einer fundierteren Grundlage getroffen. Genau das versteht Campana & Schott unter einem PMO 4.0: eine Weiterentwicklung, die klassische Projekt-Governance mit datengetriebener Steuerung, KI-Untersttzung und gezieltem Change Management verbindet. Ziel ist es, operative Komplexitt zu reduzieren und gleichzeitig die Entscheidungsfhigkeit nachhaltig zu strken. A key prerequisite for this is the ability to clearly describe tasks. Those who have learned how to structure and delegate work have a clear advantage. At the same time, the AIs scope of action remains well defined: Copilot operates within existing permissions, works in a context-aware manner, and involves users at critical pointsfor example, for approvals or corrections.

In addition, recurring requirements can be captured through so-called skills. These are reusable instructions that Copilot automatically takes into account during execution, such as design guidelines or formatting rules. This makes it possible to standardize workflows and scale them consistently.

Note for Europe: Data processing for Cowork currently takes place outside the EU Data Boundary. As a result, many companiesespecially those in regulated environmentsare not yet using Cowork in production. An EU-compliant solution has been announced. Work IQ, in the context of Microsoft Copilot Wave3, describes how work can be understood, evaluated, and guided when AI and agents are continuously embedded in the flow of work. While Cowork focuses on the collaboration between humans and AI, Work IQ addresses the question of impact: What work is being created, how do decisions change, and where does real value emerge?

Work IQ consists of multiple technical building blocks that provide Copilotwith both simple prompts and agentsthe appropriate context, without requiring extensive manual input from users as was previously the case. The principle still applies: the more precisely the context matches the request, the better the result. With Work IQ, this context is now automatically identified and supplied. It includes data from Microsoft 365, information from third-party systems, role-based context, and personalized usage data. This is complemented by the integration of skills and tools.

The technical foundation is the Microsoft Graph as the central intelligence layer of Microsoft 365. It connects signals from emails, meetings, files, tasks, and collaboration and provides the working context that Copilot and agents rely on. On this basis, AI does not generate content in isolation, but can recognize relationships, prepare decisions, and support work in a context-aware manner.

Work IQ leverages this intelligence layer to create transparency around which activities are handled by AI, where human work is deliberately enhanced, and how work and decision-making processes evolve overall. It thus becomes a framework for orientationhelping organizations design AI-supported work not only more efficiently, but also consciously, controllably, and responsibly. Agent 365 establishes the central governance and management layer for the use of agents within an organization. IT leaders gain transparency into which agents are in use, what they are used for, and under which rules and approval processes they are allowed to operate.

This creates the foundation for managing the use of agents in a controlled and scalable wayespecially in environments where multiple platforms are used in parallel. Agent 365 takes into account not only Microsoft-native solutions, but also agents from third-party systems such as Salesforce or SAP. This results in an end-to-end view of agent-based automation and collaboration, regardless of the underlying source system. Agent 365 is scheduled to become generally available in May 2026.

What these three building blocks enable together: workflows can be standardized, reused, and transferred to other areas. Copilot thus evolves from a tool for individual productivity into a platform for operational processes. Wave 3 is not a standalone product, but an extension of existing Microsoft 365 offerings. For organizations, this shifts the licensing question accordingly: not whether new licenses are required, but which capabilities are already available and how they can be combined effectively. Wave 3 is not a classic feature update. It marks a clear shiftfrom ad hoc support to the structured automation of workflows.

What matters is not that new possibilities are emerging. Many of these approaches already existed. What is new is how they are integrated into everyday work, making them usable at a much broader scale.

With Wave 3, the technological prerequisites are in place. Whether this translates into real impact depends less on the technology itself and more on the organization behind it. Why AI scaling still fails in many companiesand what needs to changewill be explored in the second part on Copilot Wave 3. Sie mchten wissen, wo KI in Ihrem PMO den grten Mehrwert schafft? 

Nehmen Sie gerne Kontakt mit uns auf. 

Learn more

In this interview, Jana Mller, Senior Manager at Campana & Schott, explains why many transformations fail not during strategy development, but during implementation. Companies must continually change to meet customer demand and stay competitive. Transformation programs are part of every corporate agenda. Yet despite their high relevance, these programs often fail and don't deliver the intended impact. They get launched, budgets are approved and spent, teams work with great energybut in the end, the results often fall short of expectations. At the same time, day-to-day operations have to keep running. Jana Mller, Head of Practice Division Transformation of Business, knows these patterns well. In this conversation, she explains why transformation so often stalls, what agility alone can't solve, and why companies need to manage change differently. CS: Jana, companies invest heavily in transformation. Yet the impact often falls short of expectations. In your experience, why is that?

Jana Mller: The vision and the corresponding strategy often aren't the problemprovided they focus on areas where they can have a tangible effect on business success, in other words, where value can be created. In many companies, it's fairly clear where they want to go, or even where they have to go.

The real challenge often lies in reconciling sound strategies with the individual realities of a company, and in building and sustaining buy-in across the organization. To do that, the strategy, goals, value drivers, and priorities all need to be clear and translated into operational decisions. People want to understand and help shape the direction; when decisions are made for them instead of with them, and when goals aren't clear enough, energy is lostand with it, impact. Transformation inertia and employee resistance are common reasons why transformations fail.

Between the target vision and day-to-day operations, organizations often lack the ability to realistically assess the scale of change required and the organization's capacity to adapt, as well as to continuously respond to shifting conditions. Equally, it's often underestimated how important it isbeyond setting clear goalsto structure transformation initiatives appropriately within the organization, plan them carefully, and manage them professionally. This is where many initiatives stall. Not because of missing or poor ideas about the company's future direction, but because translating those ideas into the company's concrete reality and managing implementation alongside day-to-day business doesn't succeed well enough. CS: Why does this happen so oftenare companies doing something fundamentally wrong?

Jana Mller: Many companies still treat transformations like a traditional project or programwith a beginning, an end, a clearly defined scope, and the assumption of stable conditions. But that's not what reality looks like. Within companies, multiple initiatives are intertwined, priorities shift, new requirements emerge, and conditions change. Clean project plans, experienced project managers, and elaborate capacity planning alone are no longer enough to handle this. What's missing is a robust implementation and governance logic that views these initiatives within the company's overall context. CS: What does that mean in concrete terms?

Jana Mller: Company leadership needs to keep the goal clearly in sight, communicate the change credibly, and lead by example. At the same time, they have to manage the entire transformation portfolio, set priorities, and quickly course-correct when needed. Because transformation only succeeds when goals are translated into the organization and initiatives are consistently aligned with one anotherdespite dependencies, limited capacity, and competing budgets. CS: So is this more of a structural issue than a methodological one?

Jana Mller: Yes, absolutely. Many companies today work with good methods and have launched the right initiatives. The problem tends to arise where everything has to come together. That's why many organizations initially believe they have an execution problem. But that diagnosis often falls short. In reality, what's usually missing is the ability to manage change across the board and align it consistently. Transformation often fails not because of individual teams or ideas, but because changes at the organizational level are no longer brought together cleanly and aligned consistently with the strategy. In many cases, external support is needed to build this capability. CS: How does this gap between strategy and execution show up in practice?

Jana Mller: The key aspects are translating the strategy into actionable initiatives and managing them along the way. On paper, much of it looks coherent at first. In most cases, there are target visions, roadmaps, and clearly defined initiatives. In reality, though, things often look different. Conditions change without it being clear how this affects ongoing initiatives; decisions take longer than planned or aren't made at all. Coordination efforts increase, and teams set their own priorities, which means they unintentionally end up working in different directions. That's exactly what eventually pushes many organizations to their limits. And it's not uncommon for the question to arise then whether the initiative should have been set up differently from the start. CS: Many companies are betting heavily on agility. Isn't that the answer to dynamic times?

Jana Mller: Agility definitely helps. But applying it only in isolated areas isn't enough here. Agile teams can respond to change faster, make decisions closer to day-to-day operations, and implement initiatives more flexiblythat's a good thing. The problem in companies begins where many changes are happening at the same timeand this is exactly where agility can show its full effect. In practice, we often see the following: individual teams work very well, initiatives are set up sensibly, and yet, in the end, the shared direction is missing. Then things happen in many places, but not necessarily what matters most for the company as a whole at that moment.

By introducing scaled agility, companies extend agile ways of working to multiple teams, divisions, or even the entire organization, making an important contribution to better governance across the organization as a whole. This brings them a big step closer to the goal of improving their overall transformational capability. Because ultimately, transformational capability is what determines how changes are jointly managed and aligned across teams, divisions, and initiatives. CS: What does it actually look like in companies when this capability is missing?

Jana Mller: The system becomes overwhelmed and loses direction, and change turns into constant stress. Teams work on an ever-growing number of new topics at the same time, priorities are set independently and shift constantly, and decisions drag on or aren't made at all. Communication overhead rises, a lot of energy goes into coordination instead of execution, and the conversation revolves around problems rather than their solutions. From the outside, this often looks like a high level of activity. Internally, however, frustration takes over: employees lose motivation, get sick, or quit. The corporate culture suffers, and customers often leave. As a result, companies lose their operational stabilitywhich is critically important for handling both day-to-day business and new challenges. CS: What do companies where transformation works better do differently?

Jana Mller: They accept reality, don't treat transformation as a state of emergency, and work continuously to improve their transformational capability. There, changewhether driven by new conditions or by internal initiativesis a natural part of day-to-day business.

That's why these companies invest not only in individual initiatives, but also in their ability to bring change together more effectively as a whole. They communicate their vision and strategy clearly across the entire organization. They're honest with themselves, assess their transformational capability realistically, and factor that assessment into how they plan their initiatives.

At the same time, they look at their entire portfolio and align it consistently with the strategy. They analyze dependencies and chains of impact, turn them into clear priorities, and communicate these transparently. On this basis, decisions are made that gain acceptance and are then followed through consistently in action. Beyond that, they make dependencies visible and reach decisions faster and more decisively. These companies make wrong decisions too. The difference, though, is that they learn from them.

They put people at the center and work in a way that fosters a culture grounded in shared valuesone that gives everyone a sense of direction. This culture is characterized by a strong willingness to learn and by leadership that builds trust rather than fear. CS: Many people would probably say now: this sounds like more processes and more governance. Doesn't that actually make a company slower?

Jana Mller: A lot of people are wary of that at first. But that's not really the point. Often, organizations aren't slowed down by too much governance, but by unclear decision-making paths, unclear priorities, and a lack of conflict resolution. When that clarity is missing, unwanted friction arises. Good governance therefore doesn't create more bureaucracyit creates direction and the ability to act, and with that, speed. CS: So has the ability to transform become a core competency in itself?

Jana Mller: Yes, absolutely. In fact, the ability to deal with change, organize it well, and drive it forward with combined efforts is increasingly becoming a central competency for companies. The good news is: transformation competency grows with every successful change, and it can also be supported through targeted organizational development programs, for example. Companies with strong transformational capability can adapt to changing conditions faster, implement change more effectively, and thereby strengthen their efficiency, innovative power, and long-term viability. CS: What does that mean concretely for companies? What would they need to do differently?

Jana Mller: Many companies react to problems reflexively with the next program or the next initiative. Yet often what's missing isn't another initiative, but the ability to bring the changes already underway together in a meaningful way and steer them toward the desired outcome.

That's why companies should initially focus less on new initiatives and instead assess their own transformational capability. How well do they currently manage to set priorities, make dependencies visible, reach decisions, and steer change across the board? The answers to these questions usually reveal very quickly where the greatest leverage lies.

What's decisive isn't just what companies want to change, but whether they can actually steer change effectively under real-world conditions. And that's exactly what their competitiveness will hinge on going forward. Sie mchten wissen, wo KI in Ihrem PMO den grten Mehrwert schafft? 

Nehmen Sie gerne Kontakt mit uns auf. 

Learn more

Why Communication and Change Management are now core elements of modern project delivery. Table of Contents

Communicate Early and Authentically Instead of Waiting for PerfectionFoster Dialogue, Not One-Way CommunicationCreate Clarity, Not Just Share InformationTarget Stakeholders, Dont Treat Everyone the SameEngage Leaders, Dont Just Inform Them Theres rarely a shortage of communication formats in transformation initiatives: status updates, project newsletters, and regular check-ins are all part of day-to-day project work. And yet, misunderstandings persist, resistance often surfaces too late, or changes simply fail to reach the organization.

Transformations rarely fail due to a lack of informationits usually because stakeholders dont understand the underlying rationale, cant make sense of developments, or are brought in too late.

If communication ultimately determines whether people understand, accept, and support change, it can no longer be seen as a supporting activity. It is a critical success factor for transformation initiatives.

This also expands the role of the Project Management Office / Project Office in transformation initiatives (hereafter referred to as PMO). In addition to coordinating timelines, dependencies, and risks, communication, facilitation, and stakeholder management are now core responsibilities of modern PMOs. They provide orientation, make changes understandable, and foster acceptance as well as sustainable implementation. PMOs are therefore not just project coordinatorsthey act as a vital link between the initiative and the organization.

As a result, communication and change management are not topics that can simply be supported or coordinated. They are part of the core service portfolio of modern PMOs and must be understood as an integral part of project delivery from the very beginning.

The following five approaches highlight what matters most in practice. There is rarely such a thing as communicating too earlybut often as communicating too late. Especially in transformation initiatives, target states evolve iteratively. Strategies are refined, requirements adjusted, and decisions recalibrated. This is not a sign of poor planning, but a natural part of complex change initiatives.

Even so, this often creates uncertainty among employees and stakeholders. When PMOs wait until every detail is finalized, they leave room for interpretation, rumors, and speculation. Communication should therefore start earlynot with fully formed answers to every question, but with a clear sense of direction. People dont necessarily need complete certainty. In a world where information is always accessible, what they expect most is transparency and orientation. They want to know what has already been decided and which questions are still open.

At the same time, trust is not built by communicating only positive or fully resolved information. Especially during challenging project phases, employees expect an open and transparent approach to uncertainty, competing priorities, and change. Avoiding difficult topics or waiting for the perfect moment can undermine credibility and acceptance.

For PMOs, this means starting communication early and remaining transparent even when not all answers are available. Authentic communication creates clarity and trust. It makes visible what decisions have been made, which questions remain open, and what the path forward looks like. Communication doesnt end with sending a message. Transparency emerges where questions, discussions, and feedback are possible. For transformation initiatives, this means that employees need the opportunity to ask questions, raise concerns, and understand decisions. This is the foundation for acceptance and active engagement.

What matters is not just the existence of dialogue formatsemployees also need to feel encouraged to use them. This requires an environment in which questions, uncertainties, and critical feedback can be expressed without negative consequences. This kind of psychological safety is a key prerequisite for effective participation.

Communication doesnt end with a meeting or a major announcementin many cases, thats where the real dialogue begins. Follow-up conversations reveal how messages have been understood, which questions remain, and where misunderstandings or concerns still exist.

For PMOs, this feedback provides valuable steering insights. It highlights where communication efforts need to be adjusted, decisions need to be better explained, or project activities need to be refined. Orientation is not created through isolated communication efforts, but through continuity. Much of what has been discussed within the project team for months only gradually reaches the broader organization. This is exactly why its not enough to share information at specific points in time. Communication needs to provide context, explain interdependencies, and make developments understandable throughout the entire lifecycle of an initiative.

For PMOs, this means treating communication as an integral part of project delivery. Just like timelines, risks, or dependencies, communication activities must be planned, managed, and continuously refined. The PMO plays a central role in this: aligning communication efforts with project planning, ensuring consistent messaging, and creating transparency around progress, decisions, and change.

Communication thus becomes an ongoing processone that provides orientation and makes change understandable step by step. Not all stakeholders need the same information. Employees, managers, functional teams, and project teams view change from different perspectives and are affected to varying degrees. Treating all target groups the same risks misunderstandings, information gaps, or a lack of relevance.

Employees primarily want to know: What is changing? Why is this happening? And what does it mean for my day-to-day work? Effective communication answers these questions for each target group and takes their differing information needs into account.

This requires the right formats, clear and accessible language, and consistent communication throughout the entire initiative. Consistent terminology and audience-specific messaging help make change tangible and highlight its relevance for different stakeholders. Transformation initiatives are not implemented by the project team alonethey are realized within the organization. Leaders play a key role in this process. They translate change into the day-to-day work of their teams, address questions, and help make sense of decisions. In many cases, employees trust the perspective of their direct manager more than official project communications.

When leaders are only informed after messages have already been communicated, organizations miss out on one of the most important communication channels in the initiative. Modern PMOs recognize this role early on and deliberately integrate leaders into their communication planning. This creates communication cascades that do more than simply distribute informationthey build understanding and provide clear direction. Successful communication is not a supporting activityit is an integral part of effective project delivery. It ensures that decisions are understood, changes are put into context, and people are actively engaged in the transformation. Anyone aiming to successfully steer transformation initiatives must therefore plan communication with the same rigor as timelines, budgets, and risks.

In this context, the PMO plays a central role as an orchestrator, translator, and connecting link between the initiative and the organization. Communication and change management are not value-added extrasthey are part of the core responsibilities of modern PMOs and must be actively planned, managed, and continuously refined. Only then can change be sustainably embedded within the organization. Sie mchten wissen, wo KI in Ihrem PMO den grten Mehrwert schafft? 

Nehmen Sie gerne Kontakt mit uns auf. 

Learn more

AI works. Pilot projects show results. And still, the real impact doesnt materialize. The issue is rarely the technologyits how organizations structure AI. Table of Contents

From Pilot to ImpactUnderstanding the Root Causesand Their ImplicationsLack of Clear GovernanceData and Integration as BottlenecksArchitecture Without a Clear Target StateAI as a Project Rather Than a ProgramWhat Successful Companies Do DifferentlyConclusion In many organizations, AI is already in useyet the value it creates remains limited. According to the MIT study The GenAI Divide: State of AI in Business 2025, 95 percent of generative AI pilots fail to deliver measurable impact on revenue or profitability. The reason is rarely the technology itself, but rather how companies organize AI, embed it into processes, and scale it across the business.

With Microsoft Copilot Wave 3, this challenge is moving further into focus. While Wave 2 primarily addressed individual productivitypositioning Copilot as a personal assistant in Teams, Outlook, or WordMicrosoft is now fundamentally expanding its approach: Copilot is becoming a platform for integrated agents and cross-process automation. At the same time, another development is becoming increasingly evident: the use of powerful AI capabilities and autonomous agents can no longer be viewed solely as a licensing topic. With usage-based pricing models for certain AI services, cost control, value tracking, and prioritization are moving to center stage. Organizations therefore need to decide not only where AI can be deployed from a technical perspective, but also where it delivers measurable value to enterprise-wide performance.

However, achieving this requires more than technology. The more AI is embedded in cross-functional processes, the more critical governance, data availability, integrated workflows, and clear ownership become. In many cases, the technology is evolving faster than the organizational structures required to scale it effectively. Use cases emerge where there is a clear, tangible needwithin individual business functions and close to their processes. Teams develop solutions that work well within their specific context. A common pattern: marketing teams automate content creation with Copilot, sales builds its own agent for proposal processes, and HR develops solutions for onboarding workflows. Each solution works effectively within its own domain and delivers visible value there.

However, as soon as end-to-end processes come into play, these isolated solutions begin to reach their limits. Systems are not aligned with one another, permission models do not integrate seamlessly, and processes are not designed holistically.

As a result, these approaches remain confined to individual functions. Learnings are not systematically transferred, and broader evolutionor integration into interconnected processesrarely takes place.

As integration across chained processes increases, this tension turns into a structural challengeone we see in many client engagements: a single solution works, but as soon as three functions share the same process, the chain breaks. These root causes rarely appear in isolation; instead, they tend to reinforce each other. Without clear guardrails, parallel solutions begin to emerge. Teams develop their own use cases and agents without alignment or prioritization. At the same time, binding approval processes for production deployment are often missing. As a result, solutions remain stuck in pilot phases or are not scaled further due to uncertainty. Responsibilities remain unclear, and standards evolve inconsistently. In practice, this leads to similar solutions being developed multiple timeswith varying quality and little to no reuse.

Microsoft addresses this challenge with Wave 3. Agent 365 introduces a centralized control layer and provides transparency into which agents are in use, what they are used for, and under which rules they operate.

The use of Cowork also requires clear guardrails, as it is capable of executing actions autonomously and across applications. The potential is significant. At the same time, however, the demands on governance increase. Organizations must not only ensure that agents operate in compliance with policies and that sensitive information is protectedthey must also be able to assess which use cases actually deliver value. This question becomes even more important as usage-based pricing models continue to expand. Governance therefore extends beyond compliance and risk management to include the economic steering of AI: Which agents are being used? Where are costs incurred? And what business value do individual use cases create?

Flat, one-size-fits-all allocation of budgets or credits falls short in this context. Successful organizations deliberately prioritize where automation delivers measurable impactsuch as reducing bottlenecks, lowering manual effort, or creating additional capacity. This is an important foundation. However, it does not replace the need for a clear organizational decision on who owns AI governance and how prioritization is actually managed. Much of the relevant data is either unavailable or not usable. It is fragmented across different systems, incomplete, or accessible only to a limited extent. While AI agents can be implemented from a technical standpoint, they often operate with too limited a context. As a result, outputs remain superficial or require manual supplementation.

The bottleneck, therefore, is not the AI itself, but the underlying data foundation and its accessibility. This is where many organizations are currently rethinking their approach: integrating relevant data is increasingly seen as a critical prerequisite for enabling true end-to-end automation through agents. At the same time, many organizations are still in the early stages of this integration. Data is distributed across systems, permissions are inconsistently managed, and connections between datasets are difficult to establish.

With Wave 3, this challenge becomes more critical in two ways. First, context-based assistance can only deliver value if the underlying data is complete and accessible. Second, as the use of agents increases, questions arise around which data an agent is allowed to access and use. Without clear data classification and access controls, risks emerge that go beyond quality issues alone.  The effort required to integrate systems, data flows, and permissions afterward is significantand increases with every use case built without a target state in mind. With Wave 3, cross-process workflows and integrated agents are moving further into focus. This requires consistent alignment across all layers. An architecture designed for isolated, standalone solutions will not be sufficient in the long term.

Building without a clear target state today creates integration overhead tomorrowultimately offsetting the efficiency gains that AI is meant to deliver. In many organizations, AI is still managed as a time-bound project. Individual use cases are identified, implemented, and then considered complete. While this often results in working solutions, they typically remain limited to their specific context.

At the same time, key initiatives run in parallel: HR trains employees, IT defines policies, and business units develop their own use cases. Whats missing is the connection between these efforts. There is no shared target state, no consistent prioritization, and no clear ownership for further development beyond individual use cases.

This is precisely where the challenge for scaling arises. AI does not create value in isolated solutions, but through the interplay of use cases, data, processes, and organization. When managed as a project, responsibility often ends with implementation. Systematic evolution, reuse, and scaling rarely take place.

A program-based approach, by contrast, pursues a different objective. AI is not treated as a one-off initiative, but as a capability continuously built within the organization. Use cases are not considered in isolation, but are developed, prioritized, and advanced in alignment with shared goals. Responsibilities are anchored over the long term, and progress is managed through clear metrics. This includes governance mechanisms such as OKRs, which link business objectives, AI initiatives, and measurable outcomescreating transparency around the actual contribution of individual efforts.

What all four root causes have in common is the lack of this overarching approach in many organizationsone that brings together technology, organization, and processes. As AI becomes increasingly embedded in operational workflows, this evolves from an efficiency issue into a strategic vulnerability. These challenges cannot be addressed through technology alone. Successful companies therefore go beyond tools, transforming how AI is used and managed across the organizationon two levels. Governance, data quality, and architecture determine whether scaling is effective. Microsoft provides the technology with Wave 3. But the more AI is embedded in operational workflowsand the more usage-based costs come into playthe more critical organizational maturity becomes. Organizations must make clearer decisions about where AI is deployed, the value it creates, and who is responsible for steering its development.

This is exactly where we at Campana & Schott support our clients: with a structured approach that brings together technology, enablement, and organization. If you want to understand what the next steps toward scaling AI should look like in your organization, get in touch with us. Sie mchten wissen, wo KI in Ihrem PMO den grten Mehrwert schafft? 

Nehmen Sie gerne Kontakt mit uns auf. 

Learn more

Generative AI has moved from experimentation to everyday practice in many organizationsoften faster than governance structures and responsibilities can keep up. At what point does routine AI use become a risk no one anticipated? Table of Contents

The Expensive Wake-Up CallAI Growth Beyond IT OversightHigh Adoption, Limited Business ValueAdoption Is Not the Same as ScaleThe First Step: Understand Your Current State Most AI success stories start the same way: a pilot delivers promising results, enthusiasm builds, and confidence grows that the technology has long-term potential. As early wins accumulate, broader adoption quickly gains momentum. What begins as experimentation is steadily becoming part of day-to-day business operations.

The latest Swiss Social Collaboration Study, based on responses from more than 200 executives, highlights this trend. Nearly 59 percent of German organizations have already invested in generative AIan increase of roughly 20 percentage points compared to two years ago.

As adoption expands, a fundamental shift takes place. AI becomes routine. More teams rely on it for more tasks, across a growing range of use cases and decisions. Yet while usage becomes commonplace, governance often does not. More than 80 percent of organizations using AI remain stuck in isolated pilots and limited use cases. The structures required to manage AI at scale are frequently missing. And wherever adoption grows without governance, control gradually erodes. Organizations rarely address this gap proactively. Governance usually becomes a priority only after something goes wrong: an unexpectedly high bill caused by excessive token consumption, infrastructure capacity reaching its limits, or a noticeable decline in output quality.

Security risks often accumulate quietly in the background. Rising costs, by contrast, tend to attract immediate attention from IT.

The opposite problem is equally common. Concern about risks can lead organizations to restrict broader AI adoptionparticularly the deployment of AI agentsinstead of putting the right governance mechanisms in place to enable it safely. As a result, the next stage of AI-driven transformation remains out of reach. At that point, governance becomes unavoidable.

That does not necessarily make it appealing. For many, governance means endless planning meetings, lengthy policy documents no one reads, and the challenge of regulating a technology that evolves almost daily. But postponing the conversation is increasingly risky. AI is no longer a future topicit is already part of operational reality. The push for greater AI adoption often originates at the executive level. What is frequently missing, however, is a clear roadmap that translates ambition into measurable objectives. Business units experience this lack of direction most directly. Employees see every day where processes are slow, where repetitive work consumes valuable time, and where better outcomes seem achievable. Unsurprisingly, many begin experimenting with AI themselves and integrating it into their daily work.

In principle, that is a positive development. The people closest to the process are often best positioned to identify valuable applications. When they can streamline recurring tasks without relying on lengthy IT processes, tangible benefits emerge quickly. Over time, these efforts often lead to the creation of small, highly practical AI tools.

Challenges arise when this innovation happens without a shared framework. Consider an employee in accounts payable who develops an AI agent to help prepare invoices. The tool works well. Colleagues adopt it, word spreads, and before long an entire team depends on it. What started as an individual productivity tool has become a business-critical process. Yet IT may have no visibility into it. Questions remain unanswered: What data does the agent access? Who can view the output? When is human review required? How is the solution protected against misuse or attack? And can a tool originally designed for a single user reliably support a growing business function?

Without IT involvement, both development and ongoing operation may depend on a single individual. This rarely remains an isolated case. In one scenario, no one takes responsibility when an AI agent produces incorrect results. In another, employees upload company data through personal accounts into tools that use the information to further train their large language models. Viewed individually, such incidents may appear manageable. Taken together, they reveal a broader issue: AI adoption has begun to outpace the organizations ability to govern it. Over time, the absence of governance affects more than risk managementit also limits business impact. Broad adoption alone does not create value. Deloittes recent The ROI of AI study illustrates this clearly. While Germany ranks among the leading countries in AI adoption, only a small share of organizations use AI to fundamentally redesign processes or business models. Most benefits remain confined to operational efficiency gains.

The challenge is rarely the technology itself. More often, it is the depth of integration. Organizations that want to generate meaningful value must move AI beyond personal productivity and embed it directly into core business processes. Measurable return on investment emerges when AI supportsor takes overcritical operational activities. This level of integration requires structure. As soon as AI becomes part of a business-critical process, clear ownership is essential: ownership of outcomes, regulatory compliance, internal policy adherence, and incident response. These responsibilities are difficult to establish when solutions emerge independently across departments. At the same time, fragmented experimentation prevents organizations from realizing broader benefits. When every department develops its own solution, value remains local. Without shared standards and reusable approaches, teams repeatedly solve the same problems instead of building on each other's success. Viele relevante Daten sind nicht verfgbar oder nicht nutzbar. Sie liegen fragmentiert in unterschiedlichen Systemen, sind unvollstndig oder nur eingeschrnkt zugnglich. KI-Agenten lassen sich technisch zwar umsetzen, arbeiten jedoch hufig mit einem zu begrenzten Kontext. Ergebnisse bleiben oberflchlich oder mssen manuell ergnzt werden. 

Der Engpass liegt damit nicht in der KI selbst, sondern in der Datenbasis und deren Zugnglichkeit. Genau hier zeigt sich aktuell in vielen Unternehmen ein Umdenken: Die Integration relevanter Daten wird zunehmend als entscheidende Voraussetzung verstanden, um Prozesse berhaupt End-to-End ber Agenten automatisieren zu knnen. Gleichzeitig stehen viele Organisationen bei dieser Integration noch am Anfang. Daten liegen verteilt in unterschiedlichen Systemen, Berechtigungen sind nicht konsistent geregelt und Zusammenhnge lassen sich nur eingeschrnkt herstellen. 

Mit Wave 3 wird dieser Punkt kritischer, und zwar in zwei Richtungen. Erstens entfaltet kontextbasierte Untersttzung ihren Wert nur dann, wenn die zugrunde liegenden Daten vollstndig und zugnglich sind. Zweitens stellt sich mit zunehmendem Agenteneinsatz die Frage, welche Daten ein Agent berhaupt verwenden darf. Ohne klare Datenklassifizierung und Zugriffskontrollen entstehen Risiken, die ber reine Qualittsprobleme hinausgehen.  The cost dynamic is changing as well. Many AI services have benefited from significant vendor subsidies to date, but pricing is gradually moving closer to the true cost of operation. Expenses that were negligible during experimentation can become significant at enterprise scaleparticularly when there is no oversight of which tools and models are being used across the organization. As a result, insufficient governance becomes a tangible business risk. It affects not only data security, but also an organization's ability to scale successful AI initiatives. More ambitious opportunities, such as data-driven products and new business models, remain out of reach. 

Organizations hoping these issues will resolve themselves are likely to be disappointed. Demand from business teams continues to grow, and the longer governance lags behind, the wider the gap becomes. The encouraging news is that getting started does not require a comprehensive governance framework or a fully developed operating model. The first steps are often much more pragmatic. How these insights translate into concrete next steps for scalable AI governance is the focus of Part 3 of this series. Effective governance begins with visibility. Across many organizations, business units are already experimenting with AI, developing use cases, and building practical experience. That is the best place to start. Understanding where AI is already being used makes it easier to identify promising initiatives, address unresolved questions, and make informed decisions about next steps.

In this way, governance becomes more than a control mechanism introduced after the fact. It becomes the foundation that allows successful initiatives to grow sustainably.

In the next article of this series, we explore how initial transparency can be translated into practical guardrailsand why effective governance accelerates AI adoption rather than slowing it down: Guardrails, Not Gateways: How Effective Governance Accelerates AI Adoption.

Sie mchten wissen, wo KI in Ihrem PMO den grten Mehrwert schafft? 

Nehmen Sie gerne Kontakt mit uns auf. 

Learn more

For many organizations, AI governance still carries a reputation for bureaucracy and red tape. It is often viewed as a compliance exercise that slows innovation rather than enabling it. But what separates governance frameworks that help organizations move faster with AI from those that end up as unused policy documents? Table of Contents

Governance Pitfall #1: Overregulation    Governance Pitfall #2: Paper GovernanceThree Levers That Make the DifferenceDont Just Document RulesBuild Them InRules and Roles Only Work When People Understand ThemGovernance Must Evolve Alongside AI  Few organizations instinctively associate AI governance with innovation. More often, it is seen as a control mechanism0 a necessary constraint on the path toward an AI-enabled future.

In reality, however, AI adoption rarely stalls because governance gets in the way. More often, organizations struggle because teams lack the guidance and capabilities needed to use AI strategically. The pace of change is relentless: new models, new capabilities, and new use cases emerge almost daily, making it difficult for traditional structures to keep up. As a result, many employees already use AI to enhance individual productivity. Yet only a small number of organizations successfully make the leap from personal experimentation to embedding AI in business processes and creating value at scale.

This scaling gap represents a significant opportunity for organizations with effective AI governance in place: Rather than slowing people down, it provides employees and IT teams with a clear framework, practical direction, and the confidence to innovate responsibly. The challenge is that defining such a framework is often easier in theory than in practice. So what distinguishes governance that enables speed and innovation from governance that becomes a barrier or disappears into forgotten folders and intranet pages?

Without a clear understanding of what makes governance effective, many organizations fall into one of two common traps. When uncertainty increases, organizations often respond by tightening control. This tendency becomes particularly strong after security incidents, data leaks, or other AI-related risks. What begins as open experimentation can quickly turn into approval workflows, forms, reviews, and rigid processes. While well intended, these measures often produce the opposite of the desired outcome. Decision-making slows down, responsibility shifts upwards, and innovation loses momentum. At the same time, business teams remain under pressure to leverage the latest AI tools to increase efficiency and stay competitive.

This tension frequently leads to the emergence of shadow AI. Employees turn to publicly available tools and access them through personal accounts because approved alternatives are unavailable or internal approval processes take too long. In practice, this often means that sensitive spreadsheets, customer information, or other business-critical data find their way into external AI applications simply because someone needs a quick analysis or a presentation slide. Such actions are rarely malicious. More often, they are pragmatic responses to a lack of accessible, approved solutions.

The result is a growing loss of visibility. IT and AI governance teams no longer have a clear overview of which services are being used across the organization or how information is being processed. This increases security and compliance risks while making it harder for leadership teams to identify and scale high-value AI use cases. The second common mistake occurs when governance exists only in documentation. Organizations invest considerable time creating policies, guidelines, and governance frameworks in workshops, steering committees, and strategy sessions. Yet these documents often have little influence on day-to-day work. A lack of visibility and poor integration into existing workflows are usually to blame.

The symptoms are easy to spot. Problems that governance was intended to addressexcessive token consumption, policy violations, or inconsistent AI usage practicescontinue to occur. Employees repeatedly ask questions that are already covered by official guidelines. Uncertainty about approved tools and acceptable usage persists. In short, daily AI usage remains disconnected from the governance framework.

Both patterns highlight the same problem: governance that exists only as a formal structure is not enough. To support innovation and responsible adoption, governance must become part of how people actually work. Genau diese Einbettung aber gelingt ohne Struktur und Governance nicht. Sobald KI einen geschftskritischen Prozess trgt, muss es klare Ownership geben: fr ihre Ergebnisse, fr die Einhaltung gesetzlicher und interner Vorgaben, fr den Ernstfall. Genau das fehlt, wenn Lsungen unkoordiniert in den Fachbereichen entstehen. Hinzu kommt, dass aus den vielen Einzellsungen kein groes Ganzes entsteht: Wo jede Abteilung ihre eigene Lsung baut, bleibt der Nutzen lokal. Ohne gemeinsame Standards wird das Rad immer wieder neu erfunden, statt gute Lsungen im Unternehmen weiterzuverwenden. Effective governance cannot be achieved by simply attaching instructions to an AI application or adding prompts to a chatbot. Boundaries cannot be enforced through documentation alone. Instead, governance should be implemented directly within the underlying systems and tools. Approved pathways, access rules, and usage restrictions need to be configured so that they are applied automatically. Employees should still understand the policies that govern AI usage. Yet in their daily work, they should be able to trust that the software itself prevents prohibited actions from taking place. When guardrails are built into technology, employees no longer need to consult policy documents before every action or hesitate because they are unsure whether something is permitted. This reduces complexity, accelerates workflows, and improves security by preventing mistakes before they occur. At that point, governance is no longer perceived as an additional task. It becomes an invisible, enabling layer operating in the background. Technology alone cannot solve every governance challenge. Even the most carefully designed policy is ineffective if employees are unaware of it or if it fails to fit naturally into the way they work. Successful governance needs to become as routine as any other established business practice. The rationale should be clear, the expected behaviors understood, and adherence reviewed regularly. For AI, this means that guardrails must be visible, clearly communicated, and integrated into the environments where employees actually work. For example, if an AI tool is suddenly blocked without explanation, frustration quickly follows: Why did this work last week but not today? The predictable outcome is an increase in support requests and growing tension between users and IT.

To turn guidance into momentum, organizations also need an environment where questions are encouraged and mistakes can be discussed openly. When employees know where to seek support, they are far less likely to circumvent official processes through personal accounts or unauthorized tools. Dedicated points of contact for AI-related topics, clearly defined responsibilities, and transparent evaluation criteria help organizations implement ideas more quicklywithout requiring every decision to be escalated to senior leadership. Governance is not something that can be defined once and considered complete. It is a continuous process rather than a finished product. Organizations do not need to wait for a perfect framework before taking action. A small number of practical, well-understood guardrails create far more value than an extensive rulebook that nobody reads. What matters is that governance evolves alongside AI adoption. As new tools, risks, and use cases emerge, the governance model must adapt accordingly. The starting point is always the same question:

What do we want to achieve with AI?

The answer determines how much risk an organization is willing to accept and how quickly it can move forward. A technology startup will deliberately allow different levels of experimentation than a bank operating in a highly regulated environment. Organizations that are clear about their objectives are better positioned to strike the right balance between control and flexibility. This is how governance becomes a catalyst for AI innovation. It provides employees with confidence, accelerates decision-making, and helps organizations move promising use cases from experimentation into real-world deployment more quickly. Once this foundation is in place, AI can be scaled in a targeted and responsible way, provided the right building blocks are established early on. Sie mchten wissen, wo KI in Ihrem PMO den grten Mehrwert schafft? 

Nehmen Sie gerne Kontakt mit uns auf. 

Learn more

What AI guardrails should be established now, what can evolve over time, and why governance does not have to slow down AI adoption. Effective oversight is built incrementally through day-to-day operationsoften far more pragmatically than many organizations expect. Inhaltsverzeichnis

Starting Beats WaitingHow Clear Is Your Starting Point?A Practical Starting Point: Where to Focus FirstGet the Basics Right Before ScalingGive Accountability a HomeWhat Scales Next: Enable, Dont RestrictLooking Ahead: From Isolated Solutions to an Agent FactoryActionable Today, Not Perfect Tomorrow Organizations that wait until AI governance is fully designed before defining clear rules pay a double price. AI adoption continues to grow without a clear strategy, while the gap to organizations that have already put the right governance structures in place widens as this scaling gap increases.

In reality, getting started requires only a few essential building blocks: a clear objective for how AI should support the business, a central point of accountability, and teams equipped with the right skills and guidance. With these foundations in place, organizations can start small and refine their approach over time, building a governance framework that evolves alongside AI adoption. Think big, start small. Before defining new policies, it is worth taking a reality check. A few practical questions often reveal where governance is missingand where solid foundations may already exist. Genau diese Einbettung aber gelingt ohne Struktur und Governance nicht. Sobald KI einen geschftskritischen Prozess trgt, muss es klare Ownership geben: fr ihre Ergebnisse, fr die Einhaltung gesetzlicher und interner Vorgaben, fr den Ernstfall. Genau das fehlt, wenn Lsungen unkoordiniert in den Fachbereichen entstehen. Hinzu kommt, dass aus den vielen Einzellsungen kein groes Ganzes entsteht: Wo jede Abteilung ihre eigene Lsung baut, bleibt der Nutzen lokal. Ohne gemeinsame Standards wird das Rad immer wieder neu erfunden, statt gute Lsungen im Unternehmen weiterzuverwenden. If these questions remain unanswered, that is not a sign of failureit is a valuable starting point. They highlight areas where important topics remain unaddressed and where solid foundations already exist for a governance approach that provides guidance rather than creating barriers. Organizations looking to accelerate this assessment process or establish a prioritized roadmap more quickly may benefit from external support, such as an AI Governance Check-Up. An assessment should not lead directly to a comprehensive rulebook. It should lead to a roadmap. Some governance requirements only become relevant as AI adoption matures and can therefore be introduced later. Measures that immediately reduce risk should be addressed first. For many organizations, that means focusing on two fundamentals: platform security and clear ownership. The first steps are rarely glamorous. Before designing sophisticated governance processes, it is worth reviewing the default settings of existing platforms. Many AI and automation environments are surprisingly open out of the box. Users can often create new workspaces, connect tools, and integrate data sources with few restrictions. Closing these unnecessary access points eliminates a significant number of security risks and helps prevent the uncontrolled proliferation of solutions that can become difficult to manage later. In most cases, IT teams can address these issues within days or weeks.

The next step is to create an inventory of what is already in use. Which AI tools and agents are currently running? Who developed them? How critical are they to business operations? This visibility enables informed decisions about which solutions can continue as they are, which require modifications, and which should be retired or brought into a structured governance framework. Priority should be given to applications that access sensitive data or support business-critical processes. For individual decisions to translate into reliable governance, accountability needs a permanent home within the organization. In practice, this is usually a small cross-functional team. In many organizations, this takes the form of a Center of Excellence (CoE).

The CoE serves as the central hub for AI-related topics, reviews requests from business units, and determines what can be implemented and under which conditions. This prevents every decision from being escalated to senior leadership and ensures that AI becomes a shared responsibility rather than remaining solely an IT concern.

IT, business teams, security, compliance, risk management, and data protection functions all contribute to this governance model. Building such a structure requires time and investment. Yet it is often a highly effective investment. According to the Swiss Social Collaboration Study, only 6.2% of organizations currently have a centralized AI governance function such as an AI Office. This represents a significant implementation gap, especially considering that nearly 80% view cross-functional AI governance as necessary.

Organizations that establish these foundations early gain a meaningful advantage. Decisions can be made faster, successful approaches scale more easily, and organizational maturity increases while others are still debating ownership and responsibilities. Once the first governance guardrails are in place, success depends on how governance works in everyday practice. Teams need clarity about what they can do independently, when support is required, and which scenarios demand stricter oversight. Policies alone are not enough. Organizations also need enablement, clear decision criteria, and technical controls that provide practical guidance. One effective approach is a tiered modelessentially an AI competency framework. 

Employees who demonstrate a solid understanding of AI fundamentals can build and deploy simple applications independently. More advanced agents, additional data sources, or solutions with broader organizational impact require higher levels of qualification and governance. This allows autonomy to grow with capability rather than applying the same restrictions to everyone. At the same time, IT teams are freed from reviewing every individual use case. The nature of the use case also matters. 

An agent that helps a single team automate routine tasks can typically operate with minimal oversight. A solution that influences decisions, processes customer data, or interacts with core business processes requires a more rigorous governance framework. When these distinctions are clearly defined and embedded in technical controls, initiative remains an asset rather than becoming a source of risk. Different governance levels create structure and confidence without slowing innovation. As organizations mature, governance is no longer just about enabling individual initiatives safely. The focus shifts to making successful approaches reusable and scalable. An Agent Factory can be a natural next step. It provides a centralized environment for validated building blocks, templates, approved data integrations, and reusable agents. Teams no longer have to start from scratch every time. Instead, they build on proven capabilities that have already demonstrated value.

Security, traceability, and accountability are embedded into these reusable assets from the outset. Once established, this model can gradually be extended across the entire AI landscapefrom individual agents and Copilot solutions to more advanced AI applications. The result is a shared framework where new use cases are no longer developed in isolation but are orchestrated centrally and continuously improved across teams and business functions. Effective AI governance starts with a handful of clear decisions that provide direction. Everything else can evolve from there. The objective is not to regulate every aspect of AI from day one, but to ensure it remains manageable, transparent, and controllable as adoption grows. Organizations that move early create room to innovate. They can continue advancing their AI capabilities without losing oversight and respond to emerging requirements before they become challenges.

The simplest way to get started is through an AI Governance Check-Up. In a focused workshop, we assess your current situation, identify and prioritize the most important areas for action, and develop a tailored governance roadmap that defines the next steps for your organization. Sie mchten wissen, wo KI in Ihrem PMO den grten Mehrwert schafft? 

Nehmen Sie gerne Kontakt mit uns auf. 

Learn more