This term might be unfamiliar with indonesian, but this is important if you build product and hope people gonna use it.
A product has a long and sometimes tedious processes, from initiations, designing, architecturing, if the product is a software, doing the coding, go back and forth, finalizing story, bargaining, a lot of process, sometimes drama, and we shipped the product. Did user happy? who is the user? did we heard their feedback, or if the product is not exist yet, did we do research first? how cooked the story, requirement.
The one thing that sometimes we missed is, did we as someone who make the product use the product itself? did we as the maker understand what we build? is the product itself speaks our story, and reflected on our product. if the the maker did not use their own product, how can they understand what people need, we won’t have empathy towards our targetted customers, no sense of ownership, feeld nothing, just plain emotion, work just work, no sense of belonging and urgency whether our product being used by the user or just a bunch of features that they did not need at all.
If the product built by team, and in that organization have multiple team like sales, marketing, products etc, make all the team use it, make all the team get the sense of what our users feels, the crash, the frustations. and in my opinion, it is better if our internal team finds out what went wrong, rather than if our customers in the wild, they can complain, and it’s good, but if they did not, and decided to just not use and uninstall our product, that’s the worst thing that could happened to your product.
Listen your customers feedback, listen their whining, their complain, improve, repeat. avoid adding too much feature that sometime the users itself did not need. the feature will overburden the team with no benefit for all.