ownpath

ownpath is a design and product company that partners with enterprises and startups to design and build great products.

We’re hiring for ownpath studios!

[ownpath @ownpath_hq]

@shashankasrao @shrys_s @NCResq @irishdrug1511 @PriyRanjan96 @shbhmndshwr7 @sj_jindal Awesome, thank you! Our team will reach out to you soon

[ownpath @ownpath_hq]

our designers when devs say they can manage design with claude.

[ownpath @ownpath_hq]

Last Friday, Anish, our Design Lead, traded pixels for paper and took us through an origami session. 🐘📄

Safe to say, we left with more patience, a little character development (and a cute little elephant, of course). 😅

[ownpath @ownpath_hq]

Read the full article on the ownpath Substack: https://t.co/bgafWSKA7c

[ownpath @ownpath_hq]

Product teams spend a lot of time studying user behaviour.

But over time, those snapshots start to show their limitations, because behaviour shifts as products evolve.

Shreya Agarwal (Senior Design Manager, Grab) unpacked this idea in her session from the ownpath archives.

[ownpath @ownpath_hq]

Shreya’s bigger point: behaviour and interfaces don’t move one way. They co-evolve.

Design shapes habits. Habits reshape design.

The real tension isn’t whether products shape behaviour, but whether we stay conscious of what we’re shaping as product builders.

[ownpath @ownpath_hq]

Collaboration is moving from translation to shared understanding.

Designers are closer to execution intent when they set out to flesh out screens, and that changes everything downstream.

Read the full story on the ownpath Substack.

https://t.co/oz1kjbVO50

[ownpath @ownpath_hq]

Design–dev collaboration has always been framed as a handoff problem.

Better specs. Cleaner files. More annotations.

But the real issue lay beyond those things.

[ownpath @ownpath_hq]

Lately that distance has closed in meaningful ways.

Feedback loops are tighter. Context carries further.

This shift didn’t come from a new process or framework, but from tools that sit between design and code reducing friction and making intent easier to interpret.

[ownpath @ownpath_hq]

Read the full article on the ownpath Substack: https://t.co/cjjdNSVat2

[ownpath @ownpath_hq]

When designers talk about inclusion, the conversation often starts at interfaces, components, or accessibility checklists.

But as @somyeah reminded us in her interview from the ownpath archives, exclusion usually begins much earlier. Long before a single screen is designed.

[ownpath @ownpath_hq]

How do designers influence product teams to care about representing the right voices?

Somya outlines a few paths:

- Advocating in your individual capacity
- Questioning organizational values
- Using data and business insights to make the case for inclusion

[ownpath @ownpath_hq]

As responsibility grows, something else can quietly erode: joy.

Many leaders respond by performing authority—changing their personality to match the role.

Abhinit’s advice is simple: Don’t become someone else.

Read the full post on the ownpath Substack: https://t.co/pgrj0m9w3j

[ownpath @ownpath_hq]

Design leadership isn’t just about better products.

It’s about not losing yourself as responsibility grows.

In a session from the @ownpath_xyz archives, Abhinit Tiwari (ex-SVP of Design, Gojek) shared an inward look at what design leadership demands. (1/n)

[ownpath @ownpath_hq]

So what actually holds a team together over time?

Not process. Not rituals.

Conviction.

“If you don’t fully believe in what the company stands for,” Abhinit says, “your team will feel it before you say it.”

Belief becomes the anchor. ↓