5 exercises — practise converting verbs to nouns (implement→implementation, deploy→deployment, refactor→refactoring) to raise the register of sprint reports, postmortems, proposals, and architecture documents.
0 / 5 completed
1 / 5
A developer wants to make a technical report more formal. The draft reads: "We implemented the new caching layer last sprint." Which sentence uses nominalisation correctly to raise the register?
"The implementation of the new caching layer was completed last sprint." is the best nominalization. Nominalisation converts a verb (implement) into a noun (implementation), which becomes the grammatical subject or object. This increases information density and formality — essential in sprint reports, technical proposals, and architecture documents. The pattern is: verb → noun + "of" + object: implement → implementation of, deploy → deployment of, configure → configuration of. Option A ("the implementing of") uses a gerund, not a true nominalisation, and sounds unnatural in formal IT writing. Option C keeps the agent "we" with the nominalisation, which reduces the register gain.
2 / 5
A tech lead writes in a postmortem: "The service failed because we deployed too quickly." Which version correctly nominalises the verb deploy in a formal root-cause analysis?
"The service failure was due to a rapid deployment." nominalises both the cause (deploy → deployment) and the effect (fail → failure). This double nominalisation is characteristic of formal postmortems and incident reports. The structure "X was due to Y" with nominalised nouns is highly formal: "The outage was due to a misconfiguration of the load balancer", "The data loss was due to an incomplete rollback." Option A uses a gerund (deploying), which is informal. Option C uses the infinitive deploy rapidly — grammatically incorrect after "due to". Option D mixes informal gerund with the correct phrase structure.
3 / 5
An architecture document reads: "We need to authenticate users before they can access the dashboard." Which formal rewrite best nominalises this sentence?
"User authentication is required prior to dashboard access." demonstrates two nominalisations: authenticate → authentication and access (verb) → access (noun). The result is a compact, authoritative noun phrase typical of technical requirements documents and system design specs. Note the compound noun pattern: user authentication (noun + noun) rather than "authentication of users" — the compound form is more common in IT English. Similarly, dashboard access rather than "access to the dashboard". Option B ("the authenticating of") is a gerund phrase, not a true nominalisation. Option D drops the article before a singular countable noun ("authentication of user") — a grammatical error.
4 / 5
A software engineer writes a ticket title: "Refactor the payment module". The project manager wants a more formal noun-phrase title for the epic. Which option is correct?
"Payment module refactoring" is the most natural and concise nominalised epic title in IT English. In technical project management, epic and story titles use compound noun + nominalisation patterns: "Database migration", "API endpoint redesign", "Authentication flow refactoring". Note: refactoring (from the verb refactor) functions as a gerund-noun here — established as a standard IT term. Option A ("refactoring of the payment module") is grammatical but verbose for a title. Option C uses the non-standard "refactorisation" — the correct British nominalisation is refactoring in IT contexts. Option D is a full sentence, not a title.
5 / 5
A developer needs to make this sentence more formal for a technical proposal: "We will monitor performance and then optimise the queries if they run slowly." Which rewrite uses nominalisation most effectively?
"Performance monitoring will be conducted, with query optimisation to follow if degradation is detected." achieves the highest register through three nominalisations: monitor → monitoring, optimise → optimisation, and degrade → degradation. It also removes the first-person agent (we), which is typical of formal proposals and technical white papers. The structure uses passive voice with nominalisation — a combination that is the hallmark of advanced IT English in formal writing contexts. Option A is valid but uses the verbose "carry out" and "do" constructions. Option C repeats "the … of …" twice — technically correct but awkward. Option D retains the informal first person and uses gerunds rather than true nominalisations.