Project Initiation: SMART Goals and the Project Charter

Project initiation is the short phase where you decide whether a project should happen and what it must achieve, before anyone spends serious money. It ends with a signed project charter: a one-page document that authorizes the project, names the project manager and sets the goal, budget and deadline. Skip it, and you'll spend the rest of the project arguing about what you were supposed to build.

1. Define the problem
2. Check the business case
3. Write SMART goals
4. Draft the charter
5. Kick it off

Step 1: start with the problem, not the solution

Projects usually arrive as solutions: "we need a new website," "let's buy a CRM," "build us an app." Before you accept that, ask what problem the solution is supposed to fix and how you'll know it's fixed. Sometimes the answer reveals a cheaper fix. Sometimes it reveals that the project is worth far more than anyone thought.

Here's the example for this lesson. Summit Ledger is an 85-person accounting software company in Denver. Its support team handles about 6,000 tickets a month, and agents say a large share are simple "how do I…?" questions. The VP of Customer Success wants a self-service help portal: searchable articles, short videos and a chatbot that answers common questions.

The real problem isn't "we don't have a portal." It's "simple questions eat agents' time, customers wait too long and support costs grow every time we add customers." That framing gives you something to measure.

Step 2: build a quick business case

A business case answers one question: is the expected benefit worth the cost and the risk? For a small or mid-size project, a few lines of math are enough. Summit Ledger's finance team estimates that each ticket costs about $9.50 in agent time. The team expects the portal to deflect 25% of tickets. Building it will cost $180,000, and running it (software subscription and content upkeep) will cost $2,250 a month.

Monthly gross savings = 6,000 tickets × 25% × $9.50 = $14,250
Monthly net savings   = $14,250 − $2,250 running cost = $12,000
Payback period        = $180,000 ÷ $12,000 = 15 months after launch
3-year net benefit    = 36 × $12,000 − $180,000 = $252,000
Simple 3-year ROI     = $252,000 ÷ $180,000 = 140%

A 15-month payback on a tool the company will use for years is a strong case. But notice where the risk sits: the whole case depends on that 25% deflection rate. If only 10% of tickets are deflected, net savings drop to $3,450 a month and payback stretches past four years. That's why the goal you'll write next must measure deflection directly.

Step 3: write SMART goals

A goal like "improve customer support" can't be checked, so it can't be achieved. SMART goals fix that by passing five tests:

Two of those are outcome goals (fewer tickets, happier customers) and one is a delivery goal (launch on time and on budget). Good charters have both. A project that ships on time but doesn't change anything is still a failure; it's just an efficient one.

Step 4: draft the project charter

The project charter is the project's birth certificate. It formally authorizes the work, names the project manager and gives that person authority to use company resources. It is short on purpose: details come later in the plan. Here's Summit Ledger's charter, section by section:

Assumptions vs. constraints

People mix these up all the time. An assumption is something you believe is true but haven't proven ("agents can spend 4 hours a week writing articles"). A constraint is a limit you must work within ("must pass the security review," "budget can't exceed $180,000"). Write both down: assumptions become risks if they turn out to be false, and constraints shape every plan you make.

Step 5: hold a kickoff meeting

Once the charter is signed, get the team and key stakeholders in one room (or one video call) for an hour. The goal is a shared picture, not a lecture. A simple agenda:

1. 5 minWelcome and introductionsWho's who and what each person brings.
2. 10 min · SponsorWhy this project mattersThe problem, the business case and the SMART goals, in the sponsor's own words.
3. 15 min · PMScope, milestones and budgetWhat's in, what's out, the key dates and how decisions will be made.
4. 10 minRisks and assumptionsAsk the room: "What could stop us?" You'll hear risks nobody wrote down.
5. 15 minRoles and communicationWho does what, when the team meets, where files live and how to escalate.
6. 5 minNext stepsThree or four concrete actions with owners and dates.

Before you send the charter for signature, run through this checklist:

• The problem is described in business terms, not as a solution.
• Each objective has a number, a baseline and a date.
• Scope lists what's in and what's out.
• Budget and milestones are stated, with a contingency.
• The PM and the PM's spending authority are named.
• The sponsor has read it and agreed to sign.

Gross savings = 40 h × $20 + 10 × $120 = $800 + $1,200 = $2,000 a month
Net savings   = $2,000 − $400 software = $1,600 a month
Payback       = $24,000 ÷ $1,600 = 15 months

Summary

• Initiation decides whether a project is worth doing and what it must achieve.
• Frame the business problem first; a quick business case uses payback and simple ROI.
• SMART goals are specific, measurable, achievable, relevant and time-bound. Include outcome goals, not just delivery goals.
• The charter fits on one page: purpose, objectives, scope, milestones, budget, risks, stakeholders, PM and sponsor signature.
• Assumptions are unproven beliefs; constraints are fixed limits. Write both down.
• A one-hour kickoff gives everyone the same picture and surfaces hidden risks.

Next lesson: Project Scope and the Work Breakdown Structure (WBS). You'll define exactly what's in and out of the project and break the work into manageable pieces.