View source for FAST Goals

''Created by Frederik Mørup Carlsson, February 2021.''

Creating a plan is pivotal for the success of any project and the management of said project<ref name="PMBOK" />. Key to any plan is goals: Objectives, milestones, or deliverables<ref name="PMBOK" />. Whatever shape the goal takes, without goals a plan is imperfect. Correct utilization of goals is therefore critical for project and project management success. Setting the wrong goals will waste valuable resources<ref name="PMBOK" />, setting the goals too low will result in lower quality outcomes <ref name="GSTOM" />and failure to communicate the goals adequately will leave those within the project without direction<ref name="MWM"> "Doerr, J, 2018, ''Measure What Matters,'' Penguin." </ref>. Ensuring high quality of the goals and correct utilization within the project is therefore a skill that project managers must master to save time and resources. FAST goals is a framework created to help practitioners setting and managing goals by ensuring the quality and proper usage of their goals through the acronym ''''FAST'''': '''F'''requently talked about, '''A'''mbitious, '''S'''pecific, and '''T'''ransparent<ref name="FNS"> "C. Sull, D. Sull, 2018, ''With Goals, FAST Beats SMART'', MITSLOAN Management Review, viewed 27-02-2021, <https://sloanreview.mit.edu/article/with-goals-fast-beats-smart/?gclid=Cj0KCQiA-OeBBhDiARIsADyBcE75IeLmrTVGP9FWKwgV2KQ45pq52D9FxXBbO0WPF0D5BfxNmw4YTzYaAoMxEALw_wcB>" </ref> .

FAST goals strays from more traditional goal setting methods such as SMART goals, and proposes itself as a reorientation to the way practitioners approach goals<ref name="FNS" />. Based on research and industry success the FAST goals attempt to summarize how goals as a whole should be approached and utilized, modernizing goal setting through the inclusion of more agile practices and a focus on the surrounding environment <ref name="FNS" />. This article will further explain the meaning and qualities of each of the four letters in FAST as well as exploring the application and limitations of the FAST goals within project management. This article aims to provide information on the strengths and limitations of the FAST goals, and how to apply them so that project managers can extract the most value of the methodology.


== Effective goal setting that enhances strategic alignment ==
In the PMBOK guide, the purpose of a project is defined as such "''Projects are undertaken to fulfill objectives by producing deliverables.''" <ref name="PMBOK"> "Project Management Institute, 2017, ''A guide to the project management body of knowledge (PMBOK guide)'', Sixth edition, Project Management Institute, Inc."  </ref> 

Intrinsically linked to the purpose of the project, the reasoning for why it has been undertaken is the project objective.  A project is not a project without something that it tries to achieve. The overarching goal of the project is divided into many smaller goals which combine to be the project plan. Depending on the complexity of the project these goals can be divided further over and over again until the goals reach a manageable size. Goals permeate the very nature of projects with entire management styles revolving around the creation and execution of goals <ref name="GDPM"> "Andersen, E, Grude, K & Haug, T, 2017, ''GOAL DIRECTED PROJECT MANAGEMENT: Effective techniques and strategies'', fourth edition, Kogan Page." </ref>.


The importance of goals within project management is therefore critical. Not only are goals abundant in project management, but correct utilization of goals can also bring benefits such as higher motivation <ref name="GSTOM"> "Lunenburg, F, 2011, Goal-Setting Theory of Motivation, ''International Journal of Management, Business, and Administration.'', vol. 15, no. 1, pp. 1-6." </ref>, higher performance and work satisfaction<ref name="WM"> "Kleinbeck, Uwe (ed.), Quast, H (ed.), Thierry, H (ed.), H„cker, H (ed.),  ''Work Motivation'', Psychology Press, pp. 3-25." </ref>. Poor utilization of goals negatively influence the planning, poor planning then is associated less chance of success of reaching goals <ref name="GDPM" />pp. 69, waste of resources, reduction in quality and frustration <ref name="PRINCE2"> "AXELOS, 2017, ''Managing Successful Projects with PRINCE2'', 2017 edition, The Stationery Office Ltd" </ref> .


It should therefore come naturally to all project managers to strive for setting goals of high quality. However, what is a goal of high quality? The PRINCE2 project management guide suggests that project objectives should adhere to the SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) goals framework <ref name="PRINCE2" />. The SMART goals framework dates back to 1981 <ref name=''S.M.A.R.T''> Doran, G, 1991, ''There's a S.M.A.R.T. Way to Write Management's Goals and Objectives,'' Management Review, vol. 70, pp. 35-36. </ref>, and depending on the source each letter of the acronym can take a new meaning. Some even suggest an updated version of the acronym to SMARTER (Specific, Measurable, Achievable, Relevant, Time-bound, Efficacy, Rewarding) <ref name=''RSG''> Rubin, R, 2002, ''Will the Real SMART Goals Please Stand Up,'' The Industrial-Organizational Psychologist, vol. 39, no. 4, pp. 26-27. </ref>, again the newly included latter two letters take on new meaning dependent on the source. According to the PRINCE2 guide a SMART goal is a high-quality goal, yet there exist management practices that diverge from SMART in favor of other ways to set high-quality goals. 

One such practice is the OKR (Objectives – Key Results) methodology. It proposes a vastly different approach to goals compared to SMART goals. In the OKR methodology, objectives are set up with a set of key results attached. The act of the goal-setting in the OKR methodology is reminiscent of how goals are set using SMART goals however, the emphasis in the OKR methodology is split between the initial creation of OKRs, feedback and revision, strategic alignment, and transparency <ref name = "MWM" />. The OKR methodology embraces adaptiveness by focusing not only on goal setting but including surrounding factors to ensure the goals stay relevant and correctly prioritized throughout the project. This is a particularly important thing that is built into the OKR methodology which is not in SMART. As such the OKR methodology does not seek only to answer the question, what is a high-quality goal? It attempts to give a methodology that serves as a way to both set high-quality goals and be high-performing when executing those goals. 


In 2018 an article called: ''With Goals, FAST Beats SMART'' was published as part of a series of articles dubbed The Strategic Agility Project. The Strategic Agility Project series of articles aims to help practitioners find better alignment between strategy and goals within organizations <ref name="SAP"> "D. Sull, 2021, ''The Strategic Agility Project'' MITSloan Management Review, viewed on 24/02-2021, <https://sloanreview.mit.edu/big-ideas/strategic-agility/>." </ref>. In this article the sentiment of the OKR methodology is echoed, to construct goals that align with strategy, it is not enough to set goals of high quality. Donald Sull and Charles Sull describe how generally people have become too focused on the act of setting goals, and not enough attention is being given to how goals are used. Proposed in this article is the ''''FAST'''': ('''F'''requently talked about, '''A'''mbitious, '''S'''pecific and '''T'''ransparent) goals, a new goal methodology with the aim of reorienting how goals are perceived and worked with. It is proposed that through utilizing the FAST goals framework the way goals are utilized can be reframed to bring about goals that increase motivation, produce higher quality outcomes, and better aligns with the overall strategy. The purpose of the FAST goals is thusly aiding in both the setting of high-quality goals and facilitating the environment surrounding the goals, which allows for high-performance utilizing the goals, executing on what is strategically important, and improving the work environment <ref name="FNS" />.

== FAST goals ==
[[File:FASTGOALS.png|right|thumb|600px|A visual representation of the core tenets of the FAST goals. Own creation.]]

If the above section served to answer the question, why should you care about the FAST goals, the following section aims to answer the following: What exactly are the FAST goals, and how can using this tool benefit me?

As mentioned earlier the sentiment of the pioneers of the FAST goals is that there is a wrongful one-track focus on goal setting for practitioners. The FAST goals then try to widen the scope of what goal setting is through including a focus on surrounding culture and agility in order to bring additional benefits <ref name="FNS" />. The FAST goals, however, are not a readymade template that can be plugged into any project and be expected to work, they are instead a set of tenets which if adhered to and properly applied within a project can bring tremendous benefits. These tenets are the four letters that make up the acronym FAST. Frequently talked about, Ambitious, Specific, and Transparent. A figure depicting these alongside the acronym FAST is included for a visual overview.
Each of the tenets will be described in detail in the following sections and points of note will be highlighted. Accompanying these sections will be a figure which depicts the definition and recaps a list of benefits derived from the correct utilization of each tenet by the authors of the FAST goals. These are intended as a means to quickly introduce or refamiliarize the tenets of the FAST goals.


==== Frequently talked about ====
[[File:FASTGOALS2.png|right|thumb|600px|A representation of the definition and benefits of the first tenet of FAST goals. Own creation based on <ref name="FNS" />.]]


The first of the four tenets of  FAST is F, for Frequently talked about. The definition of Frequently talked about coined by D. Sull and C. Sull is:

''"Goals should be embedded in ongoing discussions to review progress, allocate resources, prioritize initiatives, and provide feedback.  "''<ref name="FNS" />

Two particular things in this definition are important. The first of which is the word frequent. For many, the standard practice is to set goals and forget about them for upwards of a year before reviewing them <ref name="FNS" />. To make goals FAST it is a necessity to frequently review your goals. Frequent is up to interpretation, however the FAST goals advocates for normalizing discussion, reflection, and revision of goals <ref name="FNS" />. The second thing of importance in the definition is what frequently needs to be discussed is not merely progress. Instead, it is several factors that relate to the goal. The focus on feedback, resource allocation, and prioritization shifts the focus from the one-track approach of setting a goal and measuring whether or not it is reached <ref name="FNS" />. A FAST goal is therefore not the same from its conception to its end, it can adapt and change as the environment around it does. FAST goals take the typically predictive approach to goal setting and change it to be a more adaptive approach.

Frequently talking about goals is one of the ways FAST goals draw inspiration from OKR methodology, and while the FAST goals are a new and mostly undocumented methodology the benefits that frequent discussion surrounding goals can have can be extrapolated from the OKR methodology. In John Doerr’s book “Measure What Matters”, he describes the OKR methodology as having four superpowers, three of which are derived in some way from the frequent conversation around goals <ref name="MWM" />. These three superpowers are Focus and commitment to priorities, alignment and connectivity for teamwork, and the ability to track for accountability <ref name="MWM" />. Frequently talking about goals enables these superpowers in ways such as ensuring goals fit with priorities, talking about goals allows for revision which then provides focus, and it enhances teamwork through a reduction of uncertainty across teams.

==== Ambitious ====
[[File:FASTGOALS3.png|right|thumb|600px|A representation of the definition and benefits of the second tenet of FAST goals. Own creation based on <ref name="FNS" />.]]

The second tenet of FAST, defined as:

''"Objectives should be difficult but not impossible to achieve"''<ref name="FNS" />.

Several studies link ambitious goal setting to worker motivation <ref name="WM" /> <ref name="GSTOM" /> <ref name="FNS" />, the PMBOK guide even puts one of the project managers' responsibilities in terms of managing teams to be providing challenging goals <ref name="PMBOK" />pp. 346. The same study which linked ambitious goals to motivation also links ambitious goals to high performance.<ref name="WM" />. This is further exemplified in the book Measure What Matters where John Doerr establishes the importance of setting ambitious goals in order to perform higher <ref name="MWM" />pp. 184. 
In the previous section, three of the superpowers of OKR methodology described in the book Measure What Matters was highlighted. Setting ambitious goals is the fourth. It is described as the enabler for achieving more than what could possibly be expected, as a way to test limits and unleash creativity <ref name="MWM" />. The core of the reason for ambitious goals can be summarized by this quote in the aforementioned book from one of the founders of Google, Larry Page. 

"''If you set a crazy, ambitious goal and miss it, you'll still achieve something remarkable.''"<ref name="MWM" /> pp.102.

From the quote, it can be read that ambitious goal comes with the risk of not meeting goals. To facilitate aiming high and creating ambitious goals, it must be accepted not to reach them. However, in some instances, there are goals that must be met, for example, the construction of facilities for the Olympic Games. In this example failure to deliver is not an option and an ambitious goal could be a detriment. One way to work with ambitious goals which account for these need to be met goals can be seen in the OKR methodology. At Google there is a distinction between what they call a committed OKR and an aspirational OKR. The objective of a committed OKR is expected to be 100% complete, and time and resources will be committed to ensuring that. Aspirational OKRs are however only expected to average out to complete about 70% of what it set out to do, with an expectation of high variance from this average <ref name="MWM" />pp.172. It is also important to keep ambitious goals somewhat feasible as the reverse effect of ambitious goals, lack of motivation, and low performance, has been linked to goals that are impossible to reach<ref name="GSTOM" /> <ref name="FNS" />.

The challenge of setting ambitious goals will be different from project to project, but for inspiration, a few ways that Google tries to ensure ambitious goals will be highlighted from Google's OKR Playbook in the book Measure What Matters. 

-When setting aspirational OKRs, one way Google starts is looking at the current situation and attempting to answer the question: ''"What could we do if we had extra staff and got a bit lucky?"'' <ref name="MWM" />pp.173.

-Another similar way proposed is starting by asking the question: ''"What could my (or my costumers) world look like in several years if we were freed from most constraints?"''<ref name="MWM" />pp.173.

-The final suggestion is doing the Litmus test: "''If you ask your customers what they really want, does your aspirational objective meet or exceed their request?''"<ref name="MWM" />pp.173.

==== Specific ====
[[File:FASTGOALS4.png|right|thumb|600px|A representation of the definition and benefits of the third tenet of FAST goals. Own creation based on <ref name="FNS" />.]]

The third tenet of FAST, Specific, is defined as: 

''“Goals are translated into concrete metrics and milestones that force clarity on how to achieve each goal and measure progress.”''<ref name="FNS" />. 

The reasoning for this tenet might be considered common knowledge, as it is a constant throughout many goal-oriented methodologies, and the definition is quite straightforward. Both the PMBOK guide and PRINCE2 references the need for specificity in planning and in general throughout project management "<ref name="PMBOK" /> <ref name="FNS" />. Other methodologies different from FAST and SMART include the need for specificity and measurability as a requirement for goal setting  <ref name="MWM" />pp. 46<ref name="NMMT2"> "Züst, R & Troxler, P, 2006, ''No More Muddling Through - Mastering Complex Projects in Engineering and Management'', Springer, pp. 83."  </ref> <ref name ="GDPM" />. Specific goals are linked to increased motivation and performance <ref name="GSTOM" /> <ref name="FNS" /> <ref name ="MWM" />, clarity around objectives <ref name= "FNS" /> <ref name ="MWM" />, and linking goals to strategy <ref name= "FNS" /> <ref name ="MWM" />.
In the article pioneering FAST goals the authors exemplify a specific goal with this example: "''Gain 100,000 followers on Twitter''" <ref name="FNS" />. This goal is easy to understand, it is easy to measure success on and there is no lack of clarity on what needs to be achieved. A non-specific version of this goal could be "Grow our social media following". In this goal, there is no specified media, there is no amount, and it is hard to track success or progress towards completion. The authors also mention that while quantifiability is important, nonquantifiable goals can also be important. While in the social media example a specific number can be put on it, it is hard to quantify hiring a new critical staff member. In that case, a goal can still be specific, another example from the article is: "''Hire a new chief technology officer''" <ref name="FNS" />.

==== Transparent ====
[[File:FASTGOALS5.png|right|thumb|600px|A representation of the definition and benefits of the fourth tenet of FAST goals. Own creation based on <ref name="FNS" />.]]
The final tenet of FAST, Transparent, is defined as: 

''"Goals and current performance should be made public for all employees to see."''<ref name="FNS" />

The key takeaway from this definition is recognizing that creating transparent goals is not about understanding the goal or the meaning behind it, it is instead how it is treated which has to be transparent. What FAST goals advocate for is enabling everyone within a project, from the project manager and through the rest of the project, to see the goals and progress of everyone else within the project. In a study done by the authors of the FAST goals, less than 25% of middle managers were found to know their company's strategic priorities <ref name="FNS" />. Being transparent throughout the organization would help combat this as at any point a middle manager would be able to look up or see those priorities. Another study highlighted in the article showed how only one in four managers understood the goals of their co-managers <ref name="FNS" />. This can lead to frictions such as improper focus, wasting resources on duplicate work, and poor cross-team communication <ref name ="FNS" /> <ref name="MWM" />pp. 59. If goals are transparent these people would be able to see the goals of their peers and how they link together with the overall strategy, removing this uncertainty and side-effects. The benefits of doing transparency right is linked to things such as better strategic alignment, improved motivation, and becoming more attractive to high-performing workers. <ref name=''TRANS1''> "Farrell, M, 2016, ''Transparency'', Journal of Library Administration, vol. 56, no. 4, pp. 444-452." </ref> <ref name="TRANS2"> "Berggren, E, Bernshteyn, R, 2007, ''Organizational transparency drives company performance'', Journal of Management Development, vol. 26, no. 5, pp. 411-417" </ref>. An example of how transparency can directly benefit an organization is highlighted in the article describing the FAST goals, in the example of production facilities, if goals and progress are public, managers of a poorly performing facility can find and seek out advice from managers of facilities performing more optimally <ref name="FNS" />.

== Application ==
As a rather new methodology, appearing first in 2018, very little evidence is publically available to document the application of the FAST goals. The authors of the FAST goals however highlight the methodology of OKR (Objectives - Key Results) as being in accordance with the FAST goals. To describe the application of FAST goals much of the basis will be taken in the application of the parts of OKR methodology which relate to the FAST goals. For a better understanding of the OKR methodology, a relevant book to suggest is Measure What Matters by John Doerr of which much of this section will be based on. To begin explaining the application of FAST goals through the application of OKRs the following quote from the aforementioned book gives perspective.

''OKRs have such enormous potential because they are so adaptable. There is no dogma, no one right way to use them. Different organizations have fluctuating needs at various phases of their life cycle. For some, the simple act of making goals open and transparent is a big leap forward. For others, a quarterly planning cadence will change the game. It’s up to you to find your points of emphasis and to make the tool your own.'' <ref name="MWM" />

The unfortunate reality is that there is no one right way to do it, no one size fits all solution. In an interview with John Doerr, he emphasizes that the OKR methodology is not a silver bullet that guarantees success. He describes how without the fundamentals of a good culture and skilled management the value of OKRs is diminished <ref name="Interview"> "D. Sull, J, Doerr, 2018, ''John Doerr on OKRs and Measuring What Matters'', video interview, MITSLOAN Management Review, <https://sloanreview.mit.edu/video/john-doerr-on-okrs-and-measuring-what-matters/>." </ref>. In order to apply either the FAST goals or OKRs, it is therefore imperative that practitioners remain acutely aware of the fundamentals of project management and management in general. Without those, there is no guarantee that the sought-after benefits from utilizing this tool will be realized. Understanding the four tenets of the FAST goals, what it is they each try to achieve, and tailoring these to your project alongside strong fundamentals is a prerequisite for unleashing the benefits of the framework. 

The following is based on a test designed by the authors of the FAST goals to determine whether or not your goals adhere to the FAST goals framework <ref name="FNS" />. If you can answer yes to the following questions your goal setting methods are aligned with the FAST goals framework. If you can not answer yes to some, it is up to the project manager to determine how to structure the necessary changes to change that no to a yes.

[[File:FAST10.png|center|thumb|600px|A set of questions to determine if you adhere to the FAST goals methodology. Own creation based on <ref name="FNS" />.]]

It should also be noted that being able to answer yes to the above questions is not a guarantee that your goal setting is optimal for your project. Understanding what each question attempts to test and understanding the relation to the four tenets of FAST and their benefits, will allow you to better compare on your project whether or not you are adhering to FAST principles and realizing the intended benefits. 
While it has been determined that it is impossible to provide a template for every project on how to establish FAST goals in any project, the following will be some examples of how to initialize the implementation which has proved to work in a variety of cases when applying OKR methodology. 


*Ease into the process
For many applying FAST goal methodology will be a disruptive change to the status quo. It is, therefore, advisable to ease into the process. For this applying the methodology at the top and working downwards has shown to be effective. <ref name="MWM" />
*Ensure that goals are made public
Many benefits are reliant on the goals being public and that everyone at any time has easy access to goals, not just their own goals but also others, especially strategic goals. Exerting the effort to make goals public is therefore a good place to start to apply the FAST goals<ref name="MWM" />.
*Frequent check-ins
Frequently checking in on progress allows for goals to be changed to reorient, or be abandoned before resources are wasted. Engaging this change is therefore critical to enable the FAST goals methodology to function. In relation to OKRs, a common change is going from annual goal review to quarterly goal review <ref name="MWM" />.
*Initiate a culture change
To be transparent, open in your frequent discussions, and ambitious in your goals, it might be necessary to undergo a culture change. It has been shown to be effective to have top management set a good example for this, and set the standard throughout the project<ref name="MWM" />.

In an interview with John Doerr, he describes the one thing which causes people to fail when attempting to use the OKR methodology is the lack of commitment from top management. He explicitly references the CEO, and them committing to the change being a key determining factor in the success of the OKR methodology <ref name="Interview" />. He goes on to explain how the most success from the methodology is seen when the entire company embraces the system and allows it to become part of the day-to-day workings of the company <ref name="Interview" />. A final suggestion extrapolated from the OKR methodology is therefore to ensure that the FAST goals are embraced by top management and that the project manager fully commits to using them. Showing off their own personal goals, measuring their performance and success, and actively including it in their personal work. Frequently talking about their ambitious and specific goals in a transparent fashion.

== Limitations ==
The way to apply the FAST goals is different from project to project, and it, therefore, relies on the project manager to adapt the tenets of the FAST goals to the individual project. This is a limitation for newcomers with little reference material to attempt to learn or adapt from. As mentioned earlier in regards to OKRs, John Doerr describes OKRs as heavily reliant on fundamentals <ref name="Interview" />. Utilizing FAST goals will not solve any and all issues and might be a detriment without a proper fundamental base to grow from. Applying the FAST goals is thusly heavily reliant on skilled management, and as little research has been done on the application or the realization of the benefits from FAST, it might be difficult or risky to attempt to apply this methodology. Furthermore, the FAST goals have been created with agility in mind <ref name="FNS" />, and where many projects and organizations have become far more reliant on adapting change there are still sectors where attempting to apply the FAST goals would simply be an addition of costs with potentially little benefit. Finally applying the FAST goals can require culture changes which can be hard to enforce, as well as structural changes which might be costly or difficult to implement.

== Annotated bibliography ==
''With Goals, FAST Beats SMART'' - The article introducing FAST goals. This is the maiden work related to the FAST goals, introducing the reasoning behind the creation of the methodology, the research which led to the FAST goals as well as the meaning behind each of the four letters of the acronym in great detail.  Additionally, this article presents the FAST goals as superior to the SMART goals, seeing it as an evolution of the concept of SMART goals more fit for modern-day project management. This article includes many real-life examples of aspects of the FAST goals in practice in high-performing companies.

''John Doerr on OKRs and Measuring What Matters'' - A sub-30-minute video interview between one of the authors of the FAST goals, Donald Sull, and the author of the book Measure What Matters, John Doerr. In this interview, OKRs are broadly introduced as are the benefits of utilizing them. John Doerr provides great insight into the methodology and manages to provide a great understanding throughout the interview. This interview provides a great entry point for those who want to know more about OKRs and the theory behind them. Furthermore, John Doerr shows his great experience within management and management with OKRs to provide many great insights into why he supports this methodology. 

''Measure What Matters'' - A book describing the OKR methodology which goes into great detail talking about benefits, real-life success stories, and more. It serves as a broad introduction to the methodology, which also provides a lot of background on how it came to be. Seeing as FAST goals are quite related to the OKR methodology this is a great entry point for any interest in one or both of the two. It also provides interesting real-life experiences and insight from some of the biggest companies like Google.

== References ==
<references />