Job Communication Vocabulary · 2026-09-09

1. hard stop
- Explanation: Noun phrase referring to a "fixed end time" in a meeting or work schedule. In a meeting, saying "I have a hard stop" means one must end at that time and cannot continue. The tone is practical and respects others' time, emphasizing "time boundary" rather than "rushing to finish". Note: commonly used as "I have a hard stop at 3pm"; should not say "hard stop is 3pm". It differs from "deadline" which refers to task completion deadline, while "hard stop" refers to the end of a time block. Also differs from "wrap up" which is about concluding, while hard stop emphasizes "time cannot be extended".
- Usage:
- I have a hard stop at 4:00, so I need to wrap up by 3:45. (I have a fixed arrangement at 4pm, so need to finish by 3:45.)
- The CEO called a hard stop to the discussion, citing the need to meet the deadline. (CEO ended the discussion, citing need to meet deadline.)
- Scenario description: Used in meeting speech to state need to end on time, communicating "I have other arrangements", managing meeting duration, or when someone in cross-departmental negotiation needs to leave for another meeting. It is a practical expression for "respecting time, reasonably scheduling meeting length, avoiding endless meetings".

2. scope creep
- Explanation: Noun phrase referring to "gradual, often uncontrolled expansion of project scope". When clients or stakeholders continuously add new requirements, functions, or changes during project execution, without adjusting the original time, budget, or resources, the project deviates from the plan. The tone is cautionary and professional, emphasizing "uncontrolled change" rather than "reasonable requirement evolution". Note: can be expressed as "scope is creeping" / "we're experiencing scope creep". Should not be confused with "feature creep", which refers to "technical/product feature increases"; scope creep focuses on "non-anticipated expansion of business/project scope", while feature creep is more about "technical/product feature additions". Also differs from "change order", which is the formal change request process.
- Usage:
- We need to stop scope creep before the client adds more requirements without adjusting the budget. (Before client adds more requirements without budget adjustment, we need to stop scope creep.)
- The project went over budget due to uncontrolled scope creep from the stakeholder group. (Due to stakeholder group's uncontrolled scope expansion, project went over budget.)
- Scenario description: Used when defining project scope at kickoff to remind the team, when client adds extra requirements during negotiation, when reporting upward about "project delayed/over budget due to extra requirements", and in project management to issue warnings and seek renegotiation of boundaries. It is a key expression for "controlling project boundaries, preventing resource over-expenditure, maintaining delivery quality".

3. parking lot
- Explanation: Noun referring to the practice of temporarily setting aside "discussion items that cannot be addressed immediately or have lower priority" in a meeting, recording them for later discussion. Derived from "parking the car to the side", the tone is practical and facilitation-oriented, emphasizing "handling secondary matters without disrupting the main process". Note: commonly used as "The parking lot is open" / "Let's park this item". Should not be understood as "ending the discussion"; it is "temporarily setting aside, to be handled later". Differ from "move on" which is a mental shift without necessarily recording the item.
- Usage:
- That's an interesting point—let's add it to the parking lot and come back to it after the main agenda. (That's an interesting point—let's add it to the parking lot and return after the main agenda.)
- The facilitator suggested putting the budget question in the parking lot for the next meeting. (The facilitator suggested putting the budget question in the parking lot for the next meeting.)
- Scenario description: Used in meeting speech to propose "put this topic in the parking lot", used by meeting facilitators to control progress, in cross-departmental communication when someone raises tangential topics to maintain meeting focus, or in upward reporting to indicate "we'll handle this in a separate follow-up meeting". It is a common technique for "maintaining meeting efficiency, avoiding topic overflow, ensuring important topics are not lost".

✅ 已保存至 workplace-communication/20260909.md