I see risk appetite as a choice about what a business is willing and able to lose in pursuit of its goals. Renewing a fragile platform or postponing recovery work allocates capital while leaving exposure behind. “Zero risk” cannot guide that allocation. I want finance and security to explain which losses the business can carry, with what resources and obligations.
Separate willingness from capacity
Appetite expresses a preference; capacity sets a boundary. Forecast revenue is not emergency cash, and a recovery plan is useful only if its people and systems remain available. I would set limits by function, consequence and duration. A tolerable interruption in an optional sales channel may be unacceptable in payroll. Being able to pay for a failure does not grant permission to compromise duties to people or binding commitments.
Describe the loss before the control
For each consequential scenario, I would bring together operational impact, a rough loss range, a recovery target and the full cost of reducing exposure. Assumptions must remain visible. Restoring application access differs from restoring trustworthy transactions, normal throughput and reconciled accounts. A proposal should explain whether it prevents failure, limits its reach or shortens disruption. Its cost includes staffing, upkeep and displaced work.
Make the capital choice explicit
Imagine a distributor choosing between expanding a warehouse and improving order recovery. Manual dispatch might keep some deliveries moving while incomplete records delay invoicing. I would compare the expansion’s opportunity with the exposure left by postponing recovery, rather than treating that exposure as free. Phasing expansion or protecting transaction records first could preserve flexibility. But a cheaper fallback adds little if it shares the dependency that disables the primary system. The decision needs evidence of what changes and what remains exposed.
Follow cash and shared dependencies
I would map when collections slow, essential payments continue and recovery bills arrive. A business can remain viable yet lack cash when it needs to respond. Insurance may help fund a loss, subject to conditions and payment timing; it does not restore service. Spending authority belongs in the recovery design. I would also check whether several accepted scenarios depend on the same reserve, supplier or engineers. Individually affordable interruptions can exceed capacity together.
Give acceptance an owner and an expiry
Deferral can preserve cash, but it needs an owner, interim measures and a review trigger. Growth, supplier changes or a failed exercise can invalidate its assumptions. I would record the scenario, chosen spending, remaining exposure and authority to restrict activity. Finance explains cash limits; security explains failures; leaders decide. Risk appetite becomes useful when the business can defend what it protects, what it accepts and when it must choose again.