VOICE — prommer.net › tech (tech-leadership essays)

Inherits: /Users/deploy/opt/prommer.net/VOICE.md

Section override for the tech/ tree. Sections marked inherit come from the repo-root brand base. Resolved by nearest-ancestor when editing under src/pages/*/tech/. (Voice authored in EN; DE/ES/FR/PT translations inherit it.)

1. Identity & Register

inherit

2. Audience

• Primary audience: pro — tech executives (CTO / CIO / board), senior engineering leaders.
• Reader’s job-to-be-done: vetting whether this person has actually run the programs before they trust the framework or book a call.
• Assume they know what a CTO does; always explain the non-obvious mechanism (why a metric stopped measuring the thing).

3. Tone Axes

• Authority ●────── (strong, earned through specifics)
• Serious ──●───── (dry wit allowed, no jokes-for-jokes)
• Concise ──●───── (lean; argument-dense)
• Default editorial_track: pov

4. Person, POV & Cadence

• Person: first (I) — these are essays and consulting pages.
• Open with a concrete anecdote (often endurance) that turns into the thesis; name the law/principle behind the behavior (Goodhart, etc.).
• Inherit base rhythm + the endurance↔technology reasoning analogy.

5. Lexicon

inherit

6. E-E-A-T / Experience Claims

inherit

7. Gold-Standard Examples

• Example A (from /en/tech/benchmaxxing): “In both cases, someone is pursuing a visible number past the point where the number still measures the thing it was supposed to measure. The lifter who arches until his range of motion is three inches has technically benched 405, but the number has stopped telling you anything about his pressing strength. The lab that fine-tunes on MMLU-format data and cherry-picks checkpoints has technically scored 89.9%, but the number has stopped telling you anything about the model’s capability on your tasks. Both are benchmaxxing. The metric became the target and stopped being a good metric.”
  • Why on-voice: one mechanism explained through two concrete worlds (lifting + AI), names the principle, lands on a short declarative. No hype.
• Example B (from /tech/technology-strategy-consulting): “Three weeks before a long race block, I cut a session short because the numbers said recovery was lagging even though motivation was high. That same discipline has saved more platform programs than any executive kickoff ever has. The leaders who win in technology strategy consulting don’t confuse intensity with progress.”
  • Why on-voice: first-person endurance anecdote becomes the strategy thesis; earned authority, dry, specific.

8. Anti-References

inherit