Project management is the work of turning a defined goal into a coordinated plan, guiding the work, and checking that the result meets its purpose. It brings together the people, decisions, resources, and timing needed to deliver something specific, whether that is a product launch, an event, a website, or a customer implementation.
A useful project plan does not have to be complicated. It should make five things clear: what you are trying to achieve, what is included, who is responsible, when key work needs to happen, and how you will know it is done.
What is project management?
Project management applies planning, coordination, and review to work with a defined outcome. A project has a beginning and an end, even if some of its work repeats. Ongoing customer support is an operation; launching a new support process can be a project.
The Project Management Institute describes project management as applying knowledge, skills, tools, and techniques to project work. In practice, the details depend on the project: a small team organizing an event needs a different level of planning from a construction project involving many organizations.
What does a project manager do?
A project manager helps keep the work coordinated from the initial goal through delivery. Depending on the team, that can include clarifying scope, building a schedule with the people doing the work, surfacing risks, communicating changes, and helping resolve blockers. The project manager does not necessarily perform every task or make every decision; responsibilities should be explicit.
In a small team, a founder or another team member may take on this role alongside other work. On a larger project, multiple specialists may manage different parts of the plan.
The building blocks of a project plan
| Building block | Question to answer |
|---|---|
| Outcome | What are we trying to deliver, and why? |
| Scope | What is included, and what is explicitly outside the project? |
| Deliverables | What tangible results or decisions need to be completed? |
| People | Who owns the work, who contributes, and who approves it? |
| Schedule | What are the milestones, dependencies, and target dates? |
| Resources | What time, budget, tools, or external support are available? |
| Risks | What could delay or change the work, and who will watch it? |
| Review | How will progress, changes, and completion be assessed? |
These elements are connected. If the scope grows, the team may need to adjust time, resources, or expectations. Make the tradeoff visible rather than quietly adding work to an unchanged plan.
A practical project management process
1. Define the outcome
Write a short statement of the result and the people it serves. For a community event, the outcome might be a completed event with an agreed program and a prepared attendee experience. Clarify who can approve the outcome and what would make it acceptable.
2. Agree on scope and deliverables
List what the team will produce and what it will not. An event project might include the venue, program, invitations, and event-day plan, while a separate ongoing community program sits outside scope. This prevents reasonable ideas from becoming invisible additions to the project.
3. Map the work and dependencies
Break the deliverables into manageable work. Identify what must happen first, who will do it, and which decisions need another person's input. For example, invitations depend on an agreed date and venue; printing may depend on an approved design.
4. Set a schedule with the team
Use milestone dates and realistic estimates from the people doing the work. Assign responsibility for each deliverable and revisit the plan as you learn more. A schedule is a plan to revisit, not a promise that nothing will change.
5. Run the work and review progress
Give the team a simple place to see the current owner, status, blockers, and next decision. Review whether the work is still within scope and whether the schedule or resources need to change. Escalate a real decision with options and consequences, not just a red status label.
6. Close and learn
Confirm whether the agreed deliverables were accepted, communicate what remains, and hand ongoing responsibilities to the right owners. Capture a few useful lessons while the work is still fresh. Closing a project is more than marking the last task complete.
What are the phases of a project?
Project phases are groups of related work that move a particular project toward its deliverables. Different projects use different phase names and may overlap or repeat activities. PMI's project lifecycle overview gives examples such as feasibility, design, build, test, deployment, and close, and distinguishes project phases from project-management process groups.
For a simple project, you might use define, plan, deliver, review, and close as plain-language stages. They are a practical starting point, not a universal sequence or a substitute for a formal method when one is required.
Project management methods: predictive and agile
A predictive approach plans substantial scope and sequencing in advance, then manages changes against that plan. It can be useful when the work and requirements are relatively well understood. An agile approach emphasizes learning and adapting through smaller increments; Atlassian's overview explains this iterative approach in a software context.
Many teams use a mix. Choose an approach based on the work, the cost of change, the people involved, and the need for feedback. A method should help the team make decisions, not become a label everyone has to perform.
What are the types of project management?
There is no single universal list of seven types. You may hear terms such as predictive or waterfall planning, agile, Scrum, Kanban, and hybrid approaches. They are not all the same kind of thing: for example, Scrum is a framework for working in short cycles, while Kanban emphasizes visualizing and managing the flow of work. A team may use elements together. Start by understanding the project's requirements, feedback needs, and constraints before choosing a method.
Is 90% of a project manager's job communication?
Communication is important because projects depend on shared decisions, handoffs, and timely information. But there is no single percentage established by the question itself, and the balance varies by project and role. The practical goal is to make the right information available to the right people when they need to act, not to optimize for a fixed proportion of the workday.
A copyable project brief
Project: [Name]
Outcome and purpose: [What will be delivered, for whom, and why?]
In scope: [Included work and deliverables]
Out of scope: [Related work this project will not cover]
Owner and decision-maker: [Names or roles]
Contributors and stakeholders: [Who does or reviews the work?]
Milestones: [Deliverable, owner, target date, and dependency]
Resources and constraints: [Time, budget, tools, availability]
Risks and open decisions: [Issue, owner, next action]
Completion test: [Who will accept the result and what will they check?]
Worked example: a customer roundtable
A fictional startup wants to host a small customer roundtable. Its goal is to bring customers together to discuss one product problem and gather feedback. The project owner agrees on an attendee limit, program, venue, and budget. A team member prepares the invitation list; another drafts the agenda; a named decision-maker approves the invitation before it is sent.
The invitation depends on the venue and date being confirmed. The agenda depends on the discussion topic and speakers. The completion test includes holding the event, capturing agreed follow-ups, and assigning an owner to each. This is an illustration, not a reported customer result or a guaranteed event plan.
Project management vs. task management
Task management organizes individual pieces of work: what needs doing, by whom, and when. Project management connects those tasks to a larger outcome, scope, schedule, dependencies, resources, and completion decision. A task list can support a project, but a list alone does not explain why the work matters or how the pieces fit together.
How do you choose project management tools?
Start with the work you need to coordinate. A small team may need a shared document and a clear owner; a complex project may need specialized scheduling, dependency, budgeting, or reporting software. Check how the tool supports your actual workflow, how people will access it, and what information needs to move between systems. Do not assume that every CRM or AI assistant replaces a dedicated project-management platform.
Keep relationship work connected to the project
Many projects depend on customers, partners, advisers, or investors. Finta's CRM can keep relationship history, available inbox context, and next steps together while your project team manages the broader plan in the tools it chooses. Aurora can help prepare work from available workspace context and supported connections; a person reviews the result and decides what happens next.
The best project plan is one your team can understand, update, and use to make the next decision. For a student-specific example, see how to keep group projects moving with AI teammates.