- Dive Club
- Posts
- š¤æ ferrari products
š¤æ ferrari products
how to break down complex design problems

Palantir is one of the most powerful products in existence today.
It provides critical government and enterprise infrastructure from the factory floors to the front lines.
You can literally use their developer platform to build anything (even your own version of Airbnb).
And itās a big reason their growth looks like this even after 20+ years š

So whatās it like being a designer at Palantir?
I was curious so I interviewed longtime design lead Aashman Goghari to go behind-the-scenes. Here are a few ideas that stood out š
š¤ WITH RAYCAST
Just when I thought I understood how powerful Raycast isā¦
They just released their all-new AI extensions āØ

So you can interact with all kinds of apps using natural language and string together actions to create custom workflows.
For example in a single command I can start a focus mode, change my slack status and press play on my favorite Spotify playlist.
And that is just the startā¦ there are already extensions for Shopify, Linear, Zoom, Google Calendar, etc.
This is a big time building block for the future of AI and productivity. And Iāve never been more excited to be all-in on Raycast.
If you want to learn more they have a really compelling video you can watch here š
š KEY TAKEAWAYS
Breaking down complex design problems
1 ā Handling complexity in UI
Aashman designs for a wide spectrum of technical ability. On one hand you have business analysts who simply interpret data, and on the other you have backend engineers building complex systems architecture.
So how do you design interfaces that preserve some semblance of simplicity while allowing users to tap into the full power of the āFerrariā?
a) Progressive Disclosure
One strategy you might be familiar with is to slowly reveal necessary elements as they get more familiar with the system.
That way less technical users arenāt overwhelmed but this can also add permanent friction for more technical users.
āit's easy to conceal something for the first time But for the returning advanced user, they're gonna be quite madā
Thatās why Aashman often uses a second strategy š
b) Multiple entry points
Itās common for Palantir to allow users multiple ways to achieve tasks with various entry points.
āwe might have a whole dedicated mini app to get into intense detail about a given workflow or to help people debugā
This way advanced users have a dedicated place to āopen the hood of the Ferrariā when needed.
Redundancy isnāt always a bad thing š¤·āāļø
2 ā Ask dumb questions
Itās not uncommon for Aashman to sit in highly technical conversations where he understands <50% of whatās being discussed.
Thatās why heās often coaching other designers at Palantir to help them get comfortable asking dumb questions (which can be scary, I admit).
āItās easy to think this is not the right forum to ask this question. It is. You should absolutely go ahead and get those clarifying questions outā
He brought this idea up multiple times so itās obviously a big part of succeeding as a designer at Palantir.
āAs a designer youāre a first-class citizen of this meeting even if youāre the only non-technical personā"
3 ā How to crush an interview at Palantir
You donāt have to have an enterprise background to demonstrate your ability to handle complexity as a designer.
Aashman says he can āderive second-order complexity questionsā out of something as simple as a calculator or weather app.
Heās looking for designers who are capable of getting ultra-specific in a single set of decisions.
āif there isn't that much to work with, I'll go deep. And I'll ask highly specific questions about state machines to understand if they've really thought about the details.ā
So the next time youāre preparing for a portfolio presentation, consider dedicating a chunk of time to go incredibly deep in a single sliver of the project (we did this during Maven interviews too).
Where did you have a concrete opinion about a seemingly small detail? Go deep there.
4 ā Breaking down problems like a developer
Aashman also shares fantastic mental models for systems thinking, breaking down problems like a developer, and a lot moreā¦ but Iāll save that for the full episode :)
How much did you enjoy this issue?Never hesitate to reply with feedback too :) |
Meet the Dive partners
I made a list of my favorite products and asked them to come on as sponsors of the newsletter/podcast. They said yes š„¹
The #1 way to support Dive Club is to check them outš
Dessn ā How I ship like a design engineer
Framerā ā How I build my websites
Genway ā How I do research
Jitterā ā How I animate my designs
Play ā How I design mobile apps
Raycast ā ā How I do most things on my computer
Visual Electric ā How I generate imagery
Thanks for reading! I'm working hard to bring you the best design resources on the planet š«¶
If you want to go even deeper you can always:
ā Read all āideasā
ā Watch all āepisodes ā
![]() |
|
P.S. if you were forwarded this email you can āsubscribe here