SMART Goals: Why 80% Are Set Wrong (And How to Do It Right)

SMART Goals: Why 80% Are Set Wrong

"We want to improve conversion rate." "The product should become more user-friendly." "We need more leads."

Do these goals sound familiar? They're all not SMART - and that's why they probably won't be achieved.

The SMART framework is over 40 years old and widely known. Yet most teams set their goals incorrectly. In this guide, we'll show you why and how to do it better.

Table of Contents

1. What Are SMART Goals?
2. The 5 Components in Detail
3. The Most Common Mistakes
4. SMART Goals for Tech Projects
5. SMART vs. OKRs
6. Templates and Examples
7. Implementation in Teams
8. FAQ

---

What Are SMART Goals?

SMART is an acronym for the 5 criteria a good goal should meet:

Letter	Meaning	Description
S	Specific	Clearly and precisely defined
M	Measurable	Quantifiable with metrics
A	Achievable	Realistically attainable
R	Relevant	Contributing to higher-level goals
T	Time-bound	With a clear deadline

The History

The concept was introduced in 1981 by George T. Doran. Since then, it's become the standard for goal-setting in business, project management, and personal development.

Why SMART Works

Psychological research shows:

• Specific goals lead to better performance than vague goals
• Measurable goals enable feedback and adjustment
• Achievable goals prevent demotivation
• Relevant goals create intrinsic motivation
• Time-bound goals prevent procrastination

---

The 5 Components in Detail

S - Specific

What it means: The goal is clear, unambiguous, and detailed.

Questions to verify:

• What exactly do we want to achieve?
• Who is involved?
• Where does it take place?
• What resources are needed?

Bad: "We want more traffic."

Good: "We want to increase organic blog traffic by 50% by publishing 12 SEO-optimized articles per month."

M - Measurable

What it means: Progress and success are quantifiable.

Questions to verify:

• How will we know we've achieved the goal?
• What metric are we using?
• How do we measure progress?

Bad: "The app should be faster."

Good: "Average app load time should be reduced from 3.2s to under 1.5s."

Important: Also define how you measure. "1.5s measured with Lighthouse on a Pixel 6" is better than just "1.5s."

A - Achievable

What it means: The goal is realistically achievable with available resources.

Questions to verify:

• Do we have the necessary skills?
• Do we have the required resources?
• Is it doable in the time frame?
• What could stop us?

Bad: "We'll become market leader in 6 months" (at 1% market share)

Good: "We'll increase our market share from 1% to 3% in 12 months."

Finding balance: The goal should be challenging but achievable. Too easy doesn't motivate, too hard demotivates.

R - Relevant

What it means: The goal contributes to higher-level objectives and is worth pursuing.

Questions to verify:

• Why is this goal important?
• Does it fit our strategy?
• Is now the right time?
• Who benefits?

Bad: "We'll implement machine learning" (without clear business case)

Good: "We'll implement ML-based recommendations to increase average cart value by 15%."

Important: A goal can be SMART yet irrelevant. Relevance connects goals to the bigger picture.

T - Time-bound

What it means: The goal has a clear deadline.

Questions to verify:

• By when should the goal be achieved?
• Are there milestones?
• What happens after the deadline?

Bad: "We'll improve conversion rate."

Good: "We'll increase conversion rate from 2.1% to 3.5% by March 31, 2026."

Tip: Also set intermediate goals. "2.5% by end of January, 3.0% by end of February, 3.5% by end of March."

---

The Most Common Mistakes

Mistake 1: Too Vague

Problem: "We want to improve customer satisfaction."

What's missing: How much? How measured? By when?

Better: "We'll increase NPS from 32 to 50 by Q3 2026."

Mistake 2: Not Measurable

Problem: "The app should become more intuitive."

What's missing: How do we measure "intuitive"?

Better: "Task completion rate for core features should increase from 68% to 90%."

Mistake 3: Unrealistic

Problem: "We'll double revenue in 3 months" (without new resources)

What's missing: Reality check

Better: "We'll increase revenue by 20% in 3 months by optimizing the funnel."

Mistake 4: Not Relevant

Problem: Team optimizes metrics nobody cares about.

Symptoms:

• "Why are we doing this anyway?"
• Goal achieved, but no impact
• Stakeholders not interested

Solution: Always ask: "What's the business goal behind this?"

Mistake 5: No Deadline

Problem: "We'll implement this eventually."

Result: Procrastination, never finished

Solution: Every goal needs a date. No date = No commitment.

Mistake 6: Output Instead of Outcome

Problem: "We'll write 20 blog articles."

What's missing: The outcome. What should this achieve?

Better: "We'll generate 500 qualified leads through 20 blog articles by Q2."

Mistake 7: Too Many Goals

Problem: 15 SMART goals per quarter.

Result: None are achieved properly.

Solution: Maximum 3-5 core goals per quarter. Focus beats breadth.

---

SMART Goals for Tech Projects

Examples for Different Areas

Performance:

• "Reduce API response time for /users endpoint from 450ms to under 100ms (P95) by Feb 15, 2026"
• "Reduce bundle size from 2.4MB to under 500KB by end of Q1"
• "Increase Lighthouse Performance Score from 62 to 90+ by release"

Quality:

• "Increase test coverage from 45% to 80% for critical paths by Feb 28, 2026"
• "Zero critical bugs in production for 30 days after release"
• "Reduce code review turnaround time from 48h to under 8h by month-end"

User Experience:

• "Increase sign-up completion rate from 34% to 65% by end of Q1"
• "Increase average session duration from 2:30 to 5:00 minutes by March"
• "Reduce Customer Effort Score (CES) from 4.2 to under 2.5 by Q2"

DevOps:

• "Increase deployment frequency from 1x/week to 3x/day by end of Q2"
• "Reduce Mean Time to Recovery (MTTR) from 4h to under 30min by June"
• "Reduce change failure rate from 15% to under 5% by Q3"

Team:

• "Reduce sprint velocity variance from ±40% to ±15% within 3 sprints"
• "Each team member holds 1 knowledge-sharing session per month starting Q2"
• "Reduce unplanned work rate from 35% to under 15% by end of Q1"

The Anti-Pattern: Feature as Goal

Bad: "We'll implement the new checkout by March."

Why bad: That's an output, not an outcome. What's the actual goal?

Better: "We'll reduce checkout abandonment rate from 68% to 45% by March through implementing a new checkout flow."

---

SMART vs. OKRs

What Are OKRs?

OKRs (Objectives and Key Results) are an alternative framework:

• Objective: Qualitative, inspiring goal
• Key Results: Measurable results that achieve the Objective

Comparison

Aspect	SMART	OKRs
Focus	Individual goals	Hierarchy of goals
Inspiration	Functional	Motivating + Functional
Time period	Flexible	Usually quarterly
Achievability	100% achievable	70% = Success
Connection	Standalone	Cascading (Company → Team → Individual)

When to Use What?

SMART is good for:

• Project-based goals
• Personal development
• Operational metrics
• Teams new to goal-setting

OKRs are good for:

• Strategic company goals
• Cross-functional initiatives
• Ambitious "moonshot" goals
• Larger organizations

Combination

Many teams use both:

• OKRs for strategic quarterly/annual goals
• SMART for operational project goals within OKRs

---

Templates and Examples

SMART Goal Template

GOAL: [What exactly do we want to achieve?]

S - Specific:
[Detailed description of the goal]
Who: [Participants]
What: [Concrete result]
Where: [Context/area]

M - Measurable:
Metric: [Which KPI?]
Current state: [Baseline]
Target: [End value]
Measurement method: [How do we measure?]

A - Achievable:
Resources: [What do we need?]
Skills: [Do we have the competence?]
Risks: [What could go wrong?]

R - Relevant:
Company goal: [Which higher-level goal does it support?]
Impact: [Why is it important?]

T - Time-bound:
Deadline: [Date]
Milestones:
- [Milestone 1]: [Date]
- [Milestone 2]: [Date]
- [Milestone 3]: [Date]

---

Implementation in Teams

Step 1: Create Context

Before setting goals:

• What are the company goals?
• What is the team mission?
• What were past learnings?

Step 2: Define Together

Goals that come from above are rarely achieved.

Better:

1. Leadership provides direction
2. Team proposes concrete goals
3. Joint refinement
4. Commitment from all

Step 3: Document

Goals belong in systems, not heads:

• JIRA/Confluence
• Notion
• Monday.com
• Simple spreadsheet

Important: Visible to all and regularly referenced.

Step 4: Review Regularly

Weekly: Are we on track? Monthly: Adjustment needed? Quarterly: Goals achieved? New goals?

Step 5: Celebrate or Learn

• Goal achieved: Celebrate, recognition, documentation
• Goal missed: Retrospective, learnings, no blame

---

Conclusion

SMART goals are easy to understand but hard to implement correctly. Most teams fail due to vagueness, lack of measurability, or unrealistic expectations.

The key: Take time for definition. A well-formulated SMART goal is half the work. And don't forget the most important letter: R for Relevant. A goal can be perfectly SMART and still be pointless.

At Balane Tech, we help teams lead their digital projects to success with clear, measurable goals. Contact us for more information.

---

FAQ

How many SMART goals should a team have?

Maximum 3-5 per quarter. Focus is more important than breadth. With more goals, all are achieved mediocrely.

What if the goal changes during the project?

That's normal. Adjust the goal, but document why. Transparent adjustment is better than stubbornly sticking to irrelevant goals.

Are SMART goals also suitable for personal development?

Yes, very much so. "I'll get better at Python" → "By June 30, I'll complete a Python project with 3 API integrations and achieve 80% test coverage."

What's the difference between SMART and KPIs?

KPIs are metrics you continuously track. SMART goals are time-bound changes to these metrics. "Conversion rate" is a KPI. "Conversion rate from 2% to 4% by Q3" is a SMART goal.

Does SMART work for creative work?

Yes, but focus on measurable outputs or outcomes. Not "more creative design," but "design achieves 80% positive ratings in user tests."

What if the goal isn't measurable?

Then it's not a good goal. Ask: "How would we know we succeeded?" The answer is your metric.