Goal Setting Software: Connecting Targets to the Daily Board

The quarter started with five goals written clearly enough that everyone nodded. Ten weeks later the document has not been opened since week two, two of the goals no longer describe what the team is working on, and the status is whatever the person presenting says it is. Nothing was mismanaged. The goals simply lived somewhere the team never goes, while the work lived on a board that changes every day.

That gap is what goal setting software is sold to close. Some of it does. Most of the difference between a tool that helps and a tool that becomes another abandoned tab is not in the feature list, it is in where the goal sits relative to the work and how its number gets updated.

What the software is actually being asked to do

Strip the category down and there are three separate jobs, and tools are good at different ones.

The first is holding the statement. A goal needs a name, an owner, a period, and a target that can be judged true or false at the end. This is the easy part. A shared document does it.

The second is holding the number. Somebody has to say where the goal stands now, and that has to be updatable more often than once a quarter without a meeting. This is where documents start to fail, because a number in a document has no history, so nobody can see whether progress is flat or moving.

The third is the connection to work. A goal is a claim that certain work will produce a certain result. If the tasks are in one system and the goal is in another, the connection is a human habit rather than a link, and habits decay under deadline pressure.

Most teams buy for the first job, get frustrated by the second, and needed the third. That is worth knowing before comparing prices, because the tools cluster by which job they were built for.

Two shapes of tool, and what each costs

Broadly there are dedicated goal and OKR platforms, and there are goals built into a tool where the team already tracks work. The second group puts the goal next to the tasks. The first group offers more structure around the goal itself, including strategy maps, weighting, and check-in cadence.

Tool	Where goals sit	Plan that includes goals
Perdoo	Dedicated OKR platform	Free for up to 5 users, Premium at 6.40 EUR per user per month, Supreme at 8.00 EUR
Asana	Inside the work tool	Goals listed on the Advanced plan, 24.99 USD per user per month billed annually, 30.49 USD monthly
ClickUp	Inside the work tool	Goals and Portfolio Management listed on the Unlimited plan, 7 USD per user per month billed yearly, 10 USD monthly
monday.com	Inside the work tool	Free plan covers up to 2 seats and 3 boards, goal tracking built from board columns on paid seats
Notion	Built by the team	Free plan is unlimited for one person, block limits apply once a workspace has several members

Two things in that table matter more than the numbers. Dedicated platforms often price view only access separately, which is how the whole company can read goals without a full seat each. Perdoo lists view only licences at 1.50 EUR per month, for example. Work tools usually put goals on a middle or upper plan, which means the real cost of goal tracking is the difference between the plan you are on and the plan that has them.

The second thing is that a dedicated platform adds a system to keep in sync. The goals live there, the work lives elsewhere, and somebody maintains the relationship between them. For a team of five that is often a worse trade than a simpler goal held next to the tasks.

How the number gets updated is the whole decision

There are only three ways a goal's current value can change, and choosing between them determines whether the system survives the quarter.

A person types it in

Someone checks in weekly with a number and a sentence. Honest, cheap, and it works as long as the check-in is attached to something that already happens, such as a weekly review. The failure mode is silence: nothing forces the update, so the goal shows last month's figure while everyone assumes it is current.

It rolls up from the work

The tool calculates progress from the tasks or cards beneath the goal. This never goes stale, because moving a card moves the goal. The catch is that it measures activity rather than outcome. Ten of twelve tasks done says nothing about whether the result arrived, and a goal that reads 83 percent while the outcome has not moved is worse than no number at all.

It comes from a system of record

The number is pulled from analytics, billing, or a database, so it is the real figure. The best option where it exists, and it only exists for goals that a system already counts. Revenue and signups qualify. Quality of onboarding does not.

Mixed use is normal and sensible. Outcome goals take the measured number. Delivery goals roll up from the board. The mistake is rolling up task completion and calling it an outcome, because the reporting then looks healthy right up to the end of the quarter.

Write the target so the tool can hold it

None of the three update paths work if the goal is phrased so that no value fits in the field. Improve client communication cannot be typed into a number box, so it will sit at zero all quarter and then be marked green by whoever is presenting. Rewriting it as a countable version, such as every active project sends a status note each week, makes the update trivial and turns the software into a place that records facts instead of opinions.

The practical rule is to decide the unit before choosing the tool. If the unit is a count, almost anything with a number field works. If the unit is a percentage of a moving denominator, check that the tool stores both numbers rather than the ratio, because a ratio alone hides whether the top or the bottom changed.

Why goals go stale in week three

The pattern repeats across teams and tools, and it has recognisable causes.

Too many goals is the first. Five goals for a team of five is already one per person with no slack. When there are twelve, the list becomes a catalogue nobody reads, and the response to a busy week is to update none of them.

The second is a missing owner. A goal owned by the team is owned by nobody. Someone specific has to be the person who reports the number, even when the work is shared.

The third is distance. If the goal is in a tool the team opens once a quarter, it is out of sight during every decision it was meant to influence. This is the argument for keeping goals where the work is visible, or at least mirroring them there. A pinned card at the top of the board with the quarter's targets, updated weekly, beats a well structured system in an application nobody has open.

The fourth is that nothing happens when a goal is off track. If a red goal produces no decision, the status is decoration. The point of a number is to trigger a conversation earlier than the deadline would. Teams that get value from goal software usually have one standing slot where off track items are discussed and something is actually cut or moved.

What to check before paying per seat

A short list of questions that decide the real cost.

Does everyone need a full seat? Executives and stakeholders usually only read. Tools that price viewers separately, or do not count view only guests, change the arithmetic for a small company considerably.

Is goal tracking on the plan you are already on? Upgrading an entire team to reach a goals feature is a large jump for one capability. Compare that with adding a custom field and a pinned card in the tool you already pay for.

Can the goal reference the work? A link from goal to project is the minimum. Being able to see, from the board, which goal a card serves is better, because that is the direction the question gets asked in during the week.

Can the history come out? Goals are most useful compared year over year. Check that check-in history exports, rather than living only in charts inside the product.

What happens at the end of the period? Some tools archive a closed goal with its final value and its check-in trail intact, and some simply let it roll on with a stale date. The archive is what makes the next planning session short, because last quarter's five goals with their outcomes are the best available evidence about how much a team of this size can actually move in twelve weeks.

How much structure is genuinely needed? Weighting, cascading levels and strategy maps earn their keep at organisational scale. For a small team they add administration, and the honest comparison is against a simpler setup described next. The comparison pages cover how the major work tools differ on the plan boundaries that matter here.

A setup that works without buying anything new

For teams under about ten people, the following holds up and takes an afternoon.

Create one board, or one list, for the quarter's goals. One card per goal, maximum five. Each card carries the owner, the target with its unit, the deadline, and a custom field for the current number. A tool with custom fields and a list view will do all of this, and the features overview is a fair checklist for whether yours can.

Add a comment to the card every week with the new number and one sentence of why it moved. The comment thread becomes the history, which is the part that documents lack. Link the projects or cards that are meant to move the goal, so the connection is visible from both directions.

Then put a recurring slot in the calendar where the five cards are read in order. Ten minutes. Any goal that has not been updated since the last slot gets updated on the spot or dropped. Dropping goals mid quarter is not failure, it is the mechanism that keeps the remaining ones credible.

If that routine survives two quarters, the case for dedicated software becomes clear on evidence: the specific thing the routine could not do. Buying first and hoping the routine follows is the order that usually fails.

What to change first

Cut the list to five goals, give each one a named owner, and put them on a card at the top of the board the team already opens every morning. Then hold one ten minute weekly slot where each number is said out loud. If the tool in use cannot hold a custom field, a comment history and a list view without an upgrade, Pinateca includes all three from the free plan for up to five people.

Q1. Is dedicated OKR software worth it for a team of five?

Rarely as a first step. At that size the binding constraint is the weekly habit of updating numbers, not the structure around the goals, and a dedicated platform adds a second system to keep in sync with the work. Run the routine in the tool you already use for a quarter, then buy against the specific gap that shows up.

Q2. Can goal progress be calculated automatically from tasks?

Several work tools do exactly that, rolling completion of child items up into a percentage. It is reliable and it measures activity rather than results, so it suits delivery goals and misleads on outcome goals. For anything where the outcome is a number a system already counts, take the number from that system instead.

Q3. How many goals should a small team run at once?

Three to five per quarter, with a single named owner each. More than that and the list stops being read, which removes the only thing that makes goals useful during the quarter. If a goal cannot be assigned to one person, it is usually two goals or a project.

Q4. What is the difference between goals in a work tool and a spreadsheet?

The spreadsheet holds the statement and the current number perfectly well. What it lacks is history that nobody has to maintain, notifications to the owner, and any link to the tasks meant to move the number. If goals are reviewed in a meeting where somebody reads the sheet aloud, a spreadsheet can be enough.

Q5. Do goals need to cascade from company level down to individuals?

Cascading helps when there are enough layers that team goals could otherwise conflict. Under roughly fifty people it mostly creates paperwork, since everyone can already see how the pieces fit. Start flat with a handful of shared goals and add levels only when two teams genuinely pull in different directions.