# Operating Model — making the strategy run

A strategy you can't sustain is a wish. This is how the choices become a working, repeatable
engine — and how the brand actually wins, not just shows up.

## The strategic wedge — how this brand wins

Showing up with "good content" is table stakes; it's not a strategy. The **wedge** is the
differentiated reason this brand wins attention on its chosen channels, and it comes straight
from the brand's POV and positioning (`brand-profile`). A wedge is usually one of:

- **A distinct point of view** — a stance the brand consistently takes that others won't
  ("radical transparency," "build less").
- **An underserved angle** — "the only one teaching X *for* Y" (a specific audience others
  ignore).
- **A signature format** — a recognizable, repeatable content form the brand owns.
- **A voice/personality** — a way of sounding that stands out in a beige feed.

Name the wedge explicitly. If you can't articulate why this brand wins beyond "we'll post good
stuff," the positioning needs sharpening first — surface that.

## The content engine

Strategy wires the other skills into a repeatable flow so the brand isn't starting from zero each
week:

```
Foundation (brand-profile · voice · audience)
      ↓
Pillars (content-pillars)            ← the themes
      ↓
Plan (batch-content-plan)            ← the calendar
      ↓
Produce (caption/reels/hook/…)       ← the posts
      ↓
Repurpose (cross-platform-repurposing) ← multiply
      ↓
Schedule (scheduling-and-queue)      ← ship
      ↓
Engage (community skills)            ← the relationship
```

The strategy's job is to make sure this engine points at the chosen objective and channels.

## Cadence — realistic, sustainable

Set a cadence per chosen channel that the brand can actually keep. **Consistency beats volume**:
a steady, modest cadence sustained for a year builds more than a burst that collapses in a month.
Derive cadence from capacity (see below), not ambition. (Detailed cadence guidance lives in
`batch-content-plan/references/calendar-and-cadence.md`.)

## Phasing — start focused, then expand

Don't launch everywhere on day one. Phase it:

- **Phase 1 — Win one channel.** Pick the single best-fit platform, commit a sustainable cadence,
  and get genuinely good at it. Establish the pillars, voice, and engine here.
- **Phase 2 — Extend efficiently.** Add a secondary channel, fed largely by
  `cross-platform-repurposing` so it doesn't double the workload.
- **Phase 3 — Expand deliberately.** Add channels only as capacity and results justify.

Most brands overreach in Phase 1 and stall. Narrow focus early is the unlock.

## Capacity & roles

Be explicit about what the brand can produce and who does it:

- Who creates content, who engages/replies, how much time per week.
- How much is net-new vs repurposed (repurposing is what makes a small team's cadence viable).
- The honest constraint: plan to the time that actually exists, then use the engine (pillars +
  batching + repurposing) to get the most from it.

A focused strategy on one channel, run by one person sustainably, beats an ambitious multi-channel
plan that burns out. Build the engine to the capacity, not the fantasy.


---
资料：Frank Heijdenrijk / pavelhov/social-media-skills

原始版本：https://github.com/pavelhov/social-media-skills/blob/1680b37bf0dc32b52da247a8196ef27a6cd47bd4/skills/social-strategy/references/operating-model.md

许可：MIT。目录与内部链接已经整理，未收录图片已省略。

MIT License

Copyright (c) 2026 Frank Heijdenrijk

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.