What Did That Thumbs-Up Sign Off On?

A Slack thread just got three reactions on Claim_V3: a thumbs-up from the brand manager, eyes from account, and a heart from the creative director. Someone else drops "LGTM" as a reaction, not a message. Design asks if they can start the end card. Traffic asks if the hero is locked. You are the creative project manager. The channel looks friendly. Nobody wrote a close in the thread. A reaction got treated as if it were a lock — and the round stays open while everyone pretends the emoji closed it.

This is not a Slack etiquette problem. You can teach "use words" forever and still accept a thumbs-up as approve. The failure is structural: a reaction without a written close in the thread is not a lock. It shows support, not a decision. Until you get a written close in the same thread, thumbs-up, eyes, heart, "LGTM," and "+1" will keep the work looking decided while the lock never lands.

The Wrong Diagnosis Is Always Better Emoji Hygiene

The room will tell you people are busy, that reactions are faster than typing, or that "everyone knows a thumbs-up means yes" so you should stop being pedantic.

You pin a Slack etiquette note. You ban hearts on decision threads. You ask people to "please reply in words." Next week still arrives with the same thumbs-up on Claim_V3, because reaction volume was never the constraint.

A reaction that names no object is not a fast approval. It is no decision. The problem is not how cute the emoji is. The problem is that the channel accepted a glyph as if it closed something. Creative teams treat thumbs-up as warmth. Account treats eyes as "I'm watching." Leadership treats "LGTM" as technical sign-off. The round treats all of it as permission to move.

More etiquette will not fix this. This post is what to do when a Slack reaction lands on an open creative decision — and how you refuse an emoji, "LGTM," or "+1" that never becomes a written lock.

A Reaction Without a Written Close Is an Open Round

That is the structural problem.

Most creative teams treat reactions as progress. Thumbs-up sounds affirmative. Eyes sounds attentive. Heart sounds supportive. "LGTM" sounds like engineering rigor. "+1" sounds like consensus. None of them is a written close: a sentence in the thread that says what was decided and survives a screenshot tomorrow. So Round 2 stays Round 2. Design keeps holding capacity. Status can still look Green. The board can show activity. The decision never closed.

A real lock from Slack needs four things in writing in the same thread — not only in the reaction tray:

1. Named object (Claim_V3, hero layout, end card, offer, colorway — not "the work," "this," or the whole channel)
2. Named decision type (approve / revise with criteria / kill / reopen with cost — not "vibes," "LGTM," or "+1")
3. Named owner who can close it (brand manager, legal, creative director — not "the group," not "reactions look good")
4. Written close in the thread (a sentence that states the lock — not a glyph that disappears when someone clears reactions)

Without those, the reaction is not a decision. The tone can look collaborative. The emoji can look unanimous. The round is still open.

This sits next to three posts you may already know:

• Approved With Comments Is Not a Lock: a soft written yes with caveats that reopen.
• Your Status Is Green. Concept Is Still Open.: board color lying about locks.
• I'll Circle Back Is Not a Decision Date: time phrases pretending to be a plan.

This post is the reaction tray that pretends emoji is a decision system.

Reaction Rules Before You Treat Slack Like a Lock

Do not ban warmth. Ban warmth that replaces a written close. Write these rules into the thread the moment the reaction lands on an open object — before you move the card, before design starts the end card, before traffic hears "it's approved."

1. Translate every reaction into a written decision sentence

Thumbs-up is not approve. Eyes is not "I own the review." Heart is not brand lock. "LGTM" as a reaction is not a named owner's close. "+1" is not consensus with authority. Reply with the sentence you need — or ask for it. If they will not write the close, they have not approved. They have reacted while keeping the round open.

2. Name the object in the same sentence as the close

A reaction on a message that contains three attachments is not a lock on any of them. "Brand manager approves Claim_V3 — hero claim only; layout and end card still open." Not "looks good" on a thread that mixed claim, layout, and offer. Reactions attach to messages. Locks attach to named objects and versions.

3. Name who can close it — reactions are not a vote

If five people thumbs-up and the brand manager stays silent, you do not have a lock. You have a popularity contest. Write the named owner. Account may react. Account may not substitute for the brand manager's written yes. The CPM owns the lock sentence in the channel. The named approver owns the answer.

4. Separate acknowledgment reactions from decision reactions

Eyes can mean "seen." Heart can mean "thanks." Thumbs-up can mean "got it." None of those are approve / revise / kill. If the channel uses the same glyphs for courtesy and for lock, you must force the decision type in words. Courtesy reactions are fine. Courtesy reactions that move the board are not.

5. Price what "reaction-as-lock" costs when it unravels

When yesterday's thumbs-up becomes today's "wait, I only meant I saw it," name the cost: round slip, design redo, freeze risk, dropped size, overtime. Reaction locks love deniability: a reaction is easy to walk back, and design pays for the redo. Cost the unwind, or the emoji will keep winning.

6. Do not move the board to Approved on a reaction tray

Moving the card to Approved on reactions alone makes the board look decided when nothing has closed. Approved is only honest when the thread already holds object + decision type + owner + written close.

The Sentences That Stop Reaction-as-Lock

A reaction rule nobody defends is decoration. These are the lines to send when someone tries to replace a written close with a glyph.

1. Thumbs-up on Claim_V3 with no words

They say: (thumbs-up reaction on the Claim_V3 mock)

Do not send: "Awesome — locking Claim_V3."

Send:

"Reading the thumbs-up as acknowledgment only until I have a written close on Claim_V3 in this thread: one sentence that says approve, revise with criteria, or kill. Until that sentence lands, the round stays open and I will not treat a reaction as approve. Reply with the close or say you cannot decide yet — those are different sentences."

Why it works: you respected the human without accepting a glyph as a schedule.

2. Eyes from account, then "we're good"

They say: (eyes reaction) then in a side DM: "we're good — they saw it"

Do not send: "Copy — marking approved."

Send:

"Eyes means seen, not locked. I need the brand manager's written close on [Object]_[Version] in the decision thread — approve, revise with written criteria, or kill. Account can confirm they saw it; account cannot substitute a reaction for the named owner's sentence. Until that sentence exists, design holds and the board stays open."

Why it works: you refused to launder a lock through a DM translation of an emoji.

3. Heart from the creative director on a mixed message

They say: (heart on a Slack message that includes Claim_V3, hero layout, and end card)

Do not send: "Love it — locking the package."

Send:

"Heart noted as support. Which object is closed? Claim_V3, hero layout, end card, or all three? I need a written line per object from the named owner. A reaction on a mixed message is not a lock on every attachment. Reply with object + decision type per piece or I keep all three open."

Why it works: you forced object boundaries the reaction tray cannot express.

4. "LGTM" reaction from someone who cannot approve

They say: (LGTM reaction from a coordinator or junior designer)

Do not send: "Ship it — LGTM."

Send:

"LGTM from [Name] is peer signal, not the lock. Locking owner for [Object]_[Version] is [Brand manager / CD / Legal]. Need their written approve / revise / kill in this thread. I will not move traffic or the board on a reaction from someone who cannot close the object."

Why it works: you separated useful peer signal from authority.

5. "+1" pile-on treated as consensus

They say: four "+1" reactions, no named owner sentence

Do not send: "Consensus — locking."

Send:

"+1 is not a decision type and pile-on is not an owner. I need one named person who can close [Object]_[Version] to write approve, revise with criteria, or kill. Until that sentence lands, reactions stay social and the round stays open. If nobody can own the close, say so — that is an honest open, not a fake lock."

Why it works: you refused to let a count of reactions stand in for an approver.

6. Brand manager reacts thumbs-up, then later "I only meant I saw it"

They say: "Wait — the thumbs-up was just 'got it,' not approve."

Do not send: "No worries!" and leave the board on Approved.

Send:

"Thanks for clarifying. I am reverting [Object]_[Version] to open. Going forward I will not treat reactions as locks on this thread. Need a written close from you in this thread when you are ready. Cost of the unwind: [round slip / design hold / freeze risk]. Confirm the object is open so traffic does not pull a false FINAL."

Why it works: you priced the unwind and reset the board without blaming anyone.

7. Leadership asks why you will not "just take the thumbs-up"

They say: "Why are we forcing essays? A thumbs-up is clear enough."

Do not send, in the leadership thread: "Stakeholders never write complete sentences."

Send, privately to account or your lead first, then one clean line upstairs:

"We are not forcing essays. We are refusing to treat thumbs-up / eyes / heart / LGTM / +1 as a lock. Without a written close, the round stays open while the reaction tray looks decided. I offered a one-sentence lock template. Waiting on glyphs is how capacity dies quietly when someone clears a reaction tomorrow. Happy to lock the moment a real close exists in the thread."

Why it works: you refused the blame story and reported the missing objects.

What Changes When Reactions Cannot Replace Written Locks

Rounds close in sentences or they stay honestly open. Designers stop starting end cards on a thumbs-up. Account stops translating eyes into "we're good." Brand managers learn that approve needs words, not a glyph. Traffic gets a written decision instead of guessing from emoji. Status can say Approved only when a written close already exists. Leadership sees deniable reactions lose to dated written closes.

In-house, there may be no agency account lead. There is still a brand manager, a creative director, and a Slack that loves reaction shortcuts. Same rule. Warmth does not close the claim.

In production environments, picture-lock already demands a named slate, not a vibe. Steal that. "Brand manager approves Claim_V3 — hero claim only" belongs in Slack the same way a lock note belongs on a call sheet.

None of this requires a new Slack app. It requires refusing to let the reaction tray authorize an open round forever.

Frequently Asked Questions

Is every thumbs-up a failure?

No. Thumbs-up plus a written close in the same thread is optional color on a real lock. Thumbs-up alone is an open round with manners. Whether the written close exists decides which one you have.

What if the stakeholder truly only meant "seen"?

Write that. "Seen — decision still open on Claim_V3" is honest. It is different from treating eyes as approve. Honest acknowledgment lets you keep capacity planned. Reaction-as-lock pretends the close exists.

Who owns forcing the written close — the CPM, account, or creative director?

The CPM owns the lock sentence in the channel. The named approver owns the yes/no. Account owns the client conversation when courtesy tries to skip the sentence. The creative director owns whether design starts the next piece on a glyph. One classification in the thread — not three private interpretations of a thumbs-up.

How is this different from Approved With Comments, Circle Back, Status Green, or One More Thing?

Approved With Comments is soft written yes with caveats that reopen mid-round. Circle Back is time phrases that never become a decision date. Status Green is board color lying about locks. One More Thing is a Friday cutdown sold as collaboration. This post is the reaction tray: emoji, LGTM, and +1 treated as approve without a written close. Same family. Different trigger.

What has to be in the thread before a reaction counts?

Named object and version, decision type (approve / revise with criteria / kill / reopen with cost), named owner, and a written close sentence. The reaction may sit beside that sentence. The reaction may not replace it. Without those, do not move the card to Approved and do not promise traffic a false FINAL.

Do I need a certification to refuse reaction-as-lock?

No. You need the habit of translating glyphs into written closes before the round pretends it has a decision. A creative-specific credential helps if you want decision closure as one system. It is not required to refuse a thumbs-up as approve.

Closing

If open rounds keep surviving on thumbs-up, eyes, heart, "LGTM," and "+1," the problem is probably not that your team needs a Slack etiquette workshop. It is that a reaction was allowed to replace a written lock — an open round wearing a friendly glyph.

You do not need another emoji policy. You need reaction rules before you treat Slack like a lock: named object, decision type, named owner, written close, and a priced consequence when yesterday's thumbs-up becomes today's "I only meant seen."

Who should skip this: if your team already translates every decision-thread reaction into a written close, courtesy glyphs never move the board, and "LGTM / +1 / thumbs-up" cannot keep a round looking locked without a sentence, you do not need this post. Keep the habit. Come back when the next reaction tray tries to pretend emoji is a decision system.

Start with Level I at $147 if you want the method first — eight self-paced modules, typically 10 to 15 hours, 70% to pass, unlimited retakes. The credential is a Certificate of Completion, emailed when you finish. It never expires. 5-day full refund if it is not the right fit. Start with Level I.

When you want the full path, the Bundle is Level I + Level II + the Creative PM AI Kit + the PM Resume Kit for $297 one-time. Bought separately those are $498, so you save $201. Self-paced. Unlimited exam retakes. Both certificates emailed when you finish — they never expire. Enroll in the Bundle.

Not ready yet? Start with the free eBook, The Essentials of Creative Project Management.

The Only Certification Built for Creative Project Managers

CPMA is the only certification built exclusively for creative project managers, developed with veterans from Disney, Google, Snap Inc., Red Bull, Sony Pictures, Accenture, and Paramount Pictures. Level I is $147. The Bundle is $297, or start with the free eBook.