Small projects in PNG and the South Pacific often lose time for simple reasons: unclear tasks, weak follow-up, poor reporting, slow testing, limited field technology, and no single person holding the program together. Good project management is not only for large infrastructure. It is often what small projects need most.
Small Does Not Mean Simple.
Small projects often look easy from the outside. A geotechnical investigation. A short access road. A building site assessment. A drainage upgrade. A small subdivision. A routine laboratory test.
None of these sound complex. Yet across PNG and the wider Pacific, these projects often take longer than expected. A task that should take days becomes weeks. A simple test result sits in a queue. A contractor misses a date. A consultant waits for data. The client asks for an update, and nobody has a clear answer. That is not always because the work is difficult. Often, it is because the project is not being managed.
The Hidden Cost of Weak Follow-up
For private investors, banks and developers, time is not a soft issue. Time affects finance, sales, holding costs, contractor availability and confidence. When deadlines slip, the usual explanations appear... The weather caused the delay. The contractor was busy. The lab was slow. The client changed something. The staff member was sick. The data was missing. The team was waiting on someone else.
Sometimes those explanations are true. But they are not a project management system.
A managed project has assigned tasks, dates, owners, dependencies and follow-up. It has a program and it has records. It has a person responsible for asking the awkward question before the delay becomes normal: what is due, who owns it, and what happens if it is late?
Without that discipline, small projects drift. Nobody shows up with a proper program. Nobody updates the client with enough detail. Nobody owns the chain of decisions. The result is a project where everyone is involved, but nobody is accountable.
PNG Does Not Need Excuses. It Needs Systems.
It is too easy to blame “Pacific time” when projects run late. This explanation is lazy and it shelters the real issue.
Small projects often struggle because teams lack access to tools, training, reliable technology and quality assurance systems. Field teams may not have reliable internet. Staff may need to return to the office to update project plans, send files or access systems. Remote sites create logistical pressure. Yet these problems are practical, and that means they can be managed!
Although better internet access including satellite options, will help [sic: Starlink], technology alone is not enough. Teams need to know how to use it. They need clear templates with good reporting habits, escalation points and simple project controls that fit local conditions.
A Gantt chart does not build the project. But it shows whether the project is moving.
Small Projects Need Professional Project Management
Large projects usually have formal governance. They have project managers, reporting cycles, risk registers, programs, approvals and budget controls. Conversely, small projects often get treated differently. They are left to informal coordination, phone calls and assumptions. This is where things go wrong...
Professional project management skills gives small projects some structure because it turns loose activity into a controlled process. It helps the client understand what is happening, what is late, what decision is needed, and what the next risk might be. For a property developer, this matters because delays affect sales and holding costs. A developer's contracts with their customers are at risk due to sunset clauses. And for a bank, it matters because project slippage affects finance risk.
Good project management does not need to be complicated. For small projects, the basics are often enough: a clear scope, a simple work program, named task owners, weekly meetings, issue tracking, document control and active follow-up. However it's the absence of these basics creates most of the damage.
Accountability is not about blame. It is about clarity.
A contractor should know what is due and their project manager should know where the delay sits and what action is being taken. When this works, delays become visible early. This is especially important in PNG and the South Pacific, where projects often face remote access, workforce capacity gaps, lab testing delays and contractor performance issues. Those conditions make project management more important.
The harder the delivery environment, the more discipline the project needs.
The lesson for investors and developers
Small projects should not be managed casually because they have smaller budgets. They should be managed carefully because they have less room for waste. A delayed lab result, incorrectly acquired or projected survey data, unclear approval requirements or slack contractor updates can stop progress for weeks. The cost is often most obvious in the client’s confidence and the quality of the final outcome.
The core point is simple: small projects need professional project management because small delays still cost money. In PNG and across the Pacific, better delivery will not come from accepting slow progress as normal. It will come from clearer programs, better tools, stronger training, tighter follow-up and a culture where people are expected to account for the work they agreed to do.
This article is inspired by the team at MC Infrastructure, who regularly undertake multidisciplinary project workflows across PNG. They utilise Microsoft Dynamics to ensure all projects are adequately managed.
