December 28, 2025

There was a day—maybe a Tuesday, perhaps a Wednesday—when I learned that saving a life and failing to save a life can feel like the same thing. I was working the day shift, which was unusual for me.

I’ve always been a night person. Something about the quiet after dark, the way a city breathes differently when most people are asleep. But that day, I was on patrol in broad daylight when the call came in: an older gentleman had collapsed on a walking path. Not breathing.

I was close. A minute away. Maybe less.

When I got there, I saw his skin—blue and pale in a way I’d never seen before. I could see the life leaving his body. That was the only thought I had time for. A nanosecond. Then training kicked in.

I grabbed the defibrillator.

Told the crowd to give me space.

There was a woman already kneeling beside him, doing chest compressions. She said she had some kind of credential—I don’t remember what.

She could’ve said she was Kermit the Frog.

I just needed help.

We worked. I did the compressions. She kept checking for breath. The defibrillator did its thing. It felt like forever before EMS arrived, but when I checked the logs later, their response time was average. Better than average, even. It’s just that when you’re on scene, time doesn’t work the same way.

When the ambulance crew got there, they took over like an Indy 500 pit crew—four or five of them, maybe more. Each one knew exactly what to do. I stepped back, out of breath, watching them work.

The scene cleared. I was told the gentleman regained a pulse in the ambulance. He was alive when they got him to the hospital.

I felt relief. Then I moved on to the next call. That’s what you do. You don’t follow up. You just keep going.

A couple of weeks later, I was called in to receive an award: a Lifesaver commendation. It was a big deal in the department. Prestigious, even.

A Senior ranking Officer handed me the pin. He looked at me and said, “I don’t know why we’re giving you this. You know the guy died, right?”

I stood there.

I didn’t say anything.

I took the pin.

I went home.

I didn’t wear it.

I put it in my locker and left it there.

Here’s the thing about being a first responder …

… you’re supposed to show up ready for anything. You’re supposed to stay sharp, stay present, never get complacent. That’s what they train you for. But what they don’t train you for is the dissonance.

The dissonance of trying to do your best work in a place that doesn’t fully see you. The dissonance of being awarded for something you’re told didn’t matter. The dissonance of going home to Dunbar—your community, the place that raised you—and wondering if you’re betraying them by wearing the uniform in the first place …

[ During my tenure, I was asked, Why didn’t I become a cop where I lived? ]

I didn’t have a good answer then. I just knew I needed to go where I—or people who looked like me—had never been. I needed to serve in a place that was foreign to me. Not because I didn’t love my own community, but because something told me that’s where the work was.

This was before 2014. Before Ferguson. Before the nation watched the fault lines between Black communities and police departments crack open in ways that couldn’t be ignored. Before officers who looked like me had to answer, publicly and repeatedly, for a system we didn’t design but were asked to represent.

There’s a tension that doesn’t resolve.

Being Black is an identity I can’t remove—the world sees it before I speak. Being Blue was an identity I could take off at the end of a shift—except it never fully came off. The uniform lives in your posture, your vigilance, and your way of entering a room.

Some say the system is rigged. Others say it’s just broken. Others insist it’s working exactly as designed. I was an A-type cop—the kind who shows up for all of it. We’re here to help, serve, protect, and fix. If we can make it safe and secure, we will.

I later synthesized it this way

I was trying to learn how to be safe in a place where I didn’t instinctively know the codes. I was trying to understand what it meant to serve across the gap—between who I was and where I was, between what I believed and what the system allowed me to become.

That gap has a name now. I call it …

The Affect Gap™

I’ve been auditing that gap for 20 years.

I realized that the system and I were measuring two different things.

It was tracking External Goods—the commendation, the procedure, the pin. I was protecting Internal Goods—the human connection, the outcome, the actual impact.

The Affect Gap™ is the structural friction you feel when the rewards the system offers don’t match the excellence the work requires.

This isn’t about fixing ourselves to fit broken systems. What I have come to understand is that for some of us, it’s about recognizing that our craft has outgrown the institutions claiming to house it.

I eventually took the pin out of my locker. It took me about four or five months, but I did it. I wore it underneath the other pins I’d earned—hidden, but there. For a long time, I carried it like a failure. Like a reminder that I was the first responder who didn’t really save anyone. I was awarded for an attempt, not an outcome. But I’ve come to understand it differently now.

This wasn’t a failure of personhood; it was a revelation of a structural ceiling. I realized the existing framework wasn’t designed for the depth of this work. It lacked the architecture to navigate true dissonance or the capacity to hold space for the complex reality of serving across difference.

And the gentleman? He got to the hospital. He got a chance. Maybe he got to say goodbye to someone. Maybe someone got to say goodbye to him. That matters. Even if I didn’t see it. Even if the outcome wasn’t what I hoped for.

That’s the work.

Showing up.

Doing what you can.

Knowing it might not be enough.

And doing it anyway.

Final reflection and perspective

I’ve come to understand that the Affect Gap™ isn’t just about individual resilience—it’s about structural design.

The systems we build either honor the full weight of the work, or they hollow out the people doing it. That realization became the foundation of what I now call Capacity-as-a-Service™ (CaaS™)—a framework for protecting the Essential Servant™ from the forces that would reduce them to an NPC.

This essay is part of a series exploring what I call the Affect Gap™—the structural friction between the excellence work requires, and the reward(s) systems offer. It’s a theme I develop fully in my forthcoming book, Cause and Affect: Why the Essential Servant Is Burning Out—and How to Stop It. The Affect Gap™ and the CaaS™ (Capacity-as-a-Service) Framework are tools I’ve built over twenty years of navigating the gap between service and survival—first as a police sergeant, then as a housing executive, now as the founder of AVANTKOFA.

Leave a comment

Subscribe now

As the architect Le Corbusier reportedly said, "A house is a machine for living in." I grappled with that, viewing housing solely as a commodity. In what follows, I extend that thought: our communities are systems built by policy (more system play), and we are the users.

Did you ever look at a cityscape from above and think it looked like a motherboard under a microscope?

That visual analogy struck me recently as I revisited an article I wrote almost four years ago. The central idea—that policy acts as the essential, foundational circuitry dictating the flow of resources and outcomes in our communities—deserved a clearer title and a fresh hero image.

Thus, my revisit of a 2022 reflection article written on my LinkedIn platform aims to illuminate a notion:

Policy as the Motherboard of Community Growth," which is a reflection on why policy is never truly benign and how these "architectures of consequence" shape everything from zoning laws to HR practices (even the absence of an HR policy, as I painfully recently experienced).

“ April 2, 2022

As I close out a fruitful and enlightening week with personal reflections and professional development reads, I was delighted to come across this report:

“A Better Building Code, recommendations for increasing Housing Resilience and Racial Equity for Minnesota Renters.“

Aside from being an innovative approach to policy for the people (rather than “to” the people), it demonstrated that unjust policies are not benign. If a policy can work to heal, it is conceivable that some policies have hurt and caused harm and losses.

This report and initiative of the Minnesota Housing Partnership and its partners complement several aspects of why policy matters and how it intersects with the overall well-being of people and places. To some, all forms of policy have the potential to be systemic in scope (or the lack thereof ).

Consequently, to a few, anything that impacts the part can affect the whole (i.e., organization or community). Therefore, policymakers are often encouraged to frequently introspect on how their policy as instruments intersects with people, performance, and the production of outcomes and outputs. For example, since the early 1990s, there has been much research on the relationship between long-term systematic poverty, racial segregation, and socioeconomic inequality and its impact on growth in the United States.

Nevertheless, I believe that there is still an underappreciation on the part of some of how housing policy profoundly affects each of these factors. Building and zoning codes (i.e., public policy) matter, and they always have. While reading this report, I thought about a conversation I had earlier in the week regarding the ‘power of knowing’ and a later conversation regarding ‘policy and managing expectation and performance.’

In short, though very different applications of thoughts, which occurred unrelated and unconnected to one another, this article caused me to juxtapose the various impacts of policy on people and places. Moreover, the brainstorming this read caused was helpful to several policy/advocacy developments I may be working on in the months to come.

In closing, policies must exist at all levels, even in government or private firms’ human resources management. Policies and practices are part of the structures of an organization, which create or perpetuate outcomes or outputs. All policies and long-standing institutional practices have the power to effect change or perpetuate the status quo (i.e., the way things are and have always been).

May this sharing merely serve as food for thought. I am happy to receive and welcome engagement on this subject. So leave a comment, or inbox me your thoughts/feedback. ”

“

“

Leave a comment

Subscribe now

January 22, 2026

There are many ways to discover that housing algorithms measure the wrong things. Some people learn it when choosing between a child’s medication and rent results in a permanent eviction filing on their record. Others learn it when years of housing policy expertise don’t translate to passing an automated screening system. Different starting points, different circumstances—same destination: a system that optimizes for patterns instead of people.

I learned it both ways. As someone who experienced algorithmic rejection while working inside the systems that deploy these algorithms. And as someone who helped permanently house thirteen people after those same systems said no.

Marcus was one of those thirteen people.

What the algorithm saw:

• Eviction filing from 18 months prior

• Credit score: 510

• Risk assessment: DENY

What I knew: The eviction filing came when Marcus chose to pay for his daughter’s asthma medication instead of rent during a particularly difficult month. The case was dismissed, but the filing stayed on his record. He was a father who prioritized his child’s ability to breathe over a landlord’s ledger.

What happened: Through a community-based housing initiative, we gave Marcus the chance that standard screening wouldn’t. Eighteen months later, he had never missed a rent payment, earned a promotion at work, and his daughters were thriving in stable schools for the first time in years.

The algorithm had measured his past. We measured his capacity.

Perhaps I write this because I am Insecure, or have been there before.

I applied for housing while working in housing policy. I understood screening systems because I’d helped implement them. I knew the credit thresholds, the background check protocols, the risk assessment formulas.

And I was rejected. The algorithm measured credit damage from caregiving costs and employment transitions—the same life circumstances millions of working Americans navigate. It saw patterns that correlated with risk in its training data. It didn’t see consistent rent payment history, stable employment, or a deep understanding of housing systems.

Different route from Marcus. Same destination: DENIED.

What does it mean when the screening system rejects both the father, prioritizing his daughter’s health, and the professional administering housing programs? When it fails across income levels, education levels, and life circumstances?

It means the algorithm isn’t measuring housing stability. It’s measuring conformity to historical patterns—patterns built on decades of discriminatory lending, healthcare inequity, and economic instability.

The Pattern Across Different Routes

That first year, we permanently housed thirteen people—every one of them rejected by standard algorithmic screening. They included a practicing architect relocating from California, two truck drivers navigating wage insecurity, a CNA with two children (one with significant health needs), recent college graduates, a traveling nurse, a couple working while homeless, and a family displaced by storm damage.

Thirteen different routes to algorithmic rejection. Zero evictions once housed. Zero failures. The algorithm was 0 for 13.

Beyond direct placement, we engaged nine additional community members as an advisory and working group—residents, family members, and stakeholders directly impacted by housing instability. They participated in program design, attended closings, and helped shape how the work evolved. We also provided emergency shelter when needed.

Twenty-two people served in different capacities that first year—because housing solutions require community leadership, not just professional administration.

What Gets Lost When Housing Becomes Strictly Data

When housing decisions are automated through algorithmic screening, we lose the ability to see what systems can’t measure:

• The algorithm sees: Credit score below threshold | What it misses: Years of consistent rent payment despite economic shocks.

• The algorithm sees: Eviction filing | What it misses: A parent choosing their child’s health over a landlord’s timeline.

This isn’t about making emotional decisions or ignoring financial sustainability. Property owners have legitimate interests in reliable tenants. The question is: what actually predicts housing stability? The data from our thirteen permanent placements suggests the algorithm is measuring the wrong things.

I-It vs. I-Thou: What Algorithms Can’t See

The philosopher Martin Buber described two ways we relate to the world: I-Thou and I-It.

I-Thou is relationship. It’s seeing another person fully—their context, their capacity, their humanity. It’s presence, not transaction.

I-It is different. It’s seeing another person as object, as means to an end, as data point. It’s necessary sometimes—we can’t have deep relationships with everyone. But it becomes dangerous when institutions enforce I-It relationships where I-Thou should exist.

Housing should be I-Thou. It’s about people finding home, building stability, and creating community. It requires seeing capacity, understanding context, and recognizing that someone’s ability to maintain housing can’t be reduced to a credit score.

But algorithmic screening enforces I-It relationships. When Marcus walked into that housing office, the algorithm saw: credit score 510, eviction filing, risk assessment DENY. It couldn’t see Thou—the father navigating impossible choices, the worker building toward stability, the human being whose capacity the numbers couldn’t capture.

This isn’t about abandoning data. It’s about whether our systems preserve the possibility of a relationship even as they process information. Can we build accountability mechanisms that allow us to see both the pattern AND the person? Can we measure what actually matters without reducing people to data points?

That’s the question algorithmic screening forces us to answer.

The Burning House

Dr. Martin Luther King Jr. feared we were “integrating into a burning house”—gaining access to systems already failing.

Today, we’re integrating housing into algorithmic systems—replacing human judgment with automated screening that encodes historical bias in code.

When algorithms reject both those experiencing poverty and those working to address it, when they fail across demographic and economic lines, when their predictions prove wrong more often than they prove right—we’re not building better systems. We’re automating the failures of the old ones.

The house isn’t just burning from historical discrimination. It’s burning from the belief that complex human decisions can be reduced to credit scores and pattern matching.

Building Systems That Measure What Matters

The solution isn’t abandoning data—property owners need sustainable models. But we need systems that measure what actually predicts housing stability.

At AVANTKOFA, we’re building solutions grounded in these principles:

Transparency by default: People should know when algorithms assess them, what factors matter, and how decisions are made. The current black-box approach—where applicants receive only “DENIED” with no explanation—prevents meaningful appeal or improvement.

Community oversight built in: The communities most affected by algorithmic screening should have power in how these systems are designed and deployed. Not just consultation—actual decision-making authority.

Human override always available: There must be pathways for human judgment to supersede algorithmic decisions when context matters. Marcus’s situation required someone who could understand that an eviction filing during a medical crisis says nothing about future housing stability.

Alternative assessment models: We should measure what actually predicts success. Rental payment history is weighted more heavily than credit scores. Employment trajectory over current income snapshots. References from community members who can speak to character and capacity.

Right to explanation and appeal: Anyone denied housing based on an algorithmic assessment should receive a clear explanation of the decision factors and a meaningful opportunity to contest errors or provide context.

These aren’t radical proposals. They’re basic accountability measures for any system with this much power over people’s lives.

What Comes Next

Housing insecurity is reaching crisis levels. The systems we’ve built to address it—including algorithmic screening meant to remove bias—are often perpetuating the problem.

We can build better. Not by choosing between data and humanity, but by designing systems that measure what actually matters.

This is the work of closing the Affect Gap™—building systems that see capacity, not just patterns. That measure what matters, not just what’s measurable. The Essential Servant™ navigating algorithmic rejection is experiencing the same structural friction as the first responder receiving a pin for a life they couldn’t save. Different contexts. Same gap.

The thirteen people we housed didn’t need the algorithm to be more lenient. They needed it to measure the right things. They needed someone to see their capacity, not just their patterns. They needed a system designed for housing stability, not pattern conformity.

If you’re a housing authority, state agency, or private sector leader ready to move from analysis to action, let’s build these alternatives together. The proof of concept exists. The framework works. The question is whether we have the will to implement it.

This essay connects to what I call the Affect GaaP™—the structural dissonance between human capacity and systemic measurement. When algorithms measure the wrong things, they widen the gap between what people can do and what systems allow them to become.

I explore this fully in my forthcoming book, Cause and Affect: Why the Essential Servant Is Burning Out—and How to Stop It. The CaaS™ (Capacity-as-a-Service) Framework offers a structural response—for individuals navigating precarity and for institutions ready to measure what actually matters.

At AVANTKOFA, we’re building the civic infrastructure that closes these gaps—housing, workforce, and digital systems designed for human capacity, not pattern conformity.

Subscribe to Forward Notes (Substack) for more, or reach out: hello@antoinemwilliams.com

Leave a comment

Subscribe now

Introducing the Affect Gap™ and why the Essential Servant™ is burning out

• It’s what disaster preparedness training never covers.

• It’s the crisis your employer doesn’t have a policy or benefit for—even when your job is to solve that exact crisis for others.

• It’s the disaster we haven’t named yet.

We are perfectly attuned to spotting failures in the tangible world: a bridge buckles, a power grid goes dark, a bank collapses. When that happens, we know exactly who to blame, what budget was cut, and which infrastructure needs rebuilding. But what happens when the infrastructure isn’t steel and concrete, but people?

Imagine that one morning, every single employee from the cashiers to the regional managersat a company like Best Buy simply vanished. It would be inconvenient, certainly. It would cause market churn. But in a few months, the retail function would be absorbed by Amazon or Target, or a new digital service. The market adjusts.

Now, imagine that one morning, every essential worker, the City Planner who manages the sewer system, the Nurse responsible for public health protocols, the Analyst who processes food assistance, the Policy Expert trying to de-politicize flood maps, wakes up, and the vocation that anchors them vanishes. They are still physically present, but their integrity, their expertise, and their sense of mission are gone. They have been hollowed out, transformed into a mere NPC in their own professional lives.

The system still looks operational. But the human foundation (the Essential Servant™) has become so fragile, so overworked, and so emotionally detached that the integrity of the state begins to decay from the inside out.

The difference is critical: Losing a retailer is a market event. Losing the integrity of the public servant is a failure of the social contract.

The Affect Gap™

I first experienced what I now call the Affect Gap™ not as an academic studying data, but as an architect of systems who realized the foundation was rigged.

I was sitting in a high-stakes planning meeting, ready to present a major, data-driven initiative—a new, expansive strategy designed to create stability and improve community outcomes. My work was meticulous, sound, and critically aligned with the public interest.

The response from the governing body was not skepticism, but disinterest. Not a challenge on the facts, but a silent, political dismissal.

In that moment, I understood something I call the Crisis of Allegiance. I was not serving the public; I was serving a system that treated my expertise as optional, disposable, and, frankly, annoying (internalized or actualized the effect and affect caused was real and manifested).

The realization of my status came later, when I overheard a colleague use the term “NPC” (Non-Player Character) to dismiss a dedicated public servant’s contribution in a conversation with senior leadership. The casual cruelty of that designation, implying functional irrelevance, was a chilling affirmation.

I realized I hadn’t just become irrelevant; I had already been designated as such by the system.

Defining the Gap

The Affect Gap™ is the gulf between a professional’s Purpose Alignment (their genuine desire to do good work for the community) and the System’s Capacity (its ability to resource, protect, and reward that alignment).

When the system fails to match dedication with structural support, the resulting dissonance drains emotional and professional capital.

It is the reason you go home feeling exhausted, not from the work itself, but from the friction of the bureaucracy. From fighting red tape. From arguing with algorithms. Defending your integrity against political cynicism.

The Affect Gap™ manifests as:

→ Moral Exhaustion: The fatigue of enforcing policies you know are counterproductive, or prioritizing political agendas over community needs.

→ Loss of Agency: The feeling that your expertise has been devalued to irrelevance. If the data is discarded for politics, why bother collecting it?

→ The Isolation Tax: The loneliness of defending your work against public cynicism. The private sector worker can claim profit; the public servant can only claim a public good, a metric increasingly attacked and questioned.

From Soul to System

The Affect Gap™ is not a private matter. It is the crucial middle link in what I call the Crisis of Causation:

Individual Precarity (Cause) → Affect Gap (Mechanism) → Systemic Decay (Effect)

When the Essential Servant suffers from moral exhaustion and loss of agency, the community is the ultimate victim:

→ Erosion of Service Quality

• Disengaged, burnt-out employees become less creative, less empathetic, and more likely to cling to rigid processes. The bureaucracy becomes slower, which ironically fuels the public distrust that caused the problem.

→ Loss of Institutional Memory

• The most experienced, mission-driven professionals leave first, taking decades of specialized knowledge with them. This is the Brain Drain—the ultimate budget cut.

→ Political Vulnerability

• An agency with low morale and high turnover is easily manipulated. The leadership vacuum created by the Affect Gap™ is instantly filled by those seeking personal gain rather than the public good.

The Framework: Capacity-as-a-Service™ (CaaS™)

It requires what I call Capacity-as-a-Service™ (CaaS™)—a structural intervention that transforms the individual’s career from a vulnerable, disposable job into an indispensable, resilient service.

CaaS™ is built on five pillars:

1. Income Security — Financial buffers independent of a single employer’s fate

2. Benefits Access — Decoupling essential services (healthcare, retirement) from employment

3. Skills Currency — Continuous expertise updates against technological disruption

4. Network Capital — Diverse professional ecosystems providing support and alternatives

5. Purpose Alignment — Uncompromising dedication to the mission that serves the community

These aren’t recommendations; they are engineering specifications. They are the non-negotiable components of the professional armor required to survive what I call the Age of Precarity.

You Are Not an NPC

I left that planning meeting years ago and realized the challenge wasn’t just fixing the system; it was designing a new kind of professional armor. A social technology that could secure the human worker, enabling them to resist the corrosive forces trying to hollow them out.

Perhaps, the Research & Book I’m writing—Uncommon Wealth... Why America’s Essential Servants are Burning Out—and How to Stop It ... the full framework. It diagnoses the Crisis of Causation, maps the Affect Gap™, and provides the tools for individuals, organizations, and communities to rebuild the human infrastructure.

Antoine M. Williams is the Founder & Chief System Entrepreneur at AVANTKOFA and creator of the CaaS™ (Capacity-as-a-Service) Framework. His book, Cause and Affect, is forthcoming in 2026. More at Forward Notes (Substack) or reach out: hello@antoinemwilliams.com

Subscribe now

Leave a comment

Waiting for the perfect plan is a sophisticated form of a false start. In business, as in track, the gun doesn’t wait for your “readiness.” It waits for your presence.

The October Pivot

In 2025, my momentum was a ghost. No brand strategy. No “masterpiece” concept. Just a deep-seated need to move.

The Tooling

• I reached into my design bag (Adobe Creative Suite and Figma).

The Act

• Built the graphic. Posted it. Ran before I could overthink the stride.

The Logic

• Performance toward progress is the only metric that matters when your back is against the wall.

The Program of Work (POW)

Systems don’t break; they reveal. When you are grappling with income insecurity or slow traction as a social entrepreneur, your POW must be agile:

Identify the Insecurity

• Whether it’s food, housing, or capital—call it by its name.

Leverage the Multi-Skill

• I used my graphic design background to jumpstart my Management Consulting visibility. What “hidden” tool are you leaving in the bag?

Secure the Partnership

• Growth rarely happens in a vacuum. It happens in the Public-Private Partnership (P3) / Philanthropic (e.g., Community Foundations or Some Family Offices) what some in the space call a (4P) model.

The Program of Well-Being (POW)

You cannot build a “Beloved Community” on an empty tank.

Integrity check

• Is your current sprint fueled by “grind culture” or by a vision of long-term stability?

The Saturday Shift

• Finish strong so you can pour into what matters most tomorrow.

Space over Speed

• Speed gets you out of the blocks; space allows you to finish the race.

Integrity check

• Is your current sprint fueled by “grind culture” or by a vision of long-term stability?

The Saturday Shift

• Finish strong so you can pour into what matters most tomorrow.

Space over Speed

• Speed gets you out of the blocks; space allows you to finish the race.

The February Gear

February is more than a page-turn; it’s a new frequency. I am currently scaling my Strategic Planning and Grant Writing engagements for those ready to move from “insecure” to “impactful.”

Note for the Sprint,

Consistency beats perfection. Always!

Subscribe now

In my forthcoming book (Untitled), I leverage the work of great thinkers like Barbara Ehrenreich... and Michael Lewis... to frame the problem.

Recently, in my LinkedIn Timeline, a video with commentary on Don Norman‘s The Design of Everyday Things (2013) appeared. As I understood the commentator’s points, in essence, this work is about stuff or things and about why some systems prevent failure, and others invite it. Norman’s core concept is the forcing function, a design constraint that makes undesired outcomes structurally difficult or impossible.

For example, A microwave that won’t run with the door open. A car that won’t shift out of park unless you press the brake. A system that builds the safeguard into the architecture itself, rather than relying on user vigilance. Norman’s insight is deceptively simple: good design doesn’t blame the user when things go wrong. It builds the protection into the structure.

To the point: Burnout isn’t A Personal Failing. It’s A Design Flaw.

Barbara Ehrenreich (Natural Causes, 2018) diagnosed the wellness trap: a culture that treats structural problems as personal deficiencies. When the system fails you, you’re told to try yoga. The burden shifts from broken architecture to individual inadequacy.

Michael Lewis (The Fifth Risk, 2018) documented the essential servants: the people who manage nuclear waste, predict hurricanes, and keep the lights on. Invisible by design. The system depends on them absolutely. Protects them not at all.

• Ehrenreich diagnoses the cultural deflection.

• Lewis documents the invisible labor.

Some Program Managers, First Responders I know and have recently interviewed, CNA’s and Care Givers I personally know, Teachers too, all echo what Ehrenreich describes: a system that says we see your sacrifice; we will not be structurally support it, in that it extracts a toll your own life cannot structually support.

FOR THE RECORD: I am not a burnout expert, nor am I peddling a ‘magic cure.’ At best, I have a Sticky Notion. One I’ve set with for for some time, which wasn’t shaped into a linear thought until now.

By cross-examining the mechanics of exhaustion through a Lewisian, Ehrenreichian, and Norman lens, my personal journals have coalesced into a singular notion: Burnout is not a psychological failure of the individual; it is a structural failure of security.

I leverage every tool available to scale this message, but the core of it is a lived and working body of knowledge. This thesis wasn’t born in a library; it was forged in the ‘Affect Gap’—the structural friction that occurs when the high-stakes demands of service outpace the professional architecture meant to support the servant. It is a mechanical failure, not a moral one; the current design simply lacks the ‘hardware’ to sustain the human drive it requires.

Employers, Cities, Anyone, Kindly Note:

Excerpts from my LinkedIn Article and title, THE BOOK BETWEEN THESE TWO BOOKS … on Same Points of Discussion.

This is where the Capacity-as-a-Service (CaaS) Framework™

• CaaS™ is the forcing function Ehrenreich implies but doesn’t build.1

• CaaS™ is the protective structure Lewis documents the absence of. 2

• CaaS™ is Norman’s design principle applied to the human career.3

The framework of my forthcoming book asserts that these five pillars form the professional infrastructure that the system refuses to build:

1. Income Security - the forcing function against financial hardship. Buffers that make economic coercion structurally difficult. A paycheck cannot trap you if you have runway.

2. Benefits Access - the forcing function against the golden handcuff. Healthcare, retirement, and essential services are decoupled from any single employer. You cannot be held hostage by insurance if you’ve decoupled the anchor.

3. Skills Currency - the forcing function against obsolescence. Continuous expertise updates make professional irrelevance structurally difficult. The automation trap closes on those who stop learning.

4. Network Capital - the forcing function against isolation. A diverse professional ecosystem that makes the Affect Gap survivable. Moral loneliness is a design flaw; network capital is the architectural repair.

5. Purpose Alignment - the forcing function against betrayal. The non-negotiable commitment to mission that provides the courage to deploy the other four pillars when the system demands compromise.

They transform the Essential Servant from an exposed employee vulnerable to the Quadripartite Erosion of austerity, politics, technology, and isolation into a self-directed Architect capable of delivering their service with integrity.

Subscribe to Forward Notes (Substack) for more, or reach out: hello@antoinemwilliams.com

Subscribe now

I’ve been writing notes my whole career.

Not polished memos. Not formal reports. Notes. The kind you scribble during a planning meeting when something clicks. The kind you leave on your desk as a reminder of what matters. The kind you pass to a colleague when the official channels won't carry what needs to be said.

Why “Forward Notes”?

In project management, there’s a concept called the punch list—the running tally of what’s incomplete, what needs attention, what can’t be forgotten before the work is done.

In agile methodology, there are sticky notes on walls, sprint retrospectives, and continuous iteration toward something better.

In my two decades of public service—first as a police sergeant, then as a housing executive, now as a civic infrastructure architect—I’ve kept my own version. Notes on what’s broken. Notes on what’s possible. Notes on the gap between where we are and where we need to go.

Forward Notes is where I’m sharing those observations publicly.

What You’ll Find Here

This newsletter sits at the intersection of three things I’ve spent my career navigating:

1. The Human Side of Systems

I write about what it feels like to work inside institutions—the moral weight, the bureaucratic friction, the moments when doing the right thing and doing what the system rewards are not the same thing. I call this the Affect Gap™, and it’s the central theme of the book I’m writing.

2. Housing, Workforce, and Civic Infrastructure

I’ve managed $10M+ housing funds, catalyzed $280M+ in development, helped secure $22.9M in workforce grants, and co-founded organizations focused on housing equity. I’ll share what I’ve learned—the frameworks, the failures, the things that actually work.

3. The Architecture of Professional Preservation

I’m developing a framework called Capacity-as-a-Service™ (CaaS™)—a structural approach to career resilience for the Essential Servant. The people who keep communities running are often the first to burn out. Forward Notes will preview that work as the book develops.

Share © 2026 Forward Notes | Produced by Antoine M. Williams

Who This Is For

If you’ve ever felt like your expertise was dismissed for politics—this is for you.

If you’ve gone home exhausted not from the work, but from the friction around the work—this is for you.

If you’ve wondered whether the system you serve is capable of serving you back—this is for you.

If you’re building housing, workforce, or civic infrastructure and want to think alongside someone who’s been in the trenches—this is for you.

A Note on the Name

“Forward” because that’s the only direction that matters.

“Notes” because this isn’t a finished manifesto—it’s a working document. I’m thinking out loud, iterating in public, and inviting you into the process.

The tagline I keep coming back to: Fly forward, fetch the past. That’s the Sankofa principle that anchors my work at AVANTKOFA. Progress requires understanding where we’ve been. These notes are how I’m working that out.

If this resonates, and if you have your own notes—observations from the front lines of public service, housing, workforce development, or civic infrastructure—I want to hear them. Reply to any email or reach me at hello@antoinemwilliams.com.

Let’s build the punch list together.

— Antoine

Antoine M. Williams is the Founder & Managing Director at AVANTKOFA, a Civic Venture Studio engineering physical and digital infrastructure for a resilient America. He is the creator of the CaaS™ (Capacity-as-a-Service) Framework and author of the forthcoming book Cause and Affect.

Subscribe now