Authority
Who is entitled to decide this, and does that entitlement survive the distance between where the decision was made and where it took effect?
Enterprise operator. Founder & Chief Architect. Board Director.
Keisha J. Williams works across how work gets done, how decisions are made, and how change is implemented. Her central question becomes harder to answer as execution spreads across people, software, agents, and institutions: who still holds authority — and how would anyone know?
This surface is where that question is asked in public. LogicalFlo is where the answer gets built.

Work no longer moves through one set of hands. A decision is proposed in one place, shaped in another, executed somewhere else, and recorded somewhere else again. Some participants are people. Some are software. Some are agents acting under delegated permission. Some are entire institutions operating under their own rules.
The institutional condition this creates is not merely a technology problem. It is a question of authority and answerability, and it resolves into four parts.
Who is entitled to decide this, and does that entitlement survive the distance between where the decision was made and where it took effect?
When the decision is questioned — by a regulator, a board, a court, a community — what record exists, who produced it, and does it show what actually happened rather than what was intended?
Can the organization actually do what it has committed to do, or has it described a capability it does not yet hold?
If the answer were demanded today, without notice and without preparation, would it be available?
These questions predate any current technology and will outlast it. They become harder to answer as execution spreads out, which is why they are worth asking now rather than after an incident makes them urgent.
Williams holds a position on how they should be answered. But the question is prior to that position, and it belongs to the reader as much as to her.
The same question keeps reappearing in different institutional settings. Traced backward, it runs in one direction.
Systems are experienced by individuals before they are evaluated by institutions. Whatever a structure does to the people inside it is the first fact about that structure, not a downstream consideration.
People organize into institutions to hold what individuals cannot hold alone — continuity, obligation, memory. Institutions concentrate capability, and they concentrate consequence with it.
Institutions run on rules: charters, statutes, contracts, policies, thresholds. Rules are how an institution tells the truth about what it will and will not do, and how it can be held to it.
Rules are increasingly executed by systems rather than administered by people. Execution moves faster, reaches further, and becomes harder to observe from the outside.
If a rule is executed by a system on behalf of an institution that exists to serve people, someone must remain accountable for the result — identifiable, answerable, and able to intervene.
That is the throughline, and it is why LogicalFlo exists. Not as the subject of this page. As the reason the question could not stay theoretical.
The work advances in three ways, each with a clear place to explore it.
Open problems, working arguments, and revisions in public.
Read the Field Notes →Structural, operational, systems-level, enterprise, and commercial work is delivered through LogicalFlo.
Visit LogicalFlo →Selected questions, evidence, and public instruments are available through the LogicalFlo Observatory.
Explore the Observatory →These routes are open, and each is bounded.
Convenings where the question can be examined seriously rather than summarized. Considered individually.
Substantive treatments of authority, evidence, and institutional readiness.
Governance service where the mandate genuinely includes oversight of distributed execution.
Keisha serves on the Board of Directors of Measure, contributing governance experience to an organization focused on community-led data, evidence, and systemic change.
Collaboration with researchers working on adjacent questions.
Narrowly bounded, personal, and infrequent. Anything requiring build, delivery, or sustained operational involvement is routed to LogicalFlo instead.
Availability is limited and assessed case by case. A request that fits the question is more likely to be taken up than one that fits a calendar.
What follows is here because it explains how the question was encountered — not where, and not how impressively.
Years of work inside federal public-service environments, at regional scale, where institutional rules, human-capital systems, government information systems, and operating procedure all had to function together. The work included administering human-capital programs and the systems of record that held them, maintaining the internal information systems staff depended on daily, and drafting the procedural policy those systems then carried out. Writing a rule and running the system that executes it are different jobs. Doing both makes the distance between them visible.
Executive responsibility for a neighborhood housing and development organization in Newhallville — operations, procurement, and program budgets. Accountability there was immediate and local: the people affected by a decision lived where the decision was made, and could say so.
Board service, including as chair, for community and nonprofit organizations. This is the vantage point from which one is answerable for what an institution does without being the person who executes it — the gap the page is about, encountered from the side that has to sign for it.
Oversight of publicly and philanthropically funded programs, and review of community investments on behalf of a funder. The recurring question was not whether money had been spent but whether the record showed what had actually been done with it.
Sustained work in human-capital and workforce administration — recruitment, training, and the systems that route people through institutions. It is difficult to treat the human consequences of institutional systems as abstract after administering the systems themselves.
Work inside a global corporation's human-resources operations and reporting, and operating experience with the enterprise systems of record that institutions rely on. The relevant part is not familiarity with particular platforms. It is what happens once a rule is encoded in a system: the record becomes whatever the system says it is, and someone still has to answer for the difference.
Additional record exists and is deliberately not published here. Where the specifics are material to a decision a reader is making, the engagement boundary below is the correct route.
My writing moves across technology, institutions, work, governance and human capability. These questions provide a way into the collection.
I welcome a limited number of conversations where my experience and perspective can be useful—on stage, in the boardroom, in research, or around a difficult question.
For speaking, media, board and director interest, research collaboration, and narrowly bounded personal advisory.
Start a ConversationIf your organization is working through an operating, governance, technology, workforce, or implementation problem, start with the problem at LogicalFlo.
Submit an Inquiry ↗