Workflows must have a benefit

Every workflow and process you have has a cost, including the following:

• Managing your infrastructure as code as part of your development workflow
• Creating project and solution design documents and getting wide feedback as part of your project workflow
• Running automated tests with CI/CD as part of your deployment workflow

Each of these slow down delivery:

• Infrastructure as code is slower than having admin permissions and making the changes directly
• Gathering requirements, defining a clear definition of done, getting stakeholder feedback, etc, takes time and delays starting the implementation
• CI checks take time and when they fail they prevent code from being deployed

But they’re all there for a reason, because they help us get achieve a better outcome at lower overall cost/risk to the business.

If your data contracts workflows don’t demonstrably lead to better outcomes and lower overall costs/risks then they are not worth doing.