Start with the decision question.
A good analysis begins with what needs to be understood, proven, falsified, or decided.
I analyze public data, build dashboards, and surface the operational patterns behind city services. My work turns missing context into clearer evidence, better questions, and decisions people can actually use.
Budgets. Utilities. Housing. Family services. Operations. Every public system produces signals about what is working, what is breaking, and who is carrying the cost.
Information is abundant. Understanding is not. The work is turning messy administrative data into clear evidence that helps agencies see patterns, ask better questions, and make better decisions.
City systems are not abstract. They shape daily life, neighborhood stability, and whether public service feels navigable or opaque. Good analysis restores the context people need to act with confidence.
I’m Jonathan Martinez, a Native New Yorker whose work sits at the intersection of public systems, data analysis, dashboards, and systems thinking.
I’m especially interested in NYC government because city agencies hold the data, constraints, and responsibility of real-world operations. I want to help turn that data into analysis that is clear, usable, and connected to decisions.
A good analysis begins with what needs to be understood, proven, falsified, or decided.
Before solving a problem, understand the agency, population, process, and constraint environment that produced it.
Dashboards and notebooks should make conclusions defensible, not just visually impressive.
Row counts, filters, missingness, and caveats are part of the argument—not cleanup chores.
My AI workflow helps plan, review, and pressure-test analysis while keeping human responsibility at the center.
The best analysis becomes a method others can rerun, audit, adapt, and trust.
My dashboards and notebooks are produced through a repeatable AI-assisted analyst workflow: plan the argument, structure the notebook, handle large data safely, convert evidence into memos, and review the work before publishing.
Every notebook starts with a claim, decision question, required data, metrics, validation checks, and risks before code begins to sprawl.
PlanningLarge local files are handled through scoped columns, chunked reads, early aggregation, deterministic samples, and visible scan validation.
ExecutionRaw notebooks become concise artifacts that show the conclusion, why it is credible, how it was produced, and where the limits are.
CommunicationBefore sharing, I pressure-test execution order, filters, evidence, charts, caveats, reproducibility, and whether the conclusion is supported.
Quality controlOutside of my professional work, I maintain Studio 16 as a small research practice for AI, systems thinking, and organizational decision-making.
Related work ↗These artifacts show how I think with data: dashboards, analytical notebooks, evidence memos, and public-data studies built to make complex systems easier to understand.
Selected dashboards and public-data analyses that demonstrate analytical judgment, civic context, and the ability to communicate findings clearly.
A proof-of-work dashboard for tracking client revenue, invoice status, and business performance signals.
A diagnostic study of utility spending, resident opportunity cost, and hidden public-housing burden.
NYC youth-system data examined across intake, retention, and the consequences of institutional boundaries.
I bring data analysis, dashboard development, requirements thinking, and a systems lens to civic technology and public sector work—especially where complex operations need evidence people can trust.