Have you ever worked in an organization where everyone insists they don’t really have “projects,” but somehow there are always dozens of things people are working on that suck up a lot of time? There may be no formal implementation plan, no project manager, no steering committee, and no Gantt chart, but the work effort still exists. Finance wants a better report, HR wants to clean up a process, Sales needs a small automation, or Operations wants to change how information is collected, reviewed, and communicated.
That’s often where smaller organizations get stuck. The work does not feel large enough to become a formal project, so it never enters any kind of meaningful prioritization process. It gets handled through hallway conversations, emails, staff meetings, individual preferences, or whichever issue happens to be causing the most irritation that week. The organization may avoid the overhead of project management—and I’ve seen people do that proudly—but that habit also avoids the discipline that helps people decide which work should happen first.
This reminds me of the Duck Test: if it looks like a duck, walks like a duck, and sounds like a duck, it’s probably a duck. Saying you “don’t do projects here” doesn’t mean you actually don’t, it means you don’t call it that. Yet sometimes, it just needs to be called what it is: it’s project, and maybe you should treat it as one.
But it’s not always best to turn every small idea into a full project, especially if you don’t have the staff or resources to make it happen. That would be absurd, and probably a good way to ensure nobody ever tells you about an improvement idea again. A small reporting change does not need a charter, a full blown project plan and a governance committee, even if it takes a couple weeks to make the change. Some work simply needs to be understood, sized, prioritized, assigned, and completed.
The discipline is in treating smaller work as though it deserves the same quality of thinking as a project, without forcing it through the same level of formality. That distinction matters because many small ideas still consume real capacity. A two-day improvement may not sound significant until ten people each have five of them, all competing with regular operations. A “quick fix” can still interrupt a team, create dependencies, introduce risk, or distract from something more important. Leaders often forget that a dozen “quick fixes” is just an unstructured project. When smaller work is not visible, leaders tend to underestimate how much effort is already committed, and teams are left trying to reconcile priorities that were never actually prioritized.
A practical operating model begins with a simple question: does this idea deserve attention? That does not need to become complicated. The idea should be clear enough to explain what problem it solves, who benefits, what outcome is expected, and how much effort it will likely require. If nobody can explain those things, the idea may need more definition before anyone invests time in it. If the idea is clear, the next question is whether it should happen now, later, elsewhere, or not at all.
This connects naturally to the same thinking behind Getting Things Done for Executives. Smaller work should still have a disposition. Do it, delete it, defer it, or delegate it. If the idea is useful, small, and within someone’s authority, do it. If it does not create enough value, delete it. If it matters but the timing is wrong, defer it with a reason. If it belongs to someone else, delegate it with enough clarity that the person can actually act.
For work that is larger, more complex, or competing with several other ideas, the organization can borrow from the same thinking used in the Priority Model, without needing to use the full model every time. Ask whether the idea supports the direction of the organization, improves operations in a meaningful way, is feasible with current capability and capacity, and creates enough financial or practical benefit to justify the effort. That simple evaluation is often enough to prevent the loudest request from becoming the next default priority. You can even use the same prioritization chart to evaluate smaller ideas without needing a project plan to back it.
This is especially helpful in organizations that are trying to improve but do not yet have formal project structures. They may not need a project office, but they do need a way to prevent improvement work from becoming random. A small leadership team can maintain a visible list of improvement ideas, review it regularly, choose the next few items based on value and capacity, and make sure every accepted item has an owner and a clear expected outcome. It doesn’t need bureaucracy, just some basic operational discipline.
If necessary, there can also be a threshold where an idea graduates into a project. If the work crosses departments, requires meaningful investment, affects customers, changes systems, introduces risk, or needs several people coordinated over time, it probably deserves more structure. Just because you “don’t do projects” doesn’t mean you shouldn’t be open to consider some added formallity. It means the organization should stop pretending that work is just a quick task.
You don’t need a formal project, or a project management office, just to practice good prioritization. You only need enough discipline to decide what deserves attention, what should wait, who owns it, and what outcome the work is supposed to create.