It is the second of January, which means half the business owners I know have just written some version of "go digital this year" in a notebook. By March, most of those notes will be exactly where last year's were: nowhere.
The problem is not motivation. In fifteen years of building software for companies of every size, I have never met an owner who lacked enthusiasm in January. The problem is that most digital goals for business are written as projects without owners, deadlines without consequences, and ambitions without numbers. They are resolutions wearing a business costume, and they die the same way resolutions do.
Here is the structure I recommend instead. It is not clever. It is just complete.
Why digital resolutions fail by February
Look at a typical New Year list from an SME owner:
- Improve our online presence
- Start using a CRM
- Automate more processes
- Explore AI
Every item fails the same three checks:
- No named person. "We" will do it, meaning nobody will.
- No number. There is no revenue or cost figure attached, so nobody can tell if it worked, and it silently loses priority to anything with a number.
- No decision forced. "Start using a CRM" defers every hard question: which one, migrated by when, who enters the data.
A goal that survives contact with February looks structurally different: "Ibu Rina gets all 400 active customers into a CRM by 31 March, and from April the sales team logs every deal there, measured by whether month-end recap comes from the CRM instead of WhatsApp screenshots."
Longer to write. Vastly more likely to happen.
The two-to-three goal ceiling
If you run a business with under 100 staff and no IT department, your realistic capacity is two or three digital goals per year. Not per quarter. Per year.
That number sounds low until you count what each goal actually consumes: vendor selection, budget approval, data cleanup, staff training, the six weeks of grumbling while people adjust, and your own attention as the tie-breaker on every decision. I wrote a companion piece on the selection method itself in Set 3 Technology Goals for the New Year, so here I will focus on what makes goals keepable once chosen.
The short version of selection: tie every goal to a revenue number or a cost number. If you cannot state the number, you have an idea, not a goal. Ideas go in a backlog document. Goals get resources.
Anatomy of a keepable digital goal
Every goal that survives needs four parts written down, one page maximum.
The number. What moves, from what, to what. "Reduce stock discrepancy from around Rp40 million per quarter to under Rp10 million." Estimates are fine. A rough number beats no number.
The owner. One name. Not the most senior person, the person closest to the daily pain. A branch supervisor who suffers the stock chaos will push an inventory project harder than a director who reads about it in reports.
The date. Pick something uncomfortable. If your instinct says December, write July. Long deadlines do not create better outcomes, they create eleven quiet months and one panicked one.
The definition of done. Describe the observable end state. "The Monday management meeting uses the dashboard, and nobody prepares a manual recap anymore." You either see that or you do not.
The quarterly cadence that keeps goals alive
Annual planning fails because a year is too long to steer. Weekly tracking fails because owners abandon it by week five. Quarterly is the cadence SMEs can actually sustain.
Here is the full system. It takes four meetings a year, ninety minutes each.
| Quarter | What happens in the meeting |
|---|---|
| Q1 (January) | Pick 2 to 3 goals, write the one-pagers, approve budgets |
| Q2 (April) | Honest check: on track, behind, or dead? Kill or fix, no zombie goals |
| Q3 (July) | Finish or descope; if a goal is done, optionally promote one from the backlog |
| Q4 (October) | No new goals; land what is in flight, note lessons for next January |
Two rules make this work.
First, the April meeting must allow killing a goal out loud. A cancelled project costs its deposit. A zombie project costs its deposit plus a year of everyone pretending. When we helped a distributor cancel a failing app project in April instead of dragging it to December, they redirected roughly Rp60 million into fixing their order-entry flow, which actually shipped.
Second, October is for landing, not launching. New goals started in Q4 collide with year-end closing, holidays, and staff leave. They begin with a handicap. Resist.
The backlog: where good ideas wait without dying
Everything that did not make the cut goes into one shared document. New ideas that appear mid-year go there too, immediately and without debate.
This matters psychologically more than operationally. Owners resist small goal lists because cutting an idea feels like killing it. A backlog reframes the cut as a queue. The idea is not dead, it is fourth in line. In my experience, half the backlog items look obviously unnecessary six months later, which is its own lesson: urgency fades, and the backlog is where you find out which ideas had substance.
If a website rebuild is on your list, by the way, read Why Your Website Produces No Leads before you brief any vendor. Half the rebuilds I see were solving the wrong problem, and that diagnosis belongs in the goal one-pager, not in month three of the project.
The takeaway
This week, while the year is still quiet:
- Write down every digital ambition you are carrying. Empty your head completely.
- Choose at most three. Each must have a rupiah number attached, even a rough one.
- For each: one named owner, one uncomfortable date, one observable definition of done, all on a single page.
- Put everything else in a backlog document.
- Book four quarterly review meetings in the calendar now, with the owners invited, before the year fills up.
That last step is the difference between a plan and a wish. A meeting in the calendar with real people in it is a commitment. A note in your notebook is a hope. Choose the commitment.