Consultant| Canarys Automation LtdBangalore, Karnataka, India
Over the years, organizations have invested heavily in templates, playbooks, governance models, and standardized processes to improve predictability and control. While this creates consistency, I sometimes wonder:
At what point does standardization start limiting adaptability, ownership, and innovation?
In your experience:
-- Have you seen standardization accelerate delivery—or slow it down?
-- How do you decide what must be standardized versus what should remain flexible?
-- Does maturity mean more process, or smarter process?
Curious to hear how others strike the balance between structure and agility.
Standardization helps only when it removes noise, not when it restricts judgment. I have seen teams deliver faster with light guardrails and slower with heavy templates. Maturity is not “more process”, it is “just enough” process. Keep core controls consistent, but let teams adapt ways of working to context, risk and stakeholder needs. Saving Changes...
I've seen attempts to standardize slow down delivery, but you shouldn't presume that slowing down delivery is always a bad thing. You're going to run into problems when you start conflating standardization with rigidity. You standardize when variation is costly or causes harm. You standardize predictable routines. You standardize interfaces.
People often want to standardize when dealing with VUCA situations, but when the environment is shifting faster than your rules, trying to enforce standardization is rigidity.
I don't think maturity is about more or smarter processes. I see it more as about knowing when to standardize and when to be flexible; being able to adapt as conditions change. Saving Changes...
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
Standardization helps when it reduces confusion and sets clear expectations. It becomes a problem when people follow templates blindly and stop thinking about context. The key is to keep core controls consistent while allowing teams to adjust how they work based on risk, complexity, and stakeholder needs. True maturity is the ability to apply structure thoughtfully, not automatically. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The big problem is: which does mean agility? To know about that people and organizations must go to the basement: the definition created where agility and agile was "invented" USA DoD/NSF Agility Forum in 1990. I was part of it. Your statement has a mistake, taking as is then I could be wrong: agility is based on architecture, on structure. So, it is not a matter of balance. it is a matter to define the structure with focus on gain on agility. Strategy, no more than that. On the other side, standarization helps a lot to gein into agility. Just the key thing is to decide what to standarize. Saving Changes...
Daniel BarringerPresident| Projects By DesignBluffton, Sc, United States
Standardization is the antithesis of projects; projects by their definition are unique. The Stacey Complexity Model explains this very well. Standardization implies we know what we are going to do and how we are going to do it. If you already know those two things then don't projectize, you can use organizational processes for these things. The tools that projects provide solve for both of those questions and then deliver to the organization to optimize the value that is provided. That is not to deny the need for good practices, the real key for organizations is to a) expand their toolkit in project practices, and b) apply those practices in appropriate delivery patterns that fit the business situation as well as the level of uncertainty as to the "what" and the "how". To answer your question, I have never seen an organization that succeeds in project delivery through standardization, nor a PMO that survives it.
...
1 reply by Eduard Hernandez
Mar 08, 2026 4:14 AM
Eduard Hernandez
...
Daniel, the Stacey Complexity Model can be seen as a framework that helps select one project delivery approach over another, each with its own standards and governance model. Could you clarify why you believe standardization and successful project delivery are not linked?
Product Operations Program ManagerBarcelona, Cataluña, Spain
Mar 04, 2026 3:42 PM
Replying to Daniel Barringer
...
Standardization is the antithesis of projects; projects by their definition are unique. The Stacey Complexity Model explains this very well. Standardization implies we know what we are going to do and how we are going to do it. If you already know those two things then don't projectize, you can use organizational processes for these things. The tools that projects provide solve for both of those questions and then deliver to the organization to optimize the value that is provided. That is not to deny the need for good practices, the real key for organizations is to a) expand their toolkit in project practices, and b) apply those practices in appropriate delivery patterns that fit the business situation as well as the level of uncertainty as to the "what" and the "how". To answer your question, I have never seen an organization that succeeds in project delivery through standardization, nor a PMO that survives it.
Daniel, the Stacey Complexity Model can be seen as a framework that helps select one project delivery approach over another, each with its own standards and governance model. Could you clarify why you believe standardization and successful project delivery are not linked? Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Thoughtful question. Many organizations eventually face this tension as they mature.
Standardization accelerates delivery when it removes cognitive friction. Shared language, clear governance and a few common artifacts help teams coordinate faster and focus on outcomes.
But it slows delivery when it begins to control thinking rather than support execution. When templates become bureaucracy, teams optimize for compliance instead of results.
A useful principle is to standardize the architecture, not the behavior.
Standardize governance, decision rights and core metrics. Keep how teams deliver flexible.
In mature organizations, standards exist to support judgment and better decisions, not to replace them. Saving Changes...
Community Champion
