DOCA.1 - Bound the Development-Opportunity Inquiry

Type: DPF pattern

Status: Released; evolving

Normativity: Normative unless marked informative.

DOCA.1:0 - Use This When

What is the smallest useful inquiry when someone says “we should develop,” names a fashionable solution, or asks what to develop next before the receiving change is clear?

Use this pattern when a person, organization, community, AI arrangement, platform, facility, research programme, or another identified subject has a development concern or aspiration but the receiving use, horizon, protected conditions, reason to explore, or affordable inquiry effort is still loose. The first useful result is a bounded inquiry that another person can inspect, or one exact missing premise that prevents such an inquiry.

Begin here without appointing an adviser. A person can bound a self-inquiry and continue into opportunity construction. When a distinct performer is already being asked to advise a named recipient, this pattern can recover the subject, use, and horizon, but DOCA.7 governs whether the advising relationship itself is admissible.

Cheap exit. Reuse an existing inquiry when it already identifies the same subject, receiving use, horizon, protections, posture, and effort boundary and no material premise changed. If a qualified domain practice owns the whole question, use it directly. If adequate alternatives already exist and the remaining need is comparison, recommendation, or authorized choice, stop opportunity construction and use the direct decision-support owner.

Ordinary non-use boundary. A research account of change in a non-cultural population or lineage is not advice to that population. A separately authorized researcher may have an opportunity or decision question, but the researcher or sponsoring organization—not the population—then supplies the recipient and authority boundary.

DOCA.1:1 - Problem Frame

A broad wish such as “develop in AI,” “become more mature,” “modernize the platform,” or “build a learning culture” can point to several different subjects and receiving uses. It may concern a person’s capability for later Work, an organization’s contribution and arrangement, an engineered system’s service, an episteme or problem formulation, a research programme, or a proposed intervention. The same words do not make those subjects develop in the same way.

The practical danger appears before alternatives or advice. A course, tool, reorganization, model, supplier, or PatternID can become the answer before anyone names the receiver, useful difference, protected conditions, or evidence needed. The opposite failure is an unlimited discovery exercise whose growing list never returns a result that can be tested or used.

This pattern governs the inquiry boundary: the identified subject, receiving use, declared horizon, protected conditions, reason to explore, posture, inquiry budget, and first missing result. It does not establish a worthwhile problem, qualified opportunity, recommendation, choice, programme, Guide, performed Work, or observed development effect.

DOCA.1:2 - Problem

Without an explicit inquiry boundary:

• a solution label substitutes for the receiving contribution;
• “development” silently shifts among person, organization, technology, knowledge, and population meanings;
• a supplier’s promise is treated as the receiver’s problem;
• the horizon expands or contracts to make a favored direction look plausible;
• safety, workload, continuity, privacy, reversibility, or another protected condition appears only after a candidate has gained momentum;
• search effort grows without a proportional stopping reason; and
• missing authority or evidence is hidden by a polished opportunity statement.

The reader then cannot tell whether to characterize the subject, search neighboring possibilities, request a direct specialist result, bound an advising relationship, or stop.

DOCA.1:3 - Forces

DOCA.1:4 - Solution

Construct the smallest inquiry boundary that can direct one useful next action and expose one truthful stopping point.

DOCA.1:4.1 - Identify the subject and claim posture

Name what may develop or be changed at the grain that matters now: a particular person, organization, community arrangement, AI model-and-scaffold configuration, facility, platform, research programme, episteme, or another exact subject. If identification is provisional, state the candidate boundary and what would settle it.

Mark the claim posture. A proposed future contribution is not actual change. A plan is not performed Work. A model prediction is not an observed result. If development or evolution still hides the subject, continuity rule, or value claim, use E.10.DEV and return with the direct subject owner.

DOCA.1:4.2 - Identify a receiving use or an exploratory question

For a proposed contribution, state who or what could use it, in which situation, and what practical difference would matter. The receiving use may be the subject’s later Work, a service used by another System, an organization’s market or operating contribution, a research use, or a decision that consumes a qualified opportunity.

Keep the receiver’s useful difference separate from the subject’s desired learning, prestige, procurement, technology adoption, or internal activity. If no receiver or receiving situation can yet be named, keep that question open rather than inventing demand.

An inquiry can still start from material that someone can use or change: permitted records, a working procedure, a model or another construction. Name an available operation and a difference worth examining within the inquiry’s resources and permissions. C.40 supplies that development Method. Its result can suggest a receiving use for DOCA.2 or DOCA.3 to investigate. A useful local result can also finish the inquiry; it need not become a development opportunity.

DOCA.1:4.3 - Fix the horizon and protected conditions

Choose a horizon set only as finely as it can change the inquiry. A four-month inquiry may use several sub-horizons; another case may need one decision deadline and one longer consequence horizon. No universal near/middle/far sequence is implied.

Name conditions that the inquiry may not silently trade away. Depending on the subject and use, these can include safety, legal or professional limits, privacy, confidentiality, workload, service continuity, accessibility, resource ceilings, reversibility, distributional consequences, or preservation of future options. The direct practice owns their meaning and evidence.

DOCA.1:4.4 - State the reason to explore and separate its status

Write why exploration is warranted now. Distinguish:

• a qualified receiving problem or demand;
• an observed dissatisfaction or changed constraint;
• a proposed contribution or explicit problem hypothesis;
• a supplier promise, technology signal, or PatternID used only as a search lead; and
• curiosity that is valuable only if a bounded inquiry can be afforded.

Preserve competing formulations when they would send the inquiry toward different contributions. Use the direct problem-structuring pattern when deciding among those formulations is itself the current Work.

DOCA.1:4.5 - Set a proportional inquiry budget and permissions

Declare the effort, elapsed time, people, source access, conversations, computation, and other resources available for this inquiry. State the consequence level that would require stronger evidence before a later commitment.

Permission to inspect a source, interview a participant, or run a desk study does not authorize an intervention, access to restricted records, procurement, advice, or implementation. When the inquiry itself lacks permission, return the exact access or authority gap.

DOCA.1:4.6 - Select the first missing result

Ask which result would most change useful progress at the declared effort:

• a development-facing characterization from DOCA.1.CHR;
• materially different search leads from DOCA.2;
• a worthwhile problem and proposed contribution from DOCA.3;
• an admissible advising question or blocker from DOCA.7;
• a qualified result from a holder, evidence, safety, legal, professional, engineering, organization, operations, strategy, research, or other direct owner; or
• an honest stop because the existing opportunity or option set is already sufficient.

Start there. Publication order does not require all earlier PatternIDs to be used, and using this pattern does not create a lifecycle.

DOCA.1:4.7 - Return the bounded inquiry or exact gap

Use ordinary prose first. The following compact form can support a handoff when several people must inspect the same boundary:

BoundedDevelopmentOpportunityInquiry@Context:
  subjectAndBoundary:
  claimPosture:
  receivingUseAndReceiver:
  horizonSetAndDecisionWindow:
  protectedConditions:
  reasonToExploreAndStatus:
  knownPremises:
  suggestedButUnqualifiedPremises:
  inquiryBudgetAndPermissions:
  firstMissingResult:
  directOwnerOrNextPattern:
  stopOrReopenCondition:

This is a local working form, not a new root kind, WorkPlan, engagement, recommendation, or authorization. An unsettled future receiver can remain unknown while the local question guides the inquiry. Omit a field only when it cannot change the next action and that omission is apparent from the case.

A complete return can be modest: “For engineer-manager Mira’s incident-review contribution during the next four months, explore ways to reduce delayed handoff detection while preserving current service workload and confidential records. Spend up to six hours on characterization and source checks; first obtain the current and intended review characteristics. Stop before course selection or advice.”

DOCA.1:4.8 - Stop, reuse, and reopen locally

Stop when the bounded inquiry identifies a useful next result and its owner, when a truthful blocker prevents that result, or when the existing result is already sufficient for the receiving use. Do not widen merely to increase idea count.

Reopen only the affected boundary when the subject, receiver, receiving use, horizon, protected condition, posture, authority, source premise, or effort budget changes. A changed characteristic need not erase an otherwise usable inquiry; a changed receiving use may.

DOCA.1:4.9 - What changes in practice

Instead of starting with a course, tool, provider, maturity label, or long opportunity list, the practitioner can now say what is being explored and why, over what horizon, under which protections, at what cost, and which result is needed next. A proposed contribution also needs its prospective receiving use. That is enough to begin responsibly without pretending that a recommendation or choice already exists.

DOCA.1:5 - Archetypal Grounding

DOCA.1:5.1 - Person entering construction without an adviser

Mira manages an engineering team and says, “I should develop in AI this quarter.” The phrase does not yet name a receiving contribution. She identifies the subject as herself in her current engineer-manager configuration, the receiving use as improving incident-review and handoff Work over four months, and the receiver as her team and service organization. She protects current service workload, confidential incident data, and her ability to continue the existing role.

She allows six hours for an initial inquiry using current Work examples, two conversations, and qualified source checks. “AI” remains a search seed, not the result. The first missing result is a characterization of review quality, latency, explanation burden, and protected workload under DOCA.1.CHR. She can stop with that bounded inquiry without appointing an adviser or selecting a course.

DOCA.1:5.2 - Organization with a fashionable solution

An engineering company announces that it should “become platform-led.” The inquiry identifies the organization and a specific product-development arrangement, the receiving use as faster and more reliable product-family delivery, a twelve-month horizon with two decision windows, and protected safety, customer continuity, regulatory obligations, and scarce specialist attention.

The provider proposal is recorded as a suggested premise. Strategy owns any commitment, organization-change practice owns changed arrangements, systems and platform engineering own enabling-system realization, and operations owns continuing service. The first missing result is not a platform purchase decision; it is the development-facing characterization that can distinguish materially different contributions.

DOCA.1:5.3 - Advice can enter elsewhere

A committee already has three qualified development directions for an identified facility, a complete characterization, and a current joint-reachability account. Its current need is an independent recommendation. Repeating DOCA.1 adds no value. The adviser begins with DOCA.7 to establish recipient, mandate, competence, conflicts, disclosure, and reliance, then uses current decision-support results. The committee retains the choice.

DOCA.1:5.4 - Population anti-case

A researcher asks, “What should this non-cultural lineage develop next?” No population-local recipient or choice owner is identified. This pattern does not manufacture one. Evolutionary description remains with the applicable domain owner. If the researcher is instead deciding whether to fund an experiment, the researcher or sponsor becomes the decision recipient and a separately bounded research opportunity or decision inquiry can begin.

DOCA.1:6 - Bias-Annotation

• Solution-first bias: familiar technologies and providers can appear more concrete than the receiving use. Keep them as leads until a contribution is qualified.
• Human-development default: do not transfer learning, career, or capability mechanisms to organizations, AI arrangements, engineered systems, epistemes, or populations.
• Sponsor-recipient collapse: the funder, subject, receiver, adviser, and later choice owner may coincide, but name distinctions only when their difference changes protection, disclosure, authority, or use.
• Open-search prestige: a larger idea list can look more rigorous while avoiding the first discriminating question.
• Benefit-by-word bias: development, progress, and maturity establish no beneficial direction without characteristics, polarity, and evidence.
• Form bias: a completed record cannot compensate for an unidentified subject or the absence of a useful question.

DOCA.1:7 - Conformance Checklist

A conforming use or companion account:

1. MUST name the exact subject or provisional subject boundary and claim posture.
2. MUST state the receiving use and receiver when known. Otherwise, identify the local question being investigated and keep the future receiving use open.
3. MUST declare the horizon set or decision window that can change the result.
4. MUST expose protected conditions before candidate selection.
5. MUST distinguish qualified grounds, explicit hypotheses, supplier promises, and search leads.
6. MUST state a proportional inquiry budget and any permission needed for the inquiry itself.
7. MUST identify the first missing result, its direct owner or next pattern, and the smallest useful return.
8. MUST NOT present the inquiry as a recommendation, choice, programme, Guide, performed Work, observed effect, or intervention authority.
9. MUST preserve independent Construction and Advising entry; no PatternID order may be presented as a mandatory lifecycle.
10. MUST state a stop or local reopen condition.
11. SHOULD use ordinary prose before any compact form.
12. MUST return a specific gap or non-use case when the subject or a condition needed for the proposed inquiry cannot be established.

DOCA.1:8 - Common Anti-Patterns and How to Avoid Them

DOCA.1:9 - Consequences

The inquiry becomes cheap enough to start and strong enough to direct a useful next move. A person can explore without inventing an adviser; an adviser can reuse an adequate boundary without forcing construction; and a missing premise becomes a named request rather than hidden uncertainty.

The cost is explicit incompleteness. The result may be only a question, blocker, or narrow source request. Naming the subject, horizon, protections, posture, and budget also makes attractive but unsupported directions visibly weaker. That is preferable to premature certainty.

This pattern does not guarantee that search will find a worthwhile opportunity, that the subject can change, or that any later recommendation, choice, programme, Work, or effect will succeed.

DOCA.1:10 - Rationale

The earliest reusable contribution is not generic goal setting or decision-support engagement. Opportunity construction often begins before a decision, option set, or separate adviser exists. Yet a fully unbounded discovery activity cannot distinguish useful exploration from fashion following.

The selected boundary is therefore intentionally small: enough identity, use, horizon, protection, posture, and effort to choose one missing result. Characterization, opportunity search, problem construction, support configuration, reachability, portfolio retention, advising, and refresh remain separable because each changes the practitioner’s action and can be entered or stopped independently.

DOCA.1:11 - SoTA-Echoing

Practice question. How should early opportunity or idea work begin before a solution-development commitment while remaining usable across unlike development subjects?

Best-known line for this pattern. ISO 56007:2023 supplies the current opportunity/idea-management boundary before solution development and deployment. FPF E.10.DEV supplies the stronger cross-holder repair: identify the changed or represented subject, claim posture, direction basis, and direct owner rather than treating development as one mechanism. This pattern adapts those contributions in DOCA.1:4.1–4.7 by adding the receiving use, protected conditions, proportional inquiry budget, independent no-adviser entry, first-missing-result return, and explicit stop.

Serious alternative or default. A project brief that starts with a fixed goal and preferred solution is cheaper when the problem and option boundary are already adequate. Unbounded ideation is more open when the inquiry is exploratory. The first excludes useful pre-goal discovery; the second lacks a proportional return. At comparable initial effort, the bounded inquiry preserves both openness and an inspectable next result, at the price of leaving more conclusions provisional.

Source roles and limits. ISO 56007 is a normative opportunity/idea-management source, not evidence of effectiveness or a universal cross-holder procedure. E.10.DEV is the internal best-known line for semantic recovery, not a holder-specific development Method. Domain, professional, legal, safety, evidence, and decision practices retain their conclusions.

Reopen condition. Reopen this source stance if a current alternative demonstrates a lower-effort entry that preserves subject and posture distinctions, receiving use, protections, independent branch entry, proportional stopping, and exact owner return, or if ISO 56007 changes the opportunity-to-solution boundary relied on here.

DOCA.1:12 - Relations

• Uses: E.10.DEV to recover the subject, posture, and direct owner when development wording changes the next action.
• Prepares: DOCA.1.CHR when selected characteristics and current, intended, protected, or unknown readings are the first missing result.
• Prepares: DOCA.2 or DOCA.3 when the inquiry needs materially different leads or a worthwhile problem and proposed contribution.
• Coordinates with: DOCA.7 when a distinct recommending performer and recipient make advising admissibility current; this pattern does not establish that relationship.
• Returns to: the exact holder, evidence, professional, legal, safety, engineering, organization, operations, strategy, research, or other practice that owns a missing premise.
• Hands later comparison and recommendation outward: current Problem Structuring and Decision Support patterns own formed decision alternatives, comparison, recommendation, follow-up, and choice separation.
• Does not imply: a Method sequence, programme, WorkPlan, performed Work, authorization, beneficial effect, publication order, or product membership.

DOCA.1:End