Taking over a compliance portfolio has a specific trap. You need to get fluent in the regulatory detail fast, but if you slow engineering down while you ramp, you've become the exact bottleneck you were brought in to clear.
I separate the two jobs in the first weeks. Job one is learning the regulatory landscape, the commitments, the deadlines, the real exposure. Job two is keeping the existing work moving. I protect job two by not inserting myself into flows that already function. New owner does not mean new approval step.
For job one I go straight to the issues, not the policy documents. The open regulatory items show you where the real risk and the real friction live, far faster than reading the framework top to bottom. The policy makes sense once you've seen what it's actually catching.
At Intuit this approach let me build the issue lifecycle framework while the portfolio kept running, and I hit 96-plus percent on-time closure with a 31 percent backlog cut. The framework helped because it aligned regulatory commitments with the product and engineering roadmaps instead of fighting them. Compliance that fights delivery loses. Compliance that sequences with it wins.