Why “Just Get it Done” Isn’t a Project Plan (and What to Do Instead)

October 7, 2025

Ah yes, the battle cry of chaotic organizations everywhere:

“Just get it done.”

Sometimes it’s shouted across the office. Sometimes it’s whispered ominously in a meeting. And sometimes it shows up as a bullet point in a slide deck titled “Strategy.” Regardless of form, it’s always followed by a sharp increase in confusion, panic, and Slack messages that begin with “Hey, quick question…” and end three days later in disaster recovery mode.

Let’s get this out of the way:
“Just get it done” is not a plan.
It’s a prayer.

And unless you’re hiring divine intervention as a subcontractor (I checked, their rates are outrageous), you’re going to need something a little more… structured.

The Problem with “Just Get It Done”

Here’s the issue: while it feels decisive, “just get it done” is actually a blank check written against unclear expectations, undefined scope, and unrealistic timelines. It bypasses the entire planning process and assumes that the people doing the work are both psychic and miracle workers.

Spoiler: They are neither.

Let’s break down what’s usually missing in these situations:

  • No defined scope: What exactly are we getting done? What does “done” look like? Is it a one-pager or a full-blown platform migration?
  • No timeline clarity: When do you want this? And please don’t say “yesterday.”
  • No resources identified: Who’s available, what tools are needed, and who’s stuck doing two jobs because the original owner quit during the last “get it done” episode?
  • No risk planning: Because obviously, nothing ever goes wrong.

This is how “just get it done” becomes “why is it still not done?”
And then eventually: “who approved this?”

What to Do Instead (aka: Actual Project Planning)

Now for the fun part — what to do instead of winging it.

  1. Define What “Done” Means
  2. Is it a deliverable, a feature, a launch, or just an end to the madness? Write it down. Then get buy-in. If people can’t agree on what success looks like, they’re not ready for execution — they’re still in the brainstorming phase with commitment issues.
  3. Break It Down
  4. No, not emotionally. Break the work down. Use a work breakdown structure (WBS), story mapping, or just a good old-fashioned list. Clarity isn’t fancy — it’s functional.
  5. Assign Owners
  6. Tasks without owners become shared hallucinations. Assign actual people to actual deliverables. Accountability: it’s like magic, but with calendars.
  7. Establish a Timeline
  8. Not “ASAP.” Not “sometime this quarter.” Use actual dates. Add buffers. Assume things will go sideways (because they will), and plan accordingly.
  9. Flag Risks Early
  10. Make risk planning a standard step, not something you do retroactively when everything is already on fire. Capture dependencies, blockers, and the weird “this might be a problem” gut feelings. They’re usually right.
  11. Check In — Intentionally
  12. Status meetings are not the enemy. Bad status meetings are. Set a cadence. Use a format. Don’t ask “how’s it going?” — ask “what’s done, what’s next, and what’s in the way?”

Final Thought: Urgency Isn’t a Strategy

Yes, the market is moving fast. Yes, things feel urgent. But the illusion of speed without structure usually leads to rework, burnout, and finger-pointing.

Execution is only impressive when it’s repeatable.

So the next time someone says “just get it done,” feel free to respond with:

“Absolutely. I’ll get started — as soon as we define what it is.”

And then watch their face as they realize “it” is going to require actual planning.

Want help turning chaos into clarity? That’s what we do.
FiftyOne Consulting helps teams move from vague marching orders to actionable project plans that actually deliver. No prayers required.

Icon