Enterprise transformation is rarely a technology problem and almost always an organizational one. The COBOL still works. The mainframe is still cheaper than its replacement on paper. The 800-line stored procedure has tribal knowledge embedded in it that nobody documented. My consulting in this space starts by accepting these realities - you cannot rewrite the core, you have to migrate around it, and you have to do it without breaking the thing that pays for the migration.
The strangler fig pattern is still the right answer most of the time. Identify a bounded context, build a modern service alongside, route traffic incrementally through a façade, and decommission the legacy module when traffic reaches zero. I design these migrations with explicit dual-write windows, shadow-read validation, and rollback gates at every step. Zero-downtime migration is the standard, not a nice-to-have, because the business cannot pause while IT modernizes.
Identity is the foundation everything else stands on. SAML 2.0 and OIDC for human auth, OAuth 2.1 for service-to-service, SCIM for provisioning, mTLS for backend trust. I help enterprises consolidate around a single identity provider - Okta, Entra ID (formerly Azure AD), or Ping - and build the federation primitives that let new SaaS tools onboard in days rather than quarters. JIT provisioning, group-mapped RBAC, and centralized audit logs are table stakes.
Cloud strategy in the enterprise is rarely "lift and shift" anymore. It's a hybrid story - workloads that belong on-prem for data gravity or regulatory reasons, workloads that move to managed services for elasticity, and a control plane that spans both. I architect around Kubernetes as the portability layer, Terraform for multi-cloud IaC, and a clear FinOps practice so the bill doesn't become a board-level surprise. Cloud infrastructure done right is a margin lever, not a cost center.
The hardest part of enterprise work is engineering org design. Conway's Law is real - your software architecture will mirror your communication structure whether you want it to or not. I coach leadership teams on platform-vs-product team boundaries, the right level of decentralization, and how to introduce internal developer platforms that accelerate teams without imposing top-down dogma. See an enterprise modernization story or book time to scope a transformation.