The Team Is the Product
Choose the company you want to build first, pick a problem worthy of it, then treat every hire as a product launch.
- Difficulty
- Expert
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 92%
The Browser Company was designed backwards from the team. Miller and his co-founder Hursh decided first that they wanted a company where they could hire anyone they admired, then went looking for a prompt ambitious enough that the best people in the industry would want to work on it — a new form of computing, not a browser. Everything else follows: the CEO treats the team as the product he manages, interviews are designed to talk candidates out of joining, and every hire is announced publicly as a launch.
Origin
Josh Miller and co-founder Hursh, drawing on a decade of working together (their first company was acquired by Facebook). Miller cites the General Magic documentary as the emotional model: a company that failed by every traditional business measure, yet whose people remained proud and nostalgic decades later and went on to build the industry — 'if only we could be so lucky to assemble that type of group of people'.
Core principles
- 01Miller: 'I don't care about web browsers.' The category was chosen to serve the team ambition, not the other way round.
- 02The aspiration has to be big enough that the greatest minds in your industry would want the prompt — hypothetically, before you ask them.
- 03Senior people join to do the work that will define their careers, not for title or money. They arrive with an 'if I'm not on the equivalent of the early iPhone team I'll be bummed' hunger.
- 04What such people require: an ambitious aspiration, real empowerment to act on the prompt as they see fit, and a kind culture (their tolerance for anything else is near zero).
- 05Credit must land on the maker, not the CEO. Silicon Valley's CEO hero-worship is precisely what stops remarkable people from joining.
- 06Hiring compounds: the celebration of one great hire is the recruiting pitch for the next. Miller calls it a tumbleweed.
How to run it
- 1
Decide the team you want before the idea
Start from the question 'who do we want to spend a decade with?' — Miller and Hursh noticed that looking back on ten years, it was the groups of people and moments with them that were the best memories, not the products.
- 2
Pick a prompt worthy of that team
Choose a problem the greatest minds in your industry and adjacent ones would want to work on hypothetically. The Browser Company's real prompt is not a browser but a new form of computing — an internet computer — precisely because the browser framing was too small to attract who they wanted.
Pro tip State the ambition one level above what you are actually shipping, so the day-to-day work sits inside a larger promise.
Watch out The ambition must be honest. Manufactured grandiosity reads as bombast, which Miller himself flags as the risk of talking this way.
- 3
Run interviews that try to talk people out of it
Do not pitch. Miller's interview format is 'ask me anything you want, I'll be super honest, most people shouldn't want to work here'. What a candidate chooses to ask, and how they follow up, is more revealing than any question he could pose — and he screens on authenticity in the answers.
Pro tip The ask-me-anything format doubles as the values test: the questions people ask expose what they actually care about.
- 4
Make senior people ICs and let them build
Offer the highest-calibre people the chance to do the craft again as individual contributors. The Browser Company hired Darren (co-created the first Chrome prototype, ran it for 16 years, hundreds-to-thousands of reports) as an IC; Tara (original Paper by FiftyThree team, later SVP of product at Vimeo) as an IC engineer; Peter Vidani (first designer at Tumblr, later SVP of design at Slack) as an IC designer.
Pro tip Give them the ambitious promise and then get out of their way — Miller's stated formula for what heartfelt-intensity people need.
Watch out This only works if empowerment is real. Senior ICs who have already had the fancy titles have no patience for being over-managed.
- 5
Launch every hire and every maker publicly
From the very first person hired, announce them publicly and earnestly — who they are as a person, what they did — and treat it as a product launch. When you ship, name the individuals: 'this animation was fun — Sherry made that, Sherry is incredible.'
Pro tip The CEO should explicitly disclaim credit for the product: Miller says he does a lot for The Browser Company but he did not make Arc and did not make Peek.
Watch out This has to be authentic or it inverts. The point is a reinforcing cycle where great people know their work will accrue to them and not to a founder-genius myth.
In the wild
Darren, who co-created the first prototype of Chrome and then ran it for sixteen years with hundreds if not thousands of people reporting to him, joined The Browser Company as an individual contributor — and is the person Miller cites as most embodying the 'assume you don't know' beginner's-mind value.
→ A pattern of senior hires (Darren, Tara from Paper/Vimeo, Peter Vidani from Tumblr/Slack) all joining as ICs, which Miller reads as evidence the team-as-product design is working.
Before anyone at the company would have been a recognizable name, The Browser Company publicly celebrated each new hire in a heartfelt, personal way — because if the company is the product, the first designer joining is the launch.
→ A compounding 'tumbleweed' effect Miller credits for later attracting people who had already made money and held senior titles elsewhere.
Common mistakes
CEO hero worship
When credit accrues to the founder-figurehead, the people who could actually build the thing have no reason to come. Miller deliberately routes praise to the individual maker and states publicly that he does not make Arc.
Pitching candidates
Selling the company hard filters for people who want to be sold. Miller inverts it — most people shouldn't want to work here — so that the ones who push through are self-selected on genuine belief.
Choosing an idea the team you want wouldn't respect
If the prompt isn't one the greatest minds in your industry would take hypothetically, no amount of comp or culture-building fixes the recruiting problem. The idea selection is the hiring strategy.
Is it for you?
Best for
Founders early enough to still choose their category, who want to assemble an exceptional senior team and are willing to design the company around that goal.
Not ideal for
Companies already committed to a category, or leaders who need to scale headcount fast on execution rather than assemble a small group of exceptional makers.
From the transcript
“I view our product as our team”
“if I have an interview with someone I don't pitch them I say what do you want to ask me anything you want I'll be…”
“when our first designer joins we want to tell everyone about it that's a product launch that is the product launch and then whenever we…”
“from the very first person we hired we celebrated them publicly the fact that they join and in a very like heartfelt way telling you…”
From the episode
Competing with giants: An inside look at how The Browser Company builds product
Josh Miller (CEO)