Ai Stakeholder Balance logo

Ai Stakeholder Balance

Community
fatihguner
ai-stakeholder-balance

Guides leaders through the ethical and strategic complexities of balancing multiple stakeholder interests during AI adoption, from employees and customers to society at large. Provides frameworks for responsible AI deployment, stakeholder impact mapping, and moral decision-making when efficiency gains conflict with human welfare. Use when evaluating whether an AI deployment will harm employees or customers, weighing automation against workforce impact, facing pressure to prioritise shareholders over other stakeholders, designing an AI ethics governance structure, or confronting the societal consequences of algorithmic decision-making.

Overview

Publisherfatihguner
Repositoryforeman
Skill nameai-stakeholder-balance
Stars
63
Forks
10
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by fatihguner on GitHub. Read the source before you install it.

Installation

Install the Ai Stakeholder Balance AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/ai-stakeholder-balance
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/fatihguner/foreman.git /tmp/foreman
mkdir -p .claude/skills
cp -r /tmp/foreman/plugins/foreman/skills/ai-stakeholder-balance .claude/skills/ai-stakeholder-balance
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ai Stakeholder Balance in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ai Stakeholder Balance on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ai Stakeholder Balance is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

AI Stakeholder Balance

A scale, by definition, must have two sides. Most leaders deploying AI place efficiency on one side and load the other with nothing at all -- then marvel at how quickly things tip over. The promise of artificial intelligence is real: faster decisions, lower costs, sharper predictions. But efficiency is not a value-neutral concept. Efficiency for whom is the question that separates organisations that extract lasting value from AI from those that generate headlines about algorithmic bias, workforce revolts, and regulatory backlash. When Boston deployed an AI-optimised school bus scheduling system designed by two MIT graduates to trim a $100 million transportation budget, the algorithm dutifully reshuffled start times across hundreds of schools. It did not, however, consider that shifting elementary school start times to 7:15 a.m. would create a childcare gap that forced parents to change jobs or scramble for emergency arrangements. The city dropped the plan. The algorithm had optimised for cost. It had forgotten the humans.


The Framework

The Stakeholder Triad in AI Adoption

AI adoption decisions radiate outward in concentric circles. At the centre sit the three stakeholder groups whose interests a leader must actively balance: employees, customers, and society. Most leaders acknowledge the first two and entirely forget the third.

Employees are the most immediately affected. Surveys indicate that organisations expect automation to increase workforce capacity by 30 to 40 percent -- a statistic that, from the employee's perspective, reads as a 30 to 40 percent reduction in their perceived indispensability. Employees fear job loss, but they also fear something subtler: the erosion of agency, the sense that they have become appendages to an algorithm rather than professionals exercising judgment.

Customers sit at the receiving end of AI-driven interactions. An algorithm that predicts palliative care eligibility using electronic health records may achieve impressive accuracy, but it cannot hold an end-of-life conversation. It cannot understand why a patient with a terminal diagnosis might still prefer aggressive treatment over statistical probability. Anand Avati and associates at Stanford developed precisely such an algorithm in 2018, and the fundamental limitation was not technical but human: AI regresses to the mean, approximating any individual's needs by referencing the average of a population. If a customer deviates from that average, the algorithm fails them.

Society is the forgotten stakeholder. The AI decisions a company makes about hiring, pricing, surveillance, and data collection do not exist in a vacuum. Amazon's gender-biased recruiting algorithm, the UK's student grading algorithm that penalised students from poorer schools -- these were not just corporate embarrassments. They were societal harms with real victims who had no seat at the decision-making table.

Four Principles for Stakeholder-Balanced AI

Research across multiple organisations and regulatory environments yields four principles that distinguish responsible AI adoption from the merely profitable kind.

Principle 1: AI is a tool, not a stakeholder manager. The technology cannot go beyond treating a stakeholder as a data point. Supervised machine learning regresses observations to the mean and avoids outliers. Every individual stakeholder -- the atypical customer, the employee with unusual circumstances, the community with specific needs -- becomes an approximation. Leaders who delegate stakeholder management to AI are not managing stakeholders; they are managing averages.

Principle 2: Human intelligence imagines; AI intelligence extrapolates. When an organisation adopts AI to promote innovation, it needs decisions based on thinking beyond what is already known. AI excels at extrapolation from existing data. It cannot imagine what does not yet exist. The ability to anticipate, take perspective, and envision what drives stakeholders at any given moment remains irreducibly human.

Principle 3: Financial motivation corrupts stakeholder judgment. Research demonstrates that the more salient a financial incentive becomes, the more decision-makers will refrain from making the responsible choice. When Facebook was urged to address misinformation, its AI director reportedly slowed initiatives because they might harm the company's growth strategy. A heavily funded AI project creates its own gravitational pull toward financial justification at the expense of stakeholder welfare.

Principle 4: Identify all stakeholders -- especially the invisible ones. The most dangerous omissions are the stakeholders who are not immediately visible: the parents affected by a school scheduling algorithm, the job applicants screened out by a biased hiring model, the communities whose data feeds a surveillance system. Leaders must think in terms of both direct and indirect, short-term and long-term stakeholder impact.

The Stakeholder Impact Matrix

Stakeholder GroupDirect ImpactIndirect ImpactTime HorizonTypical Blind Spot
EmployeesJob redesign, skill demands, algorithmic supervisionWork identity, psychological safety, bargaining powerImmediate to medium-termAssuming silence equals acceptance
CustomersService quality, personalisation, data privacyTrust, brand loyalty, switching costsMedium-termTreating customers as data profiles
ShareholdersROI on AI investment, competitive positioningLong-term reputation risk, regulatory exposureShort to medium-termConflating short-term returns with sustainable value
SocietyEmployment patterns, inequality, public servicesDemocratic processes, social cohesion, economic mobilityLong-termAssuming societal impact is someone else's problem
RegulatorsCompliance requirements, reporting obligationsIndustry standards, public trust in technologyMedium to long-termTreating regulation as an obstacle rather than a signal

The Therac-25 Warning

The Therac-25 case -- a computer-controlled radiation therapy machine used for cancer treatment -- remains one of the most sobering examples of what happens when human oversight is subordinated to algorithmic authority. Decisions that would have been made by licensed technicians were delegated to the machine. When patients received fatal overdoses of radiation, the technicians who should have intervened failed to override the software, even as patients cried out in pain. They had been instructed that it was "virtually impossible" for the system to overdose a patient. The mindset that "the computer knows best" led directly to the disengagement of the human technician -- and to deaths that competent human oversight would have prevented.

The lesson extends far beyond healthcare. Every AI deployment carries a version of this risk: the gradual erosion of human judgment in favour of algorithmic authority, producing outcomes that no stakeholder -- not the technician, not the patient, not the institution -- actually wanted.


Prompts

Prompt 1 -- Stakeholder Impact Audit:

We are planning to deploy AI in [describe the specific AI application -- e.g., customer service automation, hiring screening, performance monitoring]. Map every stakeholder group that will be affected, both directly and indirectly, in the short term and long term. For each group, identify what they stand to gain, what they stand to lose, and where the most serious conflicts between stakeholder interests will emerge. Pay special attention to stakeholders who are not immediately visible.

Prompt 2 -- Ethical Risk Assessment:

Our AI adoption project involves [describe the project]. Conduct an ethical risk assessment: identify scenarios where the AI could produce outcomes that harm employees, customers, or society even while meeting its intended efficiency objectives. For each risk, assess severity, likelihood, and the strength of the human oversight mechanisms currently in place. Recommend specific governance structures to mitigate the top three risks.

Prompt 3 -- Stakeholder Communication Strategy:

We are deploying AI that will affect [describe affected groups]. Design a stakeholder communication plan that addresses each group's specific concerns, explains what the AI will and will not do, establishes transparency about data usage, and creates feedback mechanisms. The plan should include what to say when the honest answer is "we do not yet know the full impact."

Prompt 4 -- Society-as-Stakeholder Analysis:

Analyse the broader societal implications of our AI deployment in [describe context]. Consider effects on employment patterns in our region, potential for algorithmic bias across demographic groups, data privacy implications, and the precedent our approach sets for our industry. Recommend specific actions to mitigate societal harms while preserving the business value of the deployment.


Use Cases

Early-Traction Fintech Startup Automating Loan Decisions

A fintech startup with 30 employees deploys an AI model to automate small-business loan approvals. The model is fast, consistent, and demonstrably more profitable than the human underwriters it partially replaces. Six months in, a pattern emerges: the algorithm systematically disadvantages applicants from certain postal codes that correlate with lower-income, minority-heavy communities. The founders face a choice between a model that maximises approval accuracy (by their historical lending data) and one that serves the broader community equitably. Applying the stakeholder impact matrix, they map not just the direct impact on loan applicants but the indirect societal effect of perpetuating lending discrimination. The decision: retrain the model with fairness constraints, accept a modest reduction in predictive accuracy, and publish their fairness metrics publicly. The short-term cost is higher default rates. The medium-term gain is regulatory goodwill, brand trust, and a defensible position when lending regulations tighten -- which they invariably do.

Growth-Stage E-Commerce Company Introducing Algorithmic Performance Monitoring

A 200-person e-commerce company introduces an AI system to monitor warehouse worker productivity, adjusting individual targets based on historical performance data. Within weeks, absenteeism increases, error rates rise, and three senior packers -- the informal leaders of the warehouse floor -- resign. Exit interviews reveal a consistent theme: employees feel they are being treated like robots, monitored continuously, with targets that ratchet upward regardless of circumstance. The operations VP applies the principle of reflective procrastination -- the insight that allowing human variability, including bad days and creative pauses, produces better long-term results than algorithmic optimisation. The system is redesigned to account for individual working preferences, allow employee feedback on pace, and build in rest periods determined by workers rather than by the algorithm. Productivity data after the redesign shows reports are completed faster and with greater reliability than before -- achieved by respecting the human condition rather than overriding it.

Scale-Stage Healthcare Platform Deploying Predictive Diagnostics

A healthcare technology company deploys a predictive algorithm across 50 partner clinics to identify patients at risk of specific conditions. The algorithm performs well on aggregate metrics. A senior data scientist notices, however, that performance varies dramatically across demographic groups -- significantly worse for patients over 70 and for patients from non-English-speaking backgrounds, whose historical data is sparser. The company must decide whether to deploy broadly (maximising revenue) or restrict deployment to populations where the model is reliable (protecting patients). The stakeholder analysis reveals that broad deployment creates an invisible stakeholder harm: patients who receive inaccurate risk assessments may make medical decisions based on flawed predictions. The company restricts deployment, invests in collecting more diverse training data, and communicates the limitation transparently to partner clinics -- a decision that costs a quarter's revenue target but avoids the catastrophic trust destruction of a misdiagnosis scandal.


Anti-Patterns

  1. Treating stakeholder impact as a post-deployment audit. The time to assess stakeholder impact is before the algorithm is built, not after complaints arrive. Retrospective ethics reviews are reputation management, not responsible leadership. By the time harm is detected, the affected stakeholders have already paid the price.

  2. Equating stakeholder management with customer management. Leaders who define stakeholders as "employees and customers" and stop there are ignoring the constituency that will ultimately regulate, tax, and constrain their AI use: society. The Boston bus scheduling disaster was not a customer problem. It was a society problem that the decision-makers had not considered at all.

  3. Delegating AI ethics to the technical team. Ethics committees staffed exclusively with engineers and data scientists lack the philosophical, legal, and sociological perspectives needed to identify non-obvious harms. Hugging Face's model -- a dedicated, cross-disciplinary ethics group with a mandate to halt projects that reveal significant harm -- represents the standard that responsible organisations should aspire to.

  4. Assuming algorithmic fairness is a mathematical property. Fairness is a human value that requires human judgment. An algorithm can be optimised for statistical parity across groups while still producing outcomes that every reasonable person would consider unfair. The UK grading algorithm was statistically consistent. It was also morally indefensible.

  5. Privileging speed over deliberation. The pressure to deploy AI quickly -- to capture first-mover advantage, to justify investment, to satisfy board expectations -- creates a systematic bias against the careful stakeholder analysis that prevents harm. Speed is a business virtue. Recklessness disguised as speed is not.


By Stage

StageFocusKey Difference
IdeaStakeholder identificationAt the idea stage, the leader defines which stakeholders the AI is intended to serve -- and must resist the temptation to define that group too narrowly. The stakeholder map created now determines what harms will be invisible later.
ValidationEthical hypothesis testingValidation involves testing not just whether the AI works but whether it works fairly and without unintended harm across stakeholder groups. Prototype testing should include edge cases and underrepresented populations.
Early TractionGovernance infrastructureThe transition from prototype to production requires formal governance: who reviews algorithmic decisions, how stakeholders provide feedback, what triggers a human override. These structures are vastly easier to build now than to retrofit later.
GrowthScaling without diluting oversightGrowth creates pressure to automate oversight itself. The challenge is maintaining human judgment in the loop as the volume of AI-driven decisions increases by orders of magnitude. This is the stage where stakeholder harm most often escapes detection.
ScaleSystemic and societal accountabilityAt scale, the organisation's AI decisions affect not just individual stakeholders but entire markets, communities, and public systems. The leader must engage with regulators, participate in industry standards, and accept that their AI's societal impact is a legitimate subject of public scrutiny.

Output Template

markdown
# AI Stakeholder Impact Assessment

## AI Application
- **Description:** [What the AI system does]
- **Primary business objective:** [Cost reduction / Revenue growth / Quality improvement / Speed]
- **Deployment scope:** [Number of people/transactions affected]

## Stakeholder Map
| Stakeholder Group | Interest at Stake | Positive Impact | Negative Risk | Risk Severity (1-5) | Mitigation |
|---|---|---|---|---|---|
| [Group 1] | [What they care about] | [How AI helps them] | [How AI could harm them] | [1-5] | [Specific action] |
| [Group 2] | [What they care about] | [How AI helps them] | [How AI could harm them] | [1-5] | [Specific action] |
| [Society] | [Broader implications] | [Potential benefits] | [Potential harms] | [1-5] | [Specific action] |

## Conflict Analysis
| Conflict | Stakeholder A Wants | Stakeholder B Wants | Resolution Principle | Decision |
|---|---|---|---|---|
| [Describe tension] | [Their interest] | [Their interest] | [Which principle applies] | [How you resolve it] |

## Governance Structure
- **Ethics review body:** [Composition and mandate]
- **Override authority:** [Who can halt an AI decision and under what conditions]
- **Feedback mechanism:** [How stakeholders report concerns]
- **Audit cadence:** [How often stakeholder impact is formally reviewed]

## Commitments
- **We will:** [Specific promises to stakeholders]
- **We will not:** [Explicit boundaries on AI use]
- **We will disclose:** [What transparency looks like in practice]

Related Skills

  • AI Human-Centered Approach -- Stakeholder balance provides the strategic framework; the human-centred approach supplies the operational mindset for putting people before algorithms.
  • AI Augmentation Not Automation -- The choice between augmentation and automation is itself a stakeholder decision: automation prioritises shareholders while augmentation distributes value more broadly.
  • AI Emotional Intelligence -- Balancing stakeholder interests requires the emotional intelligence to understand what different groups actually feel, not merely what they say in surveys.
  • Trust Equation -- Stakeholder trust is the currency that responsible AI governance either builds or destroys; the trust equation provides the diagnostic for understanding why.
  • Leading Through Change -- AI adoption is a specific instance of organisational change; stakeholder balance determines whether that change is experienced as progress or as imposition.
  • Systems Thinking -- Stakeholder balance requires understanding the feedback loops between employee experience, customer satisfaction, and shareholder returns rather than treating each as independent.

Frequently asked questions

What does the Ai Stakeholder Balance AI skill do?

Guides leaders through the ethical and strategic complexities of balancing multiple stakeholder interests during AI adoption, from employees and customers to society at large. Provides frameworks for responsible AI deployment, stakeholder impact mapping, and moral decision-making when efficiency gains conflict with human welfare. Use when evaluating whether an AI deployment will harm employees or customers, weighing automation against workforce impact, facing pressure to prioritise shareholders over other stakeholders, designing an AI ethics governance structure, or confronting the societal...

Why use Ai Stakeholder Balance on TypingMind?

Because you install it once and use it with any model. Ai Stakeholder Balance is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ai Stakeholder Balance in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/ai-stakeholder-balance. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ai Stakeholder Balance?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ai Stakeholder Balance?

As many as you like. As long as a model supports skills, you can use Ai Stakeholder Balance with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ai Stakeholder Balance AI skill free?

Yes. It is published on GitHub by fatihguner under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇