Trying vs Delivering: Execution and Accountability for India Teams 2026
Trying hard is not delivering results. High-performance teams in India measure outcomes, not intentions. Here's Avinash Chate's framework for building real execution accountability.
Here's the most polite lie in Indian corporate life: 'I tried my best.' Trying is not delivering. Execution means outcomes, not effort—and the gap between them is where most organizational productivity is quietly lost. McKinsey India found that Indian managers spend 21 hours per week in meetings, 35% more than their US counterparts, and yet delivery gaps remain one of the top concerns for senior Indian executives. The difference between trying and delivering isn't effort. It's accountability, clarity, and the will to own the outcome.
TL;DR- 'Trying' hides incomplete effort—it separates the owner from the outcome and normalizes missed results
- Execution means knowing the exact outcome expected and owning it until it's delivered, not until it gets hard
- Leaders enable trying culture by accepting effort-based updates instead of outcome-based commitments
- Accountability is prospective—who owns what by when—not retrospective blame for what went wrong
- The shift from effort-reporting to result-reporting is a culture change that starts in the next meeting
Why 'I Tried' Is the Most Dangerous Phrase in Indian Workplaces
'I tried my best' is the most polite way to communicate a missed result, and every organization I've worked with has normalized it. At first glance it sounds like accountability—after all, the person is acknowledging the gap. But what it actually does is separate the outcome from the owner. 'I tried' says: the result isn't here, and the reason is beyond my control. High-performance teams I've worked with at Bajaj Auto, Tata Tech, and BRO operate differently. They don't discuss effort in progress reviews. They discuss outcomes: delivered, not delivered, and what changes next.
Effort Without Outcomes: The Accountability Gap Costing Indian Teams Results
Here's the thing about effort without outcomes: it's invisible to the customer, invisible to the business, and ultimately invisible to the market. Indian managers spend 21 hours per week in meetings, McKinsey data shows—yet delivery rates on cross-functional projects consistently disappoint. The gap isn't effort; it's execution. People are trying hard in the wrong direction, in meetings without decisions, on tasks without owners, under deadlines without consequences. The accountability gap isn't about work ethic—it's about system design. And system design is a leadership responsibility.
| Behavior | Trying Culture | Delivery Culture |
|---|---|---|
| Success metric | Hours worked, effort visible | Outcomes delivered, results visible |
| Deadline treatment | Flexible, often renegotiated | Fixed unless formally changed |
| Progress updates | "I'm working on it" | "Done / Here's the blocker / Here's the revised date" |
| Credit given for | Hard work and dedication shown | Completed results delivered |
| Manager's response to misses | "Keep trying, you're doing well" | "What shifted and what's the new commitment?" |
| Team energy | Busy, often stressed | Focused, clear, accountable |
Execution Over Effort: What Real Delivery Looks Like in Practice
Execution means knowing the exact outcome expected before you start, and owning it until it's done—not until it gets hard. Real delivery means the thing ships, the report lands, the call happens, the decision gets made. It doesn't mean 'I got most of the way there.' In my corporate training sessions for HR leaders across Maharashtra, I use a simple test: can every person on your team answer, right now, what specific result they are personally accountable for delivering this week? If the answers are vague or activity-based, you have a trying culture, not a delivery culture.
How Leaders Enable 'Trying' Culture Without Realizing It
Leaders enable trying culture more often than they realize. When a manager accepts 'I worked really hard on this' as a substitute for a missed result, they set the price of accountability at zero. When deadlines drift without consequence, the team learns that timelines are suggestions. When credit is given for effort rather than outcomes, effort becomes the thing being optimized—not results. I've watched senior leaders at otherwise strong organizations inadvertently create this pattern by being empathetic in the wrong moments. Empathy belongs after the result is delivered; during execution, clarity and accountability come first.
The Difference Between Accountability and Blame in Indian Organizations
Accountability and blame are not the same thing, and confusing them is what makes Indian managers shy away from execution conversations. Blame looks backward and assigns fault. Accountability looks forward and assigns ownership. When I ask 'who is responsible for this deliverable and by when?' I'm not blaming anyone—I'm creating the clarity that makes execution possible. Teams I've worked with at Infosys and L&T that learned to separate accountability from blame became dramatically more productive, because people finally knew what they owned—and what they could ask for help with.
Building an Execution-First Culture: From Intentions to Results
Building an execution-first culture requires four changes: replace effort-based check-ins with outcome-based check-ins; install clear owners on every deliverable, not teams or departments, but a person; create visible deadline tracking so slippage is seen early; and treat delivery—not trying—as the unit of recognition. This doesn't require new software. It requires a different conversation. The first time you say 'I appreciate the effort, and I need the result—what do we need to shift to make that happen?' everything changes. People begin solving for the outcome rather than justifying the effort.
Measuring Delivery, Not Effort: The Metric Shift That Changes Everything
The metric shift from effort to delivery changes what gets measured, celebrated, and replicated inside an organization. When you measure hours worked, you get hours. When you measure outcomes delivered, you get outcomes. At KPIT and Siemens India, the teams that made this shift stopped having status update meetings and started having result review meetings. The tone changed. The ownership changed. The pace changed. And here's what I've seen every single time: people who previously seemed to try without delivering become genuine high performers once the expectations are clear and the accountability is real.
Book Avinash Chate for Your Next Event
TEDx speaker. 11+ yrs training Army, BRO, RBI, BARC, JSW. Available for keynotes, leadership training, team building & manager development at your office or event venue.
✅ Thanks! Avinash team will reach out within 24 hours.'}).catch(function(e){f.outerHTML='Something went wrong. WhatsApp +91 8793630001
'});return false;">Select ServiceKeynote / Motivational SpeakingLeadership Development TrainingTeam Building WorkshopManager DevelopmentEmployee TrainingOutbound TrainingBook Avinash Now →Or WhatsApp directly: +91 87936 30001
Related Articles by Avinash Chate
- Ferrari Insulted Him So He Built Lamborghini and Changed History
- Building High Performance Teams in Corporate Pune: Strategies for Success
- The Universal Mechanic Effect: How Konecranes Earns 50% Revenue Servicing Competitor Cranes
Avinash Chate TEDx Speaker · Founder, The Future Corporate · 11+ yrs experience Avinash has trained Indian Army, BRO, RBI, BARC, JSW Steel and 1000+ corporate leaders across India. His work focuses on leadership development, communication skills, and behavioural training rooted in Indian values and modern business needs. |
Frequently Asked Questions
Why does 'trying' often fail to produce real results at work?
Trying separates effort from outcomes—and organizations that accept trying as success accidentally optimize for visible effort rather than real results. The moment 'I tried my best' is accepted as an equivalent to 'it's done,' the accountability link breaks. People learn that demonstrating effort is enough. This pattern compounds: teams get busier and less productive simultaneously. The fix isn't demanding more effort; it's demanding clarity about what 'done' looks like before the work starts, and maintaining ownership of the outcome until it's actually achieved.
What's the difference between accountability and blame in a workplace?
Blame is retrospective and assigns fault for what went wrong. Accountability is prospective and assigns ownership for what must be delivered. When I ask 'who owns this, what exactly is the result, and by what date?' I'm building accountability. When I say 'this failed because of you,' I'm assigning blame. Indian corporate culture often conflates the two, which makes leaders avoid accountability conversations because they feel punitive. They're not punitive; they're clarifying. Teams that separate accountability from blame consistently outperform teams where both concepts are muddled together.
How can managers build a culture of execution in Indian teams?
Start by changing what you accept in status meetings. Stop accepting effort-based updates and start requiring outcome-based updates: delivered, not delivered, revised commitment. Second, install a named owner on every deliverable—not a team or department, but a specific person. Third, make deadline slippage visible early so it can be solved, not hidden. Fourth, give recognition for delivered results, not for demonstrated effort. These four shifts, done consistently, change the culture within two or three project cycles. The hardest part is maintaining consistency, especially when outcomes are missed by someone you respect.
What does Avinash Chate mean by delivering vs trying?
The distinction is simple but important: trying means you engaged with the task; delivering means the task produced its intended result. The gap between them is where most organizational productivity is lost. When I work with corporate teams—whether at Bajaj Auto, Mahindra, or the Indian Army—I ask: what specific, measurable result were you committed to, and did it happen? If the answer is 'I worked on it but it's not quite done,' we have a delivery gap. Acknowledging that gap clearly, without blame, is the first step to building a culture where results—not intentions—define success.
Avinash Chate services
Corporate Trainer in Maharashtra · Top Corporate Trainers in Maharashtra · Leadership Trainer in Maharashtra · Top Leadership Trainers in Maharashtra · Team Building Trainer in Maharashtra · Top Team Building Trainers in Maharashtra · Motivational Speaker in Maharashtra · Top Motivational Speakers in Maharashtra · All service locations
← Back to all articles · Book Avinash Chate
By Avinash Chate — Maharashtra’s #1 Corporate Trainer & Motivational Speaker. .