Much of the important change in a small business happens through projects: installing a new machine, launching a product, moving premises, implementing software, hiring a senior manager, entering a new market or completing a large customer order. Yet many small businesses run projects informally, as a stream of tasks squeezed in around daily work. Deadlines slip, costs creep up, people are unsure who is responsible, and the project quietly drains attention from the core business.
Project management is simply a structured way to deliver a defined result on time, within budget and to the required quality. Large organisations use formal methods and certified project managers. Small businesses do not need the paperwork, but they benefit enormously from the core ideas. This article explains what a project is, the five phases every project passes through, and the ten areas that need to be managed, scaled to a small business.
What makes something a project
The Project Management Institute (PMI) defines a project as “a temporary endeavor undertaken to create a unique product, service, or result”. Two words matter: temporary and unique.
- Temporary means the project has a defined start and end. Ongoing work, such as routine recruitment, monthly invoicing or daily production, is operations, not a project.
- Unique means the output is new or different in some way. It might be a new product, a one-off installation or a change to how the business works.
For example, “hiring staff” in general is an ongoing operational activity. “Recruit and onboard a production manager by the end of March” is a project. It has a clear objective, a defined end and a set of activities that will not be repeated in exactly the same way.
The distinction matters because projects need different management from operations. Operations benefit from standard procedures and steady routines. Projects benefit from planning, clear ownership, milestones and active control of change and risk.
Project management, in PMI’s terms, is the application of knowledge, skills, tools and techniques to project activities to meet the project’s requirements. In plain language, it means deliberately planning and controlling the work rather than hoping it comes together.
The five phases of a project
Most projects, large or small, move through five broad phases.
1. Initiation
The project is conceived and defined at a high level. What problem are we solving or opportunity are we pursuing? What is the objective? Why now? Who will own it? What is the rough budget and timeframe? Is it worth doing at all?
For a small business, initiation can be a single page, sometimes called a project charter, that answers those questions and is agreed by the owner. That page prevents many later arguments about what the project was meant to achieve.
2. Planning
The work is broken down and organised. Planning answers:
- What exactly will be delivered? This is the scope, including what is out of scope.
- What work is needed? Breaking the deliverables into tasks, often in a work breakdown structure.
- Who will do it? People, roles and any external suppliers or contractors.
- When? A schedule with milestones and dependencies.
- How much? A budget covering labour, materials, equipment, services and contingency.
- What could go wrong? The main risks and how they will be handled.
- How will we communicate? Who needs updates, how often and in what form.
In the recruitment example, planning might include engaging a recruiter or briefing internal HR, defining the role, setting a timeline for advertising, interviews and decisions, and planning onboarding.
3. Execution
The planned work is carried out. People are assigned, suppliers engaged, materials ordered and tasks completed. Execution involves many moving parts and usually consumes most of the time and budget. For the recruitment project, it is the advertising, screening, interviewing, reference checking, offer, acceptance and onboarding.
4. Monitoring and controlling
Throughout execution, progress is compared with the plan. Are tasks on schedule? Is spending on budget? Is quality as required? What has changed? Monitoring means measuring. Controlling means acting on the differences: re-planning, re-allocating resources, escalating issues or agreeing scope changes.
External events can upend any plan. Supply disruptions, illness, regulatory changes or a sudden shift in demand can all force changes. Organisations that monitor projects actively see problems sooner and adapt faster than those that only look up when a deadline has already passed.
5. Closing
The project is completed and formally closed. Deliverables are handed over and accepted, contracts are finalised, final costs are recorded and the team reviews what went well and what to improve next time. Closing is often skipped in small businesses, which means the same mistakes are repeated. A one-hour lessons-learned review is one of the highest-value hours in any project.
Closing also means confirming that the objective was achieved. Projects often change along the way as new factors emerge. A capable project owner adapts the plan, re-estimates costs and timing, and still drives the project to a clear finish rather than letting it fade out.
Ten areas to manage
PMI’s guidance has traditionally organised project management into ten knowledge areas. Later editions reorganise this material around principles and performance domains, but the ten areas remain a practical checklist for any project.
1. Integration. This is about making the parts fit together and fitting the project into the business. A common small-business failure is becoming so absorbed in one exciting project that the core business suffers. Integration means balancing the project with daily operations, and making sure scope, schedule, cost and quality decisions are consistent with each other.
2. Scope. This defines exactly what is included and excluded. Scope is the project owner’s primary responsibility. Uncontrolled scope growth, known as scope creep, is the most common cause of overruns. Every proposed addition should be assessed for its effect on time and cost before it is accepted.
3. Schedule. This sets out how long each task will take, in what order, and what depends on what. A simple Gantt chart or task list with dates and dependencies is enough for most small projects. Identify the critical path: the sequence of dependent tasks that determines the earliest finish date. Any delay on that path delays the whole project.
4. Cost. This covers the budget for people, materials, equipment, services, overheads and contingency. Service businesses that deliver projects for clients live by this discipline. They estimate the people and time needed, set a price, allocate a budget to the project owner and track actual costs against it.
5. Quality. This defines the standards the deliverables must meet and how they will be checked, such as inspections, tests, reviews and acceptance criteria agreed with the customer.
6. Resources. This covers the people and equipment the project needs: how many people, with which skills, at what cost and for how long. In small businesses the same people often work on projects and daily operations, so their availability must be planned realistically.
7. Communications. This defines who needs what information, when and how. With two people, communication is easy. With a larger team, external contractors and a customer, it needs structure: a regular update, a shared task list or project tool, and clear meeting notes with actions.
8. Risk. This means identifying what could go wrong from day one and planning responses. Typical risks include a key person leaving mid-project, late supplier deliveries, a design that does not work, funding shortfalls, approvals delayed and miscommunication. A simple risk register lists each risk, its likelihood and impact, the planned response and an owner.
9. Procurement. This covers obtaining what the project needs from outside: materials, equipment, contractors, services and sometimes funding. Long-lead items should be identified early, because they often sit on the critical path.
10. Stakeholders. This means identifying and managing everyone affected by the project. Internal stakeholders include staff and management. External stakeholders include customers, suppliers, contractors, partners, lenders and sometimes regulators or neighbours. Understanding their interests and keeping them informed avoids surprises and resistance.
Delays cost more than time
Delays are rarely just a scheduling inconvenience. They extend overheads, tie up people, defer revenue and can damage customer trust. In some industries, buyers have paid deposits on the promise of delivery years ahead, only to wait far longer than promised. That experience shows how badly broken delivery commitments damage reputation. Treat schedule as a commercial commitment, not an aspiration. When a delay is unavoidable, communicate early with a revised, credible plan.
A one-page project plan template
For most small-business projects, one page is enough to start:
| Item | Content |
|---|---|
| Project name and owner | One accountable person |
| Objective | What will be achieved, measurably |
| Scope | Included and excluded deliverables |
| Milestones | Five to eight key dates |
| Budget | Total and main categories, plus contingency |
| Team and suppliers | Who is involved and their roles |
| Top risks | Three to five, each with a response and owner |
| Communication | Update frequency, format and audience |
| Success criteria | How we will know it is done and worked |
Review the page weekly during execution. Update dates, costs and risks, record decisions and keep a simple action list.
Tools
Simple tools are usually enough. A shared spreadsheet, a task board or an online project-management application can hold tasks, owners, dates, files and discussion in one place. The best tool is the one the team will actually use. Keeping project communication and documents together, rather than scattered across emails and messages, saves time and reduces errors.
A worked example: installing a new machine
A metal products business decides to install a fibre laser cutter to replace outsourced cutting. The owner appoints the production manager as project owner.
Initiation. Objective: “Install, commission and bring the new laser into full production, with two trained operators, by 30 September, within a budget of $520,000 including building works.” Expected benefit: lower cutting costs and lead times of two days instead of seven.
Planning. The production manager breaks the work into packages: equipment purchase and delivery, building works (power upgrade, extraction, slab check), installation and commissioning, operator training, nesting software and integration with the job system, material storage and handling, and transition of work from the subcontractor. The schedule shows that the power upgrade and machine delivery are on the critical path. The risk register lists delivery delay, the power upgrade taking longer than expected, operator training gaps and a temporary drop in output during transition. Responses include ordering early, engaging the electrician immediately, training two operators plus a backup, and keeping the subcontractor engaged until the laser is proven.
Execution. The machine is ordered, building works proceed and training is scheduled with the supplier. The production manager holds a fifteen-minute project check-in each Monday.
Monitoring and controlling. In week six, the electrician reports that the switchboard needs a larger upgrade than quoted, adding cost and two weeks. The production manager assesses the impact, uses part of the contingency, re-sequences training to happen at the supplier’s site before installation and keeps the overall finish date.
Closing. The laser enters production in the last week of September. Cutting costs and lead times are tracked for three months against the business case. A one-hour review records lessons, including “get electrical capacity assessed before ordering equipment”, for the next project.
Traditional or agile?
Two broad approaches to project management are often contrasted. Traditional, or predictive, approaches plan the scope, schedule and cost up front and then manage delivery against the plan. They suit projects with well-understood requirements, such as installing equipment, fitting out premises or building to a fixed design. Agile, or adaptive, approaches deliver in short cycles, reviewing and re-planning frequently as requirements become clearer. They suit software, product development and other work where the right answer emerges through iteration.
Many small-business projects benefit from a mix: a clear overall objective, budget and milestones, with short weekly cycles of planning and review inside them. The key is to match the approach to how much is known at the start.
Common mistakes in small-business projects
- No single owner. Projects with several “owners” have none.
- Vague objectives. “Improve the workshop” is not a project objective. “Install and commission the new press brake and train two operators by 30 June” is.
- Planning only the happy path. Ignoring risks guarantees surprises.
- Accepting scope changes without re-planning.
- Under-estimating internal time because staff are also running daily operations.
- Skipping closure, so lessons are lost and loose ends linger.
Summary
A project is a temporary effort to create a unique result. It moves through initiation, planning, execution, monitoring and controlling, and closing. Managing it well means paying attention to integration, scope, schedule, cost, quality, resources, communications, risk, procurement and stakeholders. Small businesses do not need heavy methods, but they do need one accountable owner, a clear objective, a simple plan, active monitoring and a proper close. Those habits turn projects from distractions into reliable engines of improvement.
If you have an engineering or operations project that needs scoping, planning or delivery support, GoCore provides project support services.
Sources: small-business training notes on project management frameworks, together with the Project Management Institute’s published definitions and knowledge areas. Examples are illustrations.
