Total Pageviews

Showing posts with label #Strategic Blunders By Indian Leadership. Show all posts
Showing posts with label #Strategic Blunders By Indian Leadership. Show all posts

Thursday, 12 February 2026

"Leadership in Project Management: From Plans to Victory" BRIG HEMANT MAHAJAN, YSMON 01 FEB26 PART 4

https://www.youtube.com/watch?v=yQHDQ1xk63E 

·        1. The "Mirror" Question (Accountability)

·        "We’ve all complained about 'Seagull Managers' today. But if we are being brutally honest, in which of your current projects are you accidentally being the Seagull because you’re too busy to stay on the ground with your team?"

·        2. The "Culture vs. Process" Question

·        "If I took away your Jira boards, your MS Project files, and your RAID logs tomorrow, would your team still know how to work together, or is your 'process' the only thing keeping the 'people' from falling apart?"

·        3. The "Shadow" Prevention Question

·        "We blame 'Shadow Stakeholders' for late changes, but here is the tough one: Did they really 'appear out of nowhere,' or did we just fail to build a bridge to them because we knew their requirements would be difficult to handle?"

·        4. The "Success Metric" Question

·        "If a project finishes on time, on budget, and within scope, but the team is burnt out and three key people resign the next day—was that project actually a success? And as leaders, why do we still check the 'Success' box in our reports when that happens?"

·        5. The "Mushroom" Test

·        "How much 'fertilizer' is currently in your status reports? If your project was failing today, do you have the psychological safety in your organization to report a 'Red' status without fear of being penalized?"

Description: We’ve all read the PMBOK® Guide. We know the processes, the inputs, and the outputs. But why is it that even the most "perfect" project plans can be derailed by a single "Seagull Manager" or a "Shadow Stakeholder" appearing at the eleventh hour?

In this high-energy session, pivots from the technical "What" of project management to the human "Who" of project leadership. Using a blend of humor, real-world "horror stories," and practical recovery strategies, we will explore:

  • Deciphering the Ecosystem: How to identify and manage the "Anti-Leadership" patterns that drain team morale.
  • The Transparency Pivot: Moving from "Mushroom Management" to a culture of radical psychological safety.
  • Future-Proofing Influence: Strategies for aligning stakeholders before they become "Ghosts in the Gantt Chart."

Join us for a session that proves that while tools track the progress, it’s the leadership that delivers the purpose. Come prepared to laugh, reflect, and walk away with a "Leadership Toolkit" that doesn't just check boxes, but builds high-performing teams.


"Leadership in Project Management: From Plans to Victory" BRIG HEMANT MAHAJAN, YSMON 01 FEB26 PART 3

https://youtu.be/VCbVOu9NqQc?si=dSefZ-LREh-MC53V 

A Few "Anti-Patterns" for Leadership

If you want to poke fun at bad leadership styles during your 25-minute slot, you can mention these "How-Not-To" strategies:

  • The Seagull Manager: Fly in, make a lot of noise, dump on everyone, and fly out.
  • The Mushroom Method: Keep your team in the dark and occasionally drop some fertilizer on them.
  • The "Shadow" Stakeholder: Someone who never attends the DiSHA conference but suddenly appears on the day of Go-Live to change the color of the entire UI.

1. Grounding the Seagull: "Strategic Air Traffic Control"

The Fix: Don’t just manage the project; manage the Sponsor.

  • The Strategy: Transition from "Reporting" to "Influencing." Establish a Engagement Contract early on. Tell your sponsor: "I need you for these 3 specific milestones, not for the daily font-size decisions."
  • The Takeaway: A leader’s job is to build a "buffer zone" that allows the team to work without the turbulence of unplanned interventions.

2. Lighting the Mushroom: "Radical Transparency"

The Fix: Replace the "Need to Know" basis with the "Need to Succeed" basis.

  • The Strategy: Use Information Radiators. Instead of hiding problems, make the "Obstacles" the most visible part of your dashboard. When the team sees that you don't punish bad news, they stop hiding in the dark.
  • The Takeaway: Trust is built in the light. If you want a high-performing team, give them the context they need to make decisions without you.

3. Aligning the Shadow: "The Pre-Mortem & Proactive Inclusion"

The Fix: Bring the "Shadows" into the light before they become "Ghosts."

  • The Strategy: Conduct a Pre-Mortem. Ask everyone—especially those quiet stakeholders—"It’s six months from now and the project has failed. Why did it happen?" This forces the Shadow Stakeholder to voice their "epiphanies" during the requirements phase, not the Go-Live.
  • The Takeaway: Silence in a meeting is not "Agreement"; it’s "Debt." Collect that debt early, or you’ll pay for it with interest during the release week.

"Leadership in Project Management: From Plans to Victory" BRIG HEMANT MAHAJAN, YSMON 01 FEB26 PART 2

https://youtu.be/SZ9ZRRYx_SM?si=fFo0zILWJUdlf7us 

"How Not to Manage" Quotations

These are perfect for sliding into a presentation to get those knowing nods and chuckles.

  • On Planning: "Planning is the process of making many mistakes on paper so that you can make them later in real life at a much higher cost."
  • On Scope Creep: "If you don't know where you are going, any road will get you there—and you’ll probably be asked to pave it along the way."
  • On Deadlines: "I love deadlines. I love the whooshing noise they make as they go by." (Douglas Adams)
  • The Golden Rule of Estimates: "The first 90% of a project takes 90% of the time. The last 10% takes the other 90% of the time."

The "Anti-Project Manager" Jokes

You can frame these as "Pro-tips for guaranteed project failure."

1. The Power of "Optimism"

A project manager, a developer, and a designer find an old lamp and a genie pops out. He offers them one wish each.

  • The designer says, "I want to be on a beach in Goa with no client feedback forever!" Poof, he’s gone.
  • The developer says, "I want to be in a mountain cabin with 10Gbps internet and no bugs!" Poof, he’s gone.
  • The Project Manager looks at the empty chairs and says, "I want those two back in their seats by 2:00 PM for the status meeting."

2. Strategic Communication

A Project Manager is walking down the street when a frog calls out, "If you kiss me, I’ll turn into a world-class Scrum Master!" The PM picks up the frog and puts it in his pocket. The frog screams, "Hey! Didn't you hear me? I said I'll turn into a Scrum Master!" The PM looks at the frog and says, "Look, I’m a Project Manager. I don't have time for a girlfriend, but a talking frog? That’s a deliverable I can actually sell."

3. The "Classic" Definition

Q: How many Project Managers does it take to change a lightbulb? A: None. They just form a committee to decide that the darkness is actually a "feature" of the room and move the deadline for sunrise.


Thursday, 23 May 2024

Project Udbhav: Indian Army to learn war tactics from vedas, puranas, and Mahabharata

The Indian Army, under its initiative Project Udbhav, is delving into the epic battles of the Mahabharata and the strategic brilliance of past Indian dynasties, shaping India's rich military heritage, Army Chief Gen Manoj Pande revealed on Tuesday.

Launched last year, this project aims to enrich the nation's outlook in the defence domain by integrating India's ancient strategic acumen into contemporary military practices, making the force "future-ready". Ancient Wisdom for Modern Military Speaking at a conference titled 'Historical Patterns in Indian Strategic Culture', Gen Pande highlighted that Project Udbhav has explored ancient texts such as Vedas, Puranas, Upanishads, and Arthashastra. These texts reveal substantial intellectual convergences between eminent Indian and Western scholars, showing resonance between their thoughts, philosophies, and perspectives.

The project aims to promote indigenous discourse in the Army by integrating India's ancient strategic acumen into contemporary military domain with a focus on making the force future-ready," Gen Pande said. Rich Heritage and Intellectual Convergences He noted that the project has not only explored epic battles and strategic brilliance but also catalyzed exploration into new areas, unveiling India's tribal traditions, the Maratha naval legacy, and the individual heroic exploits of military figures, particularly women.

Fostering Civil-Military Collaboration Gen Pande emphasized that such collective efforts broaden the scope of study of ancient India's defence and governance, enriching the nation's strategic outlook. The project has fostered civil-military collaboration among academia, scholars, practitioners, and military experts, strengthening the whole-of-nation approach.

Continued Endeavour "As we explore more into our military heritage, we understand that undertaking such projects remains a continuous endeavour," Gen Pande said. He expressed confidence that the project's findings in the form of 'Udbhav Compendium' shall benefit the Indian Armed Forces to remain progressive and future-ready, by drawing insights from the nation's historical military wisdom. Celebration of History and Heritage Gen Pande also hailed the celebration of the history and heritage of the Indian armed forces, noting that it is being celebrated as an integral part of the national culture and identity. Encouraging 'Indianisation' The move to delve into India's ancient texts and traditions comes against the backdrop of efforts by the government to encourage "Indianisation" in various areas, including education, health, science, and military practices. Project Udbhav reflects India's commitment to integrating its rich historical and cultural heritage into modern practices, ensuring that the nation's strategic outlook remains rooted in its ancient wisdom. This initiative is not just about learning from the past but also about shaping a future-ready military force that draws strength from India's millenniaold military wisdom. Exhibition on Military Evolution Alongside this initiative, the Indian Army also put up an exhibition titled 'Evolution of Indian Military Systems, Warfighting, and Strategic Thought - from Antiquity to Independence'. This exhibition showcases the evolution of India's military systems and strategy under various themes, aiming to create a deeper understanding of India's past and its position in the global arena. Indigenisation and Erasure of Colonial Traditions The Indian armed forces are also focusing on the indigenisation of military customs, erasing colonial traditions. This includes renaming British-era cantonments as military stations and adopting new symbols that draw inspiration from India's rich historical and cultural heritage. Continued Exploration With initiatives like Project Udbhav, India is not just looking back at its past but also looking forward, ensuring that its military remains adaptive, innovative, and deeply rooted in its ancient wisdom. The insights gained from these projects are expected to shape India's military practices and strategic outlook for years to come.

Sunday, 21 April 2024

1965 - An Inside Story -from a book by RD Pradhan, Former Home Secretary ,*Why India Quit When it Was Winning the 1965 War?*PART 2

 

*Road to Tashkent*



With the US disinterested in the conflict and the UK showing its true anti-India and pro-Pakistan colours, it was left to Russia to play honest broker.



It was after some initial hesitation that both India and Pakistan accepted the Russian offer. Ayub Khan later said that Pakistan went to Tashkent as it did not want to risk a veto by Moscow.



There was another reason for Pakistan’s eagerness for talks. According to Pradhan, “The continued presence of Indian troops on the east side of the Ichhogil canal, facing Lahore city, was hurting Pakistan’s pride.” The heat was clearly on Islamabad.



Before leaving for Tashkent, Shastri – who was hero-worshiped by Indian soldiers – had promised his victorious troops that he would not return the land captured from the enemy after so many sacrifices. But after six days of talks, Shastri proved once again that Indians are bad negotiators.He gave away everything.



Was Shastri feeling the pressure from the international community? Most likely not, but perhaps he felt – like his successor Indira Gandhi after the 1971 war – that showing leniency towards Pakistan would buy its goodwill.



*Mystery of Shastri’s Death*



If you were Shastri, you would dread having to face the Indian soldier back home. Hundreds of them had died while capturing the strategic Haji Pir pass, which if India had kept, would have forever nullified Pakistan’s advantage in Kashmir.



On the night of January 10, 1966, the diminutive Prime Minister but a giant among men died of a heart attack. It was his fourth cardiac seizure and was likely triggered by his anxiety at having to face an irate public and having to look into the eyes of his jawans – soldiers – whose hopes he had dashed.



There have been all sorts of conspiracy theories but the reality is that none of the major countries benefitted from his death. Russia had scored a spectacular diplomatic coup, America fully supported the Tashkent Agreement, and Pakistan was happy to get its land back.



That the Indian Prime Minister died of a heart attack comes from a most unlikely source. Shortly after Mikhail Gorbachev’s liberalisation policies in 1991, Soviet Land magazine in India published an account by an ex-KGB officer.



According to the former intelligence agent, the KGB was spying on both the Indian and Pakistani delegations in order to find out how much each country was willing to yield during the negotiations. When Shastri started getting a seizure, the KGB was listening but decided not to alert his aides because that would give away their game and lead to a diplomatic showdown with India.



*Prelude to Tashkent*



Having dissected what transpired at the negotiating table, we need to discuss the prelude to Tashkent.



Although Pakistan was on the verge of being trounced – unlike in 1971 and 1999 when it really got hammered – India generously agreed to a ceasefire after repeated pleas from the major powers.



Why did India stop fighting when it had Pakistan reeling? Why did Chavan and Shastri, who swatted away western pressure and gave a free hand to the Indian military, cave in?



The problem was army chief Jayanto Nath Chaudhuri. The Kolkata-born general came from an affluent background and had become army chief purely on the back of family connections and pure luck. He was elevated following the resignation of another Sandhurst-educated general, Pran Nath Thapar, the army chief of the 1962 War.

Chaudhuri’s mentors were the Sandhurst educated British generals – who had utterly failed before the Germans and Japanese during World War II – and predictably he also lacked war fighting qualities. “He was so good on paper that Chavan often wondered how good he would be in warfare,” writes Pradhan.



Chavan mentions in his war diary that Chaudhuri would frequently lapse into depression. Each time the Indian army suffered a setback, the general would walk into the Defence Minister’s room, and Chavan had to give him a pep talk. Chaudhuri so completely lacked courage that Chavan often forced him to visit the front and personally take stock.



Pradhan writes, “On September 20 when the Prime Minister asked Chaudhuri whether India could expect to gain if the war continued for a few days more, he informed the PM that the army was coming to an end of its ammunition holdings and could not sustain fighting for much longer. Chaudhuri advised acceptance of the ceasefire proposal. It was later discovered in overall terms only 14-20 per cent of the Indian Army’s ammunition stock had been used up. At the moment of our greatest advantage the army chief’s non-comprehension of the intricacies of the long-range logistics deprived India of a decisive victory.”



In contrast, Pakistan had expended 80 per cent of its ammo. It had also lost 250 of its latest US-supplied tanks.



Chaudhuri was also criticised for his lack of daring. When the Pakistani cities of Sialkot and Lahore could have been easily taken after the dash and bravery shown by Indian troops, Chaudhuri told Shastri: “We must move with the caution and wisdom of an elephant. We will take them in God’s good time.”



In fact, when the Pakistan Army attacked in the Khem Kharan sector in Punjab, Chaudhuri ordered the Army Commander Harbaksh Singh to withdraw to a safer position.The commander refused, and what followed was the Battle of Assal Uttar – the greatest tank battle since Kursk in 1943. The Indian counter attack on the night of September 10 was so ferocious that by the morning they had knocked out 70 Pakistani tanks.

But what the Battle of Assal Uttar will be memorable for are the 25 enemy tanks found abandoned with their engines running and wireless sets on. It was the perfect metaphor for the plight of the Pakistan Army.



Had India kept its head, today we’d have a lot more to celebrate.

1965 - An Inside Story -from a book by RD Pradhan, Former Home Secretary ,*Why India Quit When it Was Winning the 1965 War?*PART 1

In May 1964, Indian Defence Minister Yashwantrao Chavan made a visit to the Pentagon, the HQ of the American defence department. Chavan, who was trying to rapidly modernise the Indian military, requested the Americans to sell India the F-104 Starfighter – the most advanced jet fighter of that era.

Although the US had supplied the F-104 and the F-86 Sabres in large numbers – virtually free of cost – to Pakistan, India’s request was rebuffed in an extremely crude manner.

In his brilliant little book, ‘1965 War: The Inside Story’, former Maharashtra chief secretary RD Pradhan narrates what US Defence Secretary Robert McNamara told Chavan: “Mr. Minister, your Air Force is like a museum. I wonder whether you are aware of the variety of aircraft in your Air Force. You are still operating with Hunters, Spitfires, Vampires, Liberators, Harvards – exotic names of World War II vintage. All these aircraft are only worthy of finding a place in a museum.”



McNamara suggested that until India disbanded that fleet, it was no use acquiring any sophisticated aircraft.



What the American secretary said was offensive…and true. Although the US did not offer any help, what India did with its antiquated planes and vintage tanks remains the stuff of legend. Pradhan says, “With that background, it was an exhilarating moment when some of those junk planes, such as the Mysteres, Vampires and Hunters performed brilliantly against Pakistan’s sophisticated F-86s. In fact, the indigenously built Gnat, a small beaver-like fighter, brought down several F-86s.”



The 1965 War remains memorable for two things. One was a monumental miscalculation by Pakistan. President Ayub Khan, egged on by his scheming and feckless Foreign Minister Zulfikar Ali Bhutto, sent a top-secret order to his army chief General Mohammed Musa: “As a general rule, Hindu morale would not stand for more than a couple of hard blows delivered at the right time and the right place. Such opportunities should therefore be sought and exploited.”



Secondly, India’s leadership – as it has done consistently over the past 2500 years – frittered away on the negotiating table what the soldiers won on the battlefield. Pradhan writes: “In a way, India’s leadership, out of its sense of restraint, fair play and endeavour to seek enduring peace and goodwill with the neighbour, seems to have missed opportunities to solve the problem.”



At the end of a bruising 22-day war, India held 1920 square kilometres of Pakistani territory while Pakistan only held 550 square kilometres of Indian land. The Haji Pir pass was also captured by Indian soldiers after an epic battle. And yet India surrendered everything at the Tashkent Declaration in January 1966.



*Western ways*



The US, which was embroiled in a bloody war of its own in Vietnam, acted mostly through the United Nations. However, the defining western aim was to see their satellite Pakistan get through the war without getting battered. This view is amply summed by Chavan, who wrote about British Prime Minister Harold Wilson’s ceasefire proposal at a time when India had the upper hand: “I insisted on military advantages being maintained. The UK proposals look like a trap.”



As three divisions of the Indian Army were slicing across Pakistani defences and thundering across the Ichhogil canal to Lahore, Wilson sent a message to Prime Minister Lal Bahadur Shastri and Ayub Khan: “Both governments bear responsibility for the steady escalation which has subsequently occurred, and today’s attack in the Lahore area presents us with a completely new situation.”



Wilson’s message implied that India was as much to blame for the war on the subcontinent as Pakistan. “Shastri more or less brushed aside that message,” says Pradhan. “Bias on the part of Britain would rule out the UK from playing any effective role in events after the ceasefire.”



*Russian Role*



Russia, which was following the events with deep interest, maintained its traditional stand that Kashmir was part of India. Pradhan writes Moscow accepted the disturbances in Kashmir had been created by infiltrators from Pakistan.



Russia also backed India at the United Nations. K. Vijaykrishnan writes in ‘The Soviet Union and the India-Pakistan War, 1965’, “Support was available for India on some important technical points and objections India had raised,” he says. Russia supported the Indian position that the Security Council should only deal with "questions directly connected with the settlement of the armed conflict” and not drag in the Kashmir issue.



Fending off China was a trickier affair. Russia did not want an open confrontation with Beijing, but Moscow decided it would not remain a passive spectator if India had to battle on two fronts. According to Vijaykrishnan, during the thick of the conflict, India received a reassuring message from Russian Premier Alexei Kosygin indicating support in the event of a Chinese attack.



Sisir Gupta writes in ‘India and the International System’ that India was aware Russia would never like to see India humbled or weakened. “A strong and friendly India occupying a pre-eminent position in South Asia was very much a Soviet foreign policy interest. Notwithstanding the fluctuations in the Soviet attitude and the zig-zag nature of the course it pursued, there was throughout a broad assumption underlying Soviet policies towards South Asia, that India was the key factor in the region and that any policy which created distrust and dissension between the two countries was to be avoided.”



China got the message and backed off despite Pakistani appeals for help. Chinese strongman Mao Tse-Tung was reported to have told Ayub Khan that "if there is a nuclear war, it is Peking and not Rawalpindi that will be the target", writes G.W. Chaudhury in ‘India, Pakistan, Bangladesh and the Major Powers: Politics of a Divided Subcontinent’.