Architecture Review Meeting — Collocations in Context
5 exercises — read the scenario and answer questions about which collocations fit the context and why.
Scenario: The team weighs the trade-offs between two approaches, aligns on the preferred solution, one engineer proposes an alternative, another raises a concern about scalability, and the team tables the discussion until they have more data.
Decision language: weigh trade-offs, align on, sign off on
Discussion: propose an alternative, raise a concern, surface a risk
False friend alert: "table" means opposite things in British vs. American English
0 / 5 completed
1 / 5
"Weighs the trade-offs" — what does this collocation mean?
"Weigh the trade-offs" — the essential decision-making collocation in architecture.
The verb weigh here means to assess importance carefully, as if placing things on scales. Trade-offs are the inherent tensions in any technical decision: gaining one thing means giving up another.
Examples of architectural trade-offs:
Consistency vs. availability (CAP theorem)
Performance vs. maintainability (over-optimised code is hard to read)
Development speed vs. scalability (a quick monolith vs. a complex microservice)
Cost vs. reliability (more redundancy = higher cloud bill)
The collocation in use:
"Before we decide, let's weigh the trade-offs between PostgreSQL and DynamoDB."
"The trade-offs favour the event-driven approach for our scale."
Related collocations: evaluate the options, compare approaches, assess the risks, consider the trade-offs. In technical writing, trade-off analysis is a standard section in architecture decision records (ADRs).
2 / 5
"Aligns on the approach" — what does "align" mean in this context?
"Align on X" — the collaborative agreement collocation.
Align on means to come into agreement and shared understanding — like adjusting parts until they are in line with each other. It implies that multiple people or groups have converged on the same view.
This is extremely common in professional tech communication:
"We need to align on the API contract before both teams start building."
"Let's align on the definition of done for this sprint."
"Are we aligned on the rollout strategy?"
Key nuance: "align on" emphasises consensus and shared understanding, not just one person deciding. It suggests a collaborative process. Compare:
align on the approach ✅ — we all agree
agree on the approach ✅ — similar, slightly more formal
decide on the approach ✅ — a decision was made (possibly by one person)
sign off on the approach ✅ — formal approval, often from a senior stakeholder
You will hear align constantly in cross-team meetings, product planning, and engineering discussions.
3 / 5
"Proposes an alternative" — in a technical discussion, this means:
"Propose an alternative" — constructive disagreement in architecture meetings.
To propose an alternative is to offer a different option for consideration. The key word is propose — you are putting it forward for discussion, not overriding others. This is healthy technical debate.
Common patterns in architecture discussions:
"I'd like to propose an alternative: instead of Kafka, what if we used a simple PostgreSQL LISTEN/NOTIFY for our current scale?"
"Has anyone considered an alternative approach using a BFF pattern?"
The anatomy of a good alternative proposal:
Acknowledge the original: "The proposed microservice approach makes sense..."
Signal your alternative: "...however, I'd like to propose an alternative"
State it clearly: "...a modular monolith that we can extract later"
Give your rationale: "...because our team is too small to operate 12 services right now"
Related collocations: suggest an alternative ✅, offer a different approach ✅, counter-propose ✅, put forward an option ✅.
4 / 5
"Raises a concern" — what does this mean in a technical meeting?
"Raise a concern" — the collocation for surfacing risks in meetings.
To raise a concern means to bring up a potential problem or risk so the team is aware and can address it. The verb raise here means to bring something up, to put it on the table — not to increase it or build it.
In architecture reviews, concerns are typically about:
Scalability — "I'd like to raise a concern about how this approach handles 10x traffic growth."
Security — "I have a concern about storing tokens in localStorage."
Operational complexity — "My concern is that our team doesn't have the expertise to operate this."
Cost — "Can we flag a concern about the AWS cost projection?"
Related collocations:
raise a concern ✅ — most common
flag a concern ✅ — equally natural
voice an objection ✅ — stronger, more formal
surface a risk ✅ — tech-specific
address a concern ✅ — respond to it
Raising concerns is expected and valued in engineering culture — silence that leads to a bad architecture is far more costly.
5 / 5
"Tables the discussion" — WARNING: this phrase has opposite meanings in British and American English. Which option is correct?
"Table" — the most famous British/American English false friend in professional settings.
This single word causes genuine confusion in international teams:
American English: "table a motion / table the discussion" = postpone it, set it aside for later. "Let's table this until we have more data." (US) = defer, shelve
British English: "table a motion / table an item" = bring it onto the agenda NOW for immediate discussion. "I'd like to table the scalability question." (UK) = raise it, discuss it today
In the scenario: "The team tables the discussion until they have more data" uses the American meaning (postpone) — they are deferring until they have better information.
For international tech teams:
Avoid using "table" without context — it will be misunderstood
Say "defer the discussion" or "park this for now" if you mean postpone (neutral)
Say "put this on the agenda" or "discuss this now" if you mean the British sense
Other British/American false friends in tech: fortnight, on the day, quite (UK quite = moderately; US quite = very).