Technology should answer to the humans it serves.
That means the people using the tools every day. And it means the people on the hook for the decisions, the quality, and the outcomes those tools shape.
Most organizations stop interrogating their software once the features exist. Ishmael doesn't. We use a human-centered methodology to examine how technology actually behaves inside the system — how work moves, where decisions stall, where ownership blurs, where teams compensate through invisible labor, and where tools create drag instead of clarity.
Because technology doesn't stay where you put it. Software decisions become operating decisions. Vendor choices become governance choices. Workflow gaps become labor. AI adoption becomes accountability.
This work is for leaders carrying the cost of complexity they did not always create but can no longer afford to ignore. Ishmael names the condition, shows the risk, and makes the tools answer to the people they were built to serve — again.
It started with Ana.
Ana Monroe was reading systems long before she had a word for them. She grew up in the South, where hospitality comes with an unwritten rulebook — a thousand rules nobody prints, nobody teaches, and everybody somehow knows, each one quietly enforcing itself. Most kids just learn the rules. Ana wanted to know how a whole community could agree on a code no one ever wrote down — and what it was really holding in place.
She ran competitively in college, and distance running taught her the same thing from the inside. A race isn't won by the most dramatic effort. It's won by the system that holds — the pacing, the discipline to build something that lasts the whole distance instead of burning bright and folding at the turn. The work that matters isn't the impressive sprint. It's what's still standing at the end.
Early in her career she worked as an administrative assistant at a large company — a job most people underestimate. She didn't. She watched an entire organization run on human systems that long predated any software: the way a note that a client's hockey team had made the playoffs would reach the CEO before the call, not because a tool flagged it, but because someone in the network knew it mattered and made sure it moved. She was learning how information, judgment, and care travel through people — the original operating system, the one running underneath all the others.
The technology came later, and it never replaced that first lens — it extended it. She earned an MFA-STEM from Art Center College of Design and a degree from Columbia, wrote the four-volume Human-Centered Design Field Guide series practitioners now learn from, and became a founding member of the federal government's first AI Safety team — building its first principles-based, platform-agnostic AI training and red-teaming agency AI systems for ethical guardrails.
Each step was the same instinct in a new vocabulary: find where a system has stopped serving the people inside it, and set it right.
She's still chasing the same layer underneath she went looking for as a kid — what gets adopted, what holds, and what quietly gets put down. Ishmael is what she decided to build with the answer.
She didn't build it alone.
Aaron Meyers, Chief Data Officer, brings decades of data strategy from the EPA and the GSA, and a Peace Corps tour in Honduras.
Scott Kellum, Chief Design Officer, is an internationally recognized authority on design for the web, holding multiple patents in digital technology.