To prioritize IT projects, write every request down in one list, score each against the same few business drivers, adjust for effort and capacity, and fix the order in a short meeting with the people who pay for the outcome. Do it again every quarter. A small company without a large IT team gets the most from a method that fits on one page, because the real constraint is not ideas, it is the few people and dollars available to carry them out.
This guide gives you that method: which criteria to use, how to score, a worked example with a made-up 60-person company, the rules that keep security and recovery work from losing to flashier projects, and a review routine. If you want a second pair of eyes on your list, we start with a free technology assessment and hand back a prioritized plan in plain language that you own.
TL;DR
- Prioritizing means ranking projects against shared criteria so scarce people and money go to the work that matters most, instead of whoever asks loudest.
- Use five to seven drivers: risk reduction, cost savings, operational efficiency, growth, legal or compliance duty, plus effort and capacity. Never rank on one factor alone.
- Score on a 1 to 10 scale, weight the drivers to match this year's goals, then sanity-check the result against capacity and dependencies.
- Give security and recovery work a risk floor so it cannot be outscored by new features.
- Re-rank quarterly. A backlog is a living list, not an archive.
Table of Contents
- Why prioritization matters more when you are small
- Start with one list and one owner
- Choose your criteria
- Score, weight, then test against reality
- A worked example: a 60-person distributor
- Give security and recovery work a risk floor
- Match the method to the size of your list
- Special case: AI and automation projects
- Run the review every quarter
- Mistakes that sink prioritization
- Perspective: why a plan you own matters
- Get the first ranking done with us
- FAQ
- Sources
Why prioritization matters more when you are small
A large company can absorb a bad project. A 40-person company cannot. You have one or two IT people, or an outside provider, and the same people keep the lights on, answer help requests and deliver projects. Every project you start competes with all of those for the same hours.
CIO magazine warns that when projects are chosen department by department, without a view of overall strategic impact, a business risks competing for the same people and technologies, facing conflicting deadlines and goals, and even producing outcomes that hurt other areas. In a small company that looks familiar: sales wants a new portal, finance wants an ERP upgrade, operations wants order automation, and nobody has asked whether the backups have ever been restored.
There is also an upside worth naming. Harvard Business School research on IT and firm performance argues that IT capability, not simply IT spending, correlates with profitable growth, helping firms scale through standardization, streamlined operations and better management visibility. The point is not to spend more. It is to spend on the projects that build capability.

Start with one list and one owner
Before any scoring, collect every request in one place. A spreadsheet is enough. For each item capture:
- A one-sentence description of the problem, not the solution ("order entry takes 25 minutes per order", not "buy workflow software").
- The sponsor: the person who will answer for the result.
- A rough cost range and the staff time it needs, in hours.
- What it depends on (a license, a vendor, another project).
- What happens if you do nothing for six months.
That last line matters. The GAO's guide to investment decision-making recommends that each project have a business case with the sponsor's justification, the organizational need, benefits, costs, risks and proposed time frames. For a small business, that business case can be five lines in a spreadsheet row. The discipline is the same: no row, no ranking.
Name one person to own the list. In many SMBs that is the owner or operations lead, with the IT lead or a fractional technology leader advising. Without an owner the list drifts back to "whoever emailed last." If you have no one in that seat, this is exactly the kind of work a fractional CTO takes on, so that technology decisions are tied to business goals rather than to the loudest request.
Choose your criteria
You do not need twenty criteria. Published guides converge on a short set. CIO's guide lists seven common project drivers: competitive advantage, cost savings or financial benefit, operational efficiency, legislative, legal or tax implications, improved quality, risk reduction, and growth or business opportunities. An older CIO article boils it down to four: expense reduction, revenue increase, strategic impact, and legal, regulatory or security needs, and says they should be tied together in a repeatable process.
The GAO sets a floor worth remembering: ranking criteria should at a minimum include cost, risk and benefit factors, plus how well the project meets mission needs, and decisions should rarely rest on a single factor.
For a typical SMB we suggest these five scoring drivers plus one capacity check:
| Driver | The question it answers | Typical examples |
|---|---|---|
| Risk reduction | Does this lower the chance or cost of a breach, outage or data loss? | MFA, patching, tested backups, access cleanup |
| Cost savings | Does it cut recurring spend or avoid a known cost? | Cloud cost cleanup, license consolidation |
| Operational efficiency | Does it give people hours back each week? | Automating order entry, onboarding |
| Growth | Does it help win or serve more customers? | Customer portal, new integrations |
| Legal or compliance | Is there a rule, contract or insurer requirement with a date attached? | Customer security questionnaires, health or legal data handling |
| Effort and capacity (scored inversely) | Can we actually deliver it with the people we have? | Staff hours, vendor dependence, change load on users |
Pick the drivers once, write down what a 2, a 5 and a 9 look like for each, and keep them stable. That way a score means the same thing in March and in September.
Score, weight, then test against reality
Step 1: Score each project from 1 to 10
CIO's scoring process asks teams to score each project across all parameters on a 1 to 10 scale, with specific criteria assigned to each part of the range. Score as a small group, not alone. Ask the person who proposed the project and one skeptic.
Where you can, use dollars and hours. "Saves about 15 staff hours a week" is easier to score than "improves efficiency." Where you cannot, use the 2, 5, 9 definitions.
Step 2: Weight the drivers to match this year
The same CIO article describes two levers: weights on the overall drivers and weights on specific parameters, adjusted to current business priorities. If this year's goal is to protect margin, cost savings gets a heavier weight. If you are bidding for customers who demand security proof, risk reduction does.
This is also where the conversation earns its keep. One planning guide notes that the value of weighted scoring is its customizability, and that debating which criteria matter and how to weight them forces leadership to state strategy in concrete terms. Owners often discover they disagree about what the business is optimizing for. Better to find out in a spreadsheet than after the money is spent.
Step 3: Compute the total and add a capacity check
Multiply each score by its weight, add them up, and rank. Then ask the questions a score cannot:
- Dependencies. Does project B require project A first? Then A moves up regardless of its own score.
- Capacity. Add up the staff hours of your top five. If they exceed what your team has in the quarter, the lower ones wait.
- Time to value. Between two similar scores, favor the one that pays back sooner.
- Change load. Staff can absorb only so many new tools at once.
A 2x2 view of business value against effort is a useful cross-check on the scores: it sorts items into quick wins, strategic projects, fill-ins and items to avoid. If your top-scored project lands in "high effort, moderate value," look again.
A worked example: a 60-person distributor
This is an illustration with invented numbers, not a client result. Say a 60-person distributor has six requests and one part-time IT lead. The leadership team weights the drivers: risk reduction 30%, cost savings 25%, operational efficiency 20%, growth 15%, ease of delivery (the inverse of effort) 10%.
| Project | Risk | Cost | Efficiency | Growth | Ease | Weighted score |
|---|---|---|---|---|---|---|
| Automate order entry | 2 | 7 | 9 | 6 | 4 | 5.45 |
| MFA and patching on all endpoints | 9 | 3 | 4 | 2 | 8 | 5.35 |
| Restore-test the backups | 8 | 4 | 3 | 2 | 8 | 5.10 |
| Azure cost cleanup | 2 | 8 | 5 | 2 | 7 | 4.60 |
| ERP replacement | 4 | 4 | 7 | 6 | 1 | 4.60 |
| New customer portal | 2 | 3 | 4 | 9 | 2 | 3.70 |
Order automation edges out the security items on pure score. But the team applies two rules before committing.
- The risk floor. Any project that closes a known high-risk gap (no MFA, untested backups) is scheduled in the first quarter regardless of rank. These items are cheap, quick and protect everything else.
- The capacity check. MFA, patching and the restore test together need about 60 staff hours. Order automation needs far more and a vendor. With one part-time IT lead, the quarter is MFA and patching, the restore test, then order automation kicked off with outside help. Azure cleanup goes next quarter. The ERP replacement is broken into a requirements phase, and the portal waits.
Notice what the scoring did. It did not hand down a verdict; it produced a defensible starting order and exposed the trade-offs. Planoda's comparison of frameworks makes the same point: the most common failure is using the output as a substitute for the conversation rather than as a structure for having it.
Give security and recovery work a risk floor
New features are easy to justify because their benefits are visible. Security and recovery work is easy to defer because its benefit is a bad day that did not happen. That is why we recommend an explicit floor rather than trusting scores alone.
When it comes to vulnerabilities, you do not have to guess what to patch first. CISA maintains the Known Exploited Vulnerabilities catalog and strongly recommends that all organizations, including private industry, prioritize remediation of the listed vulnerabilities. Vulnerabilities in that list are ones already exploited in the wild, so they jump the queue ahead of theoretical issues.
To find the gaps that belong on the floor in the first place, a structured walk through your environment helps. Our SMB IT assessment checklist covers eight areas and ranks the top three risks, and the one-page cybersecurity checklist pairs findings with prioritized fixes.
Match the method to the size of your list
You do not always need weighted scoring. Pick the lightest tool that works:
| Situation | What fits |
|---|---|
| Fewer than eight items and the leadership team already agrees | A conversation and a ranked list, no formula |
| Many items, need a rough order quickly | A simple value-over-effort score |
| Stakeholders disagree about what matters | Weighted scoring, because it forces the criteria debate |
| A fixed deadline with a set scope | Must-have, should-have, could-have sorting |
This mirrors a published decision table: RICE for a large backlog needing fast rough order, MoSCoW for a fixed release date, weighted scoring when stakeholders disagree, and no framework for a small, aligned backlog under eight items. Most SMBs land on weighted scoring with five or six drivers, and that is what the example above uses.
Another guide notes that effective teams often use one framework to prioritize and another to communicate, for instance scoring for ranking and a Now/Next/Later view for sharing the plan. That works well for owners: the score is for the working group, and the three-column roadmap is for everyone else. Our technology roadmap template guide walks through a five-step version.
Special case: AI and automation projects
AI requests are the ones most likely to arrive with hype attached. Score them like everything else, with two additions. First, ask what workflow gets measurably faster and by how much. Second, ask what the failure mode is and who checks the output. Our approach is to rank agent opportunities by ROI and risk, build them into tools the team already uses, and ship with monitoring, rollback and human checkpoints from day one. If you want a measurement frame, the 90 day AI ROI scorecard is a good place to begin, and the workflow automation guide shows three starter workflows.
Run the review every quarter
A ranked list goes stale. Kissflow's guidance is to hold quarterly prioritization reviews so the backlog does not become a graveyard of items that were once urgent but no longer matter. A 60-minute quarterly meeting is enough:
- Remove anything done or no longer relevant.
- Add new requests, scored with the same definitions.
- Re-weight the drivers if the business goals shifted.
- Re-check capacity against the next quarter's calendar.
- Publish the top five and what is explicitly deferred.
If something urgent breaks mid-quarter, handle it, then log what it displaced. Tracking displaced projects shows leadership the true cost of reactive work and often justifies adding capacity.
Mistakes that sink prioritization
- Confusing urgent with important. The loudest request is not always the most valuable. Kissflow lists this, along with treating the backlog as permanent and ignoring capacity constraints, among the common errors.
- Letting each department rank its own. Siloed selection is how teams end up fighting over the same people, as CIO warns.
- Ranking on one factor. Cost alone, or urgency alone, produces lopsided portfolios. The GAO's guidance says decisions should rarely rest on one factor.
- Scoring without a business case. If nobody can say what the project is for and what it costs, the score is fiction.
- Treating the score as the decision. Use it to structure the discussion, then decide.
- Skipping the follow-through. A plan nobody owns or funds is just a document.
Perspective: why a plan you own matters
Most small companies do not have a prioritization problem so much as a visibility problem. Nobody has seen the whole list, the real cost of each item, or the staff hours they would consume, so decisions get made by urgency and volume.
We built our approach around that. Engagement starts with a free technology assessment. The output is a prioritized, plain-language plan that the client owns, and then we can deliver and run it. We think enterprise-grade thinking, ranked by ROI and risk and tied to real workflows, should not require an enterprise-sized team or budget.
The scoring method above works whether you run it yourself or with us. What changes with an experienced technology leader in the room is speed and honesty: the risk floor gets enforced, the capacity math gets done, and the project that sounds exciting but does not move a business number gets deferred without a fight.
jaras
Get the first ranking done with us
If your list is long and your team is small, our assessment is built for this starting point. We review your environment, rank the findings by risk and ROI, and give you a plain-language plan you keep, whether we carry it out or not. If you want ongoing leadership for the plan, our fractional CTO engagements cover it, and you can book a 30-minute call to start.

Before the call, bring your list of requests, a rough idea of who handles IT today, and the two or three business goals that matter most this year. That is enough to begin.
FAQ
How many criteria should I use to rank IT projects?
Five or six is plenty for an SMB. Published guides list seven common drivers, but most small companies only need risk reduction, cost savings, efficiency, growth, compliance and a capacity check. More criteria slow the discussion without changing the order much.
Should security projects always come first?
Not all of them, but the ones that close known high-risk gaps should get a floor in the first quarter. CISA recommends that all organizations prioritize remediation of vulnerabilities in its Known Exploited Vulnerabilities catalog. Larger security projects can be scored alongside everything else.
How often should we re-rank the list?
Quarterly works for most small businesses, with a short interim check when something major changes, such as a new compliance requirement or a big customer demand. Each review should remove finished or stale items and re-check capacity.
Who should decide the final order?
The business owners who fund and live with the results, advised by whoever leads IT. Scoring can be done by a small working group, but the final order should be agreed by leadership so departments are not ranking their own requests.
Sources
- 6 proven strategies for evaluating and prioritizing IT projects (CIO)
- Prioritizing IT Projects Based on Business Strategy (CIO)
- A Guide for Evaluating Investment Decision-making (GAO)
- IT capability and firm performance (Harvard Business School)
- Reducing the Significant Risk of Known Exploited Vulnerabilities (CISA)
- Enterprise Backlog Prioritization Models
- Roadmap Planning Frameworks Compared
- RICE vs MoSCoW vs ICE
- RICE Scoring vs MoSCoW vs Weighted
