The Go-to-Market Engineer

If the discipline exists, so does a new kind of practitioner. Here is what it would mean to be one.

I have met a few people who already work the way this whole inquiry has been pointing toward, and they are easy to recognize once you know what to look for. Sitting with one of them, what stays with you is not their cleverness, though they tend to be clever, and not their command of tools, though they usually have it. It is that they talk about the market the way an engineer talks about a structure, as a thing with describable behavior, with a load it can carry and a point where it breaks, with parts that compose into a whole that has properties none of the parts have alone. Ask them why something worked and they describe a mechanism rather than reaching for a story. Ask them what will happen if they change something and they tell you, with a number and a range, and then they change it and they are roughly right, and when they are wrong they can say why, which is the part that gives them away. They are reasoning from a model of the thing, and almost no one else in the field is.

What is striking is how undramatic it looks from the outside. There is no special intensity to it, none of the performed urgency the field associates with its stars. The engineer is often the calm one in the room, the person making small adjustments and waiting for the system to respond rather than yanking at it, and their calm can read as detachment to people used to mistaking motion for competence. The calm is the tell of someone steering a system they understand, correcting gently because they know what their corrections will do, and it is the opposite of the heroics the field tends to celebrate, which is part of why the field has been slow to recognize the engineer as the more valuable kind of operator.

There are very few of them, and most of what they know they have built privately, for one market, and cannot fully hand to anyone else. They are what the discipline would look like if it existed, scattered instances of a profession that has no name yet and no shared body of knowledge, each having reinvented in isolation a way of working that ought to be taught. This closing piece is about that person, the go-to-market engineer, understood as a kind of professional the field could produce if it built the discipline underneath the title, rather than as the job title that already exists and means almost nothing. Describing them is a way of describing what the whole project is for, because a discipline is, in the end, a way of making more people able to do what its best practitioners do, and the test of whether the discipline has been built is whether that person can be trained rather than merely born.

What they know

The question worth asking about any engineer is the one that sounds simple and is not, which is what exactly they know that others do not. For the go-to-market engineer, the knowledge has a shape, and it is worth laying out, because it is the knowledge the field would have to assemble and teach for the profession to exist in numbers.

They know the object. Where most of the field sees campaigns and channels and a stack of tools, a collection of activities that never quite add up to a thing, the engineer sees a single designed system whose job is to create and capture a market, and they hold that system in mind as an object with a structure, separate from any one campaign that runs inside it. Holding the object steady in the mind is the first thing, the move that turns a pile of parts into something that can be reasoned about as a whole, and it is the move almost no one makes, because the field has never named the object clearly enough to hold.

This sounds like a small thing and is the foundation of everything else. You cannot reason about the behavior of a system you cannot hold as a single object, cannot ask what its capacity is or how it fails or what it is rated for, because those are properties of a whole, and without the whole in mind there is only the parts, each optimized in isolation while the system they compose goes unattended. The engineer’s first move, the one that makes all the others possible, is simply to see the whole thing as a thing, which is why naming the object is the foundational act of the discipline and not a matter of vocabulary.

They know how it behaves. The engineer has an account of how the system works, an operational principle for how durable demand actually gets created and held, precise enough to reason from rather than a story told after the fact. They know the system has a capacity, a load it can carry before it strains, and they know what happens as it approaches that limit, the way performance degrades sharply near the edge rather than gracefully. They know the channels obey curves rather than lines, that doubling the spend does not double the result, that every channel has a knee past which the next dollar buys almost nothing. They know the system is a thing to be steered, sensed and corrected over time, and that steering it too hard on information that arrives too late produces the oscillation that looks like bad luck and is bad control. This is the made-knowledge of how demand systems behave, the body of understanding that no underlying science provides and that has to be built by people designing the systems and watching them run.

They know how it fails. The engineer carries a working sense of the ways a demand system breaks, the overload that comes from pushing past capacity, the brittleness of a system tuned too tightly to conditions that then change, the single points of failure hidden inside an efficient concentration, the slow exhaustion of a finite reserve like the goodwill of a market. They treat these failure modes as things to design against, building in the margin and the redundancy that guard against them, rather than discovering each one by suffering it. Knowing how things fail is most of what it means to know how to build them, and the engineer’s relationship to failure, studying it rather than narrating it away, is one of the clearest things that sets them apart.

And they know what they cannot know. The engineer understands that the most important question, whether their actions are actually causing the outcomes they see, is truly hard to answer, that the data does not contain the answer by itself, that knowing requires experiment or honest assumption and that some things cannot be known at all. They hold their numbers with the right amount of doubt, distinguishing what they have established by experiment from what they believe by assumption from what they are guessing, and this calibrated uncertainty, this refusal to mistake a confident dashboard for knowledge, is a form of knowledge in itself, perhaps the most advanced form the discipline has.

How they know it

The knowledge matters, and so do the methods that produce it, because the methods are how the knowledge gets built and how it could be taught. The go-to-market engineer learns the way engineers have always learned, and the methods are as distinctive as the knowledge.

They learn by designing, by treating each system they build as a thing specified on purpose rather than assembled by accident, which forces the questions that build understanding, what is this for, what must it carry, how will it fail. They learn by parameter variation, by changing one thing at a time and watching the system respond, mapping the curves and the limits rather than settling at a single point and assuming it holds everywhere. They learn by studying failure, treating each collapse as an experiment the world has run for them, reconstructing what happened and extracting the lesson rather than assigning the blame and moving on. And they learn by experiment in the strict sense, by running the holdouts and the controlled tests that manufacture the missing counterfactual and let them know, rather than guess, what their systems actually cause. These methods compound, each system better understood than the last, which is the feeling of a discipline accumulating, and it is the feeling the field has almost never had, because it has almost never used the methods.

There is a flywheel in this that the field has never spun. Each system the engineer designs and instruments and studies adds to a private store of understanding that makes the next system better, so that experience compounds into knowledge rather than dissipating into anecdote. In a field with a discipline, that private store would feed a public one, the lessons written into shared standards and a common literature so that the whole field advanced with each practitioner’s failures and discoveries. The engineers who exist now compound only their own understanding, which is why their knowledge tends to die with their careers, and the largest thing the discipline would add is the connection between the private flywheel and the public one, the mechanism by which one person’s hard-won model becomes everyone’s starting point.

A different kind of professional

It helps to place the go-to-market engineer against the two professionals the field already has, because the engineer is a third thing and the difference is the point. There is the marketer, who comes from brand and story and taste, who understands that markets are made of people and that attention is earned rather than bought, and whose knowledge is real and intuitive and hard to transfer. There is the operator, who comes from process and systems and tools, who can make things run and measure what happened, and whose knowledge is real and rigorous and confined to what it has already seen. The engineer is neither of these, and is not simply a blend of them, because the thing the engineer adds is the one neither has, an explicit model of the system precise enough to design with and to predict from, which is a separate achievement that does not fall out of combining taste with measurement.

This is worth being clear about, because the temptation is to imagine the go-to-market engineer as a marketer who learned to code or an operator who developed taste, an existing professional with an extra skill. The engineer is a different professional, defined by a different relationship to the work, the relationship of someone who holds a model of the object and reasons from it, the way a structural engineer is a third kind of person who knows structures as objects with calculable behavior, rather than an architect with better math or a builder with more theory. The discipline produces that third kind of person, and producing them is the whole point, because they are the ones who can do reliably and teach to others what the field currently gets only by accident from the rare individuals who stumbled into the model on their own.

You can feel the difference in a single meeting. Put a problem in front of the marketer and they reach for a story and an instinct, and the instinct is often right and never quite explicable. Put it in front of the operator and they reach for the dashboard and the process, and the process is sound and blind to what it has not measured. Put it in front of the engineer and they ask what the system is, how it is loaded, where it would fail, and what they would have to measure to know, and the difference is that they are reasoning from a model of the thing while the others reason from a feeling or a record. They are not smarter than the other two. They are holding a different kind of object in mind, and the model is what the discipline would teach.

There is a disposition that comes with all this, a temperament more than a skill set. The go-to-market engineer is comfortable acting under uncertainty without pretending the uncertainty away, willing to leave margin that looks like waste, respectful of failure as a teacher, honest about the limits of what the numbers show. And because they build systems that act on people at scale, they carry, or should carry, the duty of care that comes with that power, the sense that the ability to shape what large numbers of people want and do is a serious thing that obligates its holder, the same way the power to build a bridge obligates the person who builds it. The disposition is part of the profession, perhaps the deepest part, because the knowledge and the methods can be taught but the temperament is what determines whether they are used well.

It is worth saying that this temperament is teachable, or at least cultivable, which matters because the field’s fatalism about talent assumes the opposite. The patience to leave margin, the discipline to run the experiment instead of trusting the dashboard, the honesty to mark a number unknown, the respect for failure as a teacher, these are habits, and habits can be taught and practiced and held to by a profession that values them. The rare individuals who have them now mostly arrived at them alone, through temperament and hard experience, and there is no reason a discipline could not instill them deliberately, the way every mature engineering field instills the cast of mind its work requires in people who did not start with it. The temperament looks like a gift only because the field has never tried to teach it.

Why it is worth becoming one

There is a reason this is the right moment to become this kind of professional, beyond the intrinsic appeal of understanding your own work. For a long time, advantage in go-to-market came largely from execution, from having the resources and the people to do more than rivals could, and in that world the engineer’s deeper understanding was a quieter edge, often outrun by sheer spending. That world is ending. As the tools make execution cheap and abundant, execution stops conferring advantage, because an advantage everyone has is no advantage at all, and the contest shifts to the one thing the tools cannot supply, which is the judgment to design a sound system and the understanding to know whether it is working. The engineer’s edge, which used to be quiet, becomes the whole game, because when everyone can execute, the winner is whoever designed the better system. The skill the field undervalued for years, because raw resource could stand in for it, is becoming the scarce and decisive one, and the people who hold it are about to matter more than they ever have. To become a go-to-market engineer now is to invest in the capacity that is rising in value exactly as the old sources of advantage fall away.

The word and the discipline

There is a title now, go-to-market engineer, and it spread fast, and it means, in current use, someone who operates a stack of automation tools. The person this piece has described is not that, and the gap between the two is the gap between a word and a discipline. The word arrived first, manufactured and adopted before there was anything underneath it, and it settled onto the nearest available meaning, the tools, because nothing else had been built for it to mean. The discipline, if it gets built, is what would finally give the word something true to point at, and the person who practices the discipline is what the title would name if the title meant what it could mean.

This matters because words harden, and a title that settles permanently into meaning the operation of tools forecloses the larger thing it could have named. The opportunity in front of the field is to fill the word with the discipline before it sets, to make go-to-market engineer mean the person who knows the distribution artifact the way an engineer knows a structure, rather than the person who knows this season’s tools. Whether that happens is not decided yet, which is the hopeful part, because a word still settling is a word that can still be filled, and the discipline still mostly unbuilt is a discipline still open to whoever does the work of building it.

That is an unusually open situation, and it will not stay open forever. Right now the meaning of the term is still soft, the discipline still unbuilt, the space behind the word still empty enough that someone could fill it with something true, and that openness is exactly the opportunity. Fields do not stay undefined for long once money and attention pour into them, and the definition that finally sets is hard to move afterward, so the window in which go-to-market engineering could come to mean a real discipline rather than a toolset is the window we are in now, which is a reason to do the work sooner rather than later.

What is still missing

I want to end with honesty, which means admitting how much of this remains undone. The go-to-market engineer I have described mostly does not exist yet in any numbers, the knowledge they would need has not been assembled into anything teachable, the object has only just been named, the models are first sketches offered to be corrected, the failure taxonomy is a beginning, the standards do not exist, the ethic has not been written. What this inquiry has done is sketch the foundations, argue that the discipline is possible and worth building, name some of the pieces it would need, and propose a few of them in forms specific enough to be wrong. That is the work an opening can do, and it is not the same as the work of building the field, which is larger and slower and belongs to many people over a long time.

I have tried to be careful throughout to offer claims that could be wrong, models specific enough to fail, hypotheses framed so that someone could test them and find them false, because that is the form a contribution to a young field should take. A discipline begins with claims sharp enough to argue about, not with a system of settled truths, and the arguing is how the truths get found. If the models here are wrong, the right response is better models, made the same way, proposed and tested and corrected, and the field will be the better for the exchange than it is for the soft and unfalsifiable language it trades in now. The worst outcome would be agreement. The thing I would most want is for someone to take one of these claims, show precisely where it fails, and replace it with something truer, because that is what it looks like when a discipline starts to live.

There is something fitting in ending a book about an unbuilt discipline with an admission that it remains unbuilt. The aircraft engineers who turned a pilot’s discomfort into a science of flying qualities began the work rather than finishing it in one stroke, and the beginning was a claim that the thing could be known and a first rough attempt to know it. This has tried to be that kind of beginning for go-to-market, a claim that the variance everyone treats as the nature of the business is the signature of a field that has not yet become a discipline, and that becoming one is possible, and that the path runs through naming the object, building the knowledge, studying the failures, and accepting the responsibility. The rest is open. The word is still mostly empty, the space behind it still mostly unbuilt, and the most an opening argument can do is make that space visible and worth entering, and then leave it to the people who will enter it, who get to decide, as the first practitioners of any discipline always do, what the thing they are building will turn out to be.

---

References

• This essay draws together strands developed across a longer inquiry into go-to-market as an engineering discipline. The works underpinning each strand, on engineering knowledge, market design, dimensional analysis, queueing and control, dynamical systems, causal inference, reliability, and engineering ethics, are listed in the consolidated bibliography.
• On engineering knowledge as a distinct body of design understanding, and on the practitioner who holds it, see Walter G. Vincenti, What Engineers Know and How They Know It (Johns Hopkins University Press, 1990).