Principle

Split a message when it asks for unrelated decisions

Bundling saves sending effort but increases routing ambiguity.

Work through the ideaIllustrative example

Let separate asks close separately.

A room-layout decision and an account-access request have different owners and evidence.

Blank cream letter sheets and a dark binder clip in a mustard envelopeA draft you can inspect

Two jobs share a waiting thread.

One answer could leave the other request looking covered.

Please approve layout B and restore the shared-folder account. We need both for the workshop.
What justifies splitting these requests?

Different owners, evidence and independent closure, rather than a preference for shorter messages.

Do not fragment tightly coupled choices that need a shared trade-off.

VedokrokKeep the idea. Try the next move.

Before you use it

Use when
  • One long message asks different people to decide unrelated things.

Keep this limit in mind

  • Do not fragment tightly coupled choices that need a shared trade-off; split only when independent closure improves coordination.

Why it matters

Keep one dominant coordination job per message or section. If two decisions have different owners, deadlines or evidence, split them into separate messages or clearly isolated sections so each can close independently.

An example

A design approval and a production access request become separate asks because different people own them.

Check your result

Each decision can be answered without resolving an unrelated issue.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading
Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingSplit a message when it asks for unrelated decisions

Evidence and sources
Supports

CDC guidance recommends lists, chunks and descriptive headings to make information easier to scan and organize.

Very short messages may not need headings; structure should match complexity.

Description and Examples of Index Items · Core items 8 through 10

Supports

ONS guidance recommends writing around user needs, removing content that does not serve those needs, and using concise task-focused headings.

Regulated or audit-heavy work may require context that feels redundant to the immediate reader.

Writing and editing: Plain language · Put users' needs first; titles and headings; be concise

All sources (2)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details