Hardik Pandya

Some people are just easy to work with.

I once wrote, in a list of sixteen things about design, that the craft requires a tremendous amount of mental fortitude.

My time at Atlassian came to a close recently, and I want to commemorate it with a personal account of one chapter I loved.

Jake Weidman pinged on WhatsApp with this tweet.

AI has compressed the cost of building to the point where a five-person team can attack a market you’ve owned for a decade.

Contents TL;DR LLMs don't think in design systems Making your design system LLM-readable The setup We tried this with Atlassian's design system Why this matters for large prototypes FAQs TL;DR Your design system already exists as code: component libraries,

Designers have a lot of thoughts.

I’ve been tinkering with Claude Code for a few months.

I am generally curious about the concept of legibility of work.

AI writing has tells.

You know how large organizations with very mature systems and talent distribution still end up pulling in the same top 5 or 10 people to work on their most pressing problems?

Designers spend too much time with other designers.

Today is my birthday.

If you’re building enterprise experiences, Slack is the most important third-party surface you’ll integrate with.

In over a decade of designing products, I have learned two important things about ideas: Ideas have no value when they’re locked inside your head.

In our field, speed is often mistaken for haste.

Today’s interfaces are deterministic.

Most design leaders right now are treating AI the way they treated mobile in 2008: delegating it, outsourcing judgment, waiting for patterns to settle.

Most senior designers follow the same playbook that worked for the last two decades: prove you can design, then prove you can manage designers, then climb the ladder.

In most companies, the quality of work comes down to a few people.