9 types of goals for high-performing teams

Setting a goal sounds simple. Picking the right type of goal is where most teams go wrong.

The structure of a goal shapes how a team pursues it, measures it, and ultimately whether they hit it. A goal framed around outcomes behaves differently from one framed around process.

Using the wrong structure makes goals harder to achieve and even harder to define and know whether you're on track. Your overall strategic planning vision must gel with the types of goals you want to use.

This article breaks down nine types of goals, when each one is most useful, and how to use them together so your team always knows what they're working toward and why it matters.

What are business goals?

A business goal defines where a team is headed and when they want to get there. Good goals do three things: they focus effort, guide decisions, and give teams a shared understanding of what success looks like.

Without clear goals, teams work hard but not necessarily in the same direction. With the right goals, even complex cross-functional work stays aligned, because everyone is measuring progress against the same target.

The key is not just setting goals, but setting the right type of goal for the situation. Here are nine types that cover the full range of what teams need.

9 types of business goals to empower your team

Not all goals work the same way. Some define direction, others drive daily execution. These nine types of goals cover the full range—and most teams will use several of them at once:

1. Long-term goals

Long-term goals define the big picture. They describe where a team, department, or company wants to be in one, three, or five years. They're directional rather than prescriptive.

This type of goal gives everyone a north star without specifying every step to get there. Some use annual plan one-pager templates to prepare long-term outcomes in a succinct single document.

When to use them: Any time a team needs a shared destination to orient more granular planning around. Long-term goals answer the question: "What are we ultimately trying to achieve?"

Example: Become the market leader in business productivity software within three years.

2. Short-term goals

Short-term goals break a long-term goal into achievable milestones. They're scoped to a defined period, typically a month or a quarter, and specific enough to measure.

A stack of well-designed short-term goals is essentially a roadmap to a long-term one.

When to use them: To translate ambition into action. Short-term goals keep teams moving without losing sight of the larger destination.

Example: Increase customer satisfaction scores by 10 points in Q2 as part of a broader effort to reach market leadership.

3. Performance-based goals

Performance-based goals focus on specific outputs or behaviors over a defined period. They're often tied to individual or team responsibilities and are designed to be clearly measurable at the end of the cycle.

When to use them: When you need accountability at the task or role level. Performance goals make it clear what each person or team is responsible for delivering.

Example: Reduce average customer support response time to under four hours by end of quarter.

4. Quantitative goals

Quantitative goals are measured by numbers. They answer "How much?" or "How many?" and leave no ambiguity about whether they've been achieved.

They're especially useful when objective measurement matters: tracking growth, usage, revenue, or efficiency.

When to use them: When success needs to be unambiguous. If two people could disagree about whether a goal was hit, it probably needs to be quantitative.

Example: Increase monthly active users by 20% over the next two quarters.

5. Qualitative goals

Qualitative goals measure things that can't easily be reduced to a number: brand perception, team culture, user experience, or the quality of a creative output.

They require more judgment to evaluate, but they capture dimensions of success that quantitative goals miss.

When to use them: When what matters most is hard to count. Qualitative goals are often used alongside quantitative ones to give a fuller picture of progress.

Example: Customers describe our redesigned product as easier to use and more intuitive than the previous version.

6. Outcome-oriented goals

Outcome goals define the end result you want to achieve, without specifying how to get there. This gives teams flexibility to find the best path while staying aligned on what success actually looks like.

When to use them: When the result matters more than the method. Outcome goals work well for teams with the autonomy and expertise to determine their own approach.

Example: Launch a redesigned product website by the end of Q1 that reduces bounce rate by 15%.

7. Process-oriented goals

Process goals define the behaviors or activities a team will consistently follow, rather than the end result. The logic is straightforward: repeatable, well-designed processes reliably produce good outcomes.

Focusing on the process is a durable way to improve results over time.

When to use them: When consistent execution matters more than any single outcome, or when you're building habits and practices that compound over time.

Example: Hold weekly cross-functional standups with the website team and complete design reviews on a two-week sprint cycle.

8. OKRs (Objectives and Key Results)

OKRs pair a qualitative objective (where you're going) with measurable key results (how you'll know you've arrived). The objective is inspiring and directional. The key results are specific, time-bound, and set at a level that requires real effort.

OKRs work best when they cascade: company OKRs inform team OKRs, which inform individual OKRs.

When to use them: When a team needs to connect ambitious direction with concrete accountability, especially in fast-moving or cross-functional environments.

Example objective: Build a product experience customers recommend without being asked.

Key results: Achieve a Net Promoter Score of 45+; reduce time-to-value for new users to under 10 minutes; reach 80% feature adoption for core workflows within 90 days of launch.

9. SMART goals

SMART is a framework for making any goal more actionable: Specific, Measurable, Achievable, Relevant, and Time-bound. It's not a standalone goal type—it's a quality check you apply to whatever goal type you're setting.

A SMART goal isn't just a wish with a deadline. It's a commitment with a clear definition of success built in.

When to use them: As a filter for any goal before it's finalized. If a goal can't pass the SMART test, it's not ready to be worked toward.

Example: Increase newsletter open rate from 22% to 30% by the end of Q3 by testing three subject line formats across five sends per month.

How to choose the right type of goal

Most teams don't need to choose just one type. The most effective goal structures layer multiple types together.

A long-term goal provides direction. Short-term goals create milestones. Performance-based goals assign accountability. OKRs connect the two. SMART criteria make all of them more actionable.

A few questions to help you pick:

• Are you defining direction or tracking execution? Long-term and outcome goals define direction. Short-term, performance, and process goals track execution.

• Do you need objective measurement? Use quantitative goals. Need to capture something harder to measure? Add qualitative goals alongside them.

• Does your team need autonomy or structure? Outcome goals give teams flexibility. Process goals give them a reliable playbook.

• Are you connecting individual work to company strategy? OKRs are built for this.

The goal type you choose signals what your team should pay attention to. Get it right and progress becomes visible. Get it wrong and people work hard in directions that don't add up.

How Jira and Confluence help teams set and track goals

Goal-setting only works if it stays visible. When goals live in a document no one opens or a spreadsheet that falls out of date, they stop influencing how work gets done.

Confluence gives teams a shared space to document goals, track progress, and connect strategy to execution. The OKR template and goal-tracking pages keep everyone aligned on what's being worked toward and how it's going.

Jira makes the connection between goals and day-to-day work explicit. Teams can link issues and epics directly to strategic objectives, so it's always clear how individual tasks contribute to bigger targets.

Progress on goals becomes something you see as work moves, not something you calculate manually at the end of the quarter.

Try Confluence free or try Jira free and give your team one place to set, track, and hit their goals.

Frequently asked questions

Should a team use just one type of goal or several at once?

Several at once. A long-term goal sets direction. Short-term goals create checkpoints. OKRs connect individual work to strategy. The types are designed to layer, not compete.

What's the difference between outcome goals and process goals?

Outcome goals define the end result. Process goals define the behaviors that get you there. Use outcome goals to set the destination and process goals to build the habits that make hitting it repeatable.

When should a team use OKRs instead of standard goals?

When you need to connect ambitious direction to measurable accountability. OKRs work especially well for cross-functional teams or fast-moving environments where priorities shift and alignment is hard to maintain.

How do you know if a goal is too easy or too hard?

Too easy: your team hits it without changing anything. Too hard: people disengage before the halfway mark. The right goal requires genuine effort and stays within reach. If you're consistently hitting 100%, raise the bar.