Job Description
<div class="content-intro"><p><span style="font-weight: 400;">Archer is an aerospace company based in San Jose, California building an all-electric vertical takeoff and landing aircraft with a mission to advance the benefits of sustainable air mobility. We are designing, manufacturing, and operating an all-electric aircraft that can carry four passengers while producing minimal noise.</span></p>
<p><span style="font-weight: 400;">Our sights are set high and our problems are hard, and we believe that diversity in the workplace is what makes us smarter, drives better insights, and will ultimately lift us all to success. We are dedicated to cultivating an equitable and inclusive environment that embraces our differences, and supports and celebrates all of our team members.</span></p></div><p>Investments in core business systems and productivity tools have been made over the past several years, but consistent adoption lags across the enterprise. Business processes aren’t consistently defined, technology isn’t always configured to reflect or enable how teams actually work, and change isn’t being managed as a discipline. The creation of this role demonstrates a commitment to building repeatable process and change capabilities that help engineers, program teams, operations, and back office teams get real value from the tools that are implemented. If you’re the kind of leader who loves turning ambiguity into momentum—and you’ve built change plans that actually stick—this is a chance to do end-to-end work with visible impact.</p>
<h3>What you’ll do: </h3>
<h4>1) Build a lightweight, scalable change capability:</h4>
<ul>
<li>Stand up a practical change management and adoption playbook (stakeholder model, change impacts, comms, training, readiness, reinforcement) sized for a startup.</li>
<li>Create templates and operating rhythms that make change repeatable across initiatives (not reinvented each time).</li>
<li>Coach leaders and product owners on “change leadership” behaviors that drive adoption.</li>
</ul>
<h4>2) Lead adoption for business systems process changes:</h4>
<ul>
<li>Partner with Business Systems and functional leaders to drive adoption of tools (e.g., ERP, PLM, MES, collaboration) and the processes they enable.</li>
<li>Translate “system go-live” into role-based ways of working: who does what, when, using which tool, in accordance with which policies / procedures / standards, etc.</li>
<li>Own the integrated change plan across multiple workstreams, dependencies, and releases.</li>
</ul>
<h4>3) Drive process clarity that enables configuration:</h4>
<ul>
<li>Facilitate current-state discovery and future-state design workshops; document fit-for-purpose processes (not bureaucracy), as well as change impacts.</li>
<li>Identify where configuration, workflow, permissions, and data standards need to change to match the process.</li>
<li>Define adoption-critical artifacts: SOPs, job aids, role guides, intake/request workflows, escalation paths.</li>
</ul>
<h4>4) Make adoption measurable and improve it continuously:</h4>
<ul>
<li>Define and track adoption + readiness metrics.</li>
<li>Run pulse checks, stakeholder feedback loops, and targeted interventions (enablement, comms, leader reinforcement).</li>
<li>Provide crisp exec updates: what’s working, what’s not, decisions needed, and risks.</li>
</ul>
<h4>5) Be a hands-on partner in a fast-paced environment:</h4>
<ul>
<li> Operate comfortably with imperfect information; prioritize what matters and deliver enablement in increments.</li>
<li>Bring structure without slowing teams down—enable speed in a regulated/quality-driven environment.</li>
</ul>
<h3>What success looks like (first 90–180 days):</h3>
<ul>
<li>A working OCM playbook + reusable assets adopted by Business Systems and functional leaders.</li>
<li>A repeatable go-live readiness approach (training, comms, hypercare, reinforcement) that reduces churn and workarounds.</li>
<li>Demonstrable adoption lift for at least one imp ... (truncated, view full listing at source)