The Story
For the first time, Patricia was not only writing for a project.
She was helping lead it.
A client had hired her to coordinate a small content update.
There were three people involved: Patricia, a designer, and another writer.
The job was not large.
But Patricia felt the difference immediately.
People were waiting for her instructions.
She opened the team chat.
The designer needed to revise the homepage.
The writer needed to shorten two sections.
Patricia needed both pieces before she could finish the final review.
She typed quickly:
Send the new homepage today.
Shorten Sections 2 and 3.
Do not change the layout.
Finish before 4 PM.
She read the message.
Clear.
Very clear.
She sent it.
Draft, sitting beside the keyboard, slowly turned toward her.
“What?”
“You have definitely solved the problem from the last story.”
Patricia smiled.
“See? Direct.”
“Extremely.”
A Reader’s Reaction
An hour later, Reed reviewed the project notes with Patricia.
He saw the team message.
He did not say anything immediately.
Patricia noticed.
“What?”
Reed looked at her.
“The instructions are clear.”
“Good.”
“But if I received this, I would wonder if you were angry.”
Patricia stared at the message.
“I’m not angry.”
“I know.”
“The deadline really is today.”
“I know.”
“So what should I change?”
Reed pointed to the first line.
“Nothing is wrong with saying what you need. But the message has only commands. No context. No reason. No sign that another person is receiving it.”
Patricia read the lines again.
Send.
Shorten.
Do not.
Finish.
A mechanical voice came from behind the laptop.
“COMMAND ACCEPTED.”
Patricia closed her eyes.
“No.”
A small metal creature rolled onto the desk.
Its body looked like a tiny office robot. A megaphone was attached to one arm.
Across its chest flashed:
NOW
It pointed at Draft.
“MOVE.”
Draft moved one step to the side.
Bossy Bot pointed again.
“FASTER.”
Reed laughed.
Patricia did not.
“Bossy Bot?”
Draft nodded.
The Difference Between Clear and Harsh
Patricia rewrote the message.
Hi everyone, please send the updated files when you can. Thank you so much!
Reed read it.
“Better tone.”
Patricia smiled.
“But now I do not know when you need anything.”
Her smile disappeared.
Draft pointed between the first version and the second.
“One is clear but harsh. The other is friendly but vague.”
Bossy Bot shouted:
“CHOOSE COMMAND.”
“No,” Patricia said.
She tried again.
Hi everyone. We need to send the final update to the client tomorrow morning, so I’d like to finish the review today.
Alex, could you send the revised homepage by 3 PM?
Mina, please shorten Sections 2 and 3 by 4 PM. Keep the existing layout so the designer does not need to rebuild the page.
If either deadline is difficult, let me know as soon as possible.
Thanks.
Reed nodded.
“Now I know what you need, why you need it, and what to do if there is a problem.”
Patricia looked at Draft.
“Too soft?”
“No.”
“Too bossy?”
Bossy Bot opened its megaphone.
Draft turned it off.
“No.”
Draftspace
The office disappeared.
Patricia stood inside a giant project board.
On one side were enormous command signs:
DO THIS.
SEND NOW.
FIX IT.
DO NOT CHANGE IT.
Bossy Bot marched underneath them.
On the other side floated soft clouds:
Whenever you have time...
Maybe...
If possible...
No rush...
Patricia walked between them.
“Neither side works.”
Draft nodded.
A path appeared in the middle.
It had four markers:
What needs to happen.
Who owns it.
When it is needed.
Why it matters.
Reed appeared beside the path.
“That is useful direction.”
Draft added one more marker:
Room to respond.
Patricia looked at it.
“So clear leadership is not just giving orders.”
“No.”
“It is making the work easier to understand.”
“And easier to act on.”
Bossy Bot tried to replace the last marker with:
OBEY.
Patricia moved it back.
The Tone Check
Back at her desk, Patricia opened DeskDraft’s Tone / Directness Check.
The tool highlighted sentences that were very commanding.
It did not tell her to remove every direct instruction.
Instead, Patricia checked:
Is the task clear?
Is the deadline clear?
Does the reader know why it matters?
Does the wording sound unnecessarily harsh?
Can the person raise a problem?
She kept:
Please shorten Sections 2 and 3 by 4 PM.
She changed:
Do not change the layout.
to:
Please keep the existing layout so the designer does not need to rebuild the page.
Same instruction.
Better context.
She changed:
Send the new homepage today.
to:
Could you send the revised homepage by 3 PM so I can include it in today’s final review?
The message still had direction.
But it no longer sounded like a list of commands from a machine.
The Team Reply
A few minutes later, the designer responded.
3 PM works for me.
Then the writer:
I can finish by 4. Thanks for explaining what needs to stay the same.
Patricia stared at the second message.
Thanks for explaining.
That felt important.
She had not made the instructions weaker.
She had made them easier to follow.
Later, the client approved the final update with only one small change.
Patricia closed the project board.
She felt tired.
But also different.
Leading the work had been uncomfortable.
Not because she did not know what needed to happen.
Because she was still learning how to communicate responsibility without sounding either uncertain or controlling.
Reed read the final team message.
“Good.”
Patricia smiled.
“Only good?”
“Clear. Respectful. Useful.”
“That is three goods.”
“Do not become difficult.”
Draft laughed.
The Notebook
Patricia opened her Draftling notebook.
Bossy Bot rolled onto the page and stamped:
URGENT.
Patricia crossed it out.
She wrote:
Draftling #008 - Bossy Bot
Represents: Instructions that become too commanding, harsh, or controlling.
Weakness: Give clear direction with context, useful deadlines, respectful wording, and room for the reader to respond.
DeskDraft Feature: Tone / Directness Check.
Then she added:
Clear is not the same as harsh.
Respectful is not the same as vague.
Good instructions help people know what to do next.
Bossy Bot raised its megaphone.
“WRITE MORE.”
Patricia looked at it.
“No.”
The robot paused.
Then quietly asked:
“Please?”
Patricia smiled.
“That is progress.”
