web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Standard complexity ma...
Power Automate
Unanswered

Standard complexity matrix to define Power Automate process as Small, medium or high

(0) ShareShare
ReportReport
Posted on by

Hi, 
 
My team is planning to develop several processes using Power Automate Desktop, Cloud Flows, and AI Builder. We are looking for a complexity matrix that can help us classify processes as Low, Medium, or High complexity.
 
It would be very helpful if anyone could share a standard complexity matrix or any reference material that we can use.
 
 
Regards,
Srini
 
I have the same question (0)
  • David_MA Profile Picture
    14,956 Super User 2026 Season 1 on at
    Where I work, we don't have a single universal complexity matrix for Power Automate Desktop, Cloud Flows, and AI Builder, but a practical matrix can be built around the factors that most affect delivery effort and risk. In my experience, complexity depends on several things:
    • Process clarity: Are the business goals, inputs, outputs, and process owner clearly defined?
    • Team capability: Does the team already have the skills needed for APIs, connectors, Dataverse, approvals, AI Builder, and desktop automation?
    • Process size: How many steps, decision points, exceptions, and handoffs are involved?
    • Tooling: Does the automation require one tool or a combination of Power Automate Desktop, Cloud Flows, AI Builder, and other services?
    • Technical dependencies: Are premium connectors, custom APIs, SharePoint lists, Dataverse tables, or multiple environments required?
    • Governance and support: Is there a process owner, stakeholder buy-in, and clear support for change and testing?
    • As a simple rule of thumb, a low-complexity process is usually well-defined, uses one main tool, has few steps, and stays within standard connectors. Medium complexity typically involves multiple steps, a few integrations, and some exception handling. High complexity usually means multiple tools, API or premium connector use, custom logic, more approvals, more exceptions, and stronger dependency on team expertise.
     
    The biggest barrier to developing a matrix is that it depends on who is doing the work. Something I think is simple you may think is complex. In addition to the above of course.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard