# About


> "The aim of leadership should be to improve the performance of man and
> machine, to improve quality, to increase output, and simultaneously to bring
> pride of workmanship to people."
>
> — W. Edwards Deming

This quote guides how we think about engineering organizations. Conversations
about engineering productivity often focus on output measures: story points,
lines of code, deployment frequency. These metrics have a place. They do not
answer the important question. The important question is whether we empower
engineers to have a lasting impact on the business and its customers.

---

## The Problem With Career Frameworks

Most organizations write a career framework once, file it away, and never read
it again. The framework describes levels in vague terms like "demonstrates
leadership" or "has broad impact". Those terms mean different things to
different people. Engineers cannot use them to grow. Managers cannot use them
to set clear expectations. Nobody can use them to tell an AI agent how the team
works.

We think the answer is an agent-aligned engineering standard. The standard is a
live system. It should be precise enough that a machine can validate it. It
should be readable enough that an engineer sees the expectations at any level.
It should produce real outputs: job descriptions, agent profiles, interview
questions, and progression plans. It should do more than sit in a wiki.

---

## The Idea

Forward Impact Engineering starts from one premise. **Define what great
engineering looks like. You can then derive everything else from that
definition.**

Define your skills, behaviours, and career levels in plain YAML files. From
that single source of truth, the system produces:

- **Job definitions** that combine discipline, track, and level into clear role
  expectations
- **AI agent profiles** that match your agent-aligned engineering standards,
  scoped to specific lifecycle stages
- **Interview questions** grounded in the skills you care about
- **Progression plans** that show engineers exactly what changes between levels
- **Knowledge systems** that keep engineers briefed and organized

The agent-aligned engineering standard is infrastructure, the same way a CI
pipeline is infrastructure. Once it is in place, everyone benefits from it
continuously.

---

## People Before Process

Deming's insight is that the system creates quality. Inspection of individuals
does not create quality. The system is right when expectations are clear, tools
are good, and people understand their path. Quality then follows.

This design principle shapes every product in the suite:

**Map** gives organizations a way to state what "good" looks like. It uses
structured, validatable definitions that everyone can reference. It does not
use vague terms.

**Pathway** turns those definitions into tools engineers use: career browsers,
job descriptions, AI agents that follow team standards, and progression plans
that make growth tangible.

**Guide** is the AI agent that understands the agent-aligned engineering
standard deeply enough to reason about it. It onboards new engineers, advises
on career growth, and assesses engineering activity against the team's skill
expectations.

**Landmark** helps engineers see their own growth. It connects what they
produce on GitHub, such as pull requests, reviews, and design documents, back
to the agent-aligned engineering standard. It also helps organizations see
whether their engineering systems support the practices the standard describes.

**Summit** helps leaders make staffing decisions backed by evidence. It models
team capability as a system. The model surfaces coverage, structural risks, and
what-if scenarios before someone gets set up to fail.

**Outpost** gives engineers a personal operations center. Scheduled AI tasks
sync information, prepare briefings, and organize knowledge. Engineers can then
focus on the work that matters.

**Gear** publishes the libraries and services that make up the suite. Platform
builders install any subset from npm. Humans and agents then share one
interface and one set of documentation.

Together, these products equip engineers. They do not monitor or measure them.
Clear expectations, visible career paths, intelligent assistance, and organized
knowledge are the conditions under which people do their best work.

---

## Open Source, Real World

The entire suite is open source. The data model is yours. You define it in
YAML. A schema validates it. It lives in your repository. Different
organizations use the same model with completely different data.

There is no vendor lock-in, no proprietary format, and no SaaS dependency.

We build the tools with vanilla JavaScript and no frontend frameworks. We
design them to be simple. Each design choice reduces complexity instead of
hiding it.

---

## Who We Are

The Developer Experience team at a large pharmaceutical company builds and
maintains Forward Impact Engineering. We work in an industry where technology
serves a purpose beyond itself. The software we build, the platforms we
maintain, and the engineers we support contribute to outcomes that matter for
patients' lives.

We built FIT because we believe the best way to have a lasting positive impact
is to empower the people who do the work. When engineers have clear
expectations, visible growth paths, and tools that respect their craft, they
deliver better software. Better software means better outcomes for the people
who depend on it.
