Don’t Replace Me: A Practical AI Survival Guide for Workers and Managers Facing Automation
Don’t Replace Me is an AI survival guide offering 24 practical rules, a job-risk quiz, and actionable advice for workers and managers navigating automation.
A pragmatic book for a fraught moment in the workplace
Don’t Replace Me is an AI survival guide that reframes the automation conversation for people who are not engineers but who still face real, concrete changes to how work gets done. Published in late March 2026, the 235-page book lays out 24 rules and a set of practical assessments designed to move the debate beyond platitudes — not “learn Python” or “embrace AI” — toward a clear-eyed appraisal of what parts of a job are at risk, what can be augmented, and how people and managers should respond. For anyone worried about job security, shifting responsibilities, or how to communicate about AI at work, the book and its companion site provide specific, evidence-based guidance rather than slogans.
Why this book exists: addressing pervasive workplace anxiety
Two years of recurring conversations drove the book’s creation. The author, who has a background in AI engineering and product design with experience building automation for financial institutions and multi-agent systems, heard the same question over and over: “Should I be worried about my job?” That question isn’t binary. The answer depends on the task mix, the structure of the work, and how judgment and execution are distributed across roles. Too much of the public discussion sits at extremes — techno-optimists excited about new capabilities and alarmed observers convinced of wholesale displacement. Don’t Replace Me is written for the people in the middle: project managers, copywriters, customer service staff, paralegals, designers and others who are trying to translate headlines into practical career choices. The book exists because those conversations needed a grounded, middle-path resource that explains risk in concrete terms.
What Don’t Replace Me covers and who it’s for
The book is deliberately not a technical manual. It does not teach coding, deep prompt engineering, or the internals of model architectures. Instead it provides practical career and workplace advice through 24 rules grounded in real-world observations from the author’s experience across fintech, AI engineering, and product design. Those rules aim to help readers distinguish between tasks that are low-judgment and highly automatable versus tasks that require contextual judgment, relationship management, or creative synthesis.
Don’t Replace Me targets non-technical professionals who want to assess their own vulnerability and take constructive steps forward. It also offers managers frameworks for how to talk with their teams about AI adoption in ways that neither downplay the risks nor resort to fearful rhetoric. Creative professionals, who are already encountering market shifts, will find sections that help them articulate the unique value they offer beyond what generative models can produce. For technologists seeking deep engineering detail, the author points to other technical writings; this book is aimed at the people who must live with the systems that engineers create.
How the book was made: human judgment guided by AI tooling
Notably transparent, the author discloses that AI tools were used in the writing process. That disclosure is central to the book’s argument: tools should be treated as leverage, not a shorthand for authorship or authenticity. The process combined months of collecting notes from interviews and personal experience with AI as an engine to structure, draft, and iterate the prose. The author emphasizes that the substantive insights — the anecdotes, the career prescriptions, and the patterns of disruption — are grounded in their own observations and expertise; AI was used to scale the production of that thinking into a coherent narrative.
This practical approach to AI-assisted authorship is itself a case study the book uses to challenge a prevailing reflex: if AI touched the work, the work is devalued. Instead, the book argues readers should judge the output on whether the thinking is real, useful, and based on lived experience. That stance opens a broader conversation about authenticity, attribution, and how society should assess labor in an era where tools magnify human capability.
The book’s core framework: specificity over slogans
A recurring theme is that vague exhortations — “embrace AI” or “upskill now” — are ineffective. Real career guidance requires specificity about which tasks in a role are replaceable and which are composable into new work. The 24 rules are oriented around this diagnostic lens: identify repetitive or formulaic elements of your job, map where judgment or deep context matters, and understand how AI might either substitute for tasks or make other workers more productive (which can be a harder, less visible threat).
A practical example the book raises is the distinction between a task-based risk and a role-level risk: AI might automate a specific repetitive task within a job (e.g., initial contract drafting), but the larger risk is often that managers will reconfigure teams to extract more output from fewer people, or shift responsibilities so that roles that package judgment and relationship skills vanish. That second effect — “AI enabling others to do your job faster” — is commonly underestimated.
The companion website and risk assessment quiz
To help readers move from abstract worry to a concrete read on their situation, the author created a companion site with a free AI threat assessment quiz. The quiz asks practical questions about day-to-day responsibilities, the structure of work, and the balance between judgment and execution in a role, then returns a calibrated risk score. The goal is not fearmongering or false reassurance, but to create a shared data point that people can use to plan. The site also serves as a distribution hub for the book and will host updates, resources, and eventual audiobook announcements.
How managers and organizations should think about adoption
For people in managerial roles, the book provides frameworks for humane communication and operational decision-making. Effective adoption planning requires distinguishing efficiency gains from staffing decisions. Managers should map tasks, pilot AI augmentations on non-critical workflows, and involve affected employees in redesigning roles rather than announcing automation outcomes after decisions are made. The book advocates for transparent risk conversations, training that focuses on task composition and judgment, and policies that protect knowledge-holding employees whose institutional context is hard for models to replicate.
Where this fits in the technology ecosystem
Don’t Replace Me situates itself amid broader trends in generative AI, automation platforms, and workplace productivity tools. It references adjacent software ecosystems such as automation platforms (RPA and workflow orchestration), CRM and marketing stacks that increasingly embed AI features, and developer tools for building multi-agent systems and AI pipelines. The book underscores that developers and product teams often see automation as a set of opportunities — faster workflows, new services, and cost reductions — while employees experience the immediate uncertainty of role change. Understanding that tension is critical for product teams, HR leaders, and businesses deploying AI features inside existing platforms.
Practical guidance: what to do next if you’re worried
Readers will find actionable steps rather than generic advice. Start by cataloging the tasks you perform daily and rating them on structure, repetition, and reliance on deep domain judgment. If many tasks are structured and repetitive, prioritize automation-resistant skills: contextual judgment, client-facing decision-making, domain-specific synthesis, and cross-functional coordination. For creative roles, the book suggests emphasizing the conceptual framing and strategic decision-making that models find difficult; for administrative roles, it recommends documenting edge cases and building process knowledge that managers find costly to displace.
The companion quiz can be used as a baseline assessment, after which the book’s rules help shape a three- to twelve-month plan: short-term tactics (reorganize task ownership, document processes), mid-term moves (negotiate new role definitions, pursue targeted learning), and organizational strategies (pilot AI augmentation transparently, involve employees in workflow redesign). The book is explicit that not every reader should retrain as an engineer — the right path depends on the risk profile and what parts of a job are uniquely human.
Ethical questions and the debate over AI-assisted creation
The author invites critical discussion about the ethics of using AI to produce a book whose thesis concerns automation. That meta-layer is intentional: it surfaces questions about how society values work that includes AI as a tool and whether the presence of an AI in the creation chain should change how the content is received. Don’t Replace Me uses this to advocate for a more nuanced cultural response: judge outputs by usefulness and veracity rather than origin alone, and develop norms around disclosure and attribution that preserve trust without devolving into purity tests.
Implications for developers, product teams, and the software industry
For developers and product teams, the immediate implication is that features enabling efficiency will be adopted rapidly — but adoption carries ecosystem consequences. Automation features embedded in CRM, marketing automation, and productivity suites will shift buyer expectations and budgets. Product teams should design with human-in-the-loop patterns, robust UX for ambiguous outputs, and guardrails that surface when critical judgment is required. Security teams must plan for new risk patterns: data leakage through model inputs, reliance on third-party AI services, and auditability gaps.
Businesses must rethink job design: roles will be decomposed into tasks, and companies that manage that decomposition with fairness and strategic foresight will retain institutional knowledge and employee trust. For developers building AI systems, the book’s perspective is a reminder to prioritize interpretability, error modes, and tooling that helps non-technical users understand model limitations. These choices affect adoption trajectories and the scale of workforce impact.
Criticisms to expect and how the book handles them
Skeptics may object on two fronts: that the book understates the scale of disruption, or conversely that it overstates the practical applicability of its rules. The author expressly avoids predictions about the exact number of displaced jobs and instead offers a diagnostic framework that readers can apply to their work contexts. For critics concerned about AI-written content, the transparent description of the author’s process is a deliberate counter: openness and documented provenance create a basis for evaluating the work’s value. The book invites readers to test its prescriptions and provide feedback, reinforcing a public-facing, iterative approach.
How to use Don’t Replace Me as a workplace tool
Beyond individual reading, the book is positioned as a facilitation tool for conversations at companies, in teams, and across professions. HR leaders can use the 24 rules to run workshops that map task vulnerability and create role-transition paths. Learning and development teams can operationalize the book’s task taxonomy into microlearning modules. Professional communities and guilds can use the companion quiz to benchmark risk across roles and advocate for policies that support affected workers.
Availability is straightforward: the book is available in Kindle, paperback, and hardcover formats, with an audiobook in production. The companion site hosts the quiz and resources, and the author is soliciting feedback to iterate publicly on the ideas presented.
The debate about automation is not primarily technical — it’s social, managerial, and policy-oriented. Don’t Replace Me reframes the conversation away from abstract techno-optimism or apocalyptic fear toward practical remedies: better task diagnosis, clearer managerial practices, and tools to help workers plan. For anyone who has been living with ambient anxiety about AI, the book offers a structured way to turn that anxiety into concrete steps.
Looking ahead, the role of tools that evaluate task structure, the rise of human-in-the-loop product patterns, and organizational policies that protect critical institutional knowledge will shape whether automation amplifies productivity equitably or deepens inequality. As AI systems mature, the conversation will increasingly focus on governance, retraining pathways, and new role definitions; books and resources that combine technical literacy with occupational specificity will be essential in bridging the gap between builders and the people their systems affect.
