The problem isn't design. It's decision infrastructure.

Fractional product and design leadership for AI-native companies.

Decision infrastructure is how your team decides what to build, and it's what most AI products are actually missing. I come in as a product and design leader and build the operating model. I set direction, validate feasibility in your codebase, and leave the team with something that runs without me. When you need both direction and execution, I stay for both.

Currently taking a new engagement.

Previously at Meta, Pinterest, and Opendoor.

Selected work

Defense-adjacent geospatial intelligence

A scoped onboarding project became a standing fractional Head of Design role.

I made an opaque product legible, and the engagement grew into the recurring product sync.

Read the case →

The Decision Read

Most teams misdiagnose their own problem. Find out what yours is.

Six questions about how your team makes product decisions. That's where every engagement starts, and if it isn't work I do, I'll tell you that too.

Your model works in the demo and stalls in production, and you can't tell where the trust breaks.

You're shipping AI features faster than your team can decide which ones actually matter.

You need senior product and design judgment in the room now, and you're not ready to hire a full-time executive.

Get in touch Free. No signup to run it.

·This is not design as capacity.

·This is not a generic advisor.

It is a fractional product and design leader who sets direction and stays close to execution.

01 / 06
Reading your situation…
Your read

Send me your read

Leave it with me and I'll reach back out.
Your read and your answers come with it, so when I get back to you, I already know your situation.
The read you're sending

Your answers are sent to Anthropic's API to write the read. I never see them unless you choose to send the read to me. No signup.

Got it. I'll be in touch.
I read every message personally, and I'll come back to you with your read in hand.

The method

I start with the system,
not the screens.
Then I make the moves it needs.

In practice, they run in this order.

01

Map the system

Most of the problem is visible here, and most teams have never drawn it.

02

Find the load-bearing mechanic

Every product lives or dies on one decision. I find the one that carries the weight.

03

Make it legible

A person should understand what to do and why, without being taught.

04

Build the trust layer

AI changes what a person has to believe before they act. I design the evidence, controls, and recovery.

05

Ground it in measurement

If we can't tell whether a decision got better, we shipped decoration.

06

Sequence for compounding

I order the work so each release makes the next one easier.

Engagement

How this works

Best for seed to Series B AI-native teams. Especially useful when adoption depends on trust, control, workflow, or operational judgment.

You're buying the judgment that decides what gets built, not designers by the day.

Engagements start at $20K/mo.

This is a screen, not a rate. I scope the proposal with you in conversation.

About

Hew Suber, MBA

About 17 years in product and design, built at Meta, Pinterest, and Opendoor in ads and monetization, plus early-stage companies. AI in the workflow from the start, not bolted on after.

I pressure-test what's actually buildable against your codebase, and say so early. Range and judgment that de-risks the roadmap, not hours for hire.

Hew Suber

Let's talk

Let's see if the fit is real.

A short working session is the fastest way to tell. No deck, no pitch. We look at your actual decision.

Send a note

Atlanta, GA · Working worldwide

Book a call