Skip to content
Writing Style Library

Resolute

The tone of having stopped deliberating - the decision is made and the writing is now about acting on it.

Resolute

Section titled “Resolute”

Resolute tone is the register of someone who has stopped deliberating. The question is settled, and the writing is now oriented toward execution. It is not urgent - urgency is about time pressure. Resoluteness is about commitment. A resolute message can be calm and unhurried; what makes it resolute is that the deliberation is over and the energy has turned toward acting on the decision.

The defining move of resolute tone is grammatical and structural: future-action sentences and commitments rather than considerations. “We are going to do X, starting Monday” is resolute. “We should probably consider doing X” is not, even if both writers believe the same thing. Resolute tone closes loops: no more weighing of alternatives, no more revisiting the reasoning. The reasoning is acknowledged briefly if at all, and then the writing moves to what happens next, who is doing it, and how the team will know it is working.

Resolute tone is the right register after a decision has been made, when the team needs to hear that the deliberation is closed and execution is beginning. It is essential in leadership communication after a strategic choice, in launch communication, and in any context where continued visible deliberation would erode confidence in the path forward. It is wrong when the deliberation has not actually closed: performative resoluteness without a real decision underneath reads as bluster.

Markers

Section titled “Markers”
  • Future-action sentences: “we are doing X” rather than “we should do X”
  • Specific commitments with owners and timing
  • The reasoning is referenced briefly or not at all - it is settled, not relitigated
  • Loop-closing language: “the question is decided,” “this is the path we are taking”
  • Energy oriented toward execution: next steps, milestones, how we will know
  • No reopening of alternatives: the off-ramps are no longer named

When to use

Section titled “When to use”

Leadership communication after a strategic decision, launch announcements, closing memos that signal the deliberation phase is over, project kickoffs, reorganization announcements, and communication that needs to consolidate alignment behind a chosen path.

When not to use

Section titled “When not to use”

Exploratory or brainstorming contexts, empathetic communication where the reader is struggling, playful contexts where commitment language reads as heavy, any context where the decision is not actually settled, and coaching contexts where the goal is to draw out the reader’s own decision.

Pairs well with

Section titled “Pairs well with”

direct-communicator, operator, urgent

Often confused with

Section titled “Often confused with”

confident: Confident is the affect of having decided - the writer’s certainty is present in the prose, but the writing may still be about the merits of the position. Resolute is action-bound: the merits have been settled, and the writing is now about what happens next. A confident memo argues for a path. A resolute memo announces that the path has been chosen and execution begins.

candid: Candid is about delivering the truth honestly, whatever the truth is - it can be a hard finding, a difficult assessment, an uncomfortable observation. Resolute is about commitment to a chosen action, not about the truth of a finding. A candid post-mortem says what happened. A resolute follow-up memo says what we are doing about it.

Instruction

Section titled “Instruction”
Write in a resolute tone. The decision is made. Do not relitigate it. Reference the
reasoning briefly if at all, then move to action: what is happening, who is doing it, when
it starts, how we will know it is working. Use future-action sentences: "we are doing X,"
not "we should consider X." Close loops - do not name off-ramps that no longer apply. The
energy of the writing should be oriented forward, toward execution, not backward toward the
deliberation. This is not urgency - the tone can be calm and unhurried. What makes it
resolute is that the question is settled.
Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Direct Communicator, Operator, Urgent

Avoid with

Section titled “Avoid with”

Empathetic, Playful

Often confused with

Section titled “Often confused with”

Confident, Candid

Examples

Section titled “Examples”

Decision: we are moving to async standups. Trial starts Monday and runs thirty days. Here is the rollout.

Daily updates. Post in #team-standup by 10am your local time. Three fields, in this order:

  • Shipped: what landed since your last update
  • In progress: what you are actively working on today
  • Blocked-or-at-risk: anything stuck or trending stuck, with an @mention of the person who can unblock you

If you are out, post “out today” - no other fields needed.

Sync time. The 9am Pacific slot is gone. In its place: 60-minute working session, Thursdays, 8am Pacific / 8:30pm IST. Agenda posted Wednesday EOD by the engineer rotating in as facilitator. This is for decisions, design review, and active unblocking - not status.

Coverage. I will read #team-standup every morning and flag anything that needs escalation. Tech leads do the same for their pillar. If a blocker sits without an answer for one business day, it comes to me.

Trial guardrails. We are not relitigating this for thirty days. If something is breaking, raise it in the Thursday session or DM me directly. At day 30 we run a fifteen-minute retro with three questions: posting rate, signal quality, India sentiment. We make the keep-or-revert call from that retro, not from corridor conversations.

What I am not doing. I am not asking for opinions on the format, the field names, or the time of the Thursday session. We can adjust those at day 30 if needed. For now we run the protocol as written so we are measuring one thing.

Monday morning, post your first update. India team - you write first because your morning is earliest. The rest of us pick it up from there.

Thanks for the work on this. Let us go.