ME.1 - Choose and Reopen the Project’s Method-Engineering Focus

Primary working result: a Method-focus result that selects one Method, an established family or explicitly local grouping, a set of Method relations, or a non-Method return for one project decision. The result preserves every Method or candidate-account status and names one observation that would reopen the focus.

ME.1:0 - Use This When

Use this pattern when a project says that its “methodology”, “process”, “workflow”, or “way of working” must change, but the decision subject is still ambiguous. The live concern may be one Method, several related Methods, an established Method family, a temporary comparison grouping, or something else such as a tool, capability, support arrangement, description, resource, or project System.

Begin with the result that is missing, late, unsafe, or too costly and the representative Work in which that result matters. Recover the Methods and candidate accounts already visible there before choosing the level of focus.

The first useful move is to compare four possible focus classes: one Method; an established family or project-local grouping; named Method relations; and a non-Method return. The practical gain is that later repertoire, qualification, or architecture Work receives the smallest subject it can act on without inventing a Method or a composite.

Do not use ME.1 merely because one tool failed, one practitioner lacks capability, one document is incomplete, or one project, process, or case view is inconvenient. Return that question to its direct subject unless changing a Method would change the receiving result.

ME.1:0.1 - Working Distinctions

Name used here	Meaning
Method	A reusable way of obtaining or preserving a result, identified under `A.3.1` for the relevant participant meanings, applicability, and limits.
candidate Method account	An episteme that states a possible reusable way of doing while one or more Method-identification conditions remain open. The account is not the Method.
established Method family	Identified Methods connected by an independently governed family classification or membership basis. Shared use or resemblance is insufficient.
project-local grouping	A temporary set of identified Methods and candidate accounts collected by a stated criterion for one comparison or selector use. Its label creates no family or membership fact.
Method-relation focus	Named Methods and candidate accounts plus the relation kinds whose truth could change the project decision. It need not contain a composite whole.
project, process, or case account	A description whose direct subject is recovered from its claims under `A.15.6` and `C.2.1`. It is a `U.View` only through its own `E.17.0` conformance relation. Several accounts can concern one Work; they can instead concern a plan, Method, result, or other subject.
non-Method return	A result that redirects the decision to the actual subject, relation, and next useful question while naming what observation would reopen Method Engineering.

ME.1:1 - Problem Frame

Project teams encounter Methods through handbooks, standards, stage models, issue trackers, training, job titles, toolchains, and remembered practice. These can reveal useful Methods, but their visible boundaries rarely coincide with Method identity.

A project schedule can describe intended Work, a process account a reusable Method, and a case account the condition or acceptance of a named result. These descriptions can reveal connected Method questions without sharing a subject. When several accounts actually concern one admitted Work, preserve that identity across them. Recover the claim and subject before selecting a viewpoint; changing a representation creates neither another Work nor a Method.

ME.1:2 - Problem

A focus chosen too broadly turns every artifact and supporting System into a Method part. A focus chosen too narrowly optimizes one operation while the receiving result still depends on several Methods or a support relation. A familiar label can also turn a project-local shortlist into an alleged professional family.

The project then asks the wrong downstream question. It builds a repertoire for a tool problem, qualifies a candidate account as though it were an identified Method, or compares “architectures” that are only differently drawn views of the same Work.

ME.1:3 - Forces

Force	Tension
Affordable entry	A project needs a quick focus, while Method identity and family membership cannot be assigned by convenience.
Several useful grains	One operation may be actionable, while relations among several Methods may control the result.
Familiar labels	Project, process, case, agile, model-based, or AI wording aids conversation, while it can hide the actual subject.
Established and local plurality	A maintained family can support reuse, while a local grouping can remain useful without pretending to be one.
Reopening	The first focus must guide action now, while new Work evidence may reveal a tool, capability, or relation problem instead.

ME.1:4 - Solution

Select the smallest focus class whose subject and status are supported and whose change could alter the receiving result. Keep the rejected focus options and one observable reopen condition in the result.

ME.1:4.1 - Pattern-Use Unfolding

Name the receiving result and decision. State the result at risk, who will use it, the relevant situation and interval, and what decision the focus will enable.
Recover representative Work. Identify the Work occurrence or intended Work that exposes the difficulty. Use A.15.6 to keep the project System, use, Work, Method, support, and development subjects distinct.
Recover the subjects of the accounts already in use. For each project, process, case, lifecycle, stage, or workflow description, state what its claims concern, their actual or intended status, the question exposed, and the material omissions. Use A.15.6 when the label hides the subject. Keep unlike subjects separate; a claimed view additionally needs its exact viewpoint and E.17.0 conformance result.
Recover Method-status candidates. List Methods already identified under A.3.1, candidate Method accounts, established family facts, local groupings, related Methods, and support or capability alternatives. Preserve their statuses.
Form materially different focus options. Include each plausible one-Method, plurality, relation, and non-Method branch. A renamed package or differently drawn view is not another focus option.
Test family and relation claims. Use G.5 for any maintained family or selector claim and the applicable relation pattern for each direct relation. When no identified whole and obtaining relations exist, retain a relation focus or local grouping rather than a composite.
Choose and record. Use C.11 or a domain decision Method to select one focus for the receiving decision. State rejected options, evidence limits, next useful result, and the observation that reopens the focus.

ME.1:4.2 - Record the Result

Result position	Required content
use boundary	Receiving result and decision, situation, interval, project System or other subject, and decision authority when a choice is asserted.
representative Work	Actual or intended Work relevant to the decision, with its result and participant meanings.
accounts used	Each account’s direct subject, claim, question, important loss, and effect on the focus; exact viewpoint and conformance result when a view is claimed.
Method-status inventory	Identified Methods, candidate accounts, established family facts, local groupings, related Methods, and non-Method alternatives.
options and choice	Four focus classes considered, selected class and subject, rejected options, basis, and unresolved claims.
continuation	Next result needed and one observable reopen condition.

ME.1:4.3 - What Changes in Practice

The project stops asking which named methodology should replace another. It first decides whether the live subject is one Method, a governed family or local grouping, relations among several Methods, or a non-Method condition. Downstream Work becomes smaller, and a useful plurality can remain plural without being packaged as a fictitious composite.

ME.1:5 - Archetypal Grounding — EC-417 Release Focus

In the EC-417 release scenario, eight of twenty releases reopened. The package is commonly called the “release methodology”, so the first proposal is to replace it as one Method.

Three management questions expose different subjects in this scenario:

Management question	Direct subject and claim	Boundary
project scheduling	The release WorkPlan states intended integration at `D-21`, signed evidence at `D-8`, release at `D0`, and required people and rig time.	These are intended Work and resource claims; the schedule establishes no performed release Work.
recurring checks and approvals	The four identified Methods below supply reusable verification, integration, supplier-approval, and authorization actions; the reconciliation accounts remain candidates.	Keep each Method or account as its own subject; recurrence and co-use establish no composite Method.
closure of the pinout-evidence question	The claim to settle is whether the signed pinout and the version used in integration satisfy the release’s evidence condition.	Recover the relevant evidence and acceptance rule; the record itself establishes neither satisfaction nor release authority.

The status inventory contains four identified Methods: M-HW-Verify, M-SW-Integrate, M-Supplier-Approve, and M-Release-Authorize. It also contains candidate accounts C-Evidence-Reconcile-Internal, C-Evidence-Reconcile-Supplier, and C-AI-Trace-Review. C-EC-Release-v2 is only a proposed-whole account. The PLM, CI, test rig, AI provider, safety capability, and supplier responsibility are support, System, capability, access, or assignment subjects rather than Method candidates by position.

Focus option	Result
one Method: `C-EC-Release-v2`	rejected because the whole is not identified as a Method
established release-Method family	rejected because no governed family membership is supplied
project-local `LG-EC417-ReleaseMethods` grouping	retained only as a comparison locator; no family claim
candidate account: `C-AI-Trace-Review`	not selected as the current focus because its bounded trace suggestions govern neither evidence reconciliation nor release authority; candidate-account status is preserved
relations among the four Methods and two reconciliation accounts	selected because evidence timing, result use, allocation, and authority relations change the release decision
test-rig support decision	retained as a rival non-Method return, but current evidence does not make it the sole focus

The schedule exposes a timing conflict, the reusable accounts expose the checks and guards, and the case question identifies the evidence condition still to settle. These connections support a Method-relation focus without making the three subjects one Work. The first result is therefore a Method-relation focus. It creates no fifth Method and no composite. Reopen to a test-capability focus if two of the next three comparable delays occur while required evidence is complete and the rig is unavailable.

ME.1:6 - Bias-Annotation

Recurring bias	Likely drift	Repair
package bias	The boundary of a standard, methodology, or tool suite becomes one Method boundary.	Recover the receiving result, Work, Methods, accounts, and support subjects before choosing focus.
management-view bias	A familiar management label fixes every description to one Work or creates a new kind.	Recover the direct subject from each claim before applying its viewpoint; retain one Work only where the claims concern that Work.
family-language bias	A local shortlist is presented as an established professional family.	Name its criterion and bounded use and retain unresolved family status.
composite bias	Co-use of several Methods becomes a whole Method.	Select a relation focus until whole identity and obtaining relations are separately supported.

ME.1:7 - Conformance Checklist

The Method-focus result names the receiving result, representative Work, and current decision.
Every Method and candidate account keeps its prior status.
An established family cites an independent classification or membership basis.
A project-local grouping states its criterion, use, and non-family status.
Project, process, and case accounts preserve their actual direct subjects and intended or performed status; a claimed view has its own viewpoint-conformance basis.
The options include a non-Method return whenever a tool, capability, support arrangement, description, resource, or System could be decisive.
The selected focus states rejected focus options, uncertainty, next useful result, and an observable reopen condition.
Method, family, relation and composite claims rely on their identifying evidence; package position, a view or shared use alone is not that evidence.

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

Anti-pattern	Repair
“The process failed, so change the Method.”	Identify the result, Work, view, Method, and non-Method conditions before selecting the subject.
“These methods are our family.”	Use a local grouping unless governed membership is independently established.
“The tracker shows the real process.”	Recover what the recorded claims concern and their coverage and loss; a tracker label establishes neither a Method nor a view.
“Several contributors imply one composite.”	Return a Method-relation focus and send a proposed whole to ME.7 only when that later question is live.
“Choose the smallest item.”	Choose the smallest decision-changing subject, which may be a relation focus rather than one operation.

ME.1:9 - Consequences

Method Engineering begins with a decision-usable subject instead of a fashionable label. Later repertoire and criteria Work can remain narrow, while a relation focus exposes genuine coordination questions without pre-committing to a whole.

The cost is a short recovery of Work, views, statuses, and non-Method alternatives. Some projects will stop before Method Engineering because the useful answer concerns a support System, capability, description, or resource.

ME.1:10 - Rationale

The focus determines which claims are admissible in later Method use. Preserving the difference among a Method, family, local grouping, relation focus, and non-Method subject prevents downstream qualification or architecture prose from silently upgrading an unsupported object.

ME.1 connects questions about Methods, their descriptions, Work, capability, tools, variants and Method change. Project, process and case accounts help discover those questions. Recovering each claim’s subject before selecting its representation preserves both useful accounts of one Work and useful connections among different subjects.

ME.1:11 - SoTA-Echoing

Source	Retained contribution	Use boundary
Current FPF `A.15.6`, `C.11`, `A.3.1`, and `G.5`	Project-relative subject recovery, bounded choice, Method identity, and family/selector discipline.	These patterns do not choose the Method Engineering focus for the project.
Gericke, Eckert, and Stacey, Elements of a design method	Method-ecosystem and element distinctions that help locate a candidate focus.	Source elements are prompts, not FPF kinds or Method parts.
Bender, embedded-analytics process selection	Current context-specific selection evidence.	One application population does not establish a universal focus taxonomy.

Reopen the affected rule when a current source or representative use exposes another materially different focus class, or when an account’s subject, status, or omitted claim changes the Method question or non-Method return.

ME.1:12 - Relations

A.15.6 distinguishes project subjects and routes a Method-of-interest question here.
A.3.1 governs Method identity; G.5 governs maintained family and selector results; C.11 governs the bounded focus choice.
ME.2 may organize a repertoire for a one-Method, plurality, or relation focus. ME.3 may state criteria at that same level of focus.
ME.5 receives identified Methods and candidate accounts without changing their status. ME.6 receives a several-structure question; ME.7 receives one proposed whole only when that question is live.
ME.19 may explain an identified Method, established family inclusion, or named relations. A local grouping label is not its explanandum.