SERVICE MODEL · EDITORIAL GOVERNANCE · PRIORITIZATION
The system that decides what deserves a point of view.
Prioritization should be legible, not argued case by case. I write the constraint into the model, make intake force the case, and set a bar the team is actually willing to enforce — so the hard trade-offs happen by design instead of by argument in a meeting.
ROLE
Head of Writing Studio
COMPANY
Hitachi Vantara
OUTPUT
Tier model · Intake · Activation bar
HOW I THINK
How I think about prioritization
This is how I approach prioritization on any team, before the specific model. The Writing Studio build below is it, applied.
01
Make the trade-off legible
When capacity is full, that should be a visible fact, not a judgment call defended in the moment.
02
Write the constraint into the model
State the capacity limit up front so the hard choices happen by design.
03
Force the case at intake
A request has to name its impact, deadline, and priority before it enters the queue.
04
Set a bar, and enforce it
Be willing to decline. Declining the weak work is what protects the strong.
The thinking in action
The service model that decides what earns the studio's best work.
Here's the situation, the model, and what it changed.
01 — THE SITUATION
Demand with no gatekeeping
A studio that does everything for everyone does nothing especially well. Requests arrived from every corner of Marketing, each one urgent to the person asking, none of them weighed against the others. Without a stated basis for saying yes, no, or not yet, the answer defaulted to whoever pushed hardest.
So the work that mattered most competed on equal footing with the work that simply arrived first. I wanted the reasoning behind every answer to be visible — something a requester could read, not a verdict handed down.
02 — THE MODEL
Levels of investment, stated up front
The model sorts every engagement into a service tier, and each tier carries its own commitment. What changes across them is how much of the thinking the Studio owns — from work we run end to end, down to guidance a team can pick up without us.
TIER 1 · FULL PARTNERSHIP
CAPACITY: 2–3 INITIATIVES AT A TIME
We own the work end to end.
Strategy, narrative, and execution together, for the initiatives where a strong point of view actually moves the business. The capacity limit is written into the tier itself — when the two or three slots are full, that's a visible fact, not a judgment call to defend.
TIER 2 · SUPPORTED EXECUTION
Teams execute; we set the guardrails.
Templates and editorial review keep quality consistent while the requesting team carries the work. The Studio stays in the loop where judgment matters, without absorbing the whole project.
TIER 3 · SELF-SERVICE
Teams serve themselves.
Published guidelines and asset libraries let teams handle routine work on their own — which protects the higher tiers for the work that genuinely needs them.
03 — INTAKE
Intake that forces the case to be made
A request can't enter the queue as a vague ask. Before anything moves, the requester has to make the case in writing — and the form itself does quiet triage. A request that can't name why it matters usually answers its own question.
Business impact
What changes if this ships — and what it costs if it doesn't.
The real deadline
The date the work is actually tied to, not a placeholder “ASAP.”
Corporate priority
The named company priority this work is meant to advance.
04 — ACTIVATION FRAMEWORK
A bar for what's worth amplifying
Layered on top is a framework for awards and analyst recognition. Not every mention deserves a campaign behind it. Each recognition gets weighed against a set standard, and the framework is willing to decline — coverage that doesn't clear the bar doesn't get activated.
That restraint is the point. Declining the weak recognitions is what keeps the strong ones from being diluted.
CRITERION 01
Source credibility
How much authority the recognizing body actually carries.
CRITERION 02
Competitive benchmark
Whether it puts us ahead of the field or just alongside it.
CRITERION 03
Audience alignment
Whether the people we're trying to reach give it any weight.
The defaultIf it doesn't clear the bar, it doesn't get activated.
05 — CADENCE
Publishing against clocks we don't control
The system runs to an external calendar. Recognitions and reports arrive on their own schedule, and the Studio publishes against them at a roughly monthly cadence. Knowing which clock is coming next is what lets the tier model plan capacity ahead of time rather than react to a collision.
Partner announcements
Joint news that lands on a partner's timeline, not ours.
Analyst reports
GigaOm and Forrester cycles that reward a fast, ready response.
WEF Lighthouse
Recognition worth planning a full moment around when it comes.
06 — OUTCOME
What the model changed
The trade-offs are legible now. When Tier 1 is full, everyone can see it, and the conversation shifts from lobbying to sequencing. Requesters understand what earns full partnership, so they arrive with sharper asks. And because the calendar and the capacity are planned against each other, the Studio publishes on the beats that matter instead of discovering them late.
The real deliverable is a documented answer to the oldest question in content: what earns a point of view, and at what level.