Project management basics that actually matter

If you’re looking for a way to manage work alongside project tracking, here’s how Tallyfy can help.

Project management is the act of planning, running, and controlling work that has a defined beginning and end. That’s it. Strip away the certifications, the frameworks, the methodology wars - and you’re left with a simple question: can you get a group of people to finish something specific, on time, within budget?

Most goals worth achieving involve some kind of project. Building software. Constructing a building. Launching a website. Redesigning an onboarding process. These all share the same DNA - they’re temporary, they’re goal-driven, and they require coordination between people who don’t usually sit in the same room.

Here’s what makes projects tricky, though. The team has to juggle variables they can’t always control. Budget constraints. Shifting deadlines. Tools nobody’s used before. And everyone’s got a different communication style, a different set of priorities, and a different idea of what “done” looks like.

Our goal is to use what is already out in the field in terms of partners, but then hire in project management capability and a bit of technical capability.

— Kevin Rollins, former Dell CEO

Where project management came from

The history is more interesting than you’d think. It really starts in the 1860s with the transcontinental railroad - a massive effort that needed thousands of workers, mountains of materials, and six years of construction to connect the Atlantic and Pacific coasts.

Then Frederick Taylor showed up in the early 1900s with a radical idea. Instead of just telling employees to work harder, he studied how they worked and figured out ways to make them more efficient. Sounds obvious now. It wasn’t then.

Henry Gantt - Taylor’s associate - took it further by using graphs to track task completion. Those graphs eventually became the Gantt charts that project managers still use today. The specific tools have evolved. The core philosophy hasn’t: getting different people to work together toward a shared goal.

That’s something worth remembering as teams rush to bolt AI onto their project management workflows. If your project structure is broken, automation just breaks it faster.

What a project manager actually does

When a team assembles for a specific project, someone has to lead it. That’s the project manager. Their job is to plan, oversee, and execute - but the real skill is knowing which details matter and which ones don’t.

Project managers figure out the project scope - basically, what work needs to happen to deliver the finished product. Their responsibilities include:

• Planning and defining what the project covers
• Figuring out what resources are needed
• Estimating timelines that aren’t pure fiction
• Setting a budget that accounts for reality
• Managing problems as they pop up
• Communicating clearly with the team
• Working with vendors and outside partners
• Controlling for quality throughout

The best project managers I’ve seen share two traits: they’re analytical AND they relate well to people. That combination is rarer than you’d expect.

In our conversations with teams - from 6-person property management firms to 200+ employee restaurant technology companies - the pattern is consistent. Great PMs can zoom into the details of individual tasks while keeping the bigger picture in focus. Bad PMs get lost in one or the other.

This piece from the Harvard Business Review nails it. The most important question a project manager should ask is: “Am I focusing on the right details?” Hitting every milestone means nothing if the milestones themselves are wrong.

Five phases of a project

There are many moving parts in any project, but the process generally follows five steps. The terminology changes depending on who you talk to, but the structure stays the same.

Definition

First, pin down the real problem. The project manager works with senior leadership and other stakeholders to define what needs to be delivered. This sounds simple. It isn’t. If you settle on the wrong problem, everything that follows is wasted time and money.

Planning

Map out the tasks. Estimate how long each one takes. Set milestones. This is also where you look at budget, scheduling challenges, and risks. One delayed task can create a domino effect that throws off a dozen others - so the planning phase is where you build in breathing room.

Execution

Build the team. Assign the work. This is where the real work begins. It’s also where things start going sideways if the planning was sloppy.

Control

Track progress continuously. A good project manager maintains a bird’s-eye view of how everything’s moving. Workflow software can be helpful here - not because it’s magic, but because it makes invisible work visible. Tallyfy, for example, lets you see exactly where every task stands without chasing people for status updates.

Closure

Deliver the finished product. Evaluate the outcome. This phase is often the most satisfying and simultaneously the most frustrating - the work is done, but implementation details can be tedious.

Why most projects still fail

Here’s where it gets real. Project management sounds straightforward in theory. In practice, it’s a proper nightmare. Scope creep sneaks in. Team members lack critical skills. Deadlines are set by people who’ve never done the work. Which is maddening.

This frustrates me more than almost anything else in operations.

Every time we onboard a new team, the same issue surfaces - they adopt the latest tools without fixing the underlying structure. You can’t automate chaos. You just get faster chaos.

Feedback we’ve received tells a different story when structure exists. One digital agency reduced developer onboarding from weeks to 1-2 days by defining their project setup workflows in Tallyfy. No fancy methodology. No expensive consultants. Just clear, repeatable steps.

Process vs. project - a distinction that matters

Here’s something most project management guides won’t tell you. A lot of what people call “projects” are actually repeating processes wearing a project hat. If you’re doing the same onboarding sequence every time a new hire starts, that’s not a project - it’s a process. And it needs a different approach.

Projects are unique, one-time efforts. Processes repeat. The tools you need are different. The mindset is different. Mixing them up is one of the most common mistakes I see.

With Tallyfy, you can handle both - run one-off projects when needed, but also build repeatable process templates for work that happens again and again. That distinction alone saves teams hours of reinventing the wheel every week.

Making it work without the overhead

The project manager should stay aware of challenges so they can deal with them before they turn into crises. But awareness without structure is just anxiety.

My plain take? Most project management methodology is overthought. The fundamentals haven’t changed since Henry Gantt was drawing graphs. Define the problem clearly. Plan the work. Execute with a good team. Track progress. Deliver. Does the specific framework matter? Not really.

The tools matter less than the thinking. But when you do pick a tool, pick one that your team will actually use. If it takes 6 months of training to learn your project management software, you’ve already lost. The best tools take 60 seconds to understand - not 6 months of IT projects.

That’s the real test. Not which framework you follow or which certification you have. Can your team see what needs to happen, who’s responsible, and what’s blocking progress? If yes, you’re managing projects well. If not, no amount of methodology will save you.

Is project chaos acceptable?