November 17, 2026
Secondary considerations of nonobviousness: nexus
Connect secondary considerations of nonobviousness to patent claims with a practical nexus matrix, worked example, and business- and expert-witness requests.

Build a claim/product/evidence matrix for secondary considerations of nonobviousness: identify the asserted claim and product version, cite the evidence, explain its nexus to the claimed invention, and address supported alternative explanations. Assign each gap to the next document request or witness so counsel can assess the evidence's weight in the full obviousness record.
The focus here is secondary-considerations evidence in U.S. utility-patent litigation, with relevant lessons from Patent Trial and Appeal Board proceedings.
What are secondary considerations of nonobviousness?
Secondary considerations of nonobviousness, also called objective indicia, are real-world evidence bearing on whether a claimed invention would have been obvious. They include commercial success, long-felt but unresolved need, failure of others, industry skepticism, praise, copying, and unexpected results. They help guard against hindsight and belong in the full obviousness analysis before the decision-maker reaches a conclusion. The Federal Circuit explains that role in WBIP v. Kohler ↗.
Each category calls for a different factual inquiry:
The United States Patent and Trademark Office's Manual of Patent Examining Procedure (MPEP) addresses these categories in MPEP §716 ↗.
Use the categories to direct collection. A matter may have persuasive evidence in only a few of them. For the upstream reference-combination analysis, the §103 obviousness guide ↗ addresses that separate task.
Establish nexus before assigning weight
Nexus is the connection between the objective evidence and the merits of the claimed invention. Showing that a product practices a claim addresses one question. Explaining why the product's success or reception supports nonobviousness addresses another.
There are 2 routes to nexus:
The Federal Circuit sets out these distinctions in Fox Factory v. SRAM ↗. A challenger seeking to rebut the presumption must present evidence attributing the indicium to another cause, as WBIP v. Kohler ↗ explains. Keep both routes visible in the working record rather than ending the inquiry after a disputed coextensiveness showing.

In Volvo Penta v. Brunswick ↗, an inter partes review appeal, the patent owner's conclusory coextensiveness showing failed to support a presumption. The court nevertheless found independent nexus supported by the evidence and vacated and remanded the Board's decision. The practical distinction is between a product-to-claim mapping, a coextensiveness showing, and evidence explaining the claimed invention's contribution.
Preserve the claimed combination as a whole. WBIP permits nexus to rest on that combination even where individual elements were known. A limitation-level mapping helps explain implementation; the causal account must also address the invention actually claimed.
Build a claim/product/evidence matrix
Give each material item its own row. Start with the exact claim, including dependencies and the construction being applied. Then identify the product version or tested configuration. A family-wide patent label and a product-line name leave too much room for mismatched evidence.
Use these fields in counsel's working matrix:
Keep a citation to the underlying material beside each factual assertion. Distinguish an observed fact, such as a customer's recorded purchasing reason, from the inference counsel proposes to draw from it.
Fictional example: recovery software
Assume Claim 1 covers a recovery method combining snapshot selection using a stored consistency marker with replay of journal records after the selected snapshot. Aster Recovery's Restore 2.1 implements that combination and also includes an unclaimed compression engine. Counsel is assessing evidence collected during January–September 2026.
The first row needs a purchasing explanation alongside sales. The second needs technical support for both the result and the expectation. The third needs a more precise product and feature attribution. Those gaps produce different collection requests.
Retain the adverse evidence in the same record. If customer evaluations credit the discount, record that fact beside the proposed technical explanation. If a benchmark changes hardware as well as the claimed method, identify the change before relying on the comparison.
Ask business witnesses for purchasing evidence
Send business witnesses a bounded request tied to the relevant product and period:
Ask each witness what they personally observed, which records support the account, and who created or maintained those records. Preserve contrary customer comments and changes in the market alongside favorable evidence.
A useful interview question is: “Which dated record shows why this customer chose this product configuration?” It gives counsel a concrete starting point for the causal explanation.
In the 2026 inter partes review appeal Hafeman v. Google ↗, the Federal Circuit upheld the Board's treatment of secondary considerations where, among other problems, praise highlighted unpatented functionality and the commercial-success account lacked supporting evidence. Feature-specific source material matters more than a favorable headline.
Ask technical witnesses and experts for the bridge
The technical request should join the claim mapping to the reason the evidence matters:
MPEP §716 addresses comparative evidence and correspondence with claim scope. Its examination guidance provides useful collection questions; litigation counsel should apply the governing case law to the asserted claims and record.
For copying, seek development chronology and evidence of access, study, or replication. For long-felt need and failure of others, seek dated attempts addressing the same technical problem. Keep the underlying records attached to the explanation so the expert can address competing accounts.
Plan the evidentiary foundation during collection. Identify the personal-knowledge witness, record custodian, authentication route, and expert basis as appropriate. The evidence foundation rules ↗ separately address personal knowledge, expert testimony, business records, and authentication in Rules 602, 702–703, 803(6), and 901.
Turn the matrix into a litigation decision
Review the record claim by claim. For each proposed indicium, counsel should be able to state:
Then weigh the evidence with the prior-art and other obviousness evidence. A supported nexus gives the evidence relevance; counsel must still assess its weight in the complete record. Volvo Penta also illustrates the need to explain that weighting.
Keep separate claims and product releases separate when their supporting facts differ. A later release may introduce the feature that received praise. A broad sales total may combine configurations with materially different claim mappings. Mark those distinctions rather than carrying the same conclusion across the portfolio.
For production crosswalks and the broader matter handoff, use the invalidity contentions workflow ↗. The secondary-considerations record adds the causal explanation and witness requests that counsel needs for this specific issue.
Where Patlytics fits
Patlytics supports the claim, product, and prior-art analysis that supplies inputs to counsel's nexus record:
Counsel assembles the commercial records, witness accounts, and causal explanations in the matrix. Attorneys retain review and decision authority over sources, mappings, constructions, and legal positions.
Build a source-linked claim and product record for your obviousness assessment. Book a Demo → focused on Patlytics' invalidity and claim-charting workflows.
See it on your own patents
Reduce cycle times. Increase margins. Deliver winning IP outcomes.


















































