Skip to content

Systems

Personal methodologies, workflows, and tools.

System

Building Bias-Resistant Data Pipelines

Bias enters data pipelines at every stage, so validation should too. Gates for collection representation, label agreement, proxy features, preprocessing fairness, and output disparity, with…

System

AI Ethics for Small Teams: Practical Frameworks

A lightweight AI ethics framework for small teams: Fairlearn bias checks in pytest, prediction audit logs, Markdown model cards versioned with code, and a user…

System

Building an AI Incident Response Framework

An AI incident response framework adapted from SRE, with classification, detection, playbooks, and blameless reviews for bias, hallucination, privacy, and adversarial failures, plus an ethical…

System

Consent Architecture for AI Systems That Learn From Users

Meaningful consent for learning systems takes engineering: granular controls per data category, a consent service every component must check, transparent training summaries, and immediate revocation.

System

Responsible AI Implementation Starts With Your Deployment Pipeline

Embedding responsible AI checkpoints directly into CI/CD closes the gap where models reach production before ethics review finishes. Engineers cannot bypass a gate in the…

System

Process as Product: User Research for Workflows

An expense approval process redesigned with product research methods: user interviews, job-to-be-done analysis, usability testing, and success metrics aimed at the employee, not the committee.

System

Stakeholder Communication as Information Design

Executives need trajectory, risk, and decisions; team leads need dependencies, capacity, and scope. A layered status update serves both from one artifact instead of giving…

System

Decision Frameworks Are Tools, Not Religions

No single decision framework fits every problem. Select Cynefin, OODA, RAPID, or commander's intent by complexity, reversibility, and time horizon, set a deadline, and record…

System

Documentation Is a Product, Not an Artifact

Treat documentation as a product with users, versions, usage metrics, and planned deprecation. A part-time owner per team, templates, and review reminders keep it current.

System

Examined Workflow: Socratic Sprint Retrospectives

A retrospective method built on Socratic questioning: surface beliefs, test them against the sprint, expose assumptions, sort findings by the dichotomy of control, and end…

1 2 3 4 5 6