Which action is appropriate when a feature request conflicts with regulatory compliance?

• A. Implement the feature with a workaround.
• B. Escalate immediately to executives and pause development.
• C. Remove the feature from the backlog without analysis.
• D. Assess risk and impact, propose compliant alternatives, escalate to governance, document decision, and obtain sign-off.

Answer: (D)

When a feature request clashes with regulatory requirements, the priority is to manage risk through a formal, traceable decision process. The recommended path is to assess the risk and impact, explore compliant alternatives, escalate to governance, document the decision, and obtain sign-off. This approach ensures you understand exactly what the regulatory constraints are, quantify potential consequences, and identify ways to meet the business need without violating rules. Involving governance brings the right mix of stakeholders—product, legal, security, and compliance—so a well-considered solution can be approved and properly controlled. The documentation provides an audit trail, accountability, and clarity on what was decided and why.

Choosing a workaround can seem expedient, but it often sidesteps required controls and leaves hidden risks or technical debt that may be unacceptable under regulation. Simply escalating to executives and pausing development skips the structured analysis and formal approval that governs compliant changes. Removing the feature from the backlog without analysis avoids the issue but fails to capture the rationale or a path forward, leaving risk unaddressed and future work unresolved.