the first person I brought on to NDC

When I was hiring the first designer for NDC, my inbox filled up fast. Portfolios from people I had never worked with. Some of the work was genuinely strong. Strong enough that I could see myself making a case for any of them.

I did not go that route.

I hired someone I went to college with. Someone I have collaborated with on multiple projects in the years since. Not a hypothetical read based on a portfolio and two interviews. An actual track record going back years. I knew how they handled feedback. I knew they followed through. I knew what it felt like to build something with them when the work got complicated.

That context is not something a portfolio gives you.

What a portfolio actually tells you

A portfolio tells you what someone can produce when they have time, control over scope, and no client breathing down their neck. It tells you nothing about how they respond when a client changes direction two weeks before a deadline, how they communicate when they get stuck, or whether they flag problems early instead of letting them sit until they become your problem.

Those are the questions that matter once the actual work starts. Those are the questions that decide whether a hire is a multiplier or a drag.

A great portfolio paired with bad answers to those questions is one of the most expensive mistakes a small business can make. You hire on talent, you discover behavior, and by the time the gap is obvious you have spent months trying to make it work. Firing someone two months into a hire feels like an admission that you failed at the front end, so you keep trying.

The default founders should question

Founders default to "find the best candidate." A pool of resumes, a portfolio review, a few rounds of interviews, a decision under uncertainty.

The better question early on is "who do I already know that can do this?"

Not because familiarity is comfortable, but because verified track record is a more reliable signal than curated work samples. You have already seen the person handle the things a portfolio cannot show you. You have data. The hire is no longer a guess.

Most early hiring decisions feel risky. Hiring someone you have already built something with cuts most of that risk in half. The remaining risk is whether the role fits the person, not whether the person fits the work.

Why the default is the default

The reason founders default to portfolio search is that it feels rigorous. You can compare candidates against criteria, you can score them, you can defend the choice afterwards. The candidate-pool approach mimics what big companies do, and big companies do it because they have to. They cannot rely on personal trust at scale.

Small businesses are not big companies. Trust does not need to be replaced by process at the size you are at when you are making your first hires. Trust is the asset that small businesses have and large ones do not. Using it is a feature of being small, not a shortcut around the work.

The principle

The first person I brought on to NDC was not someone I discovered through a search. They were someone I already trusted. That trust had been earned through years of actual work together, not presented through a PDF.

That distinction has mattered every day since.