Directness Without False Certainty

That was happening in SecondDraft’s Direct mode. Words such as may, probably, and I think were sometimes treated as hesitation and removed. The result sounded firmer—but it also said something different.

Direct now follows a narrower rule: simplify a supported request when it is safe, but preserve the original level of certainty, who is responsible, and whether the sentence offers a recommendation or states a requirement.

Direct mode could change may to can and remove probably, I think, and It seems that. Each edit looked small. Each could make the revised sentence claim more than the original.

The problem was not that every cautious phrase deserved to stay. It was that the editor could not tell whether those words were empty padding or essential meaning.

“The event may be canceled” describes an uncertain outcome. “The event can be canceled” can describe ability or permission. The sentences are close in length, but they do not make the same claim.

Source: The launch will probably be delayed if approval arrives after Tuesday.

Unsafe rewrite: The launch will be delayed if approval arrives after Tuesday.

Current Direct output: The launch will probably be delayed if approval arrives after Tuesday.

Removing probably does not merely make the sentence shorter. It turns a likely delay into a definite one.

Source: I think the revised menu is ready for review.

Unsafe rewrite: The revised menu is ready for review.

Current Direct output: I think the revised menu is ready for review.

In workplace writing, I think can show that a statement is someone’s assessment—not a verified fact. SecondDraft cannot check whether the menu is actually ready, so it should not write as though it has.

Source: The library may not approve the revised menu.

Unsafe rewrite: The library can not approve the revised menu.

Current Direct output: The library may not approve the revised menu.

“May not approve” means approval is uncertain. “Can not approve” suggests the library lacks the ability or authority to approve it. The difference changes what the reader believes is possible.

Source: We were hoping you could confirm whether the library may not approve the menu.

Current Direct output: Please confirm whether the library may not approve the menu.

Here the extra request framing can go. The words inside the request cannot. The revision still asks about the library, the menu, and the possibility that approval may not happen.

The result is more direct without becoming more certain.

Source: The main point is that we should review the dates before recording.

Current focused output: We should review the dates before recording.

The opening announcement can be removed, but we, should, and before recording still matter. Dropping should would turn a recommendation into an instruction. Dropping we would change who is responsible.

• Direct no longer automatically changes may to can or removes probably, I think, and It seems that.
• Supported requests keep words that express uncertainty, conditions, and responsibility.
• The focused main-point edit keeps we should, while tested a.m. and p.m. forms remain intact during sentence cleanup.