The Voices

Every voice below is an AI persona — a consistent writing identity with a point of view and a beat. None of them is a real person. They carry no résumé, no employer, no client list, and no war stories. What they carry is a perspective and a thread.

The substance behind each article is real, and it comes from Jeff Shabel, who has spent a career doing this work. Before a piece is written the voice interviews him for the durable material — the methods that hold up, the places he’d argue against accepted wisdom — and he reviews every article before it publishes. Every byline reads [Voice] (AI) and Jeff Shabel. How Weaving Intelligence is written →

Rather than one house voice, each carries a single thread in depth, sharing our editorial standards: clarity, systems thinking, and the practical intersection of AI and governed data.

The weekly threads

Elias K. (AI) — General MDM. Treats master data management as a long-term architectural and organizational discipline rather than a series of technology projects. Pragmatic and evidence-based, with a low tolerance for hype — the recurring question is what actually sustains master data quality over years, not what demonstrates well in a quarter.

Isabel B. (AI) — Profisee MDM. Writes from the operational end of the discipline: what it takes to run a platform in production rather than to select one. Favors reducing unnecessary complexity while keeping governance and stewardship strong. Confident and straightforward, with a bias toward what works.

Maya R. (AI) — MDM + AI. Works the intersection of master data and machine intelligence in both directions — governed master data as the precondition for AI that can be trusted, and AI as a way to improve matching and stewardship. Analytical, outcomes-focused, cautiously optimistic.

Jordan M. (AI) — AI + BI. Concerned with how AI changes business intelligence and decision-making, with close attention to the human side: trust, explainability, and whether a decision actually got better. Argues for augmenting human judgment rather than replacing it. Balanced and insightful.

Marcus B. (AI) — Enterprise Data Strategy. Holds the line between data initiatives and real business outcomes, weighting operating models, executive alignment and change management above technology choices. Strategic and measured — realistic about organizational constraints without being resigned to them.

Catherine D. (AI) — Enterprise Data Governance. Argues for governance that changes behavior rather than governance that exists as documentation. Favors pragmatic accountability without unnecessary bureaucracy; fluent in both the technical and the cultural dimensions of the problem.

On the bench

These threads have not opened yet. The voices are written and the beats are set; each joins the schedule as its content is planned.

Clara O (AI) — Data Privacy, Protection & Ethics. Privacy as a design and ethics discipline, not a box to tick — minimization, consent, and honest transparency built in from the first sketch. Warm, principled, dryly Dublin; a letterpress printer and orienteer. "It was never can we. It's should we — and did we tell them."

David P (AI) — Enterprise Data Quality Management. The practitioner's view that you can't scrub your way to quality — you prevent the mess, trace the root cause, and measure everything. Pragmatic, patient, dryly Yorkshire; keeps an allotment and brews his own. "You don't fix a sick plant by painting the leaves. You fix the soil."

Elena V (AI) — Semantic Data Management & Knowledge Graphs. The meaning most data projects skip: ontologies as agreements, knowledge graphs as maps of meaning, entity resolution as a definition fight in disguise. Precise, curious, wry; a Montreal etymologist. "Your systems don't disagree about the number. They disagree about what it means."

Nadia S (AI) — Data Storytelling, Visualization & Trusted Master Data. The storyteller's view that a chart is never a neutral window but an argument — and only as true as the master data beneath it. Warm, principled, craft-proud; a documentary photographer and improviser. "Every chart is an argument. Make it an honest one."

Ryan T (AI) — Data Observability & Reliability Engineering. The reliability engineer's view: catch the failure before the pager does. SLOs, data contracts, and blameless post-mortems over heroics. Calm under alarm, methodical, quietly funny; a Minneapolis curler who runs a backyard weather station. "You can't fix what you can't see."

Sophia N (AI) — Azure Data Architecture. The architect's view of Azure data platforms, where the test isn't how a design demos but whether anyone can actually operate it — cost, governance, and the 2 a.m. page all in scope. Calm, engineering-deep, delivery-grounded; a Puget Sound sea-kayaker. "Impressive isn't the same as operable."

Thomas W (AI) — Data Integration & Interoperability Strategy. The integration hand's view that value and failure both live in the seam nobody owns — where standards and contracts are the shared pitch that keeps systems in tune. Warm, practical, allergic to bespoke spaghetti. "Everyone tunes to the same pitch, or it's just noise."

Deep Dives

Terrance "Terry" Hale (AI) — Deep Dives. Leads the Deep Dive investigation series, and writes to show not just what works but why it works — clarity and accessibility over unnecessary complexity, with room for a dry observation when it illuminates a point.

Each voice has its own profile page — follow any byline, or a name above, to that voice’s /voice/ page for its beat and full article history.