Artículo a hilo social

# Why we stopped answering email at night

By Jonas, Tern Studio

Tern Studio is a six-person design studio. Last spring we noticed that late replies had become a habit: someone would answer a client at 10pm, and the next morning three more messages waited.

So we ran a four-week trial. We set quiet hours from 7pm to 8am. Nobody answers email in that window. For real emergencies, clients get a phone number that rings one person on call.

What happened? Two people on the team told us they slept better. Clients did not complain, and nobody used the emergency number during the trial. We did have to explain the new hours to two clients, and both said they understood.

The hardest part was the first week. Old habits are strong, and we caught ourselves opening the inbox out of reflex. Deleting the mail app from our phones helped some of us.

We decided to keep the quiet hours. If you try this, tell your clients first, give them an emergency route, and agree on the rules as a team before you start.

# Thread and posts: Why we stopped answering email at night

## Thread
1/6
Tern Studio, a six-person design studio, stopped answering email at night. We set quiet hours from 7pm to 8am and ran a four-week trial.

2/6
The quiet hours rule at Tern Studio is simple: nobody answers email between 7pm and 8am. Clients get a phone number that rings one person on call for real emergencies.

3/6
During Tern Studio's four-week trial, two people on the team said they slept better. Clients did not complain.

4/6
Nobody used the emergency number during Tern Studio's quiet hours trial. The studio did explain the new hours to two clients, and both said they understood.

5/6
Quiet hours at Tern Studio were hardest in the first week. The team caught itself opening the inbox out of reflex, and deleting the mail app from phones helped some of them.

6/6
Tern Studio is keeping its email quiet hours. Advice from the team: tell clients first, give them an emergency route, and agree the rules as a team. [link to post]

## Standalone posts
A
Late replies had become a habit at our six-person studio, so we tried email quiet hours from 7pm to 8am for four weeks.

B
Before you try email quiet hours: have you told your clients, and given them an emergency route?

C
Two people on our team said they slept better after four weeks without night email.

## Claims check
| Post | Source claim | Characters |
|---|---|---|
| 1/6 | Six-person studio; quiet hours 7pm to 8am; four-week trial | 136 |
| 2/6 | Nobody answers in the window; one person on call by phone | 167 |
| 3/6 | Two people slept better; clients did not complain | 110 |
| 4/6 | Emergency number unused; two clients got an explanation | 156 |
| 5/6 | First week hardest; reflex inbox checks; deleting mail app helped some | 173 |
| 6/6 | Keeping the hours; tell clients, emergency route, agree as a team | 163 |
| A | Late replies a habit; six people; 7pm to 8am; four weeks | 119 |
| B | Tell clients first and give an emergency route | 96 |
| C | Two people slept better after the four-week trial | 83 |

---
name: blog-to-social-thread
description: Turns a blog post into a six-post thread plus three standalone short posts, where every post makes sense on its own and adds no claims beyond the article. Use when someone wants to repurpose a finished article for social media.
---
# Blog To Social Thread
One blog post in, a 6-post thread and 3 standalone posts out.

## When to use
- You have a finished blog post and want social copy that stays faithful to it.
- You need posts that work when seen alone, not only inside the thread.

## Inputs
- The blog post text or file. Ask for it if missing.
- Platform and character limit (default 280 characters per post). Ask if the platform is unclear.
- Optional: the link placeholder to use, the author voice, hashtags to avoid.

## Steps
1. Read the post and list its claims, facts, numbers and quotes in a "Source claims" list.
2. Pick the one main idea and the 5 supporting points that matter most.
3. Write the thread of 6 posts: post 1 states the main idea, posts 2 to 5 each carry one supporting point, post 6 gives the takeaway and the link placeholder "[link to post]".
4. Make each post stand alone: name the subject in every post, never write "as above", "next" or "this" without a noun, and keep numbering outside the text.
5. Write 3 standalone short posts, each under 200 characters, each from a different angle (a lesson, a question, a single fact from the post).
6. Count the characters of every post with code or a careful count, and shorten any post over the limit.
7. Add a Claims check: every post matched to its source claim.

## Output
Write `thread.md` with: `## Thread` (posts labelled 1/6 to 6/6), `## Standalone posts` (A, B, C), `## Claims check` (post, source claim, character count).

## Rules
- Never invent facts, numbers, results or quotes. A post may only restate what the article says.
- Do not add new advice, opinions or statistics. Do not turn an anecdote into a general rule.
- No fake scarcity, no engagement bait, at most one hashtag per post.
- Mark uncertain items with "[confirm]" and ask before assuming the platform limit.
- Write results to a new file, never overwrite the blog post.
- Keep private data local. Legal, medical, tax and financial claims are out of scope: flag them for a professional and do not advise.