SMART criteria

From Infogalactic: the planetary knowledge core
(Redirected from SMART (project management))
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

SMART is a mnemonic acronym, giving criteria to guide in the setting of objectives, for example in project management, employee-performance management and personal development. The letters S and M usually mean specific and measurable. The other letters have meant different things to different authors, as described below. Additional letters have been added by some authors.

SMART criteria are commonly attributed to Peter Drucker's management by objectives concept.[1] The first-known use of the term occurs in the November 1981 issue of Management Review by George T. Doran.[2] The principal advantage of SMART objectives is that they are easier to understand and to know when they have been done.

History

The November 1981 issue of Management Review contained a paper by George T. Doran called There's a S.M.A.R.T. way to write management's goals and objectives.[2][3] It discussed the importance of objectives and the difficulty of setting them.

<templatestyles src="Template:Blockquote/styles.css" />

Ideally speaking, each corporate, department, and section objective should be:

  • Specific – target a specific area for improvement.
  • Measurable – quantify or at least suggest an indicator of progress.
  • Attainable – assuring that an end can be achieved.
  • Relevant – is the right goal at the right time for you.
  • Time-related – specify when the result(s) can be achieved.

Notice that these criteria don’t say that all objectives must be quantified on all levels of management. In certain situations it is not realistic to attempt quantification, particularly in staff middle-management positions. Practising managers and corporations can lose the benefit of a more abstract objective in order to gain quantification. It is the combination of the objective and its action plan that is really important. Therefore serious management should focus on these twins and not just the objective.

— George T. Doran, There's a S.M.A.R.T. way to write management's goals and objectives[2][3]

Other definitions

Each letter in SMART refers to a different criterion for judging objectives. Different sources use the letters to refer to different things. Typically accepted criteria are as follows.

Letter Most common Alternative
S Specific[4][5][6][7][8][9][10][11][12][13][14] (Strategic and specific)[15]
M Measurable[4][5][6][7][8][9][10][11][12][13][14][15] Meaningful
A Achievable[4][7][8][10][12][13] Agreed,[6][16] attainable,[11][15] action-oriented,[5] ambitious,[9] aligned with corporate goals,[17] (agreed, attainable and achievable)[14]
R Relevant[4][7][10][12][18] Realistic,[6][8][9][11][13][16] resourced,[18] reasonable,[5] (realistic and resourced),[14] results-based[15]
T Time-bound[4][7][8][9][14][15] Time-based,[10] time limited,[12] time/cost limited,[6] timely,[5] time-sensitive,[11] timeframe[13]

Choosing certain combinations of these labels can cause duplication, such as selecting 'attainable' and 'realistic', or can cause significant overlapping as in combining 'appropriate' and 'relevant'. The term 'agreed' is often used in management situations where buy-in from stakeholders is desirable (e.g. appraisal situations). The first column of terms provides an adequate starting structure.

Developing SMART goals

Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found. Paul J. Meyer describes the characteristics of S.M.A.R.T. goals in Attitude is Everything.[19]

Specific

The criterion stresses the need for a specific goal rather than a more general one. This means the goal is clear and unambiguous; without vagaries and platitudes. To make goals specific, they must tell a team exactly what's expected, why it's important, who’s involved, where it's going to happen, when it is going to happen and which attributes are important.

A specific goal will usually answer the six 'W' questions:

  • What: What do I want to accomplish?
  • Why: Specific reasons, purpose or benefits of accomplishing the goal.
  • Who: Who is involved?
  • Where: Identify a location.
  • When: Identify temporal requirements.
  • Which: Identify requirements and constraints.

Measurable

The second criterion stresses the need for concrete criteria for measuring progress toward the attainment of the goal. The thought behind this is that if a goal is not measurable it is not possible to know whether a team is making progress toward successful completion. Measuring progress is supposed to help a team stay on track, reach its target dates and experience the exhilaration of achievement that spurs it on to continued effort required to reach the ultimate goal.

A measurable goal will usually answer questions such as:

  • How much?
  • How many?
  • How will I know when it is accomplished?
  • Indicators should be quantifiable

Achievable

The third criterion stresses the importance of goals that are realistic and also attainable. Whilst an attainable goal may stretch a team in order to achieve it, the goal is not extreme. That is, the goals are neither out of reach nor below standard performance, since these may be considered meaningless. When you identify goals that are most important to you, you begin to figure out ways you can make them come true. You develop the attitudes, abilities, skills and financial capacity to reach them. The theory states that an attainable goal may cause goal-setters to identify previously overlooked opportunities to bring themselves closer to the achievement of their goals.

An achievable goal will usually answer the question How?

  • How can the goal be accomplished?
  • How realistic is the goal based on other constraints?

Relevant

The fourth criterion stresses the importance of choosing goals that matter. A bank manager's goal to "Make 50 peanut butter and jelly sandwiches by 2pm" may be specific, measurable, attainable and time-bound but lacks relevance. Many times you will need support to accomplish a goal: resources, a champion voice, someone to knock down obstacles. Goals that are relevant to your boss, your team, your organization will receive that needed support.

Relevant goals (when met) drive the team, department and organization forward. A goal that supports or is in alignment with other goals would be considered a relevant goal.

A relevant goal can answer yes to these questions:

  • Does this seem worthwhile?
  • Is this the right time?
  • Does this match our other efforts/needs?
  • Are you the right person?
  • Is it applicable in the current socio-economic environment?

Time-bound

The fifth criterion stresses the importance of grounding goals within a time-frame, giving them a target date. A commitment to a deadline helps a team focus their efforts on completion of the goal on or before the due date. This part of the SMART goal criteria is intended to prevent goals from being overtaken by the day-to-day crises that invariably arise in an organization. A time-bound goal is intended to establish a sense of urgency.

A time-bound goal will usually answer the question

  • When?
  • What can I do six months from now?
  • What can I do six weeks from now?
  • What can I do today?

Additional criteria

Some authors have added additional letters giving additional criteria. Examples are given below.

  • SMARTER
    • Evaluated and reviewed[4]
    • Evaluate consistently and recognize mastery[5]
  • SMARTTA
    • Trackable and agreed[13]
  • SMARRT
    • Realistic and relevance.[20] 'Realistic' refers to something that can be done given the available resources. 'Relevance' to the bigger picture and vision.

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Why SMART objectives don't work.
  4. 4.0 4.1 4.2 4.3 4.4 4.5 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 5.3 5.4 5.5 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 6.4 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 7.4 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 8.3 8.4 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 9.2 9.3 9.4 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 10.2 10.3 10.4 Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 11.2 11.3 11.4 Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 12.2 12.3 12.4 Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 13.2 13.3 13.4 13.5 Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 14.2 14.3 14.4 Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 15.2 15.3 15.4 Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 Mentioned as an alternative in Yemm, Graham (2013)
  17. Mentioned as an alternative in Piskurich, George M. (2011)
  18. 18.0 18.1 Mentioned as an alternative in Lawler, John; Bilson, Andy (2013)
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.