richardk/iso27diy-corp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

cleaning up Sparks

Browse source
This commit is contained in:
Richard Kranendonk 2026-05-14 16:57:06 +02:00
parent b8d1d4e02f
commit 704e6dd07f
162 changed files with 393 additions and 1041 deletions
Download patch file Download diff file Expand all files Collapse all files

15
Corpus/Sparks/Assessing reputational risks.md
View file

@ -1,15 +0,0 @@
From a [LinkedIn post](https://www.linkedin.com/feed/update/urn:li:activity:7272490322453028864/) by [Mads Bundgaard Nielsen](https://www.linkedin.com/in/mbundgaard/)
1. Perform a Stakeholder analysis, mapping them on two dimensions:
a) Strategic importance: Stakeholder can influence path to strategic objectives
b) Incident sensitivity: Negative reaction is influenced by your incidents.
- Note the important and sensitive stakeholders.
2. Identify events that can impact your reputation with important stakeholders: breach, service disruption, delays, budget exceedance, ransomware, fraud, etc.
- Bear in mind: Not all event types evoke the same reaction from the same stakeholder.
3. List the possible impact from negative reactions (see notes for examples); Ask yourself “what would I see, if my reputation with `stakeholder` was diminished?”. 1-3 tangible metrics will probably immediately pop up, and if not, its probably not an important stakeholder after all.
4. Identify levers: What actions (preemptive or reactive) are you able to take or plan? Probably only a handful. The good news is that your levers almost certainly mitigate >90% of the negative reputation outcomes.
![](Reputation%20Risk%20Analysis.jpeg)