Nominalization hides the action about to happen

What it is

Nominalization and hidden agency arise when an action is packaged as a noun or abstract process and the wording can drop who acts, what is affected, and what result follows. “Initiate account deactivation” names a process without settling whether the person immediately disables their account or the system later reviews a request. The problem is not the part of speech itself, but whether trigger, notice, or explanatory copy still lets readers recover the actor, action, object, and outcome.

Why it happens

Nominalization makes an event available as a topic, but permits agency, tense, modality, and affected objects to recede. Shell predicates such as “perform,” “process,” or “initiate” can present a workflow category rather than a predictable state transition. The hidden slot may contain the central risk: who shares data, which record disappears, and whether a request acts now or awaits approval. A verb does not automatically solve this—“process account” is still vague. Repair restores the necessary participants, direction, and result rather than mechanically changing a noun into a verb.

Studying it

Sample nominalized and verbal alternatives from real controls, states, notices, and help. Ask who acts, what changes, what is affected, and what happens next; record missing slots, mistaken agency, and confidence. Separate triggers, process navigation, completed states, policy explanation, and domain terminology, controlling length and familiarity so extra words are not credited to verb form. Code each slot as explicit, uniquely recoverable from adjacent context, or ambiguous. Cross-language work needs natural equivalents rather than English part-of-speech categories imposed on another grammar.

Where it stops holding

Noun phrases suit headings, object navigation, state categories, and discussion of a process. Domain terms such as “identity verification” can be the precise familiar concept. A scene with no direct command need not invent an actor; a status may need only the result and next step. Some languages naturally use action nouns, impersonal constructions, or omitted subjects while context resolves responsibility and consequence. Mandated wording may also be fixed; an explanatory layer should supply operational meaning instead of silently rewriting it.

Applying it

• Annotate actor, action, object, and outcome for triggers and consequential messages. Rewrite or explain any slot hidden by nominalization that adjacent context does not recover uniquely.
• Remove process shells that add no meaning: change “perform an export operation on the records” to “export the selected records.” For asynchronous work, say “request an export” and state how completion is delivered.
• Preserve validated domain nouns and navigation labels, while explaining roles and results around first use, permission transfer, deletion, sharing, and charges. Do not create a cross-language blacklist of nominal forms.
• Run actor-and-consequence paraphrase tests in the interface and compare answers with the real state transition. Divergent answers about actor, scope, or result fail high-risk copy even when grammar is correct.

Related

• Same group: T1.02.1 Verb-first labels are the most scannable · T1.02.3 Verbs must be specific enough to judge consequences
• Adjacent: S1.07.2 Simple sentence structure can substantially reduce ambiguity · T2.06.1 State the specific object and irreversibility scope
• Search terms: nominalization · hidden agency · buried verb