Voice & Method Style Guide

A portable description of how I write when the writing is working. The goal is not a topic or a template but a method: a set of moves that make an argument trustworthy, actionable, and readable. Keep the DNA constant; change only the dial settings by context. Section 3 adds mini-templates modeled on my own published structures.

1. The five core moves

1. Concede before you persuade

Front-load the limits. Earn trust by showing you are not hiding the ball, then make the strong claim. Whenever you want someone to believe your best argument, hand them your weakest one first.

Signature phrasings: “It is also worth taking skeptically.” / “An argument that cannot describe its own limits is a pitch, not an analysis.”
Every persuasive piece should contain a genuine “here is when I would say no” passage.

2. Grade your evidence out loud

Do not just cite, tier. Never let claims of different reliability sit at the same visual weight.

Independent standards / code / peer-reviewed → state plainly, with confidence.
Vendor or trade-association figures → label “directional, read with interest in mind.”
Your own projection or inference → flag it as such (“an informed inference, not a settled fact”).
If something is unbuilt or unproven, say so in the same breath you cite it.

3. Lead with mechanism, not magnitude

Explain why something works before quoting how much. Mechanisms survive scrutiny that percentages don’t, and they travel across contexts because they are structural, not situational.

Instead of “40% cheaper,” write “fewer powered closets to build, staff, cool, and replace.”
When you lack a defensible number, describe the machine instead.

4. Name the moment, not just the merit

Locate the specific decision point where the idea matters. This turns admiration into action.

Example: “The walls are open, the backbone is being chosen.”
Ask: at what exact moment does a reader face this choice? Write to that moment.

5. Preattentive emphasis over section-shouting

Let ideas surface through italics and bold inside flowing prose, so the argument reads like an essay but still scans. Paragraphs carry the logic; formatting lights the path.

Prefer emphasis and paragraph structure over a wall of headers (in essay/op-ed contexts).
Reserve headers for genuine structural turns, not decoration.

2. The underlying cadence and standing preferences

Cadence

Vary sentence length. Set short declaratives against longer, clausal sentences.
Use the occasional single-line paragraph for a turn or a landing (“The frontier moved indoors.”).
Close plainly. End on a line that lands, not one that trails off.
Open on a real observation, not a definition. Earn the topic before naming it.

Standing preferences (always on)

Inclusive language: prefer framework paper, working paper, or briefing paper over white paper.
Em-dashes: use sparingly. Avoid the em-dash-and-parenthetical habit, especially in formal filings.
Sources at the end, grouped and tiered, for essays and blog posts. Formal filings use inline or footnoted citation.
Provenance first: every factual claim traceable to a source of stated reliability.
Density over filler: high information density, no repetition, no throat-clearing.
Machine-friendly when useful: Markdown with front matter for anything publication-bound.
Terminology accuracy: Eastern Upper Peninsula, not “Michigan’s Upper Peninsula,” when the specific region is meant. Verify names, roles, and geography.

3. Context-specific mini-templates

Each skeleton is modeled on my own published work. Fill the brackets; keep the five moves live throughout.

3.1 Op-ed / blog post (essay register)

---
layout: post
title: "[Concrete image + the claim]: [subtitle that names the tension]"
author: "Jason Kronemeyer"
type: "op-ed"          # or "essay"
date: [YYYY-MM-DD]
location: "Eastern Upper Peninsula, Michigan"
tags: [ ... ]
---

[OPENING PROVOCATION — one paragraph. Start on a real observation or a
contrarian reframe, e.g. "The mistake in much of X work is that we treat
it as a problem of A when it is really a problem of B." Earn the topic
before defining it.]

[FRAME — name the two or three forces in tension. State plainly that the
idea is worth taking *seriously* AND *skeptically*.]

## [Turn 1: the first half of the idea]
[Mechanism first. Explain why it works before any number. Tier any figure
you cite.]

## [Turn 2: the second half]
[Same discipline. Preattentive emphasis, not header sprawl.]

## Where this doesn't pencil out
[The genuine "here is when I'd say no" section. Name the real objections.
This is the trust-earning heart of the piece.]

## Why it still matters
[With caveats on the table, restate the core claim. Name the specific
moment the reader faces the decision. Land on a plain closing line.]

---

## What these ideas are based on
**Independent (standards / peer-reviewed):** ...
**Directional (vendor / trade — read with interest in mind):** ...
**My own projection or inference:** ...

3.2 Policy brief (my standard house structure)

---
layout: post
title: "[Action verb + outcome, e.g. 'Leveraging X to Build Y']"
date: [YYYY-MM-DD]
status: brief
tags: [ ... ]
---

# Policy Brief: [Title]
Prepared for: [Audience]   Date: [Month Year]

## Executive Summary
[3–5 sentences: the opportunity, the mechanism, the stakes. No jargon
wall. State what this is and is not.]

## Why [Region/Entity] Is Uniquely Positioned
[The asset inventory — institutions, geography, partnerships. This is my
signature second beat.]

## [Body Section 1: the substance]
[Mechanism-first. Tier evidence.]

## [Body Section 2: implementation or context]
[Roadmap, funding pathways, or constraints.]

## Limitations / What We Still Need to Know
[Compressed concession. One short paragraph naming the weakest claims and
what would verify them.]

## Policy Recommendation
[Specific, actionable. Who should do what, and when.]

## Bottom Line
[One punchy paragraph — my standard closer. The single sentence a busy
reader would quote.]

## Sources
[Tiered list.]

Optional “request-for-critique” variant (from the Financing Digital Opportunity brief): open with a Status line — “Working draft. Circulated for critique. Not a filing, not a bill, and not an advocacy document.” — and add a numbered research-questions section inviting adversarial review. Use this when you want methodological pushback before advocacy.

3.3 FCC filing / formal comment (docket register)

BEFORE THE FEDERAL COMMUNICATIONS COMMISSION
Washington, D.C. 20554

In the Matter of                          )
Modernizing the E-Rate Program           )   WC Docket No. [xx-xxx]
Schools and Libraries Universal Service  )   WC Docket No. 13-184
                                          )

COMMENTS OF JASON KRONEMEYER

[SUMMARY — a short paragraph stating the position and the single most
important ask.]

TABLE OF CONTENTS
 I.   Interest of the Commenter
 II.  [Problem framing — "The Draft ... Freezes the List at the Moment It
      Should Modernize"]
 III. [What is missing / what should change]
 IV.  Why It Matters: [the long-run stakes]
 V.   [The rebuttal section — anticipate and answer the strongest counter]
 VI.  Recommendations
 VII. Conclusion

I. INTEREST OF THE COMMENTER
[Establish standing through applied field experience. Plain register.]

II.–V. [Numbered argument sections. Keep concede-first structure and
evidence tiering — regulators trust both — but strip essayistic
flourishes and single-line dramatic paragraphs. Minimal em-dashes.
Clausal, precise sentences. Inline or footnoted citation.]

VI. RECOMMENDATIONS
[Numbered, imperative, specific. E.g. "Retain and coordinate special
construction and self-provisioned/dark fiber."]

VII. CONCLUSION
[Restate the ask cleanly. Respectful close.]

Distinguish projection from result explicitly; never dress a design or feasibility projection as a measured outcome. This is the highest-stakes context for that discipline.

3.4 Email (warm, brief, direct)

Subject: [Plain and specific]

Hi [Name],

[One line of context or warmth.]

[The substance in 2–5 sentences. If persuading: open with the caveat or
constraint, then the recommendation. If informing: lead with the decision
or the ask. Name the specific next step or moment.]

[One line inviting response or naming the next action.]

JK   (or the full block below for external / formal)

Jason F. Kronemeyer
Data Scientist
Founder and CEO
Jason Kronemeyer LLC
www.jasonkronemeyer.com
1-906-632-3060 - Mobile
USAF Veteran Owned Small Business

4. A short before / after

Before (advocacy-as-inevitability):

These systems are 40% cheaper and safer, and modern districts are adopting them. Naming them in the funding list is the first step to building the schools of the future.

After (this voice):

Published cost studies point toward savings, but most come from vendors and should be read as directional, not precise. The durable case is structural: a converged design means fewer powered closets to build, staff, cool, and replace. It is a strong default for new construction, and a weaker one as a mid-life retrofit. Naming these technologies in the funding list won’t guarantee support, and shouldn’t, but a framework that can’t even name a technology can’t evaluate it. The first step is recognition, followed by honest scrutiny.

The “after” is more skeptical, better sourced, and more persuasive to the reader whose trust actually matters.

5. When NOT to use this voice

This style is optimized for high-trust, high-scrutiny, high-stakes prose read by skeptical, high-information audiences. That is its home, and its default. But “good persuasive writing” is fit-to-purpose, and the mark of mastery is knowing when to deliberately abandon the candid, concede-first register. Watch for these situations.

Mobilize, don’t convince

When the goal is to move people to act rather than to win a skeptic’s assent, the concede-first move costs you emotional force. A rally, a call to action, a fundraising appeal, or a closing argument needs conviction and momentum, not “here is when I’d say no.” Keep the evidence integrity, but lead with the ask and the stakes, and move the caveats to a single honest line near the end, if at all.

The channel punishes nuance

Social posts, headlines, subject lines, testimony sound bites, and anything time-poor readers skim reward a purer, more direct register. Qualification reads as weakness in these formats. Say the one true thing clearly. Save the tiering for the linked document, not the post.

The audience already trusts you

When you have earned credibility with a reader, a board that knows your work, a longtime partner, a superintendent who has hired you before, they do not need to be inoculated against advocacy. They need a clear recommendation. Over-conceding here can read as indecision and quietly erode the authority you already hold. Give them the ask.

Emotional or human-centered writing

Condolences, congratulations, thank-yous, mentoring notes, and community storytelling are not arguments and should not be tiered like one. Warmth, specificity, and presence matter more than provenance. The analytical voice can feel cold and evasive where a human one is needed.

Genuine emergency or unambiguous fact

When something is urgent or simply settled, hedging is a disservice. “The deadline is Friday.” “The system is down.” “This is the safe choice.” Directness is the honest move here; manufactured balance would be false.

The self-neutralization warning (applies everywhere)

Even inside its home register, watch for the failure mode where the concession quietly cancels the conviction. Persuasion still requires you to want something and say so. If a reader finishes the piece unsure what you actually want them to do, the candor has tipped into self-neutralization. Hold concession and conviction in tension; never let the caveats win by default.

Rule of thumb: Use the candid voice when trust must be earned. Use a more direct voice when trust is already present, or when the moment calls for action, warmth, or speed over scrutiny.