What are the Meesho Mantras, why do they exist, and how do they actually shape decisions? The complete, public explanation - one principle at a time.
Ask anyone who has worked at a fast-growing company the same question, and you'll get some version of the same answer: the hardest part was never the roadmap. It was making sure a thousand people, spread across a hundred small decisions a day, were all rowing in the same direction — without being told to, and without a manual for the exact situation in front of them.
That's the problem the Meesho Mantras were built to solve.
If you've searched for “Meesho Mantras,” here's the short answer: they are eleven operating principles that describe how people at Meesho think, decide, and work. Not a values poster. A working answer to a much sharper question: what do you do when nobody's watching, and there's no precedent for this exact situation?
This blog is the complete explanation — why they exist, what each one means, and how they actually show up in the work.
Why Every Company Needs Operating Principles
In a small team, culture doesn't need to be written down. Everyone's in the same room. Context passes by osmosis. “How we do things” is just whatever the most experienced person in the room already believes, absorbed by everyone else through proximity.
That works, right up until it doesn't. A company grows, and new teams form who've never met the people who shaped its earliest instincts. New managers make calls that are perfectly reasonable on their own terms, but inconsistent with how the rest of the company would have made them — not because anyone did anything wrong, but because nobody ever wrote the instinct down. Two teams solve the same kind of problem two different ways, for no better reason than that nobody agreed on a shared approach.
Without something to hold that instinct in place, growth quietly turns into drift.
Operating principles exist to prevent that. Done well, they're not inspiration — they're infrastructure. They let a decision made by someone six months into their role look, in spirit, like a decision the founders would have made themselves.
Why Meesho Created the Mantras
Meesho exists to make commerce accessible to people who've never had a real shot at it before — small entrepreneurs building a business from a single room, delivery partners covering pin codes that don't show up cleanly on a map, shoppers coming online for the very first time. There isn't an existing playbook for exactly that problem, at that scale, in that context. Nobody has solved it before, in quite this shape.
So instead of importing a generic set of “core values” — the kind built from a workshop and a whiteboard, with words like Excellence and Integrity that could describe literally any company — Meesho took a different approach: looking at how its best people were already making decisions, and writing that down.
“A value invented in a workshop has to be taught from nothing. A principle that was already true, just unnamed, is one people recognize the moment they read it.”
That's a meaningful distinction, even if it sounds like a small one. It simply gives an existing instinct a name, and gives everyone else a faster way to learn it.
It's also why Meesho calls them Mantras and not values. A value is something you're meant to hold. A mantra is something you repeat until it stops being a thought and becomes a reflex — closer to a muscle you reach for under pressure than a poster you glance at on your way to a meeting.
How the Mantras Guide Decisions Every Day
The real test of an operating principle isn't whether it sounds good. It's whether it changes what someone actually does, in a moment that has nothing to do with the principle itself.
At Meesho, the Mantras show up in ordinary-seeming decisions — how a deadline gets set, how a disagreement gets resolved, how a problem gets investigated before anyone reaches for a fix. They show up in how people talk to each other in a planning meeting, and in how a new hire decides what to do about a gap in ownership that technically isn't theirs. They also show up in how good work gets recognized, and in dedicated programs built specifically around living out a few of these principles on the ground — subjects substantial enough that they have their own stories to tell elsewhere.
Here, the focus is narrower and more useful: the eleven principles themselves, one at a time.
The Complete Set of Meesho Mantras
What follows is a closer look at each one.
Move With Purpose
Three mantras about how Meesho operates, day to day.
Lightspeed
Why this Mantra exists. Growing companies default to a comfortable pace unless something explicitly pushes against it — and a comfortable pace, applied to a problem this large, quietly loses ground every day. Lightspeed exists to make urgency the shared default, not the personality trait of a few people who happen to move fast naturally.
What this Mantra means. Constantly asking whether something could be done faster — treating the timeline everyone's used to as a starting assumption worth challenging, not a fixed constraint.
How it comes to life. A team planning a launch works backward from the fastest defensible timeline, instead of forward from how long the last similar project happened to take. Someone reviewing a plan asks, genuinely, why a piece of work needs three weeks instead of one — not as criticism, but as the first real question worth asking.
Why it matters. In a market where a seller's next sale or a shopper's next decision happens today, not next quarter, slow decisions compound into missed moments. Speed, aimed at the right things, is what lets a growing company keep pace with a country moving online in real time.
Problem-First Mindset
Why this Mantra exists. It's tempting — especially on fast-moving teams — to reach for a solution immediately, either because it feels productive or because a similar-looking problem was solved before. This Mantra exists to slow that first instinct down just long enough to make sure the effort lands on the right problem.
What this Mantra means. Understanding a problem fully, including why it exists in the first place, before designing anything meant to solve it.
How it comes to life. Before scoping a fix for a recurring support issue, someone reads through a dozen similar cases and realizes the real pattern sits further upstream, in a workflow decision — not in the specific interaction in front of them. A product manager pushes back a sprint's start date by two days specifically to run more user conversations, because the “obvious” solution kept quietly changing shape each time someone asked a new question.
Why it matters. Solutions built on a shallow read of a problem tend to need rebuilding later — a day saved now, a week spent paying it back. Getting the problem right the first time is what compounds forward for everyone downstream of that decision.
Think 10X, Take Risks
Why this Mantra exists. Incremental thinking feels safe, and safe thinking rarely produces a breakthrough. This Mantra exists to give people explicit room — and a real expectation — to reach further than what's comfortable, and to treat calculated risk as a normal part of ambitious work, not a reckless exception to it.
What this Mantra means. Aiming for outsized outcomes through genuine experimentation, rather than settling for steady, incremental improvement — and being willing to take risks that are reasoned, even when they're not guaranteed.
How it comes to life. A team asked to improve a metric by 15% spends a day asking what it would actually take to improve it tenfold instead, and finds the honest answer requires questioning an assumption nobody had touched in years. Someone proposes testing an idea that might visibly fail, because what it would teach the team is worth more than the comfort of not trying.
Why it matters. In a market this large, this early in its growth, the biggest wins rarely come from polishing what already exists. They come from someone willing to ask a much bigger question, and backing it with real effort instead of just enthusiasm.
Win As One
Three mantras about how Meesho works together — because nobody builds something this large alone.
Company > Team > Individual
Why this Mantra exists. As organisations grow, teams naturally start optimising for their own goals, and individuals for their own careers — both completely reasonable instincts that, left unchecked, quietly pull against the whole. This Mantra exists to keep the ordering of priorities explicit, rather than assumed.
What this Mantra means. When priorities genuinely conflict, the company's interest outranks a team's, and a team's outranks any single person's — understood as a matter of sequencing under conflict, not a statement that individual contributions matter less.
How it comes to life. Two teams realise they're about to build a similar internal tool independently, and instead of defending their own version, sit down to work out who should actually own it going forward. Someone disagrees strongly with a decision in a planning meeting, says so plainly, and then commits fully to executing it well once the room has actually decided.
Why it matters. Growth multiplies the number of quiet ways teams can end up working at cross purposes. Keeping this hierarchy explicit is what lets thousands of independent decisions, made by people who've never met each other, still add up to one coherent company.
People-Centric Workplace
Why this Mantra exists. Empathy and respect don't scale automatically as a company grows — without deliberate attention, they tend to erode first, quietly, under pressure and speed. This Mantra exists to make sure that doesn't happen by default.
What this Mantra means. Treating people with genuine respect and consideration, and recognising that building a workplace people actually want to be part of is everyone's responsibility — not a single function's job.
How it comes to life. A manager notices a teammate has gone quiet in meetings recently, and checks in directly instead of waiting for a formal review cycle to surface it. A team makes space, in the middle of a genuinely stressful week, to properly celebrate a colleague's personal milestone anyway — because the moment still matters.
Why it matters. People do their best work where they feel seen as people, not just as output. A workplace that treats this as incidental, rather than intentional, eventually pays for it in the work itself.
Stand Up & Speak Your Mind
Why this Mantra exists. Hierarchy and habit both quietly discourage disagreement — it's simply easier to stay quiet, especially for newer or more junior voices. This Mantra exists to counteract that default, deliberately.
What this Mantra means. Saying what you genuinely think, clearly and directly, regardless of who else is in the room or how long you've been at the company.
How it comes to life. Someone a few months into their role raises a concern about a plan that's already received leadership sign-off, and explains their reasoning plainly, rather than assuming it must have already been considered. A quieter teammate is asked directly for their view in a meeting, because their silence was never actually agreement.
Why it matters. The best insight in a room doesn't reliably come from its most senior or most confident voice. A culture that only hears from the loudest people in it is quietly discarding a lot of good thinking, without ever noticing it's gone.
Obsess & Grow
Three mantras about who Meesho serves, and who its people are becoming.
User First
Why this Mantra exists. It's easy — especially for people who don't personally resemble Meesho's typical user — to unconsciously build for someone more familiar: themselves. This Mantra exists to correct that gravity, on purpose, every time.
What this Mantra means. Treating real users, and what they actually need and experience, as the most reliable source of truth available — more reliable than internal instinct or opinion.
How it comes to life. A designer sits in on customer support calls for an afternoon before finalising a redesign, and changes course based on a specific confusion that three different, unconnected users mentioned independently. Someone designs a flow in the language and context of a first-time online shopper, rather than someone already comfortable navigating e-commerce.
Why it matters. A platform built for hundreds of millions of people, across enormously different contexts, can't be designed from assumption alone. Listening directly to users is what keeps the product honest about who it's actually serving.
Growth Mindset
Why this Mantra exists. It's natural for effort to plateau once a role starts to feel comfortable. This Mantra exists to keep that comfort from quietly becoming a ceiling.
What this Mantra means. Treating improvement — of yourself, your team, and the organisation around you — as a continuous, deliberate effort, not something that simply happens with enough time.
How it comes to life. Someone who's spent years in one function asks to shadow a completely different team for a quarter, purely to build a new muscle they don't currently have. A team runs a genuinely honest retrospective after a launch that technically succeeded, specifically to find what could have gone better anyway.
Why it matters. A company solving problems that haven't been solved before needs people who are still actively getting better at solving them — not people who've quietly settled into what already works well enough.
Hire & Grow Exceptional Talent
Why this Mantra exists. Under hiring pressure, it's tempting to lower the bar just enough to fill a seat. This Mantra exists to resist that temptation, consistently, at every level of the company.
What this Mantra means. Raising the standard with every hire and every promotion, and taking real, active responsibility — individually and organisationally — for helping people become better at what they do.
How it comes to life. An interviewer flags a strong-seeming candidate as not quite right for a specific role, even under real pressure to close the position quickly, because the bar matters more than the deadline. A manager builds an actual development plan with a report — not just a list of tasks — and checks in on it consistently, not just once a year.
Why it matters. The quality of the people around you shapes the quality of your own work. A smaller number of genuinely excellent people, growing continuously, tends to outperform a much larger group hired simply to fill capacity.
Own It For the Long Run
Two mantras about accountability, and about building things that outlast a single sprint.
Extreme Ownership
Why this Mantra exists. Ambiguity is unavoidable at a company solving problems that haven't been solved before — and when nobody clearly owns a gap, it's tempting for everyone to quietly assume someone else will handle it. This Mantra exists to close that gap by default, rather than leaving it to chance.
What this Mantra means. Treating yourself as an owner of outcomes, not just assigned tasks — stepping in on problems that sit outside a formal job description, and delivering despite ambiguity rather than waiting for someone to remove it.
How it comes to life. Someone notices a process quietly breaking down between two teams that neither technically owns, and takes it on anyway rather than escalating it and waiting for an answer. A person spots a real, fixable problem during an ordinary piece of work and resolves it on the spot, instead of filing it away for someone else to prioritise later.
Why it matters. Growing companies accumulate more ambiguity than any org chart can fully account for. Extreme Ownership is what keeps small, unassigned gaps from quietly becoming large, unowned problems.
Think Long Term
Why this Mantra exists. Short-term pressure is constant, and it's easy to solve for this quarter in a way that quietly creates a larger problem for next year. This Mantra exists to keep the far view in frame, even when it would be easier not to.
What this Mantra means. Building things — systems, teams, decisions — that are meant to hold up well beyond the immediate moment, not just survive it.
How it comes to life. Someone chooses a slightly slower, sturdier technical approach over a fast patch, specifically because the patch would need to be redone within the year anyway. A team documents the reasoning behind a decision clearly, not just the decision itself, so whoever inherits it later understands the “why,” not only the “what.”
Why it matters. A company built for the long run has to keep choosing durability over convenience, over and over, even when nobody would notice the shortcut in the moment it's taken. That discipline is what actually compounds into something built to last.
How the Mantras Work Together as One System
Read on their own, a few of these principles look like they could pull against each other. Lightspeed asks for urgency; Think Long Term asks for patience. Extreme Ownership asks individuals to push hard on outcomes; Company > Team > Individual asks them to defer to a broader priority when it conflicts with their own. Think 10X asks people to take real risks; Problem-First Mindset asks them to slow down and understand the problem properly first.
That tension isn't an accident, or a flaw in the design. It's the design.
None of the eleven Mantras is meant to operate alone. Lightspeed without Think Long Term produces speed that breaks things a year later. Extreme Ownership without Company > Team > Individual produces heroics that pull in the wrong direction. Think 10X without Problem-First Mindset produces ambition aimed at the wrong target entirely. Each principle checks another, the way a well-built system holds its own tensions in balance rather than resolving them away.
Taken together, the eleven Mantras aren't a checklist to satisfy one at a time. They're closer to an operating system — a shared, mostly invisible layer that shapes how a decision gets made long before anyone consciously thinks to reference a specific principle by name.
Closing Reflections
None of this holds up if it stays theoretical. A principle that only exists on a page is exactly the kind of thing that erodes first, the moment a company stops paying attention to it.
So the real test isn't whether these eleven ideas can be explained clearly — this blog is proof that they can. It's whether someone new to Meesho, months into their role, with nobody in the room to ask, makes roughly the decision this company would hope for. Whether they ask if something could be done in half the time. Whether they disagree openly, and then commit fully once a call is made. Whether they notice a real problem nobody assigned to them, and simply go and fix it.
That's the actual measure. Everything written above it is just the explanation.
Frequently Asked Questions
What are the Meesho Mantras?
The Meesho Mantras are eleven operating principles that describe how people at Meesho think, decide, and work day to day — covering speed, problem-solving, collaboration, ownership, growth, and long-term thinking.
How many Meesho Mantras are there?
Eleven: Lightspeed, Problem-First Mindset, Think 10X & Take Risks, Company > Team > Individual, People-Centric Workplace, Stand Up & Speak Your Mind, User First, Growth Mindset, Hire & Grow Exceptional Talent, Extreme Ownership, and Think Long Term.
Are the Meesho Mantras the same as “core values”?
Conceptually similar, but Meesho deliberately avoids that term. A value is something you're meant to hold; a mantra is meant to be repeated until it becomes reflexive — a decision-making instinct rather than an aspirational statement.
Why does Meesho call them “Mantras” instead of “values”?
Because the goal isn't for people to admire them — it's for people to reach for them automatically, under pressure, the way a practiced habit works rather than a remembered rule.
