Goals and Planning

From the environment map to a 12-week goal

Take out your Week 4 environment map. It shows one planned activity and the outside conditions it depends on: who must give permission, who must pay, which language version counts. The map tells you what could go wrong. It does not yet tell Judy's staff what to do on Monday morning.

That is the gap this week closes. When an opportunity looks exciting, people tend to speak in verbs without objects: grow, expand, scale, build the brand. These words sound decisive, but they leave the next morning's questions unanswered. Who are we serving? What result do we want in this period? What work gets our limited time and money, and what has to wait? Who may make a commitment? What must never be traded away? What would make us pause?

Judy's company faces exactly this situation. The course follows three possible directions, introduced in Week 1: Option A · Expansion (expand cheerleading and sports-entertainment talent management), Option B · Boutique (a small cross-border talent and advisory service for a few clients) and Option C · Content-centered return (return to content, advertising, food service and personal brand). The case does not say which one Judy will choose. A small company also cannot commit to a whole direction at once. It is safer to test one direction for a limited period, learn from the test and then decide whether to commit more.

So this week's question is: how can a vague ambition become a goal that tells a team where its time and money go? The chapter continues the practice scenario from Week 4, in which a Taiwan team asked Judy's company to bring a Korean performer to two home games. This week, the company treats that request as the start of a 12-week test of Option A.

Where this week fits

Week 4 produced an environment map for one activity. This week turns it into a goal tree: a one-page record that links a direction to a 12-week goal, the work under it, the people who own that work, the resources reserved for it, and the conditions that would make the company stop. Week 6 then asks whether the focus you chose is a sound strategy, or whether the company is trying to do too many things at once.

By the end of this week, you should be able to:

• tell apart a vision, a strategic goal, an operating goal, a threshold and a non-goal, and say what each one can and cannot do;
• write a 12-week goal that names who is served, what gets time and money, who decides and what would make the company stop;
• spot a goal conflict or a misleading metric before it becomes a hidden burden on someone.

Words that sound alike but do different work

Management language often squeezes several levels of commitment into one word, usually "goal". That causes trouble. A sentence can express hope without telling anyone what to do. Another sentence can assign work without explaining why it matters. The terms below separate these levels. The examples all come from the practice scenario.

• An aspiration is a direction people care about. "We want to be trusted across borders" tells us what matters to Judy's staff, but not whom to serve or what to decline.
• A mission states the company's current purpose and the obligation that gives its work a reason. "We help event partners arrange cross-border performances that are well organized and fair to performers" is narrow enough to be questioned and improved.
• A vision describes a future the company would like to bring about. It gives a direction, but it does not prove that customers exist or that the company can deliver.
• A strategic goal chooses one important result for a stated period and shows what will wait. It answers the question: which problem gets our scarce attention now?
• An operating goal turns the strategic goal into a piece of work with an owner, resources, a safeguard and a date.
• A metric is a signal the team watches, such as the number of teams that agree to pay. It shows part of the progress, never all of it.
• A threshold is a line that triggers action, such as "no photo is published without the performer's written approval". If the line is crossed, the company pauses, whatever the other numbers say.
• A non-goal is work the team deliberately will not do during the period, such as "no agreements involving more than two performers in these 12 weeks".

The table gives a team a shared vocabulary. It also shows why names matter. Judy might own the mission, a coordinator might own an operating goal and a translator might own the language check. Nobody can fairly be held responsible for a goal if they lack the authority, information or resources to act on it.

When do specific goals help?

Locke and Latham (2002) reviewed 35 years of research on goal setting. Their main finding is that specific, challenging goals help people focus, try harder, keep going and look for better methods, but only under certain conditions. People must be committed to the goal, have the skill to reach it, receive feedback on their progress and understand the task. A later review adds that goals work through these conditions, not simply because the target is higher (Locke & Latham, 2006).

The practical lesson is that a big number does not replace missing ability, information, time or authority. A target such as "double our bookings" can focus a team's attention on the wrong work. It can also push people to hide problems so that the number still looks good. When a team is doing something new, such as arranging its first cross-border appearance, a goal to learn is often more useful than a goal to perform. The team does not yet know enough to set a sensible performance target.

"Stretch goals", targets that are both extremely hard and extremely new, need extra care. Sitkin and colleagues (2011) argue that they are most dangerous when a team has little spare time or money, weak feedback and no safe way to report problems. In practice, a stretch target must never replace a line on consent, safety, quality or cash.

Imagine a team planning its first cross-border service pilot. "Become the leading regional agency in one quarter" makes a dramatic poster, but it does not tell the team what to learn. A more useful temporary goal would be: "Within twelve weeks, find out whether two teams will pay for a small appearance service, while keeping written consent from every performer, one named person who may sign agreements and a fixed spending limit." The second goal directs learning and states its limits. It also leaves room for the honest result that the team should stop.

A goal tree: from direction to Monday morning

A goal tree puts all of these parts on one page. The top names the direction being tested. The middle chooses one 12-week result and says what will wait. The lower branches turn that result into work with owners, resources and safeguards. Each goal also names the outside condition from Week 4 that it depends on.

The most revealing part of the tree is resource allocation. Resource allocation means deciding which work gets the company's limited hours, money and people, and therefore which work has to wait. A team can say that cross-border talent work is its priority. But suppose nobody is given time for translation, nobody checks the permission rules and nobody owns problems when they arise. Then the work is not really the priority. The real priorities are wherever the hours and money actually go.

Worked example: a 12-week goal tree for testing Option A

This goal tree continues the practice scenario.

Notice three things about this tree. First, the strategic goal is written as something to learn, not as a sales target, because the team does not yet know what is possible. Second, every operating goal has one owner and a reserved amount of time or money. Third, the tree says what waits. The sponsored-video deals are a real cost of the test, and writing them down makes the trade-off visible to everyone.

Write the assumption next to the goal

In Week 1 you learned to separate evidence, inference and unknown. A goal tree uses the same discipline. Next to each goal, write the assumption it depends on and the smallest check that could change the next step.

For example, operating goal 2 assumes that other teams might pay for this service. That is an inference from one team's request, not evidence of demand. The smallest check is two conversations about fees and payment dates. If the conversations support the assumption, the team continues within its limits. If they do not, the team narrows the offer, changes the payer or stops.

Keep the first version of the goal tree when you revise it. Later, the team can see what changed and why: new evidence, a failed assumption, a capacity problem or a new obligation. This protects people from being blamed in hindsight for a reasonable guess. It also lets another team learn from the reasoning.

Goal conflict and non-goals

Goal conflict happens when two outcomes a team wants compete for the same time, money or person, or when progress on one makes the other harder. Studies of individuals have found that people who carry more conflicting goals tend to report lower well-being (Gray et al., 2017). For managers, the lesson is to bring conflicting demands into the open rather than asking one person to balance them quietly.

Consider four aims: reply to every partner immediately, translate carefully, keep costs low and protect people's rest. One coordinator cannot maximize all four at once. The team has to choose: a priority order, a temporary limit on new commitments, a rule for handing work to someone else, or a line that cannot be crossed.

That last option connects to Week 3. There you met satisficing: choosing an option that meets stated minimum requirements, instead of searching for the perfect one. A minimum requirement must be met before an option can be chosen at all, and a threshold in a goal tree works the same way. Written consent before a performer's image is used is a threshold, not one criterion among many. A weighted score must not let predicted attention make up for missing consent. In the same way, a cash limit can be a threshold, because going below it would stop the company from paying people it already owes.

A mission that is too broad makes conflict worse. "Always say yes to opportunity" sounds energetic, but it makes the coordinator responsible for both growth and safety without saying which comes first. A clear non-goal gives the team permission to decline. "For this 12-week test, we will not accept agreements with more than two performers until the signing authority, the permission route and the person responsible for the performers' care are confirmed" is a much stronger instruction than "be careful".

Non-goals protect attention from scope creep, the slow growth of extra work that nobody decided to take on. A good non-goal has four parts: a period, a reason, a person who will reassess it, and a condition under which it can be reopened. Without these, a non-goal becomes a vague rule that nobody remembers the reason for.

Use metrics as signals, with red lines beside them

Numbers are attractive because they seem to settle arguments. But a number also moves attention toward what is easy to count. Ordóñez and colleagues (2009) warn that narrow targets can encourage excessive risk, shift attention away from important work and reduce learning. So before adopting a metric, ask what behavior it will encourage.

In the practice scenario, a response-time target might reward confirming a request before the terms are checked. A count of accepted bookings might reward taking on work while hiding the translation, rest and complaint handling it requires. The table shows common metrics, what they can miss and how to design around the gap.

Every important metric also needs a way to be challenged. A performer or a local partner may know that a number contains an error, or that it hides work shifted onto someone else. If nobody can question the metric, it becomes a tool of pressure rather than learning.

You may meet OKRs (objectives and key results), a format that pairs an objective with a few measurable results. OKRs can display a plan, but they do not decide whether the objective is wise or whether the key results measure real value. A set of OKRs without a non-goal, an owner, a resource limit and a review point is a scorecard, not a plan.

Who decides, and who can pause?

Goals are sometimes written at the top of a slide and handed to people who have no authority to make the choices the goal requires. A coordinator is judged on on-time delivery but cannot approve a small schedule change. A translator is asked to protect meaning but receives the text after the public deadline. The problem is not motivation. It is a gap between responsibility and decision rights, the authority to decide a stated kind of question.

Week 2 introduced decision rights. In a goal tree, name three roles for each operating goal: who prepares the information, who decides within a clear limit, and when the question must go to someone else. In a small company one person may hold several roles, but the roles should still be named.

The right to pause matters most. If a red line is crossed, the person closest to the problem needs permission to stop the work at once. Otherwise the team waits for a senior person who may be busy or unaware. A pause protects the performer, the customer and the company. A later review can decide whether to resume, redesign or stop.

Review: continue, redesign or stop

A plan without a review date is a promise that nobody will revisit when conditions change. Set the review points before the results come in, while the team can still think clearly about them. A review can be triggered by a date, a piece of evidence, an outside change, a capacity limit or a crossed threshold.

At each review, the team asks whether the goal, the resources and the safeguards still make sense. "Continue" is a valid answer, but it should come with a reason: what was learned, and why the remaining risks are acceptable. "Redesign" and "stop" are also valid answers. A plan that cannot end in a stop has confused commitment with learning.

Reviews also have an ethical side. A metric can look good while someone else quietly pays the cost, for example when fast replies push translation work into unpaid evening hours. Adding a well-being slogan to the plan does not fix this. The work, the authority and the resources have to change.

Where AI can help with planning

AI tools can help with planning tasks such as sorting sources, suggesting clearer wording for a goal or comparing versions of a schedule. They can also mistranslate a condition, repeat an outdated source or make a weak metric look authoritative. An AI tool cannot decide which cost to a stakeholder is acceptable, and it cannot be the owner of a goal. The U.S. National Institute of Standards and Technology's AI Risk Management Framework (NIST, 2023) gives organizations a way to name who is accountable when AI is used. In a goal tree, the practical rule is simple: every goal and every red line has a human owner who can explain and change it.

The three options as 12-week tests

The worked example tested Option A. The same goal tree works for each option, but each test would try to learn something different and would need different red lines. The table gives starting points. It does not rank the options.

A goal tree is not evidence that an option is good. It is a way to organize a test of the right size. If the test shows that a central assumption is wrong, stopping is a good result.

Class practice: a 12-week goal tree

This practice is done in your team, without AI tools. Your teacher will tell you which worksheet to use and how to submit it. Bring your Week 4 answers.

1. Choose a direction to test. Each member says which option they would test and why. Record the choice, including any minority view.
2. Write the 12-week goal and the "not now". What do you want to know or show by test week 12, and for whom? What will the team not do during the test, and when will you look at it again?
3. Allocate resources and decision rights. What gets the team's limited time and money, and what has to wait? Who is responsible for the goal, what may that person decide alone, and who can pause the work?
4. Set the signal, the red line and the outside condition. How will you see whether the test is working? What would make you stop, whatever the other numbers say? Which outside condition from Week 4 does the goal depend on, and what evidence would change the plan?

Label any number you invent as invented. A strong goal tree lets someone outside the company see what Judy's staff will do on Monday, what it will not do, and what would make it change course.

Key points and what you bring to Week 6

• Goals decide where attention goes. A goal is real only when it has an owner, reserved time or money, and a clear statement of what waits.
• Vision, strategic goal, operating goal, metric, threshold and non-goal do different jobs. Mixing them up produces slogans instead of plans.
• Specific goals help when people have the skill, feedback, information and authority to act. When the work is new, a goal to learn is often better than a goal to perform.
• Red lines such as consent and a cash limit are thresholds. Other good results cannot make up for crossing them.
• Name who decides and who can pause, and set review points in advance. A test that cannot end in a stop is not a test.

For Week 6. Bring your goal tree. Week 6 asks whether the focus you chose is a sound strategy, and what happens when a company tries to run several directions at once.