Concepts: Cards, Projects, and Boards

Most project management tools overwhelm you with features you don't need. PM Engine does the opposite. It's built around three core elements that actually matter: cards, projects, and boards.

These three elements give teams what they need to plan, track, and deliver work.

Cards: The core element

A card represents a single, meaningful piece of work. Something you can complete, review, and deliver.

Cards aren't simple tasks. They're complete deliverables or project increments. Think of them as the smallest unit of work that creates tangible value.

What does this look like in practice? Here are examples across different work types:

Each card keeps everything in one place. Tasks, context, discussion, details—all connected to that specific piece of work.

Projects: Defining scope

A project holds all the cards that contribute to a shared goal. It defines scope. It answers the question: what needs to be done to achieve this goal?

Every card exists in one of three stages: planned, in progress, or delivered.

The backlog contains cards planned for future implementation. In progress cards are on a board and currently being worked on. Delivered cards represent completed work—the results the project has already achieved.

Projects provide structure. They help teams track progress over time without turning that tracking into overhead.

Boards: Where work happens

A board is where work actually happens. It's a team's workbench for moving cards from idea to completion.

Here's the distinction that matters: Projects define what needs to be done. Boards help decide how to get it done.

Teams move cards from the project backlog onto a board when they're ready to start. Boards typically contain a limited set of cards—only those being worked on now or planned for the near future.

Some teams use a single board for everything they're currently working on. Others split work across separate boards for different streams like design, development, or content writing. Both approaches work.

How projects and boards connect

Projects and boards handle the two aspects of managing work: scope and process.

The connection is flexible and works both ways.

A project can use multiple boards. A product development project might connect to separate boards for software development, content writing, and UX/UI design.

One board can support multiple projects. A "content board" could handle articles and posts for several different projects simultaneously.

This flexibility lets teams organize work how it makes sense for them. Without forcing extra complexity.

Why this structure works

Most PM tools either force rigid structures or offer so much flexibility that teams drown in configuration. PM Engine gives teams just enough structure to stay aligned without dictating how work gets done.

Cards, projects, and boards. Three elements that cover planning, execution, and delivery. That's it.