What Is Project Management? Goals, Planning, and Change Decisions in a Small Campaign

September 14, 2026Shusaku Yosa

Project management connects people, work, timing, costs, and decisions so a team can deliver an agreed outcome. It involves more than maintaining a detailed spreadsheet. A small campaign becomes easier to coordinate when the team agrees on completion criteria and knows who can decide what to change.

Project management coordinates work toward an agreed outcome

PMI describes project management in terms of applying knowledge, skills, tools, and techniques to project requirements. In practice, planning is accompanied by checking what is happening and bringing decisions to the appropriate people. Read PMI’s explanation of project management.

A project is a temporary effort directed toward a particular outcome. Building a registration page for a new service differs from responding to enquiries every day after launch. Ongoing operations can also contain a bounded improvement project, with its own deliverables and review point.

Projects may close because delivery is complete, a business decision cancels the work, responsibilities transfer, or a contract ends. Closure still requires a record of what was delivered, what remains, and who will take responsibility. It is not limited to projects that achieve every original goal.

Agree on goals, deliverables, completion criteria, and stakeholders

A goal explains why the work matters. A deliverable states what will be produced. Completion criteria explain what must be checked before it can be accepted. Increasing registrations and publishing a registration page are related but different: publishing can be verified at handover, while registrations or revenue need a separate assessment.

The following fictional initiation note concerns a small campaign. D1, D2, and similar labels denote project working days. Amounts and effort are illustrative, not market prices or recommended limits.

Item	Worked entry	Confirm before starting
Purpose	Provide a registration route for a new-service webinar	Audience and intended business outcome
Deliverables	One registration landing page and one invitation email	Destination, content, and language
Completion criteria	Content approved; links and registration tested; release approved	Test conditions and final approver C
Deadline	Release approval by the end of D10	Relationship to external commitments
Cost and effort limits	JPY 300,000 and 40 internal person-hours	Cost scope and people’s available time
Roles	A coordinates; B produces; C gives final approval	Backup decision-maker and review time
Out of scope	Migration of the entire CRM	Decision route if requested
Main risk	Waiting for copy approval delays production	Copy-review deadline and alternatives

“Tested” is not sufficiently specific by itself. Agree on relevant devices, inputs, and the state to verify after submission. Stakeholders include users and the people who will operate the service, as well as the sponsor, producer, and approver.

Connect scope, schedule, cost, quality, and risk

Scope, schedule, cost, quality, and risk affect one another. This does not mean that meeting all agreed constraints is inherently impossible. A feasible scope and delivery arrangement can satisfy them. A change can alter that feasibility and must be assessed accordingly.

Adding a language may add translation, layout, content review, link testing, and approval. Break an apparently simple request into the work and acceptance conditions it creates, then update the estimates.

Schedule: include dependencies and approval waiting time.
Cost: distinguish the approved limit, additional estimates, and actual expenditure.
Quality: identify optional elements and mandatory conditions.
Risk: separate uncertain future events from issues that have already occurred.

Silently dropping required tests changes the acceptance conditions. Present the scope change, remaining risk, and decision owner instead of treating an apparently shorter schedule as proof of feasibility.

Choose predictive, adaptive, or hybrid delivery

Choose a delivery approach according to how well requirements and work are understood, what testing can reveal, and the cost of change. Predictive delivery suits work whose outputs and sequence can be planned with reasonable confidence. It can still accommodate change through impact assessment and authorization.

Adaptive delivery is useful when uncertainty warrants testing and revisiting priorities or details. Short review cycles are one way to do this, but their length is not universal. Adaptation does not remove budget limits, completion decisions, or quality expectations.

A hybrid approach might keep the webinar date and release-approval requirements fixed while testing alternative messages during production. State what is fixed, what can change, and when changes will be considered.

For a small campaign, an initiation note, major dates, and an issue-and-decision record may be sufficient. Scale the coordination to external commitments, spending, and consequences of failure. Headcount alone does not determine whether project management is needed.

Follow a small campaign from initiation to a change decision

After agreeing the initiation note, confirm production and review availability, then coordinate creation, checking, and release preparation. Suppose a stakeholder requests an additional language landing page. Before adding work, present its estimated impact and available options.

In this fictional example, the current limits are JPY 300,000 and 40 person-hours. The additional work is estimated at JPY 80,000 and 12 person-hours. Money represents the cost allowance; person-hours represent internal effort. They are separate units.

Option	Estimated cost and effort	Schedule and quality check	Decision required
Include it now	JPY 380,000; 52 person-hours	Replan capacity and approval to test feasibility by D10	C authorizes additional allowance and scope
Run it as a later initiative	Current scope stays at JPY 300,000; 40 person-hours	Keep current criteria; assess later work separately	Agree to defer the addition
Replace other work	Numerically JPY 300,000; 40 person-hours if JPY 80,000 and 12 hours can be removed	Different skills, dependencies, or acceptance requirements may alter dates	Approve removed deliverables and their consequences

The replacement option depends on removable work actually existing. Committed spending may not be recoverable. Check contracts, remaining effort, and effects on users rather than deciding solely from the arithmetic.

Record the selected option, reason, approver, and revised plan. Starting an unapproved addition as a favor can leave responsibility for cost and timing unclear.

Use proportionate records, reviews, and project closure

During execution, distinguish the baseline plan, current facts, remaining forecast, and decisions required. A general “on track” message should not conceal approval waiting time or an effect on downstream work. Update the record when it supports a decision rather than adding meetings to every task.

Check deliverables against completion criteria and record acceptance and release decisions.
Assign an owner and deadline or review date to remaining work and defects.
Hand over documentation, contacts, and unresolved issues to operations.
Record actual spending and effort, change reasons, and useful lessons.

If business outcomes will be assessed later, assign the follow-up owner and review date. Delivery completion and a revenue assessment need not occur on the same day. Practical closure leaves the next responsible person able to understand the work and make decisions.