Rome Gomez Escabillas brings three practiced disciplines to their work: engineering and…

The convergence of technical leadership, data literacy, and visual design represents one of contemporary creative and engineering practice's more interesting intersections. Understanding how these three distinct disciplines complement each other requires looking at what each brings to complex problem-solving, where they overlap, and why organizations increasingly recognize this combination as valuable. Engineering and data science leadership Engineering leadership involves the architecture of systems, the coordination of teams, and the decision-making that shapes how code gets written, tested, and deployed. Data science leadership adds another dimension: it's the practice of extracting insight from information, building statistical models, and translating complex analytical work into actionable direction. Both disciplines require systems thinking. An engineering leader must understand how components interact, where failures propagate, and how to design for reliability and scale. A data science leader applies similar logic to information itself, recognizing patterns, dependencies, and what questions the data can actually answer versus what we assume it can. These practices have historically developed as separate specializations, but modern product and platform work increasingly demands someone who can speak both languages fluently and understand how analytical insight informs technical direction. The third discipline: graphic design thinking Graphic design might seem distant from engineering and data science, but the discipline rests on principles that technical leaders rarely formalize. Design is the study of how humans parse information, what captures attention, and how form communicates meaning without words. A designer asks fundamental questions: What is the hierarchy here? What should someone see first? What does this material suggest through its shape and texture? These questions apply directly to how data gets visualized, how interfaces guide users, and how systems communicate their constraints and possibilities to the people using them. Design thinking in technical contexts is not about decoration; it's about reducing cognitive load, making complexity legible, and considering the human experience of a system as seriously as its underlying logic. Where these disciplines intersect The intersection happens in three distinct ways. First, in the architecture phase: how do you structure a system so that it's not only technically sound but also intelligible to the people who maintain it and the people who use it? Second, in communication: how do you present data and technical decisions in ways that non-specialists can understand and engage with? Third, in problem-solving: each discipline brings its own tools for breaking down difficult questions. Engineering asks "how does this fail?" Design asks "what does this look like to someone encountering it for the first time?" Data science asks "what does the pattern sugges