# Zuporta content selections · October 27, 2026 · 02:00 · hook-v3

Research-first correction: 16 LinkedIn + 16 Substack options. Proposed language for author review; no social publication is performed. Original collection remains available separately.

## Substack

### Sheila

#### Option 05 · The useful test is the question your bot cannot answer · Note

<!-- COPY START -->
An automation demo usually knows the question before you ask it.

Your customer will not.

Choose an exception your business actually sees: a change outside normal availability, an unclear service request, or a question involving an existing commitment.

Then test the route around the automated answer. Can the customer reach a person? Does the next person receive enough context? Are the promised timing and available support consistent?

The goal is to discover where human responsibility needs to remain visible. It is a useful conversation to have with your team or a supplier before agreeing to the scope.

At Zuporta, I want an honest limit and a clear next step to be part of a good customer experience.
<!-- COPY END -->

Hook basis: Use an exception to expose the gap between an impressive demo and a usable service.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 06 · Do you need to automate that step at all? · Note

<!-- COPY START -->
The recurring reminder may be pointing to an earlier problem.

An incomplete instruction creates a clarification. A missing owner creates a chase. Duplicate data entry creates a reconciliation task.

Before automating one of those follow-ups, ask what caused it. Then ask whether the original step can be made clearer or removed within the commitments you already have.

A useful review fits on one page: recurring task, reason it exists, person affected, and smallest safe change to test.

Keep anything required for accuracy, consent, or an agreed service. The aim is to remove avoidable work without losing its purpose.

This is the kind of question I want Zuporta to ask before proposing more technology.
<!-- COPY END -->

Hook basis: Use a useful reversal: remove an unnecessary task before speeding it up.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 07 · A long feature list will not explain your next step · Note

<!-- COPY START -->
A feature list can grow while the decision stays difficult.

The reader learns what is possible, but cannot tell which problem the service addresses, what to send you, or what happens after they make contact.

Try a three-sentence check on a service page:

This is the kind of business problem we can discuss.
This is the information that helps us understand it.
This is the next step, including what still needs agreement.

Use the business’s actual process rather than an idealized version. An inquiry is not an accepted project. A proposed plan is not work already delivered.

I want Zuporta’s service conversations to make those decisions easier. Clear scope begins before the sale.
<!-- COPY END -->

Hook basis: Contrast abundant product detail with the buyer’s unanswered practical question.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 08 · A small promise your team can actually keep · Newsletter

<!-- COPY START -->
A small promise your team can actually keep
Turn a brand statement into one observable action.

A promise is useful when the team knows how to keep it.

“We care about our customers” can mean many things. The person answering an inquiry still needs to know what they can confirm, when they should ask for help, and what to say when an answer is not ready.

As Zuporta’s founder, I want our work to connect that customer promise with the way the team operates.

Here is a small review an owner can run with the people doing the work. Pick one public promise. Ask what a customer should notice because it is true. Turn the answer into an observable action: a clear next step, a realistic update, a complete handoff, or an honest explanation of a limit.

Next, ask what makes that action difficult. Information may be scattered. The team may be waiting for a decision. An automated message may imply more than the service actually offers.

Choose one gap to address. Give it an owner and a way to check the result. Review an actual permitted example after the change instead of assuming that writing the rule made it work.

This is a practical foundation for service, people support, and automation. It also gives a founder something meaningful to write about without inventing a dramatic story.

Which promise would your team choose to make easier to keep first?
<!-- COPY END -->

Hook basis: Ground founder positioning in a concrete promise and the operating decisions behind it.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Egelyn

#### Option 05 · Copying the same detail twice deserves a question · Note

<!-- COPY START -->
Two copies can become two versions of the truth.

An appointment detail changes in one place. Another person still reads the earlier version somewhere else.

Before automating the copying, I would ask which record people should trust and who can change it. That conversation helps protect the work the records are meant to support.

As an administrator, I appreciate technology taking care of repetitive steps with our team. I also want to understand the route well enough to notice when something needs a person.

Choose one repeated detail in your own business. Follow it from the first message to the place the team acts on it. Any disagreement between those two is worth reviewing.
<!-- COPY END -->

Hook basis: Use a small visible repetition to uncover an avoidable operating burden.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 06 · An appointment request is still a question · Note

<!-- COPY START -->
The calendar can look organized while the appointment is still uncertain.

A client may have requested a time. A team member may still need to check it. A confirmation may not have been sent.

As an administrator, I want those states to be easy to distinguish. It helps me know what to do next and what I can honestly tell the client.

For a service business, review one route from request to confirmation. Name the person who can approve the time. Check the wording the client sees. Decide where a change or exception goes.

Only then review the reminder. It should support an agreed appointment rather than hide uncertainty behind a polished message.
<!-- COPY END -->

Hook basis: Expose the difference between a reassuring screen and a confirmed commitment.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 07 · The reminder I want to stop carrying · Note

<!-- COPY START -->
The work that stays in my head is often waiting for someone else.

I have passed on the request, but I still need to remember to check whether it moved.

As a busy administrator, I want that follow-through to be clearer. As a mother with my own business ambitions, I also want to finish a task without carrying every reminder into the rest of my day.

An owner can start by asking the team which handoffs they keep checking manually. Choose one. Name who owns the next action, how the status will be visible, and when a check is actually needed.

Technology may support that route. Agreeing what the route should do comes first.
<!-- COPY END -->

Hook basis: Turn a personal burden into a clear operating question for an owner.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 08 · Give the backup person a usable handoff · Newsletter

<!-- COPY START -->
Give the backup person a usable handoff
A name, a status and enough context to act.

Naming a backup is the beginning of a handoff.

The next person still needs enough context to act without guessing.

With unreliable internet and limited time, I want the work around me to be understandable when I am unavailable. Our team’s help with repetitive work matters. So does making it clear what a person should take over.

Here is a handoff I would want to receive. It identifies the request, explains its current status, records what the client has been told, and names the next action. It also says which decisions are already agreed and which need review.

That can be short. The goal is to include what changes the decision, not every line of a long conversation.

For example, a requested appointment time and a confirmed appointment time are different. A client asking about a service and a client who has accepted a scope are different. The backup person should not have to infer either from a friendly message.

An owner can test the handoff with one recurring task. Ask a person who did not prepare it to explain what they would do next. If the answer differs from the intended route, improve the record together.

This is a practical way to support the administrator as well as the customer. It gives the next person something useful to work from when ordinary life interrupts the plan.
<!-- COPY END -->

Hook basis: Challenge the assumption that naming a backup is enough; make missing context tangible.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW), [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Angelo

#### Option 05 · An escalation rule should fit inside a real decision · Note

<!-- COPY START -->
A person can be willing to take responsibility and still be unsure what they are allowed to decide.

That uncertainty deserves a conversation before it becomes a judgment about their confidence or ability.

As a people leader, I want expectations to be usable. Choose one recurring decision. Explain the outcome, the information needed, and the condition that requires another review. Ask the person how they would handle an ordinary case and an exception.

Then review the real work together when appropriate. Which part of the boundary helped? What was missing?

This is a practical way to develop judgment while respecting responsibility. A general instruction to be more autonomous cannot do that work on its own.
<!-- COPY END -->

Hook basis: Replace vague empowerment with a specific decision boundary.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 06 · Your strongest specialist may choose a different route · Note

<!-- COPY START -->
If I want a specialist to surpass my ability, I need to leave room for a method I would not have chosen.

That does not remove standards or accountability. It makes them more important. We need to know what the work should achieve, what constraints apply, and how we will assess the result.

For an owner reviewing work, try writing feedback in two groups: requirements that affect the outcome, and preferences you are willing to discuss.

The conversation becomes more useful when the person can see the difference.

Developing people is work I care deeply about. I want the review to help them think better, not train them to guess what is in my head.
<!-- COPY END -->

Hook basis: Use a preference-versus-outcome reversal to open a concrete leadership lesson.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 07 · Routine coordination needs an exception door · Note

<!-- COPY START -->
The ordinary case is only part of a delegation decision.

Technology may help coordinate a routine step. A request that changes scope, access, money, or a people commitment needs the appropriate human authority.

As a people leader, I want that difference to be visible before routine work is handed over.

Choose one workflow. Write down what it may do, what information it uses, and the exception that should stop or redirect it. Test the ordinary case and that exception separately.

This is a way to make responsibility concrete. It does not establish that every workflow already has the controls it needs.

The useful question for an owner is where a person must still be able to see, understand, and decide.
<!-- COPY END -->

Hook basis: Expose the edge case hidden inside a promise of autonomous coordination.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 08 · Delegation should make room for development · Newsletter

<!-- COPY START -->
Delegation should make room for development
A task handoff can also be a chance to build judgment.

I want delegation to create room for people to grow.

If every handoff returns as another approval request, I have changed the shape of my task list without changing the way responsibility works.

The work I love most is developing people who can outperform me in their own fields. To move toward that, I need to understand what each responsibility requires and what support the person needs to carry it.

Start with one task that matters. Define the outcome and the boundaries. Check capability honestly. A person may need training, better information, a smaller first assignment, or help from somebody with stronger expertise.

Next, agree on the decisions they can make and the exceptions that should come back. Technology may help with routine coordination, but it does not replace the need for those agreements.

Finally, make the review useful. Look at the work and the reasoning behind it. Ask what was difficult and what support would improve the next attempt. Give feedback that helps the person develop judgment rather than simply copy your method.

This takes attention. That is why I want trivial work handled by suitable people and technology within clear responsibilities.

For an owner, the next step can be one conversation about one responsibility. Make the handoff specific enough that both people know what growth would look like.
<!-- COPY END -->

Hook basis: Connect a familiar management goal to the less visible work it should enable.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Jed

#### Option 05 · The wrong metric can make weak research look productive · Note

<!-- COPY START -->
One number can hide several different stages of work.

In AI-supported business development, I want to distinguish prepared research, reviewed fit, authorized outreach, real replies, and agreed next steps. A sale belongs further along and needs its own evidence.

That makes the report less impressive-looking in some cases. It makes the decision more useful.

For an owner, choose one metric and ask the team to show an example of the event it counts. Then ask what the number cannot tell you.

If generated records and qualified opportunities are mixed together, separate them before deciding to scale. Data helps when the label matches what actually happened.
<!-- COPY END -->

Hook basis: Reveal a hidden quality failure behind a flattering output metric.

Measured examples: [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 06 · A hook creates a debt the post has to repay · Note

<!-- COPY START -->
The first two lines make a promise about the reader’s time.

The body needs to keep it.

If a post opens with a problem about client messages, I want it to explain a useful check: where the request goes, who owns the next action, or what happens when the normal route fails.

That is different from using a striking opening to introduce a broad list of services.

My review of an AI-assisted draft starts with the promised payoff. Can I underline the part that delivers it? Can the reader try the idea without contacting us first? Does the business connection follow naturally?

This helps me make content more useful before trying to produce more of it.
<!-- COPY END -->

Hook basis: Use a memorable business metaphor, then demonstrate the promised reader payoff.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Sabrina Ramonov](https://www.sabrina.dev/p/ai-content-multiplication-3-million-followers). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 07 · A source link is useful only if it supports the sentence · Note

<!-- COPY START -->
The link at the end of a sentence does not do the verification by itself.

I still need to open the source and compare it with the claim.

In content research, I want the engagement on the actual post rather than a creator’s audience size. In commercial research, I want to separate what a company publicly shows from what I assume about its internal work.

Those are ordinary distinctions, but an AI summary can blur them very smoothly.

A useful check takes three claims from a report and asks: where is the supporting evidence, how current is it, and what part remains interpretation?

I want data to make decisions clearer. A citation that cannot carry the claim adds confidence without adding understanding.
<!-- COPY END -->

Hook basis: Contrast the appearance of evidence with a small verification action.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 08 · One business problem, two platform-native posts · Newsletter

<!-- COPY START -->
One business problem, two platform-native posts
Adapt the idea and the payoff instead of duplicating the body.

One useful idea can support more than one post. It still needs editing for the place where people will read it.

For Zuporta, I want Substack to hold the fuller thinking and LinkedIn to introduce a focused professional lesson. AI can help prepare both versions, but the job is to preserve the idea rather than duplicate the paragraphs.

Take a service-business problem such as an inquiry that has no clear owner. The Substack version can explain the route, explore an ordinary request and an exception, and offer a small review the owner can run with the team.

The LinkedIn version might begin with the moment the customer is left waiting. It can give one useful distinction and a compact action: find the owner, next step, and expected update in the first reply.

Both pieces should help without a click. Both should keep proposed workflows separate from features that are actually available. Neither needs an invented client story to make the problem concrete.

Before publishing, review the author’s voice and check that the body delivers what the opening promised. After publication, observe the real response: useful questions, relevant conversations, and any next steps the audience actually takes.

A copied draft is still a draft. A post’s reaction count is not a sale. Keeping those differences clear helps me learn what to improve next.

Begin with one useful idea. Give each version a reason to exist.
<!-- COPY END -->

Hook basis: Make the production shortcut visible, then replace duplication with a usable adaptation process.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Sabrina Ramonov](https://www.sabrina.dev/p/ai-content-multiplication-3-million-followers), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

## LinkedIn

### Sheila

#### Option 05 · The useful test is the question your bot cannot answer · Post

<!-- COPY START -->
Ask your automated reply a question it was never trained to answer.

The interesting part is what happens next.

Does it admit uncertainty? Give a usable human route? Explain what information to include? Make a promise the team can keep?

A polished answer to the easy question is only one part of customer support.

Before accepting an automation proposal, test an ordinary request and an awkward exception. Have the people responsible for follow-up review both.
<!-- COPY END -->

Hook basis: Use an exception to expose the gap between an impressive demo and a usable service.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 06 · Do you need to automate that step at all? · Post

<!-- COPY START -->
Before you automate the reminder, check why the reminder exists.

Perhaps the original instruction is unclear. Perhaps two systems ask for the same information. Perhaps nobody owns the next step.

Automating the chase can make a broken route run more often.

Choose one recurring reminder this week. Ask the team what would make it unnecessary. Fixing the original handoff may be simpler than building a new sequence around it.

That question belongs near the start of an automation conversation.
<!-- COPY END -->

Hook basis: Use a useful reversal: remove an unnecessary task before speeding it up.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 07 · A long feature list will not explain your next step · Post

<!-- COPY START -->
Your customer may understand every feature and still not know what to do next.

A service page needs to answer an ordinary question: “How do I find out whether this fits my business?”

State the next step, what information is needed, and what that step does—and does not—confirm.

For Zuporta, the path is Diagnostic → Action Plan → Execution. The scope still needs to be agreed.

Read your own service page aloud. Where would a first-time visitor need to ask you to explain the process?
<!-- COPY END -->

Hook basis: Contrast abundant product detail with the buyer’s unanswered practical question.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 08 · A small promise your team can actually keep · Post

<!-- COPY START -->
“We care about customers” is easy to put on a website.

The harder question is what your team should do differently because of it.

For me, it begins with clear ownership, realistic updates, and a human route when the ordinary process does not fit.

Choose one promise your business makes. Ask the people delivering it what information, authority, and support they need to keep it.

The answer may improve your next sales conversation more than a stronger adjective.
<!-- COPY END -->

Hook basis: Ground founder positioning in a concrete promise and the operating decisions behind it.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Egelyn

#### Option 05 · Copying the same detail twice deserves a question · Post

<!-- COPY START -->
If I have to copy the same appointment detail twice, I want to know why.

Sometimes two records serve different purposes. Sometimes we have simply kept an old step nobody questioned.

The repetitive work our team automates gives me a reason to look more closely at what can be simplified.

Pick one detail your admin team re-enters. Check who uses each copy, which version is authoritative, and what would break if the extra step went away.

Understand the job before connecting the tools.
<!-- COPY END -->

Hook basis: Use a small visible repetition to uncover an avoidable operating burden.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 06 · An appointment request is still a question · Post

<!-- COPY START -->
An appointment request is still a question until somebody confirms it.

That difference matters when I am helping with admin work.

I want to know which time the client asked for, who can check availability, and what message confirms the answer. A reminder cannot fix an appointment that was never agreed.

Open your own booking route as a new client. Does it distinguish a request from a confirmation?

Clear wording gives the administrator and the client the same starting point.
<!-- COPY END -->

Hook basis: Expose the difference between a reassuring screen and a confirmed commitment.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 07 · The reminder I want to stop carrying · Post

<!-- COPY START -->
A task can leave my screen and still follow me through the day.

That happens when I have to remember whether somebody else has done the next step.

I want more room for my own business and family life. Team-supported automation helps with repetitive work; clear handoffs help with the reminders left around it.

Ask your administrator: “Which task do you keep thinking about after you close it?”

The answer may point to a missing owner, an unclear status, or a decision waiting too long.
<!-- COPY END -->

Hook basis: Turn a personal burden into a clear operating question for an owner.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 08 · Give the backup person a usable handoff · Post

<!-- COPY START -->
A backup person cannot work from “just check the inbox.”

They need to know what is open, what was promised, and which decisions they can make.

That matters to me when my connection is unreliable and somebody else may need to pick up a task.

Try a small handoff: one request, its current status, the next action, and the point where help is needed. Ask the backup person to explain it back.

You will find the missing detail faster than by adding another reminder.
<!-- COPY END -->

Hook basis: Challenge the assumption that naming a backup is enough; make missing context tangible.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW), [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Angelo

#### Option 05 · An escalation rule should fit inside a real decision · Post

<!-- COPY START -->
“Use your judgment” is a difficult instruction when nobody knows where the boundary is.

Give the person a real decision to work with.

What can they approve? Which information matters? What changes the commitment enough to bring it back for review?

For me, developing people includes making that boundary understandable and reviewing what they learn from using it.

Try it with one routine task before writing a broad empowerment statement. Can the person explain when they would act and when they would ask?
<!-- COPY END -->

Hook basis: Replace vague empowerment with a specific decision boundary.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 06 · Your strongest specialist may choose a different route · Post

<!-- COPY START -->
The person I am developing may eventually disagree with my method—and be right.

That is part of wanting specialists who outperform me in their own fields.

I need to make the outcome and constraints clear enough that we can discuss the work on its merits. “I would do it differently” is not always a reason to change it.

Choose one piece of work you are reviewing. Which feedback protects the result? Which feedback is only your preferred route?

That distinction gives a specialist room to grow.
<!-- COPY END -->

Hook basis: Use a preference-versus-outcome reversal to open a concrete leadership lesson.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 07 · Routine coordination needs an exception door · Post

<!-- COPY START -->
Routine coordination becomes risky when an exception looks like an ordinary task.

A reminder is one thing. Changing a commitment is another.

I want technology helping manage agreed routine work while suitable people remain responsible for the decisions that need them.

Before handing over a workflow, name the exception that should stop it or bring in a person. Then test whether that exception is recognized.

Clear limits make useful autonomy easier to discuss. “Handle everything” does not give a team enough to work with.
<!-- COPY END -->

Hook basis: Expose the edge case hidden inside a promise of autonomous coordination.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 08 · Delegation should make room for development · Post

<!-- COPY START -->
If delegation only gives me more tasks to approve, I need to review the handoff.

I want it to make room for work that needs my attention—including developing people.

That means matching responsibility with capability, providing support, and agreeing which decisions belong where. Technology can help coordinate routine work around those agreements.

Choose one responsibility you want to hand over. What would the person need to handle it well? What would you stop checking? What would you review together?

Those answers are the beginning of a development plan.
<!-- COPY END -->

Hook basis: Connect a familiar management goal to the less visible work it should enable.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Jed

#### Option 05 · The wrong metric can make weak research look productive · Post

<!-- COPY START -->
A research process can look productive while producing nothing you can act on.

“Records generated” answers a different question from “records reviewed as relevant.” A drafted message is different from a reply. A reply is different from an agreed next step.

I want the numbers in my work to keep those stages separate.

Choose one metric on your marketing report. What happened in the real world for it to increase? If nobody can explain that clearly, define it before using it to choose your next action.
<!-- COPY END -->

Hook basis: Reveal a hidden quality failure behind a flattering output metric.

Measured examples: [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 06 · A hook creates a debt the post has to repay · Post

<!-- COPY START -->
A hook creates a debt. The rest of the post has to repay it.

If I promise a way to find missed handoffs, the reader should leave with a way to inspect one. A dramatic first line followed by a generic sales pitch does not do that.

When reviewing an AI draft, I check three things: the opening’s promise, the concrete substance, and the next step the reader can take.

The goal is attention from relevant people—and something useful when they give it.
<!-- COPY END -->

Hook basis: Use a memorable business metaphor, then demonstrate the promised reader payoff.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Sabrina Ramonov](https://www.sabrina.dev/p/ai-content-multiplication-3-million-followers). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 07 · A source link is useful only if it supports the sentence · Post

<!-- COPY START -->
A source link can make a weak claim look well researched.

Open the link. Does it support the sentence beside it?

An author’s follower count is not the engagement on one post. A software demo is not proof that a client uses it. A company’s booking page does not reveal its missed-appointment rate.

When AI prepares research for me, I want that check built into my review.

Try it on three claims in your next report. Keep the statement no broader than the evidence.
<!-- COPY END -->

Hook basis: Contrast the appearance of evidence with a small verification action.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 08 · One business problem, two platform-native posts · Post

<!-- COPY START -->
Copy-pasting a newsletter into LinkedIn saves a step. It may also lose the point.

I want to carry the idea across, then rebuild it for the reader’s situation.

Start with one business problem. Use Substack to explain the reasoning and a practical example. Give LinkedIn one focused lesson and a next action that stands on its own.

Keep the facts and the author’s voice consistent. Change the structure when the platform needs it.

That is a better use of AI in my content work than multiplying identical text.
<!-- COPY END -->

Hook basis: Make the production shortcut visible, then replace duplication with a usable adaptation process.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Sabrina Ramonov](https://www.sabrina.dev/p/ai-content-multiplication-3-million-followers), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

