Back to Blog

People-First Planning, Built by a PM Who Lived It

Bal
·Feb 22, 2026·
5 min read
People-First Planning, Built by a PM Who Lived It

Every project I ran had a “second plan.”

Not the one in the tool. The one in people’s heads.
The timeline that drifted as things changed, the doc that fell out of date, the spreadsheet someone quietly stopped updating.

That silent second plan is where alignment breaks.

PlanAnything exists to keep everyone working from the same picture, even as reality changes it.

Seventeen Years of Planning Work, One Consistent Lesson

Before starting Plan Anything, I spent more than seventeen years working as a Project Manager. Twelve of those were inside large corporate environments, including Microsoft and Verizon, alongside time in startups. The contexts varied but the work was consistent: structured timelines, cross-functional delivery, and keeping stakeholders aligned across the life of a project.

The patterns behind project failure showed up again and again:

  • Ownership wasn't clear

  • Dependencies weren't mapped properly

  • Stakeholders interpreted the same timeline differently

  • Costs looked fine early on, then quietly crept up

I've watched rooms go quiet as two teams realised they were working to completely different assumptions from the same plan. In my experience, projects rarely failed because the planning software wasn't sophisticated enough.

One lesson stood out above everything else: the quality of the plan determines the quality of alignment.

A clear, well-structured plan gives teams a shared reference point. A vague or fragmented one creates room for misinterpretation at exactly the moments when clarity matters most.

That lesson shaped every decision I made when building this product.

We Built the Fundamentals First

When Tom, my co-founder and CTO, and I started building Plan Anything, the first question wasn't how to use AI. It was: what actually makes planning difficult for real teams?

Tom has spent his career building complex systems, so we agreed early that the foundations had to be solid before adding anything clever.

The answers pointed to the same things every time:

  • Starting from a blank page is slow

  • Turning a brief into structure takes effort

  • Editing timelines manually is tedious

  • Communicating a plan clearly to different audiences is hard

So we built the foundations first:

  • Gantt-style timeline: drag bars to adjust dates and see dependencies at a glance

  • Costs Dashboard: shows how spend unfolds across the life of a project, not just the total

  • Project Document: generates directly from your plan and stays in sync as it evolves

  • Weekly Snapshot: a calm, factual view of what is happening each week

  • Critical Path overlay: highlights exactly which tasks are driving your deadline

  • Presentation mode: turns your live plan into a shareable set of slides in one click

  • Baseline tracking: capture your original plan and see exactly what's slipped or changed over time

None of those features require AI. They're the fundamentals experienced PMs rely on. We built them carefully before adding anything else.

Everything You Need. Nothing You Don't.

After years inside heavyweight planning tools, one thing became obvious: unnecessary complexity breaks alignment.

So we started from scratch.

We focused on the smallest set of features real teams actually need to plan well, stay aligned, and adapt as things change. No clutter. No buried controls. No features added just because competitors have them.

The result is a tool you can pick up in minutes, build a real plan in under five, and share with anyone without needing to explain how it works.

That simplicity is deliberate.

Then We Added AI (and Here's Exactly What It Does)

Once the planning foundations were in place, we integrated AI into the parts of the workflow where it removes real friction.

The AI assistant lets you edit your actual project by text or voice: adding tasks, moving dates, extending phases, adding dependencies, assigning costs, pinning notes, and changing colours.

In practice that looks like:

"Move the Design phase to March 10."
"Make Development depend on Design Approval."
"Set QA to five working days."
"Add a note to March 5: client review call."

You can type those or speak them. The microphone button transcribes your voice and sends it as a message. Both work identically.

This matters when you're planning in real time, restructuring a plan while a conversation is still happening. Voice input shrinks the gap between a decision and the moment it appears in the plan.

Ask Pip

Pip (Planning In Progress) isn't a chatbot layered on top of planning software. Pip edits the plan itself.

When you say "Extend the testing phase by three days," the bar moves on the Gantt. The costs update. The dependency chain shifts. You're not getting a summary or a suggestion. You're editing the actual project through conversation.

Every change goes through you first. The plan stays yours. Every task, every date, every cost is still directly editable. Pip is a faster way to get to the same place, not a system making decisions on your behalf.

The Balance That Makes It Work

Successful projects are delivered by aligned people, not by software that plans for you.

Plan Anything is built around that belief:

The platform provides structure.
AI accelerates the mechanics.
You bring the judgment.

That balance is deliberate. And it comes from more than seventeen years of watching what actually makes projects succeed and fail in the real world.