Philosophy · Design · A Life's Work
This is the final post in the six-part series Build Different — How I Think. If you haven't read the others, they're all worth starting from the beginning.
Designing Around Constraints.
I never start from a blank canvas. A blank canvas paralyzes me. I need something to push against — a restriction, a problem, a condition I can't ignore — before anything starts to move.
That's not a limitation I learned to work around. It's how I've always worked. And it took me most of my life to understand that it wasn't a flaw.
You never start from a blank canvas. You start from what's already there.
Before the Tools
A blank surface with no rules was uninteresting. A surface with limitations gave me something to design inside.
Before computers, before software, before design school — I drew.
Not on paper, necessarily. There were pieces of plaster chalk near the house growing up. We used them to draw on the street. In another neighborhood, I used markers on walls. Almost always monochromatic. Patterns. Mosaics. Geometric shapes on sidewalks. Not flowers or vases — my mother enrolled me in drawing classes and I was bored immediately. Still life didn't interest me. A mosaic on a sidewalk did.
I didn't know why at the time. I know now: my brain needed structure and repetition. A blank surface with no rules was uninteresting. A surface with limitations — the shape of a sidewalk tile, the width of a chalk line — gave me something to design inside.
My Father's Method
He never praised good grades. He rewarded good understanding.
My father was an engineer with more than 35 years of experience. And he had an ability that I've never seen replicated: he could explain anything to anyone using whatever was at hand.
If the person listening was an upholsterer, he explained mechanical engineering through upholstery. If they worked in pastry, he explained it through baking. If they were a designer, he spoke in design. He adapted the explanation to the way the other person processed information — not to show off, but because getting the concept across was what mattered. The medium was irrelevant. The understanding was everything.
He never praised good grades. He rewarded good understanding. His rule was simple: understand the concept first — everything else follows. Decompose the knowledge, then recompose it in a way you can work with.
I didn't know at the time that I was learning a method. I was just a sponge — absorbing everything from everyone, especially him. But that instruction became the foundation of everything I've done since: find the formula hidden inside the problem, understand it completely, and then you'll know exactly what needs to be done.
I spent 25 years absorbing that — from birth until I left home. I became an expert at seeing the world the way he saw it.
What I didn't know until much later was that this was also how he worked. He collaborated with presidents, with multinationals, with international organizations. He solved problems of extraordinary complexity. And he never announced it. He walked down the street like anyone else. The people who needed to know what he had done — knew. And they sent others. Always by referral. Always because the work spoke before he did.
I watched that for 25 years. And I absorbed it without realizing I was learning anything.
1998. The First Computer.
The blank canvas never inspired me. A specific goal always did.
I was twelve. A PC arrived at the house. I discovered the internet — version 1.0. I spent time searching for images. When I learned I could change the desktop background, that became the daily goal. Change the wallpaper. Find something better. Change it again.
That obsession led to the first practical design decisions I ever made: a folder with dividers, printed and organized. Covers printed for notebooks. Not design projects — just solutions to small needs with the tools I had.
Then came the tutorials. Photoshop at 13. 3DS Max at 15. Freehand, Illustrator, After Effects. I learned the tools without knowing the theory behind them. I designed without structure. The blank canvas never inspired me — but a specific goal always did. Make this wallpaper. Build this effect. Solve this visual problem.
University — The Why Behind the How
The university didn't teach me to design. It taught me to think in design.
I arrived at university thinking I already knew how to design. I had the tools. I had the hours. What I didn't have was the vocabulary for why anything worked.
Balance. Hierarchy. Alignment. Typography. Proportion. Repetition. Color theory. Psychology of form. High contrast techniques. Pointillism. Building a color chart from scratch. At first it felt unexpected. Then it clicked.
Every assignment arrived as a restriction — a format, a brief, a set of rules. And automatically, before I started, I already knew the direction. The constraint didn't block me. It activated me.
A friend told me after graduation that university had been easy for me because I already knew how to design. It bothered me — it made my effort seem small. I told him: the university didn't teach me to design. It taught me to think in design. I didn't fully understand what I meant until years later.
2009 — The First Hard Technical Constraint
The tightest technical constraints produced the most creative solutions.
One of my first projects after university was building a virtual world inside a web browser. This was 2009. HTML5 didn't exist yet. Web-based 3D engines were in their infancy.
I joined the team and proposed a change: use a game engine to render everything in real time inside the browser. The restriction was severe — limited polygons, baked renders, textures compressed to 1024 pixels, all running inside a browser that wasn't designed for any of it.
It didn't last long. The funding ran out. But the lesson stayed: the tightest technical constraints produced the most creative solutions. Not despite the limitations — because of them.
The Paint Factory
The box changed. The approach didn't.
After that came the paint factory — the leading brand in the Dominican Republic. Pre-made label templates. Specific color systems. Budget limits at every level. Design that had to work within the brand, within the printing process, within the cost structure. The box changed. The approach didn't.
SIUBEN — 2013. The Hardest Brief.
How do I make someone want to look at this?
I became a father before I started at SIUBEN. I arrived focused on design. The real challenge came with the first book — a national statistical study. Hundreds of pages of data. Complex tables. Dense numbers.
I physically rejected looking at a complex statistical table — and I had to make one readable. If you've read the previous post in this series, you already know why that rejection wasn't just aesthetic.
I asked myself: how do I make someone want to look at this?
The answer was the same process I had been using my whole life, applied to data for the first time: Understand the data. Decompose it into parts. Restructure it into something worth seeing.
I used the same design principles I had learned in university — contrast, form, hierarchy, typography, negative space — but applied them to statistics instead of graphics. I didn't discover how to make infographics. I discovered I already knew how. I just hadn't applied it to data yet.
The publication was a significant success. Then I repeated the model. Understand. Decompose. Restructure. Every time.
The Formula Behind Everything
Every field has a formula. The skill is understanding it — and then designing inside it.
After 20 years of working across graphic design, communications, government, construction, and technology, I've noticed that every discipline follows the same structure:
The structures
Methodology of Research
Problem → (Data + Analysis) → Interpretation → Knowledge
Creative Brief
Challenge / Need → (Audience + Insight) → Key Message → Creative Solution
Advertising Campaign
Objective → (Insight + Creative Concept) → Media Plan → Impact / Conversion
Homelab
Need / Use Case → (Hardware + Software) → Configuration → Functional Service / Automation
3D Design / Render
Concept / Plans → (Modeling + Texturing) → Lighting / Render → Final Image / Animation
Software Development
Requirement → (Code + Logic) → Testing → Deployed Application
Fabrication / Workshop
Design / Diagram → (Cutting + Assembly) → Finishing → Completed Piece / Furniture
The domain changes. The structure doesn't. Every field has a formula. The skill is understanding it — and then designing inside it.
Working Behind the Scenes
Not visibility. Function.
My father never walked around showing his portfolio like a business card waiting to be praised. He worked hard. He did it right. He didn't announce it. And the right people always found him.
I learned that by watching him for 25 years — not because he taught it as a lesson, but because it was simply how he lived.
In almost 20 years of professional work, I've worked with every type of client — commercial, institutional, governmental, international. I've never entered a competition. I've rarely shown my work publicly. What exists is on Behance and Dribbble — and most of it is years old. The rest belongs to the people it was built for, under agreements that prevent me from showing it.
That aligns with something I've understood about myself for a long time: I work best as the number two. The person who makes things function without needing to be the protagonist. The one who finds the solution inside the constraint and hands it off without a signature.
There is a specific pleasure in watching something work — a system, a publication, a network, a kitchen — and knowing that you built it, without needing anyone else to know. My father taught me that pleasure. He lived it for 35 years. He worked with presidents and walked down the street like anyone else.
That's the version of success I understand best. Not visibility. Function.
The Closing
And what's already there is always enough to build something worth building.
My father simplified complexity. My mother invested in therapy I didn't understand at the time. The university gave me vocabulary for instincts I already had. Twenty years of clients gave me constraints I couldn't ignore. And every restriction — economic, technical, physical, temporal — produced work that unlimited freedom never would have.
You never start from a blank canvas. You start from what's already there.
And what's already there is always enough to build something worth building.
If any part of this series connected with the way you work — drop it below. I'd genuinely like to know.
Build Different — How I Think · Complete Series
Post 1 — Embrace the Mistake
Post 2 — Think Inside the Box
Post 3 — If I Have to Do It Twice, I Build a System
Post 4 — If I Can't See It, I Don't Understand It
Post 5 — Everything Wants a Second Life
Post 6 — Designing Around Constraints
This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product listed here is something I personally own and use daily.
