smart-goals

What Are SMART Goals And Why They Matter In Business

A SMART goal is any goal with a carefully planned, concise, and trackable objective. To be such a goal needs to be specific, measurable, achievable, relevant, and time-based. Bringing structure and trackability to goal setting increases the chances goals will be achieved, and it helps align the organization around those goals.

Understanding SMART goals

“SMART” is an acronym which explains how a goal might be achieved. Here is a more detailed look at each letter in the SMART acronym.

S – Specific

When considering the goal, it helps to be as specific as possible. Many individuals and businesses set goals with arbitrary dollar amounts, such as becoming a millionaire or generation 10 million dollars in revenue. If the goal is to make a certain amount of money, a more specific objective may be to make $40,000 per month for the next 5 years by selling 2500 units of a new software product.

Here, it helps to ask questions. What is it, in exact terms, that an individual or business hopes to achieve? Where, how, and when will this occur? What are the reasons for setting the goal in the first instance?

M – Measurable

Measurable goals have metrics that are used to gauge progress. This is particularly important for large and complex goals that must be broken down into smaller steps. Measurable goals also let the individual or business know that they have reached the finished line.

A- Achievable

Goals must be realistically achievable, otherwise, the temptation may be to give up on achieving them entirely. Businesses should set goals that their employees could reasonably expect to see through – given the materials and resources at hand. It’s also important to identify any short or long term impediments that may divert these resources.

R – Relevant

Relevance means that individuals and businesses set goals that are aligned with their values and long-term objectives. There is no point setting goals for the sake of it – so ensure that the reasons for conceiving a goal are aligned with broader strategies and company culture.

T – Time-based

Goals by their very definition need a deadline, particularly in business settings. Time-based goals are also important in tracking progress and setting milestones. For example, a business wanting to double its revenue in 6 months would hope to increase revenue by 50% after the 3-month mark.

Some common mistakes when setting SMART goals

Vagueness

Clarity is key when setting SMART goals. A marketing department might not know where to start when presented with the goal of selling 5000 cars in the next 4 years. However, the more specific goal of selling 5000 small cars in Italy by the end of 2025 gives them something to work with.

No KPIs

If the goal is to improve customer service, then there must be a customer service KPI with which to gauge progress. Many businesses make the mistake of setting goals that simply can’t be measured. Here, quantitative or industry research is key.

Unattainability

If a business is particularly successful, it is easy to get carried away with goal setting. An ambitious goal of selling 1 million pairs of shoes in the next 5 years is daunting and maybe unattainable without the required due diligence. In this case, smaller goals of selling 20,000 pairs every 3 months may be more suitable.

Key takeaways:

  • SMART goals are those that are carefully planned against certain criteria to increase the chances of them being accomplished.
  • SMART goals are specific, measurable, achievable, relevant, and time-based.
  • Some common mistakes when setting SMART goals include those not backed by reliable KPIs or those that are simply unattainable in the recommended timeframe.

SMART Goals vs. OKR

what-is-okr
Andy Grove, helped Intel become among the most valuable companies by 1997. In his years at Intel, he conceived a management and goal-setting system, called OKR, standing for “objectives and key results.” Venture capitalist and early investor in Google, John Doerr, systematized in the book “Measure What Matters.”

SMART goals and OKR are very similar tools, however, SMART goals are used more for personal development. Where instead OKR is a goal-setting system primarily thought for teams. So how to enable large organizations to achieve their goals at scale.

Therefore, while in terms of mindset SMART and OKR are similar. SMART goals usually are used more by solopreneurs, where OKR are used by startups and larger organizations.

SMART Goals vs. OKR vs. MBOs

mbo-vs-okr

Management by Objectives or MBO is a strategic management tool whose core principle is to define organizational objectives to align management with employees clearly. OKR is an evolution, as it breaks the silos and makes the shared objectives transparent to the whole company.

And those same objectives are aggressive and aspirational. SMART Goals can be used in the direction of OKRs but more at a personal level or at a smaller scale.

OKR and 10x thinking

OKR has been a system widely used in companies like Google to help scale up, while still aligning the company around so-called moonshots. Or small and larger bets that can make the company breakthrough in various verticals.

As OKR is by nature aggressive and aspirational, it fits well with the 10x thinking mindset.

moonshot-thinking
Moonshot thinking is an approach to innovation, and it can be applied to business or any other discipline where you target at least 10X goals. That shifts the mindset, and it empowers a team of people to look for unconventional solutions, thus starting from first principles, by leveraging on fast-paced experimentation.

Connected Agile Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.

Related reousrces:

Handpicked business resources:

Scroll to Top
FourWeekMBA