Strategy & Results · 10 min read
Project Focus, Part 5: From Goal to Owned Project: The Project Card
Part 5 of a weekly series: turn a goal into a project with one page, seven fields, one owner and about three active projects at a time.

Every January, millions of people write goals. By February, most of those goals are in a drawer, next to the gym membership and the guitar. This is not because people are lazy. It is because a goal is a direction, and a direction does not tell you what to do on Tuesday.
A business owner told me last year, with real pride, that the team's goal was "to improve customer experience." I asked who owned it. She looked around the room. Four people looked at the floor, and one looked at a very interesting plant. That is the whole problem in one picture: a goal everybody supports and nobody owns.
This is Part 5 of the series Project Focus for business success. Part 1 put the method on one page. Part 2 introduced the three engines (leads, operations and sales) with operations at the center. Part 3 gave you a scoreboard of three numbers, and Part 4 a weekly meeting to look at it. Now we answer the question the meeting keeps asking: when a number is wrong, what exactly are we going to do about it, and who is going to do it?
The answer is a small, humble piece of paper called the project card.
From wish to project in four questions
When a goal shows up in a meeting, I ask four questions, always in the same order.
- What number moves, and by when? "Improve customer experience" fails this. "Reply to every new inquiry in under one business day by January 31" passes.
- Who owns it? One name. Not "the team," not "sales and ops." A person who can be asked on Monday how it is going.
- What is the first action, and when? If the first step is not obvious, the goal is still a wish. A first action is a verb with a date: "Write the reply template by Friday."
- How will we know it is done? A project that never ends is not a project, it is a hobby with meetings.
If a goal passes all four, it is a project. If it fails one, it goes back for another conversation. This is not bureaucracy. It is the cheapest filter I know for the difference between "we should" and "we will."
The card: seven fields on one page
The card is a half sheet of paper, a card in a tool or a page in a document. It does not matter, as long as it is one page and everyone can find it. Here are the seven fields, in the order I fill them.
1. The goal, in one sentence. It has a number and a date. "Cut the time from new inquiry to first reply from 3 days to under 1 by January 31." If you cannot say it in one sentence, you have two projects.
2. The owner. One name. The owner is not the person who does all the work. The owner is the person who answers for it, asks for help and says when it is late.
3. Why it matters. One line, tied to the scoreboard from Part 3. "Faster replies are the biggest leak in our leads engine." If a project cannot point at a number you already watch, ask why you are doing it.
4. Three milestones. Not ten. Three, each with a date. Milestones are the checkpoints where you would know, without asking, whether the project is on track. If you need more than three, the project is too big and should be split.
5. The next action. The single next thing, with a name and a date. This is the field that is alive. It changes every week. A card with no next action is a card that is stuck.
6. The biggest risk. One. The thing that would most likely ruin this project, and what you will do if it shows up. For a larger project, use the risk register for small business. For this card, one line is enough.
7. What "done" looks like. A sentence you could read to a stranger and they would agree it happened. "Every new inquiry gets a personal reply within one business day for four weeks in a row."
Why one owner, and why three projects
Two rules do most of the work on this card, and both are unpopular.
One owner. Teams love shared ownership because it feels fair. It is the opposite. When two people own a project, each assumes the other is checking. When ten own it, the plant owns it. Give it one name. That person can still ask for help, and they should, but when someone asks "how is it going?" there is a single human who answers.
If you want to know who should own what across a project, the RACI chart guide is the long version. For a card, the short version is enough: one name in the owner field, and a list of who helps.
About three active projects. I use three as a working number for a small team, and it is a rule of thumb from my own practice, not a law. The reason is simple: a team has a fixed number of hours, and every project takes a share just for thinking about it. Four projects do not run at 133 percent of the speed of three. They run slower, because each one is interrupted by the other three.
Write the rest on a "later" list. Do not throw them away. Look at the list once a quarter. Some will have solved themselves. Some will have become urgent. All will be easier to prioritize than they were in the middle of a busy week.

An illustrative example: the nine-person home services company
Let me use the nine-person home services company from Part 4. Everything below is invented, labeled as illustrative, and not drawn from a real client.
At the first weekly meeting, the scoreboard shows the number the owners care about: the time from a new inquiry to a first reply is 3 days, and nearly half of the people who inquire go quiet before the team gets back to them. Nobody is slacking. Inquiries come in by phone, a form and a message app, and nobody knows whose job it is to look at all three.
They write the card:
| Field (illustrative) | Entry |
|---|---|
| Goal | First reply in under 1 business day, from 3 days, by January 31 |
| Owner | The office manager |
| Why it matters | Faster replies are the biggest leak in the leads engine |
| Milestones | One inbox by Jan 10; template and rule by Jan 17; four weeks under 1 day by Jan 31 |
| Next action | Build the shared inbox, by Friday |
| Biggest risk | Replies sent from a phone and never logged |
| Done looks like | Four weeks in a row of replies in under one business day |
The owner is the office manager, not the boss, because she sees the inquiries every day. The boss is the sponsor and agrees to take the new rule without arguing. The three milestones are a single place where all inquiries land by January 10, a reply template and a rule for who answers by January 17, and four weeks in a row of replies in under one business day by January 31. The first action: "Make a shared inbox for the form and the phone messages, by Friday."
The biggest risk is the one they know best: the owner's own habit of replying from his phone and forgetting to log it. The mitigation is a rule written on the card: replies are sent from the shared inbox or they did not happen.
Every Monday in the 30-minute meeting, the office manager says one sentence and one color. Week one: "Inbox is built, templates in draft. Green." Week two: "Rule agreed, but the phone line still goes to the owner's cell. Yellow, and I need a decision on the forwarding." The owner decides on the spot. The next week, green. Nobody writes a status report. The card is the report.
In week five, the scoreboard shows the average time to first reply at under 1 day, and fewer people going quiet. They close the card with a note: what worked, what to keep. The idea behind closing a project with lessons learned is just that, in a smaller size.
This is the same logic as the first part of the process teardown series, where the new inquiry is mapped step by step. The teardown shows where the time goes. The card organizes the work of fixing it.
A bad card and a good card
A bad card says: "Goal: improve customer service. Owner: the team. Deadline: soon. Done: when it feels better." Read it out loud and notice that nothing in it could ever be late. A card that can never be late can never be on time either, and nobody will remember it on the third Monday.
A good card says: "Goal: reply to every new inquiry in under one business day by January 31. Owner: the office manager. Next action: build the shared inbox by Friday. Done: four weeks in a row under one day." You can disagree with it, argue about it and be late on it. That is the point. A card you can be late on is a card that is real.
A useful test before you pin the card up: hand it to someone who was not in the meeting and ask them to tell you what happens on Monday. If they can answer without asking you a question, the card is ready. If they ask three questions, those questions are the missing fields. Write them in and try again. It takes five minutes, and it is the cheapest quality check in this whole series.

What the card is not
- Not a Gantt chart. If your project is large enough to need one, read the Gantt chart guide. Most small projects are not.
- Not a to-do list. A to-do list has no goal, owner or "done." A card has all three.
- Not a status report. A status report explains what happened. A card points at what happens next.
- Not a place to hide. A card on a wall that nobody opens is a decoration. It lives in the weekly meeting.
- Not a contract. If the plan changes, change the card, and say so out loud.
How the card sits in the weekly rhythm
In the 30-minute meeting from Part 4, the projects section takes about ten minutes. With three cards, each owner has about three minutes. The format is fixed: one sentence, one color. Green means on track. Yellow means I see a problem and I have a plan. Red means I need a decision from this room.
The most useful rule I know is this: a card that is red twice in a row gets a decision, not another update. Two reds mean the plan or the owner or the goal is wrong, and the weekly meeting is the one place where the right people are in the same room to fix it. If you want to be sure of the pace of decisions, the lightweight project governance article explains how to keep it simple.
Where automation and AI fit, later
Cards are paper first. Run them by hand for four to six weeks. Only then ask which parts repeat: the weekly reminder, the color roll-up, the status in the shared board. Part 6 of the series is about exactly that: when to automate and when to add an AI agent. The order matters. Automating a project nobody owns gives you a faster way to miss the date.
If you want a taste of what automation can carry, seven workflows on autopilot and the weekly status report automation are good starting points.
Mistakes to avoid
- Goals without numbers. "Better," "more" and "improve" are feelings. Use a number and a date.
- A team as an owner. One name. Always.
- Too many cards. Three active ones. The rest wait.
- A card with no next action. If the next step is not written, nothing will happen this week.
- Ten milestones. Three. If you need more, split the project.
- Never closing a card. Close it, write what you learned, and free the slot.
- Using the card to blame. The card exists to make problems visible early, not to find a culprit.
Check your goal
Try this on the goal that has been in your drawer the longest. Tick what is true today, and the tool tells you whether it is a project yet.
What to do this week
- Pick the one goal that matters most this quarter.
- Answer the four questions: what number by when, who owns it, what is the first action and how will you know it is done.
- Fill the seven fields on one page.
- Put the card on the agenda of your next weekly meeting.
- Move everything else to the "later" list and look at it again in three months.
Next in the series, Part 6 looks at when to automate and when to add an AI agent. If you want help turning a goal into a card, a rhythm and a scoreboard, see my services or take the diagnostic.
This post is general information about operations and project management. The nine-person company, its numbers and its owner are illustrative, not a real client, and I did not use any customer data.
Frequently asked questions
What is a project card?
It is a one-page summary of a project with seven fields: the goal with a number and a date, the owner, why it matters, three milestones, the next action, the biggest risk and what done looks like. It lives in the weekly meeting and is updated every week.
How many projects should a small team run at once?
As a rule of thumb from my own practice, about three. More than that and every project gets slower because each one is interrupted by the others. Keep a short "later" list and look at it once a quarter.
Can a project have two owners?
I recommend one. Others can help, but one person answers for the result and says when it is late. When two people own something, each assumes the other is watching.
What if a project is red two weeks in a row?
Take it as a signal that the plan, the owner or the goal is wrong, and use the weekly meeting to decide: change the plan, change the owner, shrink the goal or stop. Another status update is not a decision.
Everything new, once a month.
One email on the 1st of every month with everything new: articles, series parts, news, website updates, project results, where I am working and the business opportunities I am looking at. No spam.
- Fresh on the site right now
- ArticleUtah LLC: The Decisions Behind the Filing (and the Yearly Upkeep Nobody Mentions)
- NewsSalt Lake City's housing proposal and its straw polls: what a project manager sees in a plan that changes in public
- SeriesFrom goal to owned project: the project card
Join the conversation
Did this help? A quick reaction tells me what to write next.
Be the first to react.

Loading comments…