DOCA.3 - Construct a Worthwhile Problem and Proposed Contribution

Type: DPF pattern

Status: Released; evolving

Normativity: Normative unless marked informative.

DOCA.3:1 - Problem Frame

Use this when a development lead names an attractive niche, technology, course, service, or provider promise, but the receiving use and the reason to change it remain unclear. Someone may say “we need AI,” “become a leader,” or “offer faster analysis” without identifying whose result is unsatisfactory, what difference matters, or what could actually be supplied.

Start by asking the receiver what is missing or foregone in one bounded use. Relate that problem to a proposed contribution and an inspectable acceptance expectation. The first useful result is a supported worthwhile problem or an explicitly unconfirmed problem hypothesis, together with the proposed contribution, its limits, and the question that could confirm, narrow, or reject it.

The subject that might develop and the receiver of its later contribution can differ. A person may explore their own future Work without an adviser; an organization may investigate a contribution for a client; a research programme may seek an epistemic contribution rather than a commercial offer.

Ordinary non-use boundary. Reuse an adequate problem/contribution account when its receiving use, evidence, protections, and horizon remain current. Proceed to DOCA.4 if only the way of obtaining that contribution is missing. Use PSD.3 when a bounded decision-support inquiry needs materially different problem formulations. This pattern does not establish an actual commitment, choose a direction, or justify intervention by itself.

DOCA.3:2 - Problem

A niche, a worthwhile problem, and a proposed contribution answer different questions. A niche is a possible fit between a contribution and a use. The problem explains why an inadequate or foregone result matters there. The contribution says what could be supplied and how the receiver would recognize it.

If these are collapsed, a supplier’s enthusiasm becomes demand, a proposed offer becomes a commitment, and a useful intermediate result becomes a promise of benefit. “Recover missing evidence” turns into “approve faster,” although neither the time saving nor the approval is established. Alternatively, a practitioner rejects a useful problem merely because no feasible way to address it is known yet.

The needed move is to make the value and contribution claims separately inspectable, preserving uncertainty without losing a worthwhile next question.

DOCA.3:3 - Forces

DOCA.3:4 - Solution

Write a small, source-qualified account of why a change could be worth pursuing and what contribution would answer it. Keep a supported problem, an open hypothesis, and a rejected lead visibly different.

DOCA.3:4.1 - Recover the receiver’s situation

Name the developing subject, the prospective receiver, the later Work or use, the horizon, and the relevant conditions. Ask what result is currently inadequate or unavailable, what happens if nothing changes, and which evidence or participant account supports that description.

Use qualified evidence about actual Work or receiving demand when it exists. A receiver’s report can establish their stated concern; its causal explanation, scale, representativeness, and effects on others may still need qualification. Do not infer organization-wide demand from one person’s preference.

If the inquiry cannot yet identify a receiving situation, use DOCA.1 or DOCA.2 to recover a worthwhile next question. When usable material and an available operation permit a revealing local change, their C.40 entry lets that inquiry proceed before its future application is settled. A use suggested by the result is then a problem hypothesis to examine here. Keep an unknown receiver explicit; do not invent a customer to complete the account.

DOCA.3:4.2 - Separate the problem from the proposed answer

Describe the missing or inadequate result without building in one technology, provider, training programme, or staffing answer. Then state the proposed contribution separately.

For example:

• Problem: an acceptance engineer cannot recover which submitted claims lack a sufficient evidence basis before the handoff review.
• Proposed contribution: an inspectable claim-to-evidence account that identifies supported claims, missing premises, and qualification limits in the permitted source set.
• Acceptance expectation: the receiver can trace each entry to its source and identify unresolved claims under the applicable review criteria.

Faster approval is a different benefit claim; automatic approval is a different contribution and authority question. Preserve those differences if they become live rather than silently extending the proposal.

If rival problem formulations change the subject, boundary, evidence, intervention family, or affected interests, keep them distinct. PSD.3 supplies plural formulation work when a decision-support engagement is current. A change of wording that leaves those consequences identical does not create another worthwhile problem.

DOCA.3:4.3 - Establish what makes the problem worthwhile

Ask who is affected, why the missing result matters, at what scale and horizon, and under what burdens and protections addressing it could be worth pursuing. Include material contrary evidence and consequences for affected people or Systems, not only the proposed beneficiary.

Use the domain practice that owns each relied-on claim. A human capability need belongs with current HCD and representative later-Work evidence; a service failure belongs with the relevant operations and domain evidence; safety, access, finance, legal, and other specialist claims retain their own qualification. Use DOCA.1.CHR when the value account relies on unclear or incompatible characteristics.

Return the strongest supported statement:

• a worthwhile problem for this receiving use under stated conditions;
• an attributed or contested value claim requiring a named resolution;
• an unconfirmed problem hypothesis with the exact confirming question; or
• rejection or revision of the lead because no worthwhile problem is supported at the chosen scale.

A receiver’s desire alone does not defeat a binding protection. Conversely, missing feasibility does not disprove the problem: retain the worthwhile problem and name the unresolved way of addressing it. For a comparative claim such as “worth the transition cost,” obtain the applicable comparison rather than treating this inquiry as its proof.

DOCA.3:4.4 - State the proposed contribution and its acceptance expectation

Say what could be supplied, for which receiving use, under what conditions, with what exclusions, and what the receiver could inspect to determine whether that contribution was supplied as proposed. Keep the proposed result, the acceptance criterion, and any actual acceptance separate.

Use A.2.3 when a promise’s content must be identified or relied on. Read an existing provider promise from its actual source; mark a newly constructed promise as proposed. Neither description establishes a provider commitment, capability, access, provision, fulfilment, or achieved benefit.

A research contribution can be a criticism, discriminating experiment, reproducible comparison, or clarification of an unresolved claim. It need not be sold, but its intended epistemic result and evidence standard must still be inspectable. Do not impose a commercial service model on that use.

DOCA.3:4.5 - Link the contribution to the problem without assuming success

Explain why the proposed result could address the missing receiving result. Mark that connection as supported, conditional, disputed, or hypothetical according to its evidence. Identify what a plausible contrary answer would change.

Ask the smallest question that distinguishes the live possibilities. “Does the reviewer need a source-traceable account of unsupported claims, or is the delay actually caused by unavailable acceptance authority?” can redirect the contribution. “Would you like better AI?” cannot distinguish the problem from the preferred solution.

Use existing adequate results before requesting new Work. When another practice must supply an answer, use A.15.9 for the bounded result request and reliance boundary. The supplying practice answers its own substantive question. A proposed interview, measurement, or experiment still needs the permissions and conditions applicable to that activity.

DOCA.3:4.6 - Return the account at the strength it supports

Ordinary prose is enough when the receiver can recover the situation, worthwhile difference or hypothesis, contribution, acceptance expectation, evidence limits, and next question. For example:

The case’s acceptance engineer reports that unsupported claims cannot be recovered reliably from the incoming package, and the stipulated review records support that concern. We propose a source-traceable claim-to-evidence account, not approval; the next question is whether the available records and review criteria cover a representative package without breaching confidentiality.

Use DOCA.4 when the contribution premise is adequate and materially different directions need construction. Return to DOCA.2 when the lead must change. Stop with a problem hypothesis or rejection when that is the truthful result. If an adequate direction already exists, proceed directly to the missing reachability, comparison, or advising result; no mandatory cycle through earlier PatternIDs follows.

Reopen the affected problem or contribution under DOCA.8 when the receiving use, value evidence, acceptance expectation, source, horizon, or protected condition changes. A narrower permitted source set can narrow one proposed contribution while leaving the receiver’s problem and another direction intact.

DOCA.3:5 - Archetypal Grounding

DOCA.3:5.1 - Qualification support is not faster approval

This constructed example stipulates an engineering-services unit’s ninety-day inquiry. Its acceptance engineer reports repeated difficulty finding unsupported claims in incoming evidence packages; the example’s review records corroborate that bounded concern. Confidentiality, traceability, independent acceptance, and tolerable review burden are protected.

The technology lead was “use a long-record model.” The problem/contribution account instead proposes a claim-to-evidence account for one class of package. The acceptance expectation is that the reviewer can recover each included claim’s cited support and identify unresolved premises under the relevant criteria. A manual index and bounded retrieval assistance could both serve that proposal.

No result yet establishes faster approval or representative model accuracy. The first useful return preserves the worthwhile qualification problem while marking the processing route as conditional on purpose-specific access and evaluation. If the data owner permits only public, non-representative samples, a narrow demonstration remains possible; the original representative-use claim remains unsupported.

A rival lead concerns shift exceptions and the next authorized handoff action. That is a different receiving problem, not a second implementation of the same qualification account. The two remain distinct for later direction construction.

DOCA.3:5.2 - Receiver inquiry rejects a supplier lead

A supplier offers a dashboard to a small unit as an “AI transformation.” In this constructed case, the unit’s current result meets its acceptance needs, its receivers identify no consequential unmet result at the proposed scale, and the proposal adds review burden. No independent protected or foregone-result concern is established.

The inquiry rejects this lead for the current use. It does not claim that the technology is universally useless. Retaining the idea for a different receiving question would require that question and a retention reason, not relabelling the rejected proposal as a worthwhile opportunity.

DOCA.3:5.3 - A research problem remains a hypothesis

A research group suspects that an evaluation loses important failure cases when several task types are pooled. The proposed contribution is a reproducible comparison between the pooled and separated analyses, with explicit limits on what any difference would establish.

The problem is provisional: no result yet shows that the suspected loss changes the relevant scientific conclusion. The next question is whether the comparison exposes a conclusion-changing discrepancy on an admissible dataset. A negative answer closes or narrows the hypothesis; a positive answer motivates further research. Publication, funding, and improved model performance are not part of the proposed epistemic result.

DOCA.3:6 - Bias-Annotation

• Solution-first framing: the supposed problem contains the technology or intervention it is meant to justify.
• Receiver-preference inflation: one person’s interest is treated as established demand at another scale.
• Benefit inflation: an inspectable intermediate contribution is described as a guaranteed downstream improvement.
• Supplier authority: an offer is taken as evidence of need, capability, or fulfilment.
• Commercial projection: a research or community contribution is forced into a sales promise.
• Feasibility contamination: an unknown solution causes rejection of a still-worthwhile problem, or a feasible tool creates a supposed need.

DOCA.3:7 - Conformance Checklist

A conforming problem/contribution account:

1. MUST identify the developing subject, receiving use, horizon, and relevant protected conditions.
2. MUST distinguish the inadequate or foregone result, why it matters, and the proposed contribution.
3. MUST distinguish a supported worthwhile problem, an attributed or disputed claim, an unconfirmed hypothesis, and rejection where those outcomes are live.
4. MUST preserve material contrary evidence, affected-System consequences, and burdens that can reverse the worth claim.
5. MUST state an inspectable acceptance expectation without reporting actual acceptance or achieved benefit.
6. MUST distinguish a proposed promise from an existing promise and both from commitment, provision, and fulfilment.
7. MUST expose the evidence or hypothesis linking the contribution to the problem and the next discriminating question.
8. MUST NOT infer need from novelty, a supplier offer, or solution feasibility, or reject a supported receiving problem solely because solution evidence is missing.
9. MUST return to the next missing result or stop; a direction, recommendation, choice, or intervention is not required to complete this account.

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

DOCA.3:9 - Consequences

The practitioner can distinguish what might be worth addressing from what could be supplied. A useful hypothesis can survive without invented evidence, and a supplier lead can be rejected before it consumes a development programme or procurement budget. Later direction construction has an inspectable premise rather than a slogan.

The cost is receiver and evidence inquiry. Different people may value the proposed change differently, and the available evidence may justify only a narrower problem or an unanswered question. This pattern makes those limits visible; it does not settle domain truth, comparative value, or authority by naming an opportunity.

DOCA.3:10 - Rationale

Separating problem, proposed contribution, and acceptance expectation lets each be challenged without discarding the others. A receiving difficulty can remain valid when one delivery route fails. A contribution can be precisely described while its worth remains hypothetical. The distinction prevents both premature commitment and premature rejection.

An explicit confirming question gives provisional value a practical use. It says what the next answer would change instead of treating uncertainty as either permission to promise or a reason for indefinite research.

DOCA.3:11 - SoTA-Echoing

Practice question. How can a promising lead become a worthwhile receiving problem and proposed contribution without importing the supplier’s preferred solution or overstating benefit?

Best-known line for this use. Combine receiver-grounded problem inquiry with an explicit problem/contribution distinction. ISO 56007:2023 supplies the bounded opportunity/concept front-end before solution development. Current PSD.3 supplies materially different formulations and their evidence consequences; A.2.3 supplies promise-content identity without conflating commitment and fulfilment. This pattern adapts those contributions in :4.1–:4.6 to one prospective development contribution and its confirming return. Domain evidence, rather than the source combination, supports the actual worth claim.

Serious alternative and trade-off. An offer-led brief is cheaper when a qualified receiving need and acceptance basis already exist. When they do not, it hides the problem inside the offered answer. At comparable bounded inquiry effort, asking what result is missing and what would count as a supplied contribution can distinguish qualification support from faster approval and from shift handoff in :5.1. A full decision-modeling engagement can handle richer competing values, but is unnecessary when a short receiver account or a negative answer resolves the lead. Use that fuller work when it changes the decision rather than making it an entry requirement.

Source roles and limits. ISO supplies normative scope, PSD.3 formulation guidance, and A.2.3 semantic distinctions. None establishes this receiver’s need, a causal benefit, professional authority, or the empirical effectiveness of this cross-holder inquiry. A commercial promise is one possible use, not the template for every epistemic or community contribution.

Reopen. Reopen the affected move if current practice supplies a better low-burden way to expose false need, overpromised benefit, or consequential missing participants while preserving a usable first return; or if a relied-on source changes the problem, value, or promise boundary.

DOCA.3:12 - Relations

• Receives from DOCA.1 and DOCA.2: the bounded inquiry and leads whose receiving contribution remains uncertain; adequate direct inputs may be reused.
• Uses DOCA.1.CHR: characteristics and scales needed to make a worth or contribution claim interpretable.
• Uses PSD.3: plural formulations when their structural differences change a bounded decision-support inquiry.
• Uses A.2.3: identity and conditions of relied-on promise content, distinct from commitment and provision.
• Uses A.15.9: the smallest missing outside-practice result and its reliance boundary, without performing the supplier’s Method.
• Supplies DOCA.4: worthwhile problem/proposed-contribution accounts, including explicit hypotheses and acceptance expectations.
• Supplies DOCA.5: the value and contribution claims whose necessary transitions still need qualification; a worthwhile problem is not a reachability verdict.
• Uses DOCA.8: local requalification when receiving need, source, acceptance, protection, or horizon changes.

DOCA.3:End