Engineering-Product Collaboration: Phrases for Working with PMs
5 exercises on key phrases for working with product managers. Choose the most natural and professional option.
0 / 5 completed
1 / 5
A PM proposes a feature and you want to explain the technical implications. How do you frame your input?
TECHNICAL PERSPECTIVE FRAMING: "From a technical perspective..." signals that you're contributing domain expertise, not blocking the idea. It opens the door to alternatives rather than shutting down the conversation. Examples: "From a technical perspective, adding real-time sync here would require WebSockets — which is doable but adds infrastructure complexity." / "From a technical perspective, the simplest path is reusing the existing export module — no new service needed." / "From a technical perspective, this touches the payment flow, so we'd need a security review before releasing." Options A/B/D are blunt rejections or condescending — none of which advance the collaboration.
2 / 5
The PM asks why a feature is taking longer than estimated. How do you explain professionally?
EXPLAINING TECHNICAL DELAYS: "This will take longer than expected because..." followed by a specific, non-jargon reason respects the PM's need to understand and re-plan. Examples: "This will take longer than expected because the database schema needs migration before we can store this data type." / "This will take longer because we discovered a third-party API rate limit that requires us to build a queue." / "This will take longer than expected because the mobile and web codebases diverged here — we need to align them first." Options B/C/D are evasive, too brief, or dismissive — none of them give the PM what they need to manage expectations upward.
3 / 5
The feature scope is growing and you want to propose a smaller version. How do you phrase it?
PROPOSING SCOPE SIMPLIFICATION: "Could we simplify the requirements to [core scope] and defer [non-core] to v2?" is the professional way to propose a phased approach. It acknowledges the full vision while making a case for sequencing. Examples: "Could we simplify to just the CSV export for now, and add the PDF option in the next sprint?" / "Could we scope this to domestic users initially, and handle international edge cases in phase 2?" / "Could we simplify requirements to the happy path for launch, with edge case handling coming in the week after?" Options A/B/C are blunt refusals with no constructive alternative.
4 / 5
A PM asks you to include a feature that conflicts with an existing system constraint. How do you communicate this?
NAMING TECHNICAL CONSTRAINTS: "There's a technical constraint here..." gives the PM specific, actionable information. Naming the constraint — and optionally the path to resolve it — is far more useful than a flat "no". Examples: "There's a technical constraint — the mobile app doesn't have push notification permissions in the current build; adding them requires an app store review." / "There's a constraint: our CDN doesn't support server-side rendering, so this dynamic feature needs a different delivery approach." / "There's a technical constraint here — the API is rate-limited to 100 requests per minute, which won't scale to this use case without caching." Options A/C/D give the PM no information to work with.
5 / 5
The PM has given a very aggressive timeline. How do you push back professionally?
PROFESSIONAL TIMELINE PUSHBACK: "I'd push back on the timeline" paired with an alternative and the conditions for the original is the mature engineering response to unrealistic timelines. It is direct without being dismissive. Examples: "I'd push back on the one-sprint timeline — the database migration alone needs thorough testing. Can we negotiate two sprints?" / "I'd push back on the August deadline — we're still in discovery. September with full scope, or August with a reduced feature set." / "I'd push back on this — if we rush, we risk introducing tech debt that will cost more later. Can we take the extra week?" Options A/B are too blunt, D is passive and uncommitted — it doesn't help the PM make a real decision.