Ask a creative team what they're working on and you'll hear the word "project" used to mean four completely different things. The Christmas season? A project. The sermon series that carries it? Also a project. The invite card inside that series? Project. Fixing the typo on the invite card? Believe it or not: project.
When one word means everything, planning meetings become archaeology — everyone digging to figure out what layer they're actually discussing. The fix is a vocabulary with altitude built in.
Four words instead of one
A campaign is a season with a goal — Christmas, a capital push, a launch. It has a big audience question and a date range. A project is one coordinated effort inside it, with a start and an end: the sermon series package, the launch event. A deliverable is a thing that ships: the invite card, the trailer, the stage design. A task is a unit of work inside a deliverable: write the copy, cut the trailer, order the banners.
Why the altitude matters
Each level has a different owner, a different meeting, and a different definition of done. Campaigns get evaluated by outcomes — did the season do its job? Projects get evaluated by delivery — on time, on brief. Deliverables get evaluated by craft. Tasks just get done.
Mix the levels and you get familiar dysfunctions: a room full of leaders art-directing a task while the campaign has no goal. A "project" that never ends because it was actually a ministry. A volunteer crushed under a "task" that was secretly a whole project wearing a small name.
Try the ladder
Next planning meeting, take whatever's on the whiteboard and sort it: campaign, project, deliverable, task. The arguments get shorter almost immediately — because most disagreements were never about the work. They were two people at different altitudes, each certain the other was in the wrong meeting.
