Expertise

Executive communication

Progressive compression: evidence, analysis, finding, decision, summary, each level honest to the one below it.

A compression stack

  1. Evidence

    Two reports use the word denial. One counts remittance codes. The other counts a workflow status in the practice system.

  2. Analysis

    The queries can both be valid and still describe different objects. A claim can appear in one and not the other.

  3. Finding

    The reports are not comparable. The disagreement is a definition problem, not yet an operational trend.

  4. Decision

    Pick the definition that matches the decision, adjudication, or workflow, and rename the other report.

  5. Executive summary

    The denial reports disagree because they count different things. Choose a definition before acting on the trend.

Teaching example. Not a client result, and not a measured denial rate.

Executive synthesis

An executive summary is the last compression, not the first draft. It should name the decision and the reason, and it should survive contact with the evidence underneath it.

Diagrams

I use diagrams when a relationship is the point: a pipeline, a lineage, a handoff. A diagram that needs a legend the size of the drawing has failed. The figures on this site are the public examples.

Technical translation

Translation keeps the mechanism available without requiring every reader to live in it. The prompt-to-token page is that idea applied to a technical subject. The teaching page is the same idea applied to a classroom.