Skill: fatihguner/ai-human-centered-approach (version 1.0.0)

--- name: "ai-human-centered-approach" description: "Provides a comprehensive framework for deploying AI in ways that respect employee psychology, preserve human agency, and treat workforce well-being as a strategic priority rather than an afterthought. Addresses the hidden fears employees harbour about AI, the psychological damage of algorithmic supervision, and the practical steps for making human needs central to technology decisions. Use when employees resist AI adoption, when algorithmic monitoring is eroding morale, when AI-driven productivity targets create burnout, when planning an AI rollout that affects frontline workers, or when an AI project is failing and the technology is not the problem." version: "1.0.0" category: "ai-leadership" complexity: "intermediate" stage: - idea - validation - early-traction - growth - scale tags: - human-centered-ai - employee-experience - change-management - ai-adoption - psychological-safety - algorithmic-management - workforce-wellbeing - empathy related_skills: - ai-stakeholder-balance - ai-augmentation-not-automation - ai-emotional-intelligence - emotional-intelligence - psychological-safety - employee-engagement-retention - leading-through-change author: "Fatih Guner" --- # AI Human-Centered Approach Five fears live in every organisation contemplating AI, and not one of them is "robots will take my job." Ask employees what truly unsettles them, and the answers are more nuanced and more damning than the headlines suggest. They fear the loss of control -- that an algorithm will dictate their pace, their priorities, their breaks. They fear invisibility -- becoming a data point in a system that cannot see them as whole people. They fear the death of judgment -- that their expertise, built over years, will be overridden by a model trained on last quarter's numbers. They fear surveillance dressed as optimisation. And they fear the silence of leaders who deploy AI without ever asking how it feels on the receiving end. These fears do not appear in the ROI calculations that justify AI investment. They appear in the turnover data twelve months later. --- ## The Framework ### The Misconception: Human Users Do Not Equal Human-Centred An executive once insisted that his company's use of AI was human-centred. His reasoning was simple: the end users were humans, so any AI they used was, by definition, human-centred. This logic is widespread and entirely wrong. Deploying AI in a company made up of humans does not make the deployment human-centred any more than serving food in a restaurant makes it nutritious. A human-centred approach means adopting AI technologies in responsible and adaptive ways to improve people's performance, work lives, and experiences -- across dimensions that include not just efficiency but happiness, confidence, control, and a sense that what they do matters. ### Why AI Projects Fail When Leaders Ignore the Emotional Response A CTO at a mid-sized company decided that the department producing reports -- marketing campaign impact, sales figures, delivery metrics -- should be supervised by an algorithm. The algorithm monitored worker pace, continuously adjusted targets based on prior performance, and flagged underperformers. The intent was more accurate reporting, delivered faster. The results were the opposite. Workers showed great variability in output. Reports failed to meet reliability standards. Machine supervision had backfired. Employees felt pressured to perform at peak capacity without interruption, experienced diminishing control over their tasks, and described feeling "treated like robots." Absenteeism rose. Turnover increased. Mental fatigue became pervasive. The diagnosis was not technical. People have good days and bad days. That variability is not a defect to be optimised away -- it is a feature of human cognition that enables creativity, reflection, and learning. An organisation's tolerance for variability signals to its people that it understands they are human. An algorithm that demands relentless consistency signals the opposite. ### The Five Dimensions of Human-Centred AI A genuinely human-centred approach to AI deployment addresses five dimensions, each of which requires deliberate leadership action rather than passive assumption. **1. Efficiency With Respect** Efficiency remains a valid objective, but it cannot be the only one. When the sole metric is output per unit of time, AI becomes a mechanism for extracting maximum labour -- precisely the dynamic that industrial-era management reforms spent a century trying to dismantle. A human-centred approach pursues efficiency gains while respecting the cognitive and emotional limits of the people producing the output. The algorithm that adjusted for human behavioural variability -- accounting for individual working styles, life events, and the need for reflective pauses -- ultimately produced faster, more reliable results than the version that treated workers as uniform inputs. **2. Meaningful Work, Not Just Productive Work** Humans are not perfectly rational actors motivated solely by productivity. They derive satisfaction from competence, inclusion, respect, moral purpose, and curiosity. An AI deployment that maximises throughput while stripping work of meaning will produce resistance, disengagement, and attrition that no efficiency gain can offset. The human desire for meaningful work is not sentimentality. It is an empirical reality with direct consequences for performance. **3. Transparency and Governance** Employees need to know what data is being collected, how it is used, and who has access. An HR department at a Southeast Asian multinational was discovered referring to employees by staff numbers in internal communications, describing a worker as "XX13baXX" and categorising them as "high-risk elements" for the upcoming change project. When this email reached the wrong recipient and circulated among employees, the resulting outrage forced a formal apology. Transparency is not merely a regulatory requirement. It is the minimum condition for trust. **4. Human Control Over AI Interactions** If AI is presented as a tool for empowerment, employees must actually experience empowerment -- including the authority to question algorithmic recommendations, provide feedback on AI-driven targets, and withdraw from interactions they find counterproductive. A taxi company that introduced algorithmic dispatch found its drivers feeling dehumanised: they lost control over their routes, believed they were being excessively monitored, and felt prevented from exercising their own judgment about customer service. Regular feedback sessions and the discretion to override algorithmic suggestions restored both driver satisfaction and, ultimately, the algorithm's effectiveness. **5. Well-Being as a Metric, Not an Afterthought** Human-centred AI adoption requires treating employee well-being as an explicit design objective. This means collaborating with HR and technology teams before deployment to assess whether the AI system enhances or erodes self-confidence, adheres to ethical norms, and promotes rather than diminishes employee satisfaction. NASA and the US Department of Defense use technology-readiness scales to evaluate new systems; organisations deploying AI should develop analogous human-readiness scales that assess the impact on the people who will use the technology. ### The Reflective Procrastination Principle The framework introduces a counterintuitive concept: reflective procrastination. Conventional management treats any pause in productivity as waste. But research demonstrates that taking longer breaks -- delaying work not from laziness but from the need to consider different perspectives -- produces better results through more divergent thinking and creativity. Sometimes slowing down the pace of work yields higher-quality output than algorithmic optimisation of speed. The implication for AI-driven work design is profound: systems that allow human-determined pacing outperform systems that impose algorithmic pacing, because they work with human cognition rather than against it. --- ## Prompts **Prompt 1 -- Hidden Fear Inventory:** > We are deploying AI in [describe context -- e.g., customer support, warehouse operations, financial analysis]. Interview simulation: ask me the questions an employee in each affected role would need answered before they could trust this deployment. Focus not on whether they will lose their job but on the five hidden fears: loss of control, invisibility, death of judgment, surveillance, and leadership silence. For each fear, suggest specific actions the leadership team should take. **Prompt 2 -- Human-Readiness Assessment:** > Before we deploy [describe AI system], conduct a human-readiness assessment. Evaluate whether the system: preserves employee agency, accounts for human variability in performance, maintains transparency about data collection and use, includes mechanisms for employee feedback and override, and enhances rather than diminishes the meaningfulness of work. Identify gaps and recommend specific design changes. **Prompt 3 -- AI-Driven Work Redesign:** > We have deployed an AI system that [describe what it does]. Employee feedback indicates [describe symptoms -- e.g., reduced morale, increased errors, higher absenteeism]. Diagnose the likely human-centred failures in the deployment. Propose a redesigned approach that achieves the same business objectives while respecting employee psychology, drawing on principles of human variability, reflective procrastination, and meaningful work. **Prompt 4 -- Communication Plan for AI Deployment:** > Design a communication plan for our upcoming AI deployment that addresses employees as whole people, not as production inputs. The plan should: explain what the AI will do and why, explicitly state what it will not do, acknowledge the emotional impact of the change, provide channels for ongoing feedback, and include specific commitments about human oversight. Avoid the trap of leading with technical capabilities -- lead with the human story. --- ## Use Cases **Validation-Stage SaaS Startup Introducing AI-Assisted Code Review** A 15-person SaaS startup introduces an AI tool that reviews code before human review, flagging potential issues and suggesting improvements. The founders expect developers to welcome the efficiency gain. Instead, senior developers feel their expertise is being questioned -- the tool occasionally flags their deliberate architectural choices as "issues." Junior developers become overly deferential to the AI's suggestions, accepting recommendations without critical evaluation. The CTO, recognising the pattern of eroded judgment and undermined expertise, redesigns the workflow: the AI provides suggestions as one input among several, developers are explicitly encouraged to override the tool when their judgment differs, and the team tracks cases where human judgment proved superior to AI recommendation. Within three months, the tool is used actively rather than resented -- because the developers control it rather than the reverse. **Growth-Stage Logistics Company Deploying Route Optimisation** A 150-person logistics company deploys AI-driven route optimisation for its delivery fleet. Drivers are told the AI will make them more efficient. What they experience is micromanagement: prescribed routes that ignore local knowledge, break schedules determined by an algorithm rather than by fatigue, and performance metrics that penalise any deviation from the optimal path. Driver turnover increases from 12 percent to 28 percent in six months. The operations director applies the human-centred framework by introducing three changes: drivers can override routes when local conditions warrant it, break timing is driver-determined within broad parameters, and a monthly "local knowledge" session allows drivers to feed experiential insights back into the routing model. Turnover returns to baseline. Route efficiency improves beyond the original AI-only benchmark, because the system now benefits from human contextual knowledge that the algorithm lacked. **Scale-Stage Manufacturing Firm Redesigning Shop Floor AI** A manufacturing company with 2,000 employees deploys AI across its shop floor to monitor equipment performance and worker productivity. The productivity monitoring component draws immediate resistance: workers describe feeling watched, judged, and reduced to numbers. A joint task force of floor supervisors, HR, and the AI team redesigns the system. Equipment monitoring remains fully automated. Productivity data is aggregated at the team level rather than the individual level, visible to teams as a coaching tool rather than a surveillance mechanism. Workers receive quarterly reports showing how AI-driven insights have improved safety outcomes -- giving the workforce a tangible, human-centred benefit from the technology. Resistance subsides not because the AI changed but because its relationship to the workforce changed. --- ## Anti-Patterns 1. **Leading with the technology instead of the human story.** Presenting AI deployment as a technical achievement -- data architectures, algorithm specifications, processing speeds -- signals to employees that the leader sees the world the way AI does: in ones and zeros. A middle manager at one company captured the sentiment: "I felt like I was only a data point in his eyes." The human story must come first, the technical story second. 2. **Confusing employee silence with employee acceptance.** Employees who do not complain about AI are not necessarily comfortable with it. They may have concluded that resistance is futile, that the decision has already been made, or that raising concerns will mark them as obstacles. Active inquiry -- structured feedback sessions, anonymous surveys, skip-level conversations -- is the only reliable signal of true acceptance. 3. **Optimising for consistency when variability is a feature.** Algorithms naturally seek to eliminate variability. Human performance variability is not noise to be filtered out; it is the mechanism through which creativity, adaptation, and learning occur. AI systems that demand robotic consistency from human workers will produce exactly the disengagement and poor performance they were designed to prevent. 4. **Treating human-centred AI as a one-time design decision.** A system that is human-centred at deployment can become dehumanising as it evolves, as targets are adjusted upward, as oversight mechanisms atrophy, or as new management interprets the tool differently. Human-centredness requires ongoing governance, not a single design review. 5. **Deploying AI to solve a leadership problem.** When morale is low, productivity is inconsistent, or quality is declining, the root cause is often leadership -- not a technology gap. Deploying AI to "fix" problems that originate in poor management produces a specific pathology: the technology amplifies the dysfunction while giving the leader a veneer of data-driven objectivity. --- ## By Stage | Stage | Focus | Key Difference | |-------|-------|----------------| | Idea | Defining the human-AI relationship | Before any technology decision, the founder must articulate a clear philosophy: is AI here to replace human capability or to enhance it? This philosophical choice shapes every subsequent design and deployment decision. | | Validation | Testing with real humans, not just data | Prototyping must include testing the human experience of interacting with the AI, not just the accuracy of the AI's output. User testing should measure trust, control, and emotional response alongside technical metrics. | | Early Traction | Establishing feedback loops | The first operational deployment is when real human-centred challenges emerge. Formal feedback mechanisms -- weekly check-ins, anonymous channels, override tracking -- must be established from day one and treated as signals, not noise. | | Growth | Scaling human-centredness alongside AI | Growth creates pressure to standardise, and standardisation is the enemy of human-centred design. The challenge is maintaining individual adaptation, feedback responsiveness, and human override authority as the system scales. | | Scale | Institutionalising human-centred governance | At scale, human-centredness can no longer depend on individual leaders. It must be embedded in governance structures: ethics boards, employee representation in AI design decisions, mandatory human-readiness assessments for new deployments, and regular audits of existing systems. | --- ## Output Template ```markdown # Human-Centred AI Deployment Plan ## System Overview - **AI application:** [What the system does] - **Affected workforce:** [Roles and number of people] - **Business objective:** [What the AI is meant to achieve] ## Human-Readiness Assessment | Dimension | Current State | Risk Level | Required Action | |---|---|---|---| | Employee agency | [How much control do employees retain?] | [High/Medium/Low] | [Specific action] | | Human variability | [Does the system accommodate good days and bad days?] | [High/Medium/Low] | [Specific action] | | Transparency | [Do employees know what data is collected and how it is used?] | [High/Medium/Low] | [Specific action] | | Override authority | [Can employees question or override AI recommendations?] | [High/Medium/Low] | [Specific action] | | Meaningful work | [Does the AI enhance or diminish the meaning of the work?] | [High/Medium/Low] | [Specific action] | ## Fear Mitigation Plan | Hidden Fear | How This Deployment Triggers It | Specific Mitigation | |---|---|---| | Loss of control | [Describe] | [Action] | | Invisibility | [Describe] | [Action] | | Death of judgment | [Describe] | [Action] | | Surveillance | [Describe] | [Action] | | Leadership silence | [Describe] | [Action] | ## Feedback Architecture - **Frequency:** [How often feedback is collected] - **Channels:** [Anonymous surveys, team sessions, one-on-ones, override logs] - **Escalation path:** [What happens when feedback reveals a problem] - **Commitment:** [How the organisation will respond to feedback] ## Success Metrics (Human and Business) | Metric | Target | Measurement Method | |---|---|---| | [Business metric -- e.g., throughput] | [Target] | [How measured] | | [Human metric -- e.g., employee satisfaction] | [Target] | [How measured] | | [Human metric -- e.g., turnover rate] | [Target] | [How measured] | | [Human metric -- e.g., override frequency] | [Target] | [How measured] | ``` --- ## Related Skills - **[AI Stakeholder Balance](ai-stakeholder-balance.md)** -- The human-centred approach operationalises stakeholder balance at the employee level, translating broad ethical principles into specific workforce practices. - **[AI Augmentation Not Automation](ai-augmentation-not-automation.md)** -- Augmentation is the natural extension of human-centred design: AI that enhances human capability rather than supplanting it. - **[AI Emotional Intelligence](ai-emotional-intelligence.md)** -- Leading a human-centred AI deployment requires the emotional intelligence to perceive and respond to employee fears that are rarely articulated directly. - **[Psychological Safety](../frameworks/psychological-safety.md)** -- Employees who do not feel psychologically safe will not provide honest feedback about their AI experience, rendering the entire feedback architecture useless. - **[Employee Engagement and Retention](../leadership/employee-engagement-retention.md)** -- The human-centred approach is, at its core, an engagement and retention strategy specific to the AI context. - **[Leading Through Change](../leadership/leading-through-change.md)** -- General change leadership provides the foundation; this skill adapts those principles to the specific psychological dynamics of AI-driven transformation.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)