Citizen Dev & Power Platform: Why Governance Is Non-Negotiable

The promise of Citizen Development is appealing: let business teams build simple applications themselves, responding quickly to their needs without mobilizing the entire IT department.

In this article, we’ll focus mainly on Citizen Development with Microsoft Power Platform, because it’s currently the most widespread platform in companies already anchored in the Microsoft ecosystem.

What is citizen development?

Citizen Development is the idea that non-developer employees build applications themselves to meet their own business needs.

This is nothing new. Back in the 1990s, many companies used Access to set up their own databases. Then Excel and its VBA macros became the go-to tool for automating calculations, managing processes, or building reports.

These local solutions had two advantages: a fast response to needs, and a degree of autonomy from the IT department. But they also came with limitations: critical yet unsecured files, dependence on a single person “who knows,” and difficulty maintaining them over the long run.

Today, low-code platforms like the Microsoft Power Platform (Power Apps, Power Automate, Power BI, Power Virtual Agents) are carrying the torch. They let business teams build applications that are more robust, integrated with the information system, and easier to maintain than an isolated Excel file.

In fact, many of our clients come to us with the same request: “We have Excel files that have become critical, used by the whole team. We want a real application, because we’ve hit the limits.”

But one thing remains constant: without clear governance, citizen development ends up recreating the very same pitfalls as before.

What criteria should decide whether an application can be built by a citizen developer?

Not every application is suited to citizen dev. The first step in a serious approach is to define clear criteria. Here are a few examples, to be adapted to each company’s context.

1. Functional complexity

• Good candidate: tracking internal stock, managing HR requests, automating simple approvals.
• Poor candidate: a critical, multi-stakeholder process with numerous workflows and deep system integration.

2. Target audience

• Internal: Power Apps is perfect for employees already in the Microsoft ecosystem.
• External: if the application is meant to be used by customers or partners, it’s better to consider other, more suitable solutions.

3. Expected user experience

• Internal use where the UX can stay basic.
• Cases where the user experience is critical. (A little wink: our UX designer doesn’t like Power Platform at all for this very reason.)

4. Number of users

• A few dozen or a few hundred internal users.
• Several thousand users with varied needs: now you’re entering a project that demands more advanced design and stronger governance.

These criteria aren’t exhaustive. Their role is to frame expectations and prevent business teams from launching into projects on their own that exceed the scope of citizen dev.

Licensing and costs: a major point of vigilance

The question of licensing is often underestimated. On the surface, the Power Platform is “already included” in the Microsoft environment, notably through Office 365 licenses. But the reality is more nuanced:

• The basic features let you quickly build simple applications connected to SharePoint or Excel.
• As soon as you want to access premium connectors (ERP, CRM, external databases, business APIs), you have to subscribe to premium licenses.

And costs can skyrocket. Without governance, each department can multiply the applications requiring these additional licenses, resulting in an unanticipated budget explosion.

A joint business / IT approach

Citizen dev shouldn’t be seen as a way to bypass the IT department, but as a joint approach.

• The business teams: they know their pain points and their processes. They’re best placed to imagine fast solutions.
• The IT department: it guarantees security, technical consistency, alignment with the information system, and compliance with budget constraints.

Success comes through an alliance: giving business teams autonomy while letting the IT department play its role as guarantor.

The pillars of effective governance

1. Train the teams

Governance starts with building skills. Training future citizen developers on Power Apps, Power Automate, and Power BI is essential. But it’s not just about technical tutorials:

• Raise awareness of good design practices (user experience, performance, mobile compatibility).
• Explain the platform’s limits to avoid unrealistic projects.
• Provide the basics of security and data management (who can access what, how to secure an API, etc.).

2. Appoint business champions

Rather than letting each employee experiment in isolation, it’s better to designate citizen dev champions in each department.

• These “super users” support their colleagues in designing applications.
• They act as a filter and prevent the proliferation of uncoordinated initiatives.
• They also serve as a privileged point of contact for the IT department, which can focus its support on a few trained and aware contacts.

3. Have an identified contact on the IT side

The ideal model is neither to hand all control to the IT department nor to bypass it. The balance comes through an identified contact on the IT side, responsible for:

• Validating the connectors used and their compatibility with existing systems.
• Checking compliance with security and data governance rules.
• Maintaining a map of the applications built to avoid duplicates and inconsistencies.

This coordination role can be held by a digital factory, an entity that is often already in place.

4. Set up a Starter Kit

Providing a starter kit is a powerful lever for channeling initiatives without stifling them.

• Ready-to-use application templates.
• Standardized documentation templates.
• Common naming conventions.
• Validation checklists before going to production.

Microsoft already offers a “Center of Excellence Starter Kit” that often needs to be adapted to the company’s needs and culture. This reduces the learning curve and ensures a degree of consistency across deliverables.

5. Quality control before going to production

This is the step that’s often overlooked, yet the most important for avoiding disasters. An application can work perfectly well in internal testing but become unusable as soon as it’s deployed to 500 users.

We recommend a systematic quality audit before going to production. At ezacae, we developed Kali, a quality audit tool for low-code applications, which ensures that every application going into production meets a minimum standard and can be maintained over time.

And beyond Microsoft?

The Power Platform is an obvious choice for organizations already in the Microsoft ecosystem. But it isn’t the only option.

• For data-oriented cases, tools like Airtable or Timetonic are powerful and offer great flexibility.
• For applications centered on workflow and task management, solutions like Monday.com, Notion, or Coda make it possible to roll out lightweight tools quickly.

These alternatives show that citizen development is a deep-rooted trend, well beyond Microsoft.

Conclusion: empower business teams, but not without a framework

Citizen dev is nothing new: yesterday Access, then Excel, today Power Platform. The difference is the maturity of the tools and their ability to turn local solutions into genuine enterprise applications. But one rule remains immutable: without governance, you recreate the same problems as before.

Defining clear criteria, establishing a joint business/IT approach, and instituting quality standards is what turns citizen development into a sustainable lever for innovation and efficiency.