How to say “Politely describe lack of speed” professionally

“Politely describe lack of speed”

Say this insteadLV.1 Professional

“I wanted to check in on the status of [Project/Task Name]. Understanding the current timeline would help me better align my dependent tasks and ensure our overall project schedule remains on track.”

SafeUnhinged

The Anatomy

The chain of dysfunction that forced you to say this.

Tap to expand

The Multiverse

You said one thing. Everyone heard something different.

YOUR INTENT

You're moving at a glacial pace, and I can't do my job because of it.

YOUR BOSS'S READ

Ah, [Your Name] is eager and proactive, demonstrating initiative. I'll get to it when I have a spare moment, probably after my golf game.

PM'S READ

Excellent, [Your Name] is highlighting a potential resource constraint. I'll add this to the risk register and assign it to someone else to monitor.

HR'S READ

A clear example of proactive communication and expectation management, fostering a culture of accountability. Let's incorporate this into our next 'Synergy & Velocity' workshop.

How to say "Politely describe lack of speed" to your boss

Level 1: I wanted to check in on the status of [Project/Task Name]. Understanding the current timeline would help me better align my dependent tasks and ensure our overall project schedule remains on track.

Level 2: Regarding the [Project/Task Name] update, I've outlined my subsequent steps contingent on its completion. Could we establish a clear estimated completion date so I can effectively manage my workload and avoid any potential downstream delays?

Level 3: Per the original project charter and our agreed-upon RACI matrix, the [Project/Task Name] deliverable was a critical path item. Could we revisit the sprint velocity metrics, as the current pace is impacting the projected burn-down rate and overall resource allocation for Q3?

Level 4: The lack of progress on [Project/Task Name] is creating a significant bottleneck for [Your Task/Team]. If we don't see an acceleration by [Date], we will need to re-evaluate the project timeline and potentially escalate to senior leadership to mitigate broader impact.

Level 5: Are you done yet?

How to say "Politely describe lack of speed" to your client

Level 1: We're currently awaiting the necessary [Feedback/Assets] to proceed with [Next Phase]. Once received, we can continue to advance the project efficiently and maintain our agreed-upon delivery schedule.

Level 2: To ensure we can meet the target launch date of [Date], we require the [Feedback/Assets] by [New Proposed Date]. Expediting this would significantly help us prevent any further impact on the overall project timeline.

Level 3: Referencing our Statement of Work, the agreed-upon client input for [Phase Name] was anticipated by [Original Date]. The current delay is causing an accumulation of internal resource hours and will necessitate a formal change request if the critical path continues to be impacted.

Level 4: The project is currently on hold due to outstanding [Feedback/Assets]. Without these by [Firm Deadline], we will be unable to meet the [Project Deadline], and this will incur additional costs and require a formal re-scoping of the project deliverables.

Level 5: Your inaction is costing you money.

How to say "Politely describe lack of speed" to your coworker

Level 1: I'm checking in on the status of [Task Name]. My next steps are dependent on its completion, so any update on its progress or an estimated timeline would be very helpful for my planning.

Level 2: For the [Project/Module], I've completed my portion and am ready for your input/next steps. I'm keen to keep our momentum going, so let me know if there's anything I can do to facilitate your progress.

Level 3: Following up on the [Task Name] deliverable. As per the collaborative workflow established during our last stand-up, my capacity for [Dependent Task] is currently blocked. Perhaps we can re-evaluate resource allocation if the current timeline presents challenges?

Level 4: The delay on [Task Name] is now directly impacting my ability to meet the [Project Deadline]. I need an immediate update and a revised completion timeline from you, or I'll have to flag this as a critical path risk to [Manager/Team Lead].

Level 5: Still waiting. Or should I just do it?

The Decoder's Analysis

Effectively communicating concerns about execution speed is crucial for maintaining project momentum and managing expectations without appearing accusatory. This skill supports effective workload management, helps reinforce scope of work boundaries, and improves overall professional communication, preventing bottlenecks and ensuring timely delegation where necessary. Mastering this nuanced feedback is vital for career progression and team efficiency.

When to use this

USEWhen a key deliverable from a cross-functional team is consistently behind schedule, impacting your ability to meet your own deadlines.

USEWhen a direct report is struggling with task velocity and you need to address it constructively as part of their performance feedback.

USEWhen a vendor's progress on a critical component is slower than agreed, jeopardizing the project's overall timeline.

AVOIDWhen confronting a senior leader about their personal working style in an open meeting without prior private conversation.

Related Deflections

→ How to say “Politely criticize capability” professionally → How to say “Politely criticize quality” professionally → How to say “Politely criticize effort” professionally

Also searched as

professional way to say slow