Start a brief

Approach

Understand the operation before designing the interface.

HMD begins with the people, systems of record, decisions and exceptions around one useful outcome. Technology follows that map.

Method

Four disciplined stages.

  1. 01

    Observe

    Identify users, authoritative sources, handoffs, permissions, exceptions and the cost of the present friction.

  2. 02

    Define

    Agree a bounded result, exclusions, test cases, dependencies and named decision owners.

  3. 03

    Build and challenge

    Create the review version, test failures and preserve manual fallbacks before production release.

  4. 04

    Hand over

    Deliver the version, test evidence, access map, limitations and operating instructions.

AI boundary

Assistive where useful. Never vague about authority.

AI may

Draft, classify, summarize, extract, reconcile, propose routing and flag exceptions inside an agreed boundary.

AI may not

Authorize flights, dispatch missions, determine airworthiness, release maintenance, approve legal or financial commitments, or silently change authoritative records.

People remain responsible

Named client personnel review consequential outputs and approve external release, filing or status change.