Shreya Murthy

How can we limit the number of steps it takes to get what you want out of the product?

And I think that workflow of just being so obsessive, which is coming from how we want to feel.

So when I say we pour our heart and soul into building Partiful, it's not just a platitude.

What it means in practice is that when we're building something, we think about how we would want to feel, how we would want to be treated.

So, you know, if you see an app with like a bunch of pop-ups and it's like really annoying and you have to tap out of everything, it's like, that sucks.

Like, I hate it when apps do that to me.

So why would I do that to our users?

And instead, I pay attention when I do encounter a product that feels very effortless and delightful and makes me smile.

And I do think about why is that?

Why did that just feel so good and easy?

And so we take our own user experience as people in the world feeling the same problems that I think all of our users feel.

And we try to pour that into every product decision we make.

So that we're always aligned with what we think is in the best interest of our users because it's what we would want for ourselves.

So the big thing is we hire incredibly creative people and we let them loose on the product.

We have some defining principles for how we build, but we're very careful to not have too many rules.

I think one of the most common things I find myself saying, especially to our design team, is go crazy with it.

Just go into a room and just cook and tell me what you come back with in a few days.

And when you hire incredibly creative people and you give them that kind of freedom, you're allowing great things to happen and things that you wouldn't otherwise see.

And where I think it gets constricted is when there are a lot of either explicit or implicit rules that constrain a product.

These can be more technical rules.