NOTES

Notes on how the work is done

Short pieces on method, one for each service line and two on regulation. Written by us, about no client, with every outside fact linked to its source.

ALL NOTES

Newest first

  1. What NIS2 asks of a technical team

    What the NIS2 Directive's risk-management, governance and reporting articles mean for the engineers who run the systems, read from the text itself.

  2. DORA for a company that is not a bank

    Who the Digital Operational Resilience Act reaches beyond banks, and what its third-party articles mean for a technology supplier to financial firms.

  3. Write the evaluation set before you choose a model

    Why an AI integration should start with a fixed set of questions and accepted answers, and how we write one with the people who own the work.

  4. Make staging tell the truth about production

    Why a staging environment that drifts from production makes every release a guess, and the order in which we close the differences.

  5. A missing control is not a missing record

    How we separate controls that do not operate from records that are not collected, and why the two need different work before an audit.

  6. Monitoring is not on call

    Why dashboards and alerts do not mean someone is responsible, and how we write an incident path that names who is alerted, who acts and who decides.

  7. Write the paragraph an answer engine can quote

    Why each important page needs one self-contained definition that matches its structured data, and how we write and check it.

  8. Agree the event schema before you choose the tools

    Why measurement should start with a written list of events, properties, owners and consent conditions, before any analytics tool is installed.

HOW WE WRITE THEM

Three rules for every note

  • Method, not stories

    Each note explains how we approach one kind of problem. None describes a client or claims a result.

  • Facts with sources

    Where a note states a regulatory fact, the paragraph links the text it comes from, so it can be checked in one click.

  • Obligations stay yours

    The regulatory notes describe what the texts ask engineers to make true. Whether and how a rule applies to you is a question for your lawyers.

Bring the question behind the note

Describe the system and what is not working. We reply with the questions we would ask in a first call.

Start a conversation