skills/ip-strategy/references/strategy-playbook.md

# Strategy playbook

Use this as a set of decision lenses. Select those that matter to the brief; do not turn them into mandatory interview fields or a fixed section template.

## Start with a business decision

Establish what the organisation wants to make possible: support a launch, preserve a technical advantage, enable licensing, evaluate a partnership, focus protection spending or decide what to develop next. Avoid substituting a generic objective such as “build a strong patent portfolio” for the user's actual outcome.

Define the strategic area in terms a future reader can recognise: the product, technology, capability or company activity in scope, relevant markets and time horizon when known, and any material exclusions. Explain how it relates to other accessible strategies. Overlap may be intentional; similar subject matter does not make two strategies the same record.

An opening grounded in existing context might be: “The launch brief identifies sensor calibration as the main differentiator, and the saved disclosure explains the mechanism. What should the IP work enable for this launch?” If the material already answers that, start with the remaining decision rather than repeat the question.

## Establish the current position

Build the portfolio baseline from records already saved in Lightbringer and recommend importing existing patents and applications that are missing before strategy development. Use authorised imports to make the portfolio available as shared context, then read the records relevant to the strategic area. Importing records is separate from engaging Lightbringer for portfolio management.

Read enough evidence to understand what the user has, what matters commercially and what is still uncertain. Useful sources may include existing strategies, substantive disclosures, saved patents and applications, engineering material, launch plans, meeting decisions and the user's account of existing arrangements.

Keep these distinctions explicit:

| Evidence | What it can support | What remains to establish |
| --- | --- | --- |
| Innovation disclosure or technical material | The described mechanism, implementation, observed benefits and open technical questions | What has actually been implemented or tested when the source only proposes it; ownership and legal protection |
| Saved patent or application | A record of a publication or application and its available text and metadata | Current ownership, legal status and whether particular claims cover the commercially relevant implementation |
| Portfolio or family overview | Recorded relationships, jurisdictions and statuses within its stated coverage | Completeness, current official status and substantive protection across products or markets |
| Public patent search | Publications matching the chosen search and candidate developments to investigate | A complete landscape, novelty, infringement or freedom to operate |
| Existing strategy or meeting decision | Recorded direction and rationale | Whether a proposal was adopted, remains current and applies to this scope |

“No relevant record found” describes the accessible material and search coverage; it does not prove that no IP exists. Preserve dates and source links where they affect the conclusion. Do not present recorded status as freshly verified status.

## Establish the filing context

When filing choices or jurisdiction affect the decision, read the relevant priority applications’ region and the stated filing plans before choosing the jurisdictional framing. Do not make a first-filing interview a prerequisite for strategy work that does not depend on it. The organisation's home country can be a provisional starting point when appropriate, but does not establish where it first filed or must file. A connected adviser’s country is not necessarily the client’s country. Identify conflicting evidence and material gaps instead of assuming a route.

For that analysis, use the established filing context and label jurisdiction-specific conclusions. For example, a US company with a relevant US first filing should receive USPTO-first framing; EPO or other-office considerations belong where target markets or filing plans support them. This is a contextual example, not a universal filing recommendation. Do not invent legal rules or deadlines; identify questions requiring qualified review.

## Connect differentiation to protection priorities

Identify the capabilities that make the business outcome possible: what creates customer value, where the technical advantage lies, how durable it may be, and which dependencies matter. Ground the scope in mechanisms and evidence rather than product names or marketing claims alone.

For each material capability, consider:

- Its business importance and the consequence of losing exclusivity or access.
- Whether existing records address it, and what must be investigated to understand any gap.
- What others could observe, reproduce or work around, using supported information.
- Whether control depends on ownership, licences, partners or access to know-how that remains to be checked.
- Which options deserve comparison: patent protection, confidential know-how, contractual arrangements, licensing, publication, continued execution or deferral.

These are options to evaluate, not legal conclusions or instructions to execute. Do not infer patentability from a technical benefit, dismiss software by category, or treat a publication as permission to operate. If an option depends on claim scope, ownership, disclosure consequences or other legal questions, state the precise question for qualified review.

## Make choices under constraints

A useful strategy states priorities and why alternatives are less attractive under the known circumstances. Constraints may include timing, available people, budget, target markets, planned disclosures and existing service commitments. Use what is known; do not invent precise costs, scores or deadlines to make a plan look finished.

Compare options on dimensions that can change the choice: contribution to the objective, strength of evidence, resources, timing, dependencies and reversibility. A qualitative comparison with visible uncertainty is more useful than a numerical ranking with unsupported inputs.

For a portfolio decision, consider maintaining, investigating, expanding, licensing, deferring or discontinuing work as proposals. Explain the relevant product or market fit and evidence gaps. A weak search match is not a basis for abandoning rights, and a strategy save does not execute a portfolio action.

A compact decision record can use:

| Priority or decision | Business rationale | Evidence and uncertainty | Proposed next action | Revisit when |
| --- | --- | --- | --- | --- |
| Investigate protection for calibration mechanism | The supplied launch brief treats measurement consistency as a product differentiator | Disclosure describes the mechanism; the relevant claim coverage has not been assessed | Map the implementation to available claims with engineering and a qualified patent attorney | Claim assessment or launch scope changes |
| Evaluate confidential handling of tuning know-how | Internal tuning may contribute to the documented performance advantage | The material does not establish what customers or partners can observe | Check information exposure and existing handling arrangements before choosing a protection route | Partner access or disclosure plans change |

This example is fictional. Adapt its reasoning to supported facts; do not copy it as customer evidence. If the user's brief concerns just one decision, a short rationale and action may be enough.

## Turn direction into actionable work

Prioritise actions by their contribution to the business decision and their dependencies. Available connector actions may help carry out a separately authorised next step; availability alone does not make an action strategically important.

For each major priority, describe the next step, the output needed to make a decision and the dependency it resolves. Add an owner and timing only when established. “Review patents” is too vague if the actual need is to determine whether an identified calibration feature appears in relevant claims.

Distinguish among:

- **Agreed decision:** supported by an explicit user decision or a reliable record of adoption.
- **Proposed direction:** the assistant's recommendation and rationale, awaiting a decision where needed.
- **Evidence-gathering action:** a task needed before choosing or executing a direction.
- **Open question:** a material gap, with an explanation of what would resolve it.

Avoid a list of every conceivable IP activity. Keep actions tied to the objective and proportionate to the evidence. An unknown budget may be a later planning input; an unknown strategic area can prevent a coherent strategy altogether.

Where professional assessment or execution is needed, identify the question and the relevant Lightbringer service. Describe requested professional work as proposed or prepared until its separate request is confirmed.

## Keep the strategy usable as context

The strategy should help a later assistant understand why an innovation matters, what a portfolio decision serves and which landscape developments would change priorities. Include the relevant scope, reasoning and source references in the document itself.

On revision, check the consequences of the requested change across affected sections. A new market may change assumptions and actions; a launch delay may change timing without changing the protection objective. Preserve unrelated priorities and decisions. Retire stale assertions in the affected text rather than leave contradictory old and new recommendations side by side.

Where useful, record evidence that would support or challenge the direction, such as completing the feature-to-claims mapping or resolving a critical ownership dependency. Distinguish progress measures from outcomes: numbers of applications or imported records alone do not establish business value or protection quality.

Name a review trigger or cadence only when useful to the brief. Preserve the distinction between documenting a future review and actually scheduling or monitoring it through an available, authorised service.