Company focus is the act of directing the company's collective attention at specific Core Jobs of a specific segment, and subtracting every claim that would pull the attention elsewhere. It is one operation under three names. Focus is the chosen target. Attention management is the continuous routing. Subtraction is the mechanism that frees the resource by removing the competing claim. The act runs at multiple scopes inside the company: directing customer attention through the chain-walk, holding company-level focus on the segment, holding department-level focus, allocating product-portfolio focus, holding individual employee focus. The operation is the same at every scope. This page covers the meta-framework view. The customer-side mechanics in detail live in Customer Attention Management: cognitive cost, Consideration Activators as attention-loader, Aha placement, continuous chain guidance, the five attention-capture mechanics, communication as attentional engineering, subtraction as attention conservation, the advertising business model.
The page covers attention as the upstream resource (§1), the structural identity between focus, attention management, and subtraction (§2), the fractal of scopes the act runs at (§3), what company-level focus on segment plus Core Jobs requires (§4), sustaining focus over time (§5), the Innovator's Dilemma as focus that ossified (§6), the two-track investment discipline of holding focus while funding a parallel track for global-optimum moves (§7), and what employee focus looks like inside the team (§8).
1. Attention is the upstream resource every Next Move Theory effect routes through
Attention is the metabolic resource the brain refuses to spend except where it predicts a return, and every Next Move Theory effect we care about routes through it. Value detection runs through prediction errors, and prediction errors only fire on attention spent. Behavior change runs through Consideration Activators, and they only load through attention captured. Segment alignment runs through shared Jobs language, and the language only aligns the team if attention is routed to it. Communication runs through landing pages, one-liners, and visuals, all of them attention-routing artifacts. Retention runs through chain-walks, which are sequences of attention transitions. Competitive defense runs through Consideration Set position, which is pre-loaded attention.
The substrate is allostatic (Scientific Foundations §1). The brain is an energy-budget investor. Attention is one of the budget lines it rations as ruthlessly as glucose, oxygen, and dopamine. Where the brain refuses to spend attention, no downstream perception, decision, or action follows. No value the product creates ever reaches the customer.
Attention management is the operation of routing where, when, and on what the brain spends attention. Refusing to manage customer attention leaks value the customer's brain never permitted itself to register. Refusing to manage employee attention leaks work the team's brain never permitted itself to do. The discipline is foundational not as metaphor but as substrate.
Focus, attention management, and subtraction-as-attention-mechanism are three names for the same operation observed from different angles (see §2).
2. Focus and attention management are the same operation — directing a constrained resource at a chosen target. Subtraction is the mechanism through which the direction is achieved.
Focus and attention management describe the same operation in different vocabularies. To focus is to direct attention. The chosen target is the focus. The discipline of holding the direction is attention management. There is no clean line between deciding where and routing the resource. Choosing without routing leaves the focus on paper. Routing without a chosen target produces chaos. The two are one structured operation with two faces: the target (focus) and the continuous routing (attention management).
Subtraction is the mechanism through which the direction is achieved. Attention is already spent somewhere in every moment. It goes to a habit, a loud customer, a competitor's news cycle, the dominant KPI, or the default-reflex worry loop. To direct attention at X, the brain (customer's or team's) must stop directing it at non-X. Direction implies subtraction. Formally, direct(X) = subtract(claims-on-non-X). The two are the same act seen from two sides. Adding nothing on the focus side requires removing something on the non-focus side, and vice versa. The customer's brain does not add attention on AirPods. It stops spending attention on untangling cords, and the released attention lands wherever the next claim wins. The team does not add attention to the target segment. It stops spending attention on non-target segments, and the released attention lands on the focus.
The same operator runs across the Next Move Theory pillars on different constrained resources (Subtraction). When the constrained resource is attention, subtraction works as the direction mechanism above. When the constrained resource is capital, the same operator runs in Unit Economics: subtract negative-margin units, and the released capital lands on profitable ones. When the constrained resource is certainty, the same operator runs in RAT: subtract risky assumptions before building, and the released team-attention lands on smaller, validated assumption stacks. The verb is always subtract a claim on the constrained resource so the resource can be directed at the chosen target. The resource changes by pillar.
Focus is the noun form, the chosen target: target segment, focus Big Job, focus criteria, focus Core Jobs. Attention management is the discipline form, the continuous work of holding the direction across customer chain-walks, employee quarters, and the founder's calendar. Subtraction is the mechanism form, what makes the direction possible by removing the competing claim. They name the same operation at different scopes and from different angles.
When a focus appears to be losing, look first at what claims on attention have not been refused. The candidates are loud customers requesting features outside the segment, VP suggestions, competitor news cycles, processes that capture employee mornings, and a metric drifting because nobody is steering it. The focus did not weaken. The subtractions never happened, so the direction could not hold.
3. Focus is fractal — the same operation runs at every scope, with different targets and different subtractions
Five attention-direction workstreams recur inside a Next Move Theory company: directing customer attention through the chain-walk, holding company-level focus on a segment and Core Jobs, holding department-level focus on priorities, allocating product-portfolio focus across products, and each employee holding their own focus on tasks. The same operation runs at every scope: direct constrained attention at a chosen target by subtracting competing claims. What changes by scope is whose attention is the constrained resource being directed, who does the directing, what the chosen target is, and what competing claims need to be subtracted.
The five scopes that recur inside a Next Move Theory company:
- (a) Directing the customer's attention. This is our discipline of routing the customer's attention to our product, our Job Graph, and our Critical Chain of Jobs. The customer's brain responds, but the work is ours. At each step (Consideration Activators, Orientation Job, Solution choice, Critical Chain of Jobs, first Aha, repeated Ahas) the team's job is to make the customer's attention land deliberately where we need it, not wherever the next claim wins. The chosen target is our Solution performing the Big Job. The competing claims we work against are habit, competitor Consideration Activators, and mid-chain interruptions. The mechanics live in Customer Attention Management.
- (b) Main company-level focus on segments and Core Jobs. This is the team's collective focus on which customers we serve and which Core Jobs we compete on. The chosen target is the target segment plus Big Job plus criteria plus Core Jobs (§4). The competing claims are non-target segments, non-focus Jobs, adjacent opportunities, and loud customers outside the segment. The founder enforces the subtraction. Junior staff's default-attention reflex pushes against it.
- (c) Department-level focus. Each function holds focus on its own priorities. Discovery focuses on which research questions get studied, Marketing on which campaigns get run, Engineering on which technical debt is paid down, Support on which tickets are answered. The chosen target is the department's KPIs anchored on the target segment. The competing claims are inter-departmental requests, vanity metrics, and processes that capture department attention disproportionately to their value.
- (d) Product-portfolio focus. This is the team's focus across the products it ships: which products get engineering quarters, which get marketing spend, which get pruned. The chosen target is the products serving the target segment's Core Jobs. The competing claims are legacy products with revenue but no future, side projects that took root, and acquisitions that haven't been integrated. ABCDX applied at the product level is portfolio-attentional triage (ABCDX Segmentation).
- (e) Individual employee focus. This is each person's focus across the day: what tasks they pick up, what they ignore, what they think about between tasks. The chosen target is the work that serves the target segment's Core Jobs. The competing claims are inbox, Slack DMs, interruptions, meetings with no clear purpose, processes inherited from previous employers, and the loudest authority in the room. §8 unpacks this.
The scopes are nested and interdependent. Customer attention (a) does not get managed if employee attention (e) is captured by processes that don't serve the target segment. Department attention (c) does not align if company-level focus (b) is unclear. Product-portfolio attention (d) leaks if the company hasn't subtracted legacy products from the investment landscape. A team strong at one scope and failing at the others leaks the gains the strong scope produced.
Diagnose the scope before picking the mechanic. A team trying to fix customer attention with department-level KPI redesign is mis-routing. A team trying to fix portfolio drift with more brand ads is mis-routing the other way. Each scope has its own mechanics, its own targets, and its own subtractions.
4. Focus is segment-level AND Job-level attention conservation
Segmentation §8 names focus as "segment-level subtraction," the act of removing all non-target segments from the investment landscape. The same operation applies at the Job level inside the chosen segment: refuse to spend team attention on non-focus Core Jobs even when those Jobs are visible, requested, and adjacent. Focus is the act of refusing to spend collective attention on anything other than the chosen segment performing its chosen Core Jobs at the chosen criteria, until those Core Jobs are won.
Without the refusal, attention diffuses across many segments and many Jobs at once, and the team produces "everything for everyone, for no one" (Next Move Theory key theses §2). Every new segment, every new Job inside the segment, every new feature, and every new channel pulls team attention from every previous commitment. Subtraction runs in reverse: removing a segment or a Job returns attention to what remains.
Concrete US examples of focus as attention conservation:
- Stripe in 2010 focused on YC-stage developer-founders performing the Core Job "accept online payments without a multi-week integration." It refused enterprise sales, large-merchant playbooks, and international expansion at the segment level. It refused checkout-customization, marketplace-payouts, and invoicing at the Job level until the first Core Job was won.
- Notion in 2018–2020 focused on individual knowledge workers and small teams performing the Core Job "organize my notes and tasks in one workspace." It refused enterprise IT requirements (SSO, SAML, SCIM, audit log) at the segment level. It refused dedicated project-management, wiki, and database features as separate products at the Job level.
- Tesla in 2008–2012 focused on Silicon Valley tech leaders performing the Core Job "own a status-electric sports car." It refused mainstream-market dynamics and dealer networks at the segment level. It refused sedan, SUV, and commercial form factors at the Job level until the Roadster's segment was won.
Refuse, at every prioritization decision, to spend team attention outside the target segment AND outside the chosen Core Jobs inside that segment. Every initiative, hire, feature, channel, partnership, and budget line passes through "is this work for the target segment's chosen Core Jobs?" Work that fails the filter is delayed or refused. The founder enforces the filter. Junior staff's local incentives push toward serving every loud customer and every visible Job.
5. Sustaining focus over time — the meta-principle that unites customer-side and employee-side
Attention management at one moment is necessary but not sufficient. The deeper discipline is sustaining focus over time, both the customer's focus through the chain-walk and the team's focus across quarters.
Customer-side. The customer's attention can be captured at acquisition, drawn through the Aha, and then lost at any chain transition before the Big Job lands. The sequence runs from Consideration Activators to Orientation Job, Solution choice, Critical Chain of Jobs, first Aha, repeated Ahas across sessions, and habit installation. Each step is a place where focus can leak. Discontinuous attention loses. Continuous guidance is what installs the new Job Graph durably: one Aha, then another, then another, against the rising prediction bar. The mechanic is in Customer Attention Management §7: every transition between Micro Jobs is an attention-direction decision the team is making, explicitly or by default.
Employee-side. The team's focus on the segment, the Big Job, the criteria, the quality of the chain it delivers, and the metric it watches can all be sustained, or all erode over quarters. Erosion takes many shapes. A new loud customer requests features outside the segment. A VP walks by with an idea. A competitor's quarterly news cycle pulls attention to comparison. A hire's previous-company experience anchors them on the wrong segment. A metric drifts because nobody is steering it. Each is a quiet claim against the team's attentional commitment. The Innovator's Dilemma (§6) is what employee-side focus erosion looks like at the multi-year horizon.
The same mechanism runs in both contexts. Both customer-side and employee-side, sustained focus requires explicit attentional commitment renewed continuously. It is not a one-time strategy decision, not a one-shot ad campaign, not an annual OKR. The customer's brain re-decides at every chain transition whether to keep spending attention on the product. The team's collective attention re-decides at every prioritization meeting whether to keep spending on the target segment.
The structural defense in both contexts is the same: explicit attentional commitment renewed continuously, with subtraction of the new claims that appeared since the last renewal.
- For the customer chain: one Aha leftward, then the proposed Next Action at every transition, then continuous Aha Moment delivery against the rising prediction bar.
- For the team: target segment audited regularly, KPIs that route attention back to the focus, refusal of out-of-strategy claims that arose during the quarter, processes audited against attention-spent-versus-conserved.
6. The Innovator's Dilemma is focus that ossified into excessive attentional commitment to current customers
Product Strategy names the Innovator's Dilemma as excessive focus by the team that builds the product. Through the attention lens: the well-run team spends so much attention on current customers' Jobs that no attention remains for emerging Jobs of emerging segments. The Innovator's Dilemma is what §4's focus discipline looks like after the target segment is saturated and a new one has appeared, and the team kept holding the original focus anyway.
The mechanism: current customers' Jobs are visible and important, so the team spends attention on them. The customers reward the team with revenue and feedback, so the team spends more attention, and the loop tightens. Meanwhile a different segment emerges with different Jobs, served by a different Solution that looks unfit by the current team's success criteria. The current team's attentional budget cannot make space for the alternative because the loop is consuming it. The entrant looks like a toy precisely because the team has no attention left to take it seriously.
Concrete US examples:
- Microsoft Word in 2018–2023 had every team-quarter going into current Word customers' Jobs: compliance review, accessibility, enterprise admin, ribbon UX. There was no attention for "generate a usable first draft in 4 seconds." ChatGPT climbed above Word and absorbed the higher Big Job. Word's focus on its segment was correct in 2010. The same focus held into 2023 was the Dilemma.
- Small-business web-development agencies had every quarter going into hosting-administrator and site-maintenance Jobs: DNS configuration, mail-server tuning, SSL renewal, plugin upkeep. There was no attention for "have a website live for my small business turnkey." Squarespace, Wix, and Webflow climbed above and the category shrank dramatically over a decade.
- Big Three US carriers in 2010 had attention on contract-customer Jobs: device subsidy economics, family plans, retail-store conversion. There was no attention for "low-cost prepaid wireless that just works." MVNOs (Mint Mobile, Cricket, Google Fi) captured the price-first segment.
Focus held past the segment's saturation point becomes excessive attentional commitment that blocks the team from seeing the next opportunity. Focus is necessary, but it can ossify. The exit from the Dilemma runs through the Job Graph: studying the Big Job above, the adjacent segments, and the new Big Jobs appearing at the top of the customer's life-Graph (Job Graph §14). It also requires reserving company attention for that study even while the current segment is being served (§7).
7. Hold the focus AND fund a second investment track for the global-optimum move — two parallel tracks running simultaneously
The §4 focus discipline (refuse non-target segments and non-focus Core Jobs) and the §6 Innovator's-Dilemma escape (fund a separate investment track for the global-optimum move) are not in tension. They compose. Run both tracks at once.
The local-vs-global framing from Local vs Global Optimum maps directly. The local optimum is the target-segment work. The global optimum is the move to a new segment, a new Big Job, a new business model, or a new market. Either track alone is half-rate growth. Both funded together is what compounds across multi-year horizons.
The operational form:
- Refusal at the target segment. Every initiative, hire, feature, channel, partnership, and budget line for the current quarter passes through "is this work for the target segment's chosen Core Jobs?" Work that fails the filter is delayed or refused.
- Second-track investment for the global move. At least one KPI, at least one team allocation, and at least one founder-time slot every quarter is committed to studying or executing the global-optimum move, even when the target segment's work is incomplete. Without the explicit second-track investment, the local KPIs consume the entire attention budget and the global move never starts.
The second track is not a contradiction of the focus discipline. The focus discipline governs the current target segment's work. The second track governs attention and capital explicitly outside the current target segment's frame. The two are independent investment pools, with the founder's authority deciding the split.
The default failure mode is to run one track without the other. A team that refuses non-focus claims but funds no second track drifts into the Innovator's Dilemma in 3–5 years. A team that funds the second track but doesn't refuse non-focus claims at the target segment never wins the target segment in the first place.
8. Employee attention to their work — what people inside the company look at, think about, and refuse to look at
The fifth scope of attention management (§3-e) is what specific employees inside the company actually pay attention to: what they look at, what they think about, what their attention defaults to between deliberate decisions, what they refuse to look at because no one is asking them to.
"The company" as an entity has no attention of its own. The entity's apparent attention is the aggregate of every employee's attention at the moment, mediated by KPIs, processes, calendars, and the founder's attentional commitment. When a methodology talks about "the company attending to X," the literal content is "these specific people are looking at X."
Where employee attention goes by default
- Customers in front of them. Sales reps' attention defaults to whichever deal is loudest or closest to close. Product managers' attention defaults to whichever customer logged a Jira ticket today. Support's attention defaults to whichever ticket is unanswered.
- KPIs and OKRs. Whatever is measured gets attention; whatever is unmeasured doesn't (Subtraction §4(c)). A team measured on features shipped spends attention on shipping features. A team measured on NPS for the target segment spends attention on the target segment.
- Whoever has authority at the moment. A VP walks by and says "we should do X," and the next day's attention is on X. Without explicit attentional protection, the loudest authority wins.
- The founder's calendar. What the founder spends time on is what everyone learns to spend attention on, regardless of stated strategy. The calendar is the company's attentional commitment made literal.
The four observable patterns inside misaligned teams
- Researchers run studies that the product team shelves. Research-team attention is spent; Product-team attention is never received.
- Product ships features that Marketing doesn't know how to sell. Engineering attention is spent; Marketing attention is never anchored.
- Marketing brings in leads that don't fit what Product serves. Marketing attention goes to the campaign; Product attention goes to a different segment.
- Support is overloaded with C/D customers who consume 80% of energy for 0% of profit (Next Move Theory key theses §2). Support attention is captured by unprofitable, unsatisfied customers, and no attention is left for A/B customers.
Processes are themselves continuous attention spends
Processes are the often-forgotten attention surface inside the team. Sprint rituals, onboarding flows for new hires, the way Slack channels are organized, code-review SLAs, how research findings get into product decisions, how customer feedback travels from Support to Engineering, how budget decisions are escalated. Each process is itself a continuous attention spend by some role, and many of those spends are unaudited. Two failure modes recur:
- Processes that capture employee attention disproportionately to the value they produce. Standups consume 30 minutes of every engineer's morning regardless of whether anything changed. Status reports get written for an audience that doesn't read them. Meetings run with eight participants where two would have done. Review rituals gate every decision through a bottleneck.
- Missing processes that should have been routing attention but aren't. No process routes research findings into roadmap decisions. No process surfaces lost-deal interview insights to product. No process revisits the target-segment definition annually.
KPIs as attention-routing infrastructure; ABCDX as attentional triage
KPIs are Jobs of business entities (AJTBD key theses §2). Through the attention lens: KPIs are the explicit instructions for where employees should spend their attention. A KPI of features shipped routes attention to shipping features. A KPI of Big-Job-criteria-met for the target segment routes attention to landing the Big Job for the segment that matters. The hidden failure mode is KPIs routing attention to local optima while no KPI routes attention to global optima: the local KPIs consume the budget and the global move never starts (§7).
ABCDX's firing of C/D customers (ABCDX Segmentation) is attentional triage. Each C/D customer kept is attention diverted from A/B customers who would have returned more than they cost.
Cross-references
- Customer Attention Management — the customer-side mechanics view: attention as metabolic resource, three forms, Consideration Activators as attention-loader, receptivity windows, Aha, continuous chain-walk guidance, interruption resilience, Previous-Job upstream capture, the five canonical attention-capture mechanics, communication as attentional engineering, subtraction as attention conservation, the advertising business model as 100% attention-resale.
- Subtraction — subtraction as the meta-operator across the four pillars; cognitive substrate of the addition bias. The mechanism through which focus and attention management run.
- Local vs Global Optimum — local vs global attention allocation across team time horizons.
- Next Move Theory key theses §4, §10 — the cause-and-effect chain; alignment as cross-function attentional coherence.
- Segmentation §8 — focus as segment-level subtraction.
- Job Types and Properties §9 — Viral Jobs as substrate of viral capture.
- ABCDX Segmentation — firing C/D customers as attentional triage.
- Scientific Foundations §§1, 15, 18 — allostasis substrate; habit physiology; variable-ratio reinforcement.