lockes-goal-setting-theory

Locke’s goal-setting theory of motivation

The theory was developed by psychologist Edwin Locke who also has a background in motivation and leadership research. Locke’s goal-setting theory of motivation provides a framework for setting effective and motivating goals. Locke was able to demonstrate that goal setting was linked to performance.

Understanding Locke’s goal-setting theory of motivation

When an individual set challenging goals and received feedback on their progress, productivity and motivation increased. Locke also discovered that high performance was reliant on goals being specific. Indeed, the setting of more simple, general, or vague goals decreased motivation.

To guide goal-setting, Locke created five principles. In the next section, we will take a look at each.

The five principles of goal setting

  1. Clarity. Motivating goals are clear and concise goals. A lack of clarity means ambiguity which makes goals harder to understand. Most individuals utilize the SMART system of specific, measurable, achievable, relevant, and time-bound goal setting.
  2. Challenge. Defining the right level of challenge is a balancing act. Goals must be challenging enough that reaching them feels like a genuine achievement. However, they must not be so challenging that the individual becomes daunted at the prospect of achieving them and quits.
  3. Commitment. This can be created by sharing the goal with someone else to increase accountability. Employee commitment can also be increased through early buy-in where rewards are offered for hitting milestones. Visualization of the benefits of achieving the goal can also foster commitment.
  4. Feedback. As we noted earlier, feedback is critical to Locke’s goal-setting theory. Both positive and negative feedback should be received regularly. To this end, periodic meetings should be scheduled to monitor progress and provide guidance where necessary.
  5. Task-complexity. Ensure that the task is as uncomplicated as possible. If this is not feasible, then complex goals should be broken down into smaller parts. It is also important that individuals be realistic and give themselves enough time to learn complex concepts. 

Advantages and disadvantages of Locke’s goal-setting theory of motivation

Advantages

  • Task prioritization. Employees who have mastered the skill of effective goal setting spend time on the most important tasks first. Employees who do not squander time on meaningless tasks drive the business forward with purpose and momentum.
  • Self-awareness. Since Locke’s model advocates continuous constructive feedback, the individual receives important insights on their particular strengths and weaknesses. 
  • Direction. Meaningful goal setting involves creating a plan for the future. Without direction, the individual or the business has no clear idea of what constitutes success.

Disadvantages

  • Time-consuming and expensive. Some goals require a high degree of planning to ensure that the level of challenge and complexity is demanding, but not too demanding. Some businesses will inevitably choose to set simpler, more general goals instead.
  • Performance pressure. Irrespective of whether a goal is achievable, some employees will not be able to perform under pressure. Conversely, others may become so obsessed with high performance that they develop tunnel vision. They may miss new opportunities or fail to identify threats ahead of time.

Key takeaways

  • Locke’s goal-setting theory of motivation explains how individuals can set meaningful goals and be motivated enough to achieve them.
  • Locke’s goal-setting theory of motivation demonstrates that specific goal setting is related to high performance. Conversely, non-specific goal setting is related to low performance.
  • Locke’s goal-setting theory of motivation allows employees to prioritize tasks and increase self-awareness. However, some businesses will not be prepared to spend money ensuring that goals have the right mix of ingredients.

Connected Business Frameworks and Concepts

Agile Leadership

agile-leadership
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles. 

Adaptive Leadership

adaptive-leadership
Adaptive leadership is a model used by leaders to help individuals adapt to complex or rapidly changing environments. Adaptive leadership is defined by three core components (precious or expendable, experimentation and smart risks, disciplined assessment). Growth occurs when an organization discards ineffective ways of operating. Then, active leaders implement new initiatives and monitor their impact.

Delegative Leadership

delegative-leadership
Developed by business consultants Kenneth Blanchard and Paul Hersey in the 1960s, delegative leadership is a leadership style where authority figures empower subordinates to exercise autonomy. For this reason, it is also called laissez-faire leadership. In some cases, this type of leadership can lead to increases in work quality and decision-making. In a few other cases, this type of leadership needs to be balanced out to prevent a lack of direction and cohesiveness of the team.

Distributed Leadership

distributed-leadership
Distributed leadership is based on the premise that leadership responsibilities and accountability are shared by those with the relevant skills or expertise so that the shared responsibility and accountability of multiple individuals within a workplace, bulds up as a fluid and emergent property (not controlled or held by one individual). Distributed leadership is based on eight hallmarks, or principles: shared responsibility, shared power, synergy, leadership capacity, organizational learning, equitable and ethical climate, democratic and investigative culture, and macro-community engagement.

Micromanagement

micromanagement
Micromanagement is about tightly controlling or observing employees’ work. Although in some cases, this management style might be understood, especially for small-scale projects, generally speaking, micromanagement has a negative connotation mainly because it shows a lack of trust and freedom in the workplace, which leads to adverse outcomes.

Maslow’s Hierarchy of Needs

maslows-hierarchy-of-needs
Maslow’s Hierarchy of Needs was developed by American psychologist Abraham Maslow. His hierarchy, often depicted in the shape of a pyramid, helped explain his research on basic human needs and desires. In marketing, the hierarchy (and its basis in psychology) can be used to market to specific groups of people based on their similarly specific needs, desires, and resultant actions.

Eisenhower Matrix

eisenhower-matrix
The Eisenhower Matrix is a tool that helps businesses prioritize tasks based on their urgency and importance, named after Dwight D. Eisenhower, President of the United States from 1953 to 1961, the matrix helps businesses and individuals differentiate between the urgent and important to prevent urgent things (seemingly useful in the short-term) cannibalize important things (critical for long-term success).

Moonshot Thinking

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.

Lightning Decision Jam

lockes-goal-setting-theory
The theory was developed by psychologist Edwin Locke who also has a background in motivation and leadership research. Locke’s goal-setting theory of motivation provides a framework for setting effective and motivating goals. Locke was able to demonstrate that goal setting was linked to performance.

Herzberg’s Two-Factor Theory

herzbergs-two-factor-theory
Herzberg’s two-factor theory argues that certain workplace factors cause job satisfaction while others cause job dissatisfaction. The theory was developed by American psychologist and business management analyst Frederick Herzberg. Until his death in 2000, Herzberg was widely regarded as a pioneering thinker in motivational theory.

Lessons Learned

lessons-learned
The term lessons learned refers to the various experiences project team members have while participating in a project. Lessons are shared in a review session which usually occurs once the project has been completed, with any improvements or best practices incorporated into subsequent projects. 

Growth Engineering

growth-engineering
Growth engineering is a systematic, technical approach to the improvement of conversion and the user experience. Combined with business engineering it helps business people build valuable companies from scratch.

Retrospective Analysis

retrospective-analysis
Retrospective analyses are held after a project to determine what worked well and what did not. They are also conducted at the end of an iteration in Agile project management. Agile practitioners call these meetings retrospectives or retros. They are an effective way to check the pulse of a project team, reflect on the work performed to date, and reach a consensus on how to tackle the next sprint cycle.

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.”

Cog’s Ladder

cogs-ladder
Cog’s ladder is a model of group development. The ladder was created in 1972 by Procter & Gamble employee George Charrier to help management at the company understand how teams worked to make them more efficient. Cog’s ladder is a model of group formation and behavior that is used to help businesses understand how a team can work to achieve its goals.

GRPI Model

grow-model
The GRPI model was created by American organizational theorist Richard Beckhard in 1972. Although the model is almost 50 years old, its simplicity and effectiveness mean it is still in use today. The GRPI model is a tool used by leaders to diagnose the cause of team dysfunction and increase productivity, quality, and efficiency through four key dimensions that cause conflict: goals, roles, processes, and interactions. 

High-Performance Coaching

high-performance-coaching
High-performance coaches work with individuals in personal and professional contexts to enable them to reach their full potential. While these sorts of coaches are commonly associated with sports, it should be noted that the act of coaching is a specific type of behavior that is also useful in business and leadership. 

OSKAR Coaching

oskar-coaching-model
The OSKAR coaching model was developed in the early 2000s by organizational theorists and authors Paul Z. Jackson and Mark McKergow.  The OSKAR coaching model is a solution-driven method used for managerial coaching in the workplace. In their book titled The Solutions Focus: Making Coaching and Change Simple, the pair layout a framework to help coaches implement training sessions that are focused on solutions and not on problems.

Training of Trainers

training-of-trainers-model-tot
The training of trainers model seeks to engage master instructors in coaching new, less experienced instructors with a particular topic or skill. The training of trainers (ToT) model is a framework used by master instructors to train new instructors, enabling them to subsequently train other people in their organization.

GROW Model

grow-model
Though no single individual can claim to have created the GROW model, writers Graham Alexander and Alan Fine together with racing car champion John Whitmore played a significant part in developing the framework during the 80s and 90s. The GROW model is a simple way to set goals and solve problems during coaching sessions through four stages: goal, reality, options, and will (way forward).

Ulrich Model

ulrich-model
The Ulrich model helps large or complex organizations with many business units organize their human resource function. The Ulrich model was named for management coach David Ulrich after the release of his 1996 book Human Resource Champions: The Next Agenda for Adding Value and Delivering Results.

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.

Read Next: Mental ModelsBiasesBounded RationalityMandela EffectDunning-Kruger EffectLindy EffectCrowding Out EffectBandwagon EffectDecision-Making Matrix.

Related Strategy Concepts: Go-To-Market StrategyMarketing StrategyBusiness ModelsTech Business ModelsJobs-To-Be DoneDesign ThinkingLean Startup CanvasValue ChainValue Proposition CanvasBalanced ScorecardBusiness Model CanvasSWOT AnalysisGrowth HackingBundlingUnbundlingBootstrappingVenture CapitalPorter’s Five ForcesPorter’s Generic StrategiesPorter’s Five ForcesPESTEL AnalysisSWOTPorter’s Diamond ModelAnsoffTechnology Adoption CurveTOWSSOARBalanced ScorecardOKRAgile MethodologyValue PropositionVTDF FrameworkBCG MatrixGE McKinsey MatrixKotter’s 8-Step Change Model.

Main Guides:

About The Author

Scroll to Top
FourWeekMBA