The Leadership Playbooks

YOU ARE HERE: HFML

Pick a lane:

HFML.
Human-First Mechanisms.

A leadership operating system: guardrails, cadence, decision rules, and execution loops that protect humans and ship outcomes.

Flag What it is Guardrails OS Loop Artefacts Start FAQ

Flag in the sand

This is the public definition. HFML is a named framework that turns leadership into a runnable system. Not motivation. Not theatre. Mechanisms you can deploy.

HFML (Human-First Mechanism Leadership) 1) Mechanisms reduce cognitive load and meeting drag. 2) Guardrails create safe autonomy and clearer decisions. 3) Humanity is baked into the process (tone, trust, dignity, recovery). 4) AI is the execution layer that removes friction, not the boss. Default rule: If it cannot survive a Monday morning, it does not ship.

Not this

Control theatre

Scripts, micromanagement, performative process, constant re-orgs.

This

Guardrails + autonomy

Clear defaults and decision rails so people can do deep work without chaos.

What HFML is

HFML sits between vibe leadership and factory leadership. Procedural enough to run, human enough to trust.

Human-first

Dignity by default

Psychological safety, recovery time, and respectful constraints are part of the system.

Mechanism-led

Repeatable loops

Cadence, templates, decision rules, and definition-of-done. Less talking about work.

Guardrails

Safe autonomy

Constraints that prevent thrash. Clear “what good looks like”.

AI layer

Friction removal

Drafts, summaries, QA, standardisation. Faster execution, fewer meetings.

Guardrails

The guardrails (the bit most frameworks skip)

Guardrails are what make autonomy safe. They reduce ambiguity, stop whiplash priorities, and protect energy.

HFML Guardrails: - Inputs before opinions - One measurable outcome per thread - One owner per artefact - Constraints create freedom (timeboxes, templates) - Humane defaults (recovery beats hero culture) - Version everything (process evolves like product)

Meeting rule

No meeting without an artefact

If there is no doc, decision, or shipped output, it’s a chat, not a meeting.

Priority rule

One thing, properly

If everything is urgent, nothing is. HFML forces explicit trade-offs.

Operating System

HFML OS loop

A simple loop you can run weekly. It turns chaos into cadence.

HFML OS: 1) Clarify -> define inputs, constraints, outcome (in writing) 2) Mechanise -> template the repeatable bits (rails, checklists) 3) Assist -> use AI for drafts, summaries, QA, standardisation 4) Review -> measure, iterate, version, reduce meeting load

HackTheSim

Artefacts

Tools, not vibes

HFML lives as artefacts: prompts, templates, checklists, decision rails. That’s how it becomes real.

Artefact

Decision Rail

A short template that forces inputs, options, risks, and the owner.

Artefact

Definition of Done

A clear finish line that stops infinite loops and “nearly done” forever.

CORE prompt format: Context -> facts the model needs Outcome -> single measurable goal Rules -> constraints, tone, format Examples -> patterns worth copying

Open HackTheSim Read About

Start Here

Start here (pick your pain)

Choose the problem you’re living with right now, then run the smallest HFML move that creates relief this week.

Pain

Meeting overload

Introduce an “artefact-first” rule and move updates async. Kill status meetings.

Pain

Messy execution

Define done, introduce checklists, reduce batch size, enforce owners.

Pain

Flat energy

Stop thrash, reduce context switching, create recovery defaults, protect deep work.

Pain

Weak clarity

One outcome per thread. One next step. One owner. Everything written.

SSA booking

If you’re overloaded, book the shortest triage and we’ll diagnose the bottleneck.

FAQ

Question

Is HFML just “process”?

No. It’s process with humanity baked in: dignity, recovery, safe autonomy, and clarity rails.

Question

Why publish it?

Frameworks without artefacts die. HFML ships as templates, prompts, checklists, and loops.

Question

Where does AI fit?

As an execution layer: drafts, summaries, QA, standardisation. Less friction, fewer meetings.

Question

What’s the smallest move?

Artefact-first rule. No doc, no meeting. One outcome, one owner, one next step.

HFML.Human-First Mechanisms.

Flag in the sand

What HFML is

The guardrails (the bit most frameworks skip)

HFML OS loop

Tools, not vibes

Start here (pick your pain)

SSA booking

FAQ

Unlock The Kit

HFML.
Human-First Mechanisms.