Commanding the field

First, the ground

‍

Strategy fails when it begins with motion. The instinct is to move—ship a feature, open a channel, copy a rival’s tactic. Movement looks like progress, so we mistake it for it. The first move is not a move at all; it’s deciding where movement would even count. Until you can point to a clear outline of the space you intend to own, everything else is noise.

Defining the ground is not abstract. It is a stack of decisions about who must be served, which conditions matter, and what you will refuse to do even when it’s easy. This is the difference between operational excellence and strategy. Excellence raises the bar inside any field. Strategy alters the field so excellence compounds. The discipline is choosing a unique position and preserving the trade-offs that make it hard to copy [1].

How do you know the ground is defined? You can describe it in a few lines without mentioning features. You can explain why an apparently attractive path is wrong for you. And your team can finish the sentence: “We win when…” without saying “more” or “faster.”

‍

Name the arena

‍

Left unnamed, a space becomes whatever the loudest competitor says it is. Naming fixes the lens. “We’re not in ‘task apps’; we’re in ‘unblock today.’” That kind of sentence sets criteria, not slogans. When you name an arena, you inherit the duty to police it. You will decline customers you could technically serve. You will ignore benchmarks that do not apply. You will disappoint generalists and delight the few who feel seen.

This is not purity. It is the source of advantage. Markets concentrate around companies that decide the terms of engagement and maintain them long enough for compounding to show. Empirically, value creation skews—“superstar” dynamics are real. A small minority of companies capture a disproportionate share of profit and productivity growth [2]. If the shape of the field is vague, you are feeding someone else’s compounding curve.

When the arena is clear, language gets easier. Your website, sales calls, and product affordances can speak with the same mouth. If you’ve articulated how desire shows up for your customer, your words work without ornament. For a deeper frame on this, see Language of desire, which dissects how memory and longing move markets from the inside out.

‍

Edges you keep

‍

Edges are the boundaries where you will pay a cost to remain different. They are not features; they are choices that force other choices. “We do not customize.” “We will not build integrations that shift complexity to users.” “We measure weekly momentum, not quarterly output.” Each edge closes doors. Closing doors is how you hold the room.

The test for a real edge is whether it predicts a second-order design decision. If your edge doesn’t constrain architecture, packaging, or service levels, it’s a preference. Strategy demands something harsher: self-imposed limitations that make you better in your field and worse outside of it. This is the part managers resist. They try to keep every option open and end up in a crowded middle where options choose them [1].

Edges also encode values into operations. You will feel them in handoffs, roadmaps, and reviews. When your hiring bar and your roadmap both reflect the same “no,” momentum stops fracturing. Focus becomes a property of the system, not a pep talk.

‍

Make the field smaller

‍

Command is easier when the terrain is tight. Shrinking the field is not about TAM theater. It’s a method for concentrating force. Reduce scope along dimensions the market ignores but your customer feels: time window, decision surface, intensity. “We do first-week activation for developer teams under 25.” That is not a niche; it’s a pressure zone. Find the pressure zone and you find the lever.

Narrowing should improve the math everywhere. Acquisition channels sharpen because your message stops wandering. Product cycles shorten because “what matters” fits on a note card. Support gets faster. Margins rise because you stop paying the tax of context switching. If narrowing doesn’t improve at least three of those, you didn’t narrow; you just cut.

A practical check: if your field got smaller and your pace didn’t pick up, your constraint was internal, not spatial. Fix your pipeline, not your positioning. For help turning that realization into a plan, our Advisorship program  helps you translate field decisions into practice and outcomes without dragging six quarters of “maybe” behind them.

‍

Win the defaults

‍

Most buying is memory, not calculus. People reach for what comes to mind and what comes to hand. That is the whole job: mental availability and physical availability. Distinctive assets—surfaces, shapes, sounds, motions—are not decoration; they are memory scaffolds. Use them to collapse recognition time and remove decision friction. Then repeat them—consistently, for years [3].

Defaults live in stacks. In product, the default is the path with the fewest reversible decisions. In brand, it is the cue set that instantly says “us” without a logo. In service, it is the behavior customers can count on without asking. Win all three and you become the reference point: competitors will describe themselves relative to you, not you to them.

If you need a wayfinding companion to this, Beacon in the fog shows how teams make navigation visible. A clear beacon plus repeated cues builds the default state, “We go here when…” That sentence is the closest thing to command you can earn.

‍

Tempo over theater

‍

Tempo is the rate at which your position improves the experience that matters. Demos and headlines look fast, tempo is fast. It is the number of clean cycles you can run through a tight field. Shorten your loop until each pass teaches you something you will reuse. The enemy is the impressive plan that delays contact with evidence.

Tempo compounds because it clears latency from learning. You ship, you see, you shrink the uncertainty left, and you try again. Do not widen the field just to feel busy. Keep re-drawing the same outline and deepening it. You are building a groove, not a maze.

One practical device: adopt a default sprint length and defend it until evidence breaks it. Do not let stakeholder anxiety re-set the cadence. Anxiety is not signal. Your field is.

‍

Lines of play

‍

Every field has corridors where effort travels farther. A line of play is a chain of moves that stack returns inside your space. It might be “form → prefill → confirmation → expansion” in onboarding, or “inquiry → narrative → live walkthrough” in sales. Draw these chains and optimize the hinge moments where one move amplifies the next.

Lines of play let you trade breadth for inevitability. You stop asking, “Which tactic works best?” and start asking, “Which sequence makes success almost boring?” That is the difference between dabbling and design. When a sequence is strong, the next right action becomes obvious to the user and the team. Friction drains out. The experience feels “light” because resistance has nowhere to hide.

A warning: do not copy rival sequences without inheriting their field definitions. What works for them works for their field. Copying their chain while keeping your own terrain will produce a ghost—familiar gestures without the gains.

‍

Proof, not posture

‍

Command is a service you provide to your customer: less ambiguity, fewer choices, faster progress. If your position adds friction, you are not leading; you are lecturing. This is why the result must show up in time: lower time-to-value for the new user, lower time-to-answer for the buyer, lower time-to-resolution for support. Choose metrics that prove these claims weekly. When the numbers drift, your map is off.

Proof disarms copycats. Rivals can borrow language; they cannot fake the inside of your loops. If your edges are real and your tempo is tight, the cost to imitate grows as they try. That is what trade-offs were for: to make your path efficient and their path expensive [1]. Over a long enough horizon, the market’s compounding favors the one that owns the defaults and protects the edges. Concentration is not an accident; it is the emergent property of consistent, field-shaped work [2].

‍

When to widen

‍

There is a time to widen, but it isn’t when you feel cramped. Widening works when your defaults travel: when your cue set, your support behaviors, and your core line of play survive a new contour. If they break, you widened into a different field. Go back. Evolve your edges until they predict the new second-order decisions. Only then try again.

This is not caution; it’s compounding maintenance. Control what must remain true. Let everything else be plastic. This is how you expand without dissolving. And when you bring new teams or partners into the work, make the field tangible—draw it, narrate it, rehearse it. People cannot treat an outline with care if they’ve never seen it.

‍

Put it to work this week

‍

Pick one corridor that touches first-week value. Rewrite it to match your edges. Remove two decisions from that path and add one distinctive cue the user cannot miss. Measure time-to-value on Friday. If it did not fall, your field map is still theory.

For a companion on shaping mental context and constraints as you do this, read Build minds to bend reality. It pairs field command with cognitive architecture—how to construct the internal conditions for outside outcomes.