You are on page 1of 5

Interpersonal dynamics assignment

Organization: Zomato

Done by:
P.Arun kumaran
p18011
Introduction

 Zomato is a restaurant searching platform and discovery


service
founded in 2008 by Deepinder Goyal and Pankaj Chaddah.
 It currently operates in 23 countries, including India,
Australia and the
United States.
 It is named by foodiebay in 2008 but in 2010 it was
changed as ZOMATO.
 Service provided by zomato i.e restaurant searching ,
discovery, online
ordering and table reservation etc.
 Employees working in industry 2000+.
 Users of the consumer service industry is above 19 millions
visits monthly
 It is available in the various language i.e English, Turkish,
polish, Indonesian, Spanish, Italian etc.
 Compititors – Food panda and just eat.
 Internet and mobile app are the only channel used for the
whole process for customers to find a suitable restaurant
with better discount
Crtical issues on the company

1. Being in the daily meals market, they have to work with


very low ticketsizes starting at Rs 50/- with no minimum
order requirements or delivery cost. Considering the costs
associated with food production, packaging and delivery,
maintaining a strong unit margin is the biggest Issues of
the company.
2. A very high competition is already present in the
market, who have set the parameters to be a successful
among customers.
3. Confusion may happen between the restaurant and
Zomato which may effect the end customer and the
customer has to suffer.
4. Brand Zomato puts its name on stake if anything gone
wrong because of restaurants or the delivery will surely
effect its image.
5. Keeping track of their competitors .It is always
important to know what other brands in the same space
are doing since there is a strong overlap in target audience
Issues over come by interpersonal dynamics

Bulding an dish database:


Wouldn’t it be great if we could
search for restaurants serving a specific dish? For example,
it would be great to be able to find the best places that
serve a Tenderloin Steak. The only way to make this happen
is if we have structured data for every dish served in a
restaurant. We’ve already made some effort in this
direction the manual way – by typing out a few thousand
menu cards in every city that we are in. However, given the
churn rate of the restaurant industry (about 25%
restaurants shut down every quarter), it is getting difficult
for us to manually keep pace with all the new menu cards
that come our way. We are trying to create intelligent OCR
systems to supplement our existing dish ontology.
Misspellings (in the menus) and from the OCR mechanism
just make it all the more complicated , these case they over
come by giving specified row we can find the dish for easier
way.

Spam control
Two years ago, this wasn’t a problem. Why? Very
simply, a restaurant’s rating Zomato didn’t make or break its
business back then. Nowadays, it does make a difference, to a
certain extent. Since a lot of restaurant owners also realise this,
they try to game the system by planting fake reviews on the
platform. We have, over time, learnt how to identify most of
these cases, but some intelligent spam tactics skip our
automated filters. Our filters currently range from simple data
analysis and pattern matching to user behaviour mapping over a
few months. However, we realise that we constantly have to
keep track of what is making its way onto the platform to help
maintain its neutrality and usefulness to our users. Also, we need
to evolve these systems to outsmart everyone who tries to game
the system (despite following the rules). It’s an ongoing effort,
and I don’t think we will ever be able to say this problem has
been solved for good.

Lower server latency for our geographically widespread


traffic
This isn’t something new, and a few companies have already
done this very efficiently. Most companies our size don’t even
care about this. However, we want to serve all our traffic (in the
Philippines, as well as in London) from servers that sit close to
our users’ physical locations. Lower server latency = users get to
food faster. Replicating all our infrastructure in various locations
on a master-slave basis and then keeping everything in sync is
not easy for us as of now, and this is something we are trying to
address over the very short term itself.

You might also like