# SMART social media goals: worked examples

> Turn a vague request into a goal with an audience, observable change, plausible baseline, and review date.


**A SMART social media goal states what should change, how the team will observe it, why the target is feasible, and when it will be reviewed.** It helps turn a request like “improve LinkedIn” into a decision a team can understand and assess. The exercise does not prescribe an ideal percentage: the baseline and the team’s capacity need to justify the target.

## Work through a rewrite

Suppose a client says, “We want more engagement on LinkedIn.” Before suggesting posts or a target number, clarify which audience response would help the business.

In this fictional example, the team wants demo requests from operations managers. It recorded five LinkedIn requests in the previous six weeks and can produce one case-study post per week. With those assumptions, it could draft the following. The target of eight still needs justification: five previous requests and one weekly post are not enough to approve that increase.

> Over the next six weeks, get eight demo requests from operations managers through LinkedIn, recorded in the team’s tagged form, and review each week whether the case posts address their questions.

The numbers, audience, and channel are invented to show the method; they are not benchmarks or recommendations. In real work, the team would need to check whether eight requests are plausible based on its history, capacity, and business objective. If no baseline exists, first agree how requests will be recorded and for how long. Do not invent an increase to make the sentence look measurable.

## Another case: answer the questions that arrive

In this second fictional case, a team received ten eligible Instagram product-use question threads over four weeks, all during its stated support hours and under the same counting rule as the proposed goal. Six received a useful first reply within one business day. The team agrees to daily support coverage and capacity for three new threads a week. It can propose:

> Over the next four weeks, give a useful first reply within one business day to at least 80% of eligible Instagram question threads received during the stated support hours. Log receipt, first reply, and outstanding cases; review performance weekly.

An eligible thread is a non-duplicate customer question about product use. An automatic receipt confirmation does not count as a useful reply. Keep all eligible threads in the log, including unanswered ones: **threads answered within the deadline ÷ eligible threads × 100**.

The fictional baseline is 6 ÷ 10 × 100 = 60%. If ten questions arrived in the new period, meeting 80% would require eight timely replies. Daily coverage and the stated capacity make the target worth discussing; they do not prove it will be met. If demand changes, review staffing and the deadline. With zero questions, leave the rate uncalculated. This evaluates service for incoming questions without requiring more questions to meet a quota.

## Check the draft against SMART

The CDC presents one SMART version for Youth Advisory Council plans: Specific, Measurable, Achievable, Relevant, and Time-bound. Its guidance says goals should be doable with the available time and resources. This is an explicit expansion of the acronym, not a universal marketing standard; other versions may use a different word for R. [Read the CDC’s SMART framework](https://www.cdc.gov/youth-advisory-councils/action-plans/smart-framework.html).

- **Specific:** For whom, and what response? In the example, demo requests from operations managers, not “more engagement.”
- **Measurable:** Which data will show the change? The example counts requests recorded in the stated form. If the team is still choosing which measure represents the goal, use [social media KPIs by goal](/en/guides/social-media-kpis-by-goal/).
- **Achievable:** Does the target fit the observed baseline and the team’s time? Five previous requests and one case post per week are assumptions in the example; in real work, verify them and adjust the number or time frame.
- **Relevant:** Does the result support a business priority? If the team needs demo requests, more reactions that do not relate to them do not answer the brief.
- **Time-bound:** When does it end, and when will the team review it? “Over the next six weeks” sets a period; weekly reviews help check execution and surface missing information.

Apply the same SMART questions to the second case: Which questions and replies count? Is the full denominator retained? Can the support coverage meet the deadline? Does answering product-use questions matter to the team? Does the review cover four weeks? If the team lacks capacity, revise the resources or target before presenting it.

AMEC also distinguishes an aspiration from a measurable communication objective and connects communication objectives with organizational objectives. Its framework places reach and post counts among outputs, separate from audience responses and impact. [See AMEC’s Integrated Evaluation Framework](https://amecorg.com/amecframework/). “Post more” describes activity; it does not say what change the activity is meant to support.

## Fix what the team cannot yet defend

Read the final sentence and mark its assumptions. Does the team know what counts as a valid request? Can it identify requests that came from LinkedIn? Does it have a comparable six-week record? Can it make one case post each week without taking resources from another priority?

If the answer is no, do not hide the gap behind the acronym. Name the missing data, assign who will collect it, and agree when to revisit the target. A goal can begin as a hypothesis, but the hypothesis should be visible.

Once the goal is clear, work through audience, offer, channels, capacity, and the criteria for changing the plan in the guide to [social media strategy for businesses](/en/guides/social-media-strategy-businesses/). This article focuses on the workshop that turns an initial request into a goal the team can review.

The cover illustration was generated with AI.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
