A Project Starts Before the Plan

A company decides to open a new location.

An entrepreneur wants to launch a new product.

An organization needs to implement a new technology system.

A leadership team wants to transform its customer service model.

A family decides to move to another city.

At first glance, these situations may seem completely different.

But they all have something in common:

There is a current situation that someone wants to transform into a different future state through an organized effort.

That is, at its core, what a project is.

And this leads us to an important idea for every project manager:

A project does not begin when someone opens a spreadsheet, schedules a meeting, or assigns tasks. A project begins when an organization decides to turn a need, problem, or opportunity into a specific result.

Project management, therefore, is about much more than managing activities.

It involves understanding what needs to be achieved, why it matters, who is involved, what resources are available, what uncertainties may arise, and how decisions will be made along the way.

The current PMBOK® Guide – Eighth Edition places strong emphasis on connecting projects with organizational value, adaptability, leadership, accountability, and meaningful outcomes.

That perspective changes the way we look at projects.

The question is no longer simply:

“How do we finish the project?”

It is also:

“What are we trying to achieve, and what value should this project create?”

1.1 What Is a Project?

A simple definition is:

A project is a temporary, organized effort that uses resources to produce a specific result within a particular context.

The word temporary matters.

A project has a beginning and an end.

That does not necessarily mean it is short. A project can last weeks, months, or even years.

What matters is that the effort has a defined period during which the necessary work is performed to achieve specific objectives.

For example:

• building a facility is a project;
• developing a new product is a project;
• implementing an ERP system is a project;
• opening a new location is a project;
• launching a new marketing strategy is a project;
• developing an application is a project.

Once the expected result has been achieved—or the organization determines that the project should end—the temporary effort comes to an end.

This is different from an operation.

Operations exist to keep an organization running.

A company that manufactures the same products every day is performing an operation.

Developing a new production line, however, may be a project.

A restaurant serving customers every day is an operation.

Designing and opening a new location may be a project.

A company selling products every day is an operation.

Launching a new e-commerce platform may be a project.

The difference is not necessarily size.

It is the nature of the work.

Operations sustain. Projects transform.

1.2 Projects and Operations: Two Different Ways of Working

This distinction matters because organizations need both.

Operations maintain continuity.

Projects create change.

Imagine a company with a sales department.

Serving customers, preparing quotes, and closing sales are part of normal operations.

But designing and implementing a new CRM system may be a project.

Once the system is implemented and the project is closed, the organization enters a new operational phase: using the system as part of its everyday business.

Projects and operations are therefore not competitors.

They need each other.

Organizations must operate effectively today while developing projects that prepare them for tomorrow.

That is one reason project management has strategic importance.

1.3 Three Fundamental Characteristics of a Project

Projects can be extremely different from one another, but several characteristics help us recognize them.

Temporary

Every project has a defined beginning and end.

Temporary does not mean short.

A major infrastructure project may last several years and still be temporary.

Unique

Every project produces something that has characteristics specific to its context.

Two companies may implement similar sales systems, but their customers, processes, people, resources, objectives, constraints, and risks may be completely different.

Experience helps.

But experience does not eliminate the need to understand the project in front of you.

Progressive Elaboration

At the beginning of a project, we may not know every detail.

As we gather information, engage stakeholders, analyze risks, and move forward, we can refine our understanding of what needs to be done.

That is why project planning should not always be viewed as something written once and then frozen forever.

Projects evolve.

And effective project managers know how to adapt without losing sight of the intended outcome.

1.4 What Does It Mean to Manage a Project?

Managing a project does not simply mean assigning tasks.

It does not mean filling out forms.

And it certainly does not mean constantly asking people whether they have finished their work.

Project management involves integrating knowledge, skills, tools, techniques, people, information, and decisions to achieve the project’s objectives.

A project manager needs to continually ask:

What are we trying to accomplish?

Why does it matter?

What needs to be delivered?

Who needs to be involved?

What resources do we have?

How much time do we have?

What could go wrong?

How will we know whether we are making progress?

What should we do when conditions change?

This reveals something fundamental:

Project management is an integration discipline.

The project manager connects:

objectives + people + resources + time + information + risks + decisions + results.

A change in one area can affect several others.

A major scope change may require more time.

More time may increase cost.

Additional cost may require executive approval.

Approval may delay a decision.

The delay may affect the schedule.

And the entire project may be affected.

That is why project management requires systems thinking.

1.5 A Project Is a System of Decisions

One of the biggest differences between simply coordinating tasks and truly managing a project is the ability to see the project as an interconnected system.

Suppose a client asks for a feature that was not included in the original plan.

At first, it may look like just another task.

But the project manager needs to ask:

• Does it change the scope?
• How much additional work is required?
• Does it affect the schedule?
• Do we need additional people?
• Does it increase cost?
• Does it create new risks?
• Does it change acceptance criteria?
• What other activities depend on it?
• Who needs to approve the change?

A seemingly small decision can have significant consequences.

That is why a strong project manager does not ask only:

“Can we do it?”

The better question is:

“What happens if we do it?”

1.6 The Project Life Cycle

Different projects can use different life-cycle approaches.

However, we can understand the basic flow through five broad stages:

1. Initiation

Identify the need, opportunity, or problem.

Define the initial purpose and objectives.

2. Planning

Determine how the work will be performed.

This may include objectives, scope, activities, resources, schedule, cost, risk, communications, and team structure.

3. Execution

Perform the planned work and produce the deliverables.

4. Monitoring and Control

Compare actual performance with expectations.

Identify issues, changes, risks, and deviations.

Then determine what action is needed.

5. Closing

Complete the project, deliver the appropriate results, capture lessons learned, and transition or release resources.

These stages should not be viewed as rigid boxes.

Real projects evolve.

New information may require replanning.

A risk may trigger a decision.

A change in the business environment may require a different approach.

That is why project management is dynamic.

And it is important not to confuse a project life cycle, a methodology, and project management processes. We will explore those distinctions later in the book.

1.7 Projects Exist Outside the Workplace

One of the easiest ways to understand project management is to look at everyday life.

Consider planning a family trip.

You have:

• an objective;
• a date;
• a destination;
• a budget;
• people involved;
• activities;
• decisions;
• risks;
• constraints;
• reservations;
• potential changes.

That looks a lot like a project.

The same logic applies to:

• planning a wedding;
• moving to another city;
• remodeling a home;
• organizing an event;
• preparing for a certification;
• developing a personal initiative.

The point is not to turn every activity in life into a formal project.

The point is to recognize that project management is fundamentally a structured way of organizing effort to achieve a result.

1.8 From Delivering to Creating Value

For many years, project performance was often summarized through questions such as:

Did we finish on time?

Did we stay within budget?

Did we meet the specifications?

These questions still matter.

But they are not enough.

We should also ask:

Did we achieve the outcome that justified the project?

Will people actually use the product or service?

Does the solution address the original problem?

Can the organization take advantage of the result?

Is the project aligned with business needs?

A useful distinction is:

Deliverable

What the project produces.

Outcome

The change produced through the use of that deliverable.

Benefit

The value that the organization, customer, or other stakeholders may gain from that outcome.

For example, a company may successfully develop a new e-commerce platform.

The project can deliver the platform exactly as planned.

But if customers do not use it, employees are not prepared to operate it, or the organization cannot support it effectively, the expected benefits may not materialize.

Therefore:

Delivery does not automatically equal value.

1.9 The Role of the Project Manager

So what does a project manager actually do?

The answer is not simply:

“Coordinate the team.”

The project manager integrates people, information, resources, decisions, expectations, and objectives.

The role may include:

• clarifying objectives;
• facilitating planning;
• coordinating people and resources;
• aligning stakeholders;
• identifying risks and issues;
• managing change;
• facilitating communication;
• monitoring performance;
• supporting decision-making;
• maintaining focus on outcomes;
• encouraging learning.

But there is another important reality:

The project manager cannot control everything.

Markets change.

Customers change their minds.

Suppliers experience problems.

Organizations change priorities.

Technology evolves.

Unexpected events happen.

The project manager’s role is not to control the future.

It is to help the team make informed decisions as the future unfolds.

1.10 From Tasks to Results

A common project-management mistake is focusing too heavily on completed tasks.

“We held the meeting.”

“We sent the document.”

“We finished development.”

“We completed the training.”

But a completed task does not necessarily mean the project is moving toward success.

The better question is:

What result did that work create?

Suppose the project is implementing a new customer-service system.

Training 100 employees is an activity.

Having those employees effectively use the system is a result.

Improving customer service because of that system and its adoption may be part of the expected benefit.

This changes the way a project manager thinks.

The manager must look beyond the activity and ask:

What are we producing?

Why are we producing it?

Who needs it?

How will we know it works?

1.11 The Project as a Vehicle for Transformation

We can summarize the logic with a simple chain:

Need → Idea → Objective → Project → Deliverable → Outcome → Benefit

An organization identifies a need.

An idea emerges.

The idea becomes an objective.

The objective requires a project.

The project creates deliverables.

Those deliverables produce outcomes.

Those outcomes may generate benefits.

This is why project management is closely connected to business strategy.

Organizations can have great ideas.

But ideas only create organizational value when they can be translated into meaningful results.

1.12 Practical Case: A Company Wants to Expand

Imagine a growing company that decides to enter a new regional market.

The leadership team says:

“Let’s open a new location.”

That sounds simple.

But soon the questions begin:

• Where?
• Which customers?
• How much will it cost?
• When should it open?
• What people do we need?
• What systems are required?
• What permits are needed?
• Which suppliers are involved?
• What risks should we expect?
• How will we measure success?
• What happens if sales are below expectations?

At this point, “open a new location” is no longer simply an idea.

It is an initiative that requires structured management.

Think like a project manager

Need: regional growth.

Opportunity: enter a new market.

Objective: establish a new commercial operation.

Project: design, prepare, implement, and launch the new location.

Deliverables: facility, systems, staffing, training, processes, and launch.

Outcome: new operational and commercial capacity.

Expected benefit: business growth.

This is what project management is really about:

connecting the original opportunity to a meaningful result.

1.13 A Practical Tool: The Project Purpose Map

Before building a detailed project plan, ask:

This is not a substitute for a formal project plan.

Its purpose is to help the team think before it starts planning in detail.

1.14 Five Key Takeaways

1. Projects transform.

Operations sustain the business. Projects help transform it.

2. Projects are temporary.

They have a beginning and an end, even if they last for years.

3. Project managers manage relationships, not just tasks.

Scope, time, resources, cost, risk, people, and decisions are interconnected.

4. Delivery is not the same as value.

A project can deliver its outputs successfully and still fail to create the expected outcome or benefit.

5. Project management requires adaptability.

Plans guide action, but reality changes. Effective project managers know how to evaluate, decide, and adapt.

Reflection Exercise

Think about a project you have managed, participated in, or experienced personally.

It could be:

• a business project;
• a startup initiative;
• a technology implementation;
• a home renovation;
• a trip;
• a relocation;
• a certification;
• an event.

Ask yourself:

1. What was the original need or opportunity?
2. What was the objective?
3. What outcome was expected?
4. Who was involved?
5. What resources were required?
6. What risks appeared?
7. What changed?
8. Did the project achieve its intended outcome?
9. Did it create the expected benefit?
10. What would you do differently next time?

Because one of the greatest assets of a project manager is not only what they know before a project begins.

It is what they learn after it ends.

Think…

Perhaps the most important question when starting a project is not:

“What do we have to do?”

Before that question comes another:

“What are we trying to accomplish, and why does it matter?”

When a project manager understands the purpose before managing the tasks, the entire perspective changes.

They stop seeing only activities.

They see relationships.

They stop seeing only dates.

They see commitments.

They stop seeing only costs.

They see resources that must be used wisely.

They stop seeing only risks.

They see uncertainty that must be managed.

And they stop seeing only a project.

They see an opportunity to transform a current situation into a meaningful result that creates value.

That is the true starting point of project management.