Your request wasn't rejected. It was never decided.

You wrote the email. You sent the Slack message. You attached the proposal. Then nothing happened. No yes, no no, just silence, a follow-up, and more silence.

Most decisions now get made in writing, on the reader's schedule instead of yours. You can't read the room, answer objections as they come up, or rephrase when you see confusion. The document has to do all that on its own, often in the thirty seconds a busy manager gives it between meetings.

Decision Writing for Busy Professionals is a step-by-step system for memos, emails and Slack messages that overloaded managers can approve quickly. It isn't about "better prose." It's a clear structure you can check and repeat, so the person who has to decide finds it easy to say yes.

Inside, you'll learn:

1- The three ways a written request dies: it's never read, it's read but not understood, or it's understood but never decided. You'll also learn the fix for each one.

2- The four silent questions every executive asks: what am I deciding, why now, what does it cost, and what happens if I say no?

3- The decision memo structure, from the one-line ask to options, recommendation, cost, risk, deadline and who signs off.

4- A full before-and-after rewrite of a budget request that sat unread for three weeks, plus a seven-question checklist to run before you hit send.

5- Slack and chat requests that fit in one message, including how to turn a messy thread into one clear ask and how to lock in a decision.

6- Emails to senior people: subject lines that state the decision, the two-paragraph rule, and follow-ups that get answers without damaging relationships.

7- Pre-wiring: how to deal with objections before your document goes out, without drifting into back-channel politics.

8- Writing against a "no": how to reframe, shrink a big budget into a funded experiment, and propose small first steps that are easy to undo.

9- Ready-to-use templates for budget increases, new hires, software purchases, contractors, training, project stops, policy changes, vendor selection, timeline extensions and exception requests.

10- A personal decision-writing system for tracking requests and outcomes without extra admin, and for building a reputation as someone whose requests are easy to approve.

Every chapter includes real examples: the vague version that stalls, the rewritten version that gets approved, and why the rewrite works.

This book is for managers, team leads, project and product managers, analysts, consultants and anyone who needs approval from people with too little time.

Stop writing requests that wait. Scroll up and get your copy today