Policies
Define and iterate upon the business policies that shape and drive your business operations in repeatable ways.
A policy is a decision your organization has made, written down so it does not have to be re-argued every week. Most companies have hundreds of these decisions living only in people's heads and old Slack threads, which means they are not really decisions at all — they get re-litigated constantly, and everyone is exhausted by it.
I help you define the business policies that shape your operations — around security, privacy, access, retention, and how APIs get produced and consumed — and write them where they can be found, cited, and enforced. Policies come first; the technical rules that implement them come after, and I keep that order straight, because reversing it is exactly how governance turns into bureaucracy.
Done well, policy is what lets you move faster, because the settled questions stay settled.
When you are ready to turn a policy into something a pipeline can enforce, it feeds directly into machine-readable rules — the free Ruleset Commons is where you can adopt a provenanced ruleset by reference, so a policy decision carries its lineage all the way down to the check.
What you walk away with
- Documented business policies for how your operations actually run
- A clean separation between policy and its technical implementation
- A single place where policies live, get cited, and evolve
Related reading
- Policies and Style Guides: The Why Above Your Rules
- The Right API Policies, Process, and People Helps Minimize Enterprise Technical Debt
- Schema-Validated, Rules-Guided, and Policy-Driven Experiences
- The Fundamentals of API Governance (paper)
- Ruleset Commons — adopt a provenanced ruleset that implements your policies
Start with the research
Everything I know about turning policy into something machine-actionable is already written down, priced, and yours to read tonight — no call, no scoping, no proposal. Start there.
-
The Fundamentals of API Governance $25
Governance is 75% people work — here's the other 25%. -
Making API Governance Conversational $25
Governance people will actually take part in.
Free first: your Kin Score and Agent Readiness are already published on APIs.io. Look yourself up before you buy anything — the score costs nothing and it is the same rubric every report on this page is built from.
If you would rather have this done with you than do it yourself, I take a small number of engagements a year — [email protected].
Newsletters
Two emails, both Monday mornings. Take either, or both.
API Evangelist
Highlights of the stories, conversations, and API knowledge published across the industry each week.
The Specification Layer
What actually merged into the thirty specifications the Linux Foundation stewards — OpenAPI, AsyncAPI, JSON Schema, and the rest.
