šŸ¤æ 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ā€

Aashman Goghari

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ā€

Aashman Goghari

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ā€

Aashman Goghari

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ā€"

Aashman Goghari

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.ā€

Aashman Goghari

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 :)

Listen on YouTube, Spotify, Apple, or wherever you get your podcasts šŸ‘‡

How much did you enjoy this issue?

Never hesitate to reply with feedback too :)

Login or Subscribe to participate in polls.

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

Episodes you mightā€™ve missed...

Ideas you mightā€™ve missedā€¦

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:


See you next week āœŒļø 
- Ridd

P.S. if you were forwarded this email you can ā€‹subscribe here