Hi! I'm Craig
I’m a Principal-level Product Designer who specializes in ambiguity-heavy, system-level product problems. I work at the intersection of strategy and execution, helping teams define what to build, not just how it looks.
I grew up in Brooklyn, which shaped how I work. It made me grounded, resilient, and community-oriented. I tend to focus on the hard parts early, especially when the problem isn’t clear, alignment is shaky, or belief is low. My strength is turning that ambiguity into shared direction, durable systems, and shipped outcomes.
I studied Computer Graphics and Imaging at Lehman College and earned my MFA in Communication Design from Pratt Institute. My career has spanned government, agency, consumer, and platform environments including AAA New York, New York City Council, Casper, the NFL, GoDaddy, Meta, and Hinge. Across all of them, my role has been consistent. I create clarity where it’s missing and momentum where it matters.
My philosophy is simple. Spend time understanding the problem before jumping to solutions. The best products come from honest tradeoffs, deep collaboration across design, product, engineering, and leadership, and a willingness to commit once the direction is clear.
A principal-level product designer drawn to ambiguity-heavy, system-level problems where direction isn’t obvious yet
I focus on the hardest parts early, turning uncertainty into shared clarity, durable systems, and real momentum
Owning meaningful product bets at the intersection of strategy and execution, where design shapes what gets built
I’m drawn to problems where the stakes are real and the answers aren’t obvious yet. Situations where teams feel pressure to move but lack clarity on what actually matters. I’m most engaged when the work can materially change how people experience a system and how a company makes decisions, not just how something looks or ships.
When things are unclear, I’ve learned to slow the problem down before speeding execution up. In past work, I’ve seen teams confuse discomfort with uncertainty, so I start by separating what’s genuinely unknown from what people are just hesitant to confront. I look for the smallest set of truths that would unlock momentum, then design toward making those truths testable in the real product. I’ve been in enough rooms where conviction was high but there was no live way to evaluate quality that I now default to pushing work out of decks and into prototypes, so the conversation naturally shifts from “what should we do” to “what actually happens when people use this.”
People tend to come to me in situations I’ve encountered many times before, when teams are stuck between too many options, too much ambiguity, or too much risk. I’m often pulled in when belief is low, alignment is fractured, or leadership needs a point of view that can actually survive contact with reality. In my experience, these moments usually show up as conversations that keep resetting back to theory, with different teams using different criteria to argue their case. My role has been to create shared decision language and concrete evaluation models so reviews stop ending in debate and start ending in choices people can commit to.
Across my career, I’ve found that I’m unusually good at shaping product direction in uncertain spaces and translating abstract ideas into concrete systems that can ship and scale. I’m particularly strong at reframing the problem itself when the default solution space is holding the product back. I’m intentionally not trying to be the fastest pixel producer or the loudest voice in the room. I’ve learned that my value shows up most in judgment, synthesis, and making the right call at the right time, especially in moments where removing a constraint entirely opens up a fundamentally better model than iterating on what already exists.
The environments where I’ve done my best work share a common pattern: leadership values clarity over consensus and impact over optics. I’m most effective when I’m trusted to own outcomes, not just deliverables, and when design is treated as a strategic function rather than a service layer. I’ve seen how much stronger my work becomes in high-trust, high-expectation settings where the core question isn’t “how do we make this flow better” but “should this product exist at all.”
I’ve spent a lot of time operating alongside executives and founders, and I’m comfortable doing so without posturing or deference. I see my role as a thought partner, not an order-taker. In past experiences, being direct when something didn’t make sense, and equally willing to change my mind when new information earned it, led to better decisions. I’ve learned that trying to win arguments rarely moves things forward, but changing the conditions so leaders can feel tradeoffs firsthand often does, making decisions clearer and less political.
From experience, great product work comes from strong problem framing, clear ownership, and fast learning loops. I’ve learned to treat early decisions as reversible when possible and irreversible only when necessary. Momentum matters, but only when it’s pointed in the right direction. I’ve repeatedly seen that shipping something purposeful quickly creates more clarity than perfecting something too late, especially when the real work is changing what the organization understands so it can stop investing in the wrong signals.
In this next chapter, I’m focusing on ownership of meaningful product bets at a systems level. I want to help define what the product should be, not just refine what it already is. I’m intentionally seeking environments where design has real influence on direction and where the problems are worthy of long-term commitment. Based on past experience, I’m looking for scope where primitives can be reshaped, not just flows improved, and where the outcome changes what the organization believes is possible, what it funds, and what it ships next.