Tag: Leadership

  • Banas Canal

    Banas Canal

    “When will the water reach our fields?”

    It was a question that had been asked in the village for as long as anyone could remember. It came up during conversations at the tea stall, in the fields, at Panchayat meetings and sometimes in the middle of an ordinary afternoon when someone looked towards the dry stretch of land beyond the village.

    The Banas River flowed about sixty kilometres from the village. Every monsoon, the river carried more water than the village could use, while the farmers here waited for rain and watched their fields depend on the mercy of the clouds.

    People had grown accustomed to this contradiction. They had learned to plan their crops around uncertain rainfall, borrow water from neighbours and make do with whatever the season offered.

    Then Devendra Pratap returned.

    He had spent fifteen years abroad. He had seen different cities, worked with different people and experienced a life that most villagers had only heard about. He spoke confidently, knew how to hold a gathering and had a way of making complicated things sound possible.

    He was also from the village. His family had lived there for generations, and people remembered him as one of their own.

    At his first public gathering, he spoke about the Banas. “Our ancestors have heard the story of Bhagirath. Through his determination, he brought Ganga ji from Swarga to the earth. If Bhagirath could bring Ganga ji down, why can’t we bring the waters of Banas to our fields? The distance is only sixty kilometres.”

    The comparison stayed with people. It was no longer just a proposal for an irrigation canal. It had become a collective dream.

    Devendra spoke of a project worth nearly a hundred crore rupees. He said it would take five years to complete, and that the village could expect water by the fourth year. People listened. Some were sceptical, but most wanted to believe him.

    When the Panchayat elections came, Devendra was elected Sarpanch.

    His first tenure was full of activity. There were visits to district offices, meetings with engineers, trips to the state capital and delegations of villagers accompanying him to meet officials. Politicians and government representatives visited the village. Surveys were conducted. Maps were discussed. Photographs were taken.

    Eventually, a foundation stone was laid. There were speeches, sweets and promises. The village had never seen such attention around a single project. For a while, it felt as though something significant had finally begun.

    The canal work started, but progress was slow. There were technical clearances, land issues, contractor delays and administrative approvals. Each obstacle had an explanation. Devendra returned from the city with updates and fresh assurances.

    He spoke of how difficult it was to get things done in government offices and how much effort it took to keep a project of this scale moving.

    The villagers waited. The first five years passed. The water did not arrive.

    Devendra was elected for a second tenure.

    This time, he had another important promise for the village. It was about the school. He often spoke about education. He said that a village could not progress if its children had to grow up with limited opportunities. The old school building was in poor condition, and the children needed better classrooms. A new school building would be constructed, he announced. It would give the next generation a better start.

    The announcement was welcomed. Parents were hopeful. Even those who had doubts about the canal felt that a school was something everyone could understand and support.

    After some time, construction began. Eventually, two rooms came up. They were built at a cost that people later heard was considerably higher than they had expected. There was no electricity connection, and the building looked rather modest compared with what had been promised.

    Still, these two rooms were the village’s new school building. Then came the question of teachers.

    Two young women had started teaching the children. They were very young, and people initially assumed they were newly appointed teachers. It was only later that some parents discovered that they were not appointed teachers at all. The actual teacher, it turned out, had asked them to take the classes on her behalf.

    Someone raised the matter with Devendra. He listened and explained that the arrangement had been made with his permission. When someone asked how the actual teacher could be absent, he replied quite casually:

    “Arre, ladki kahaan se shehar se roz aavegi? Itni door se aana aasaan hai kya? Apne bachhon ko ek ke badle do teacher mil gaye.”

    The response left little room for further discussion. The parents had asked for a proper school and qualified teachers. They had received two rooms without electricity and two young women who were not the appointed teachers. Yet the arrangement was presented as an additional benefit.

    There was no dramatic argument. Some parents continued sending their children because there was nowhere else nearby. Others began making their own arrangements whenever they could.

    Devendra moved on to the next development proposal. The school had been built, the teachers were taking classes, and as far as the official discussion was concerned, the matter had been addressed.

    There were other changes too. Devendra had never been unfamiliar with money or a comfortable life. His years abroad had given him a taste for convenience, and he saw no reason to give that up while serving the village. His trips to the city, which had once been made by bus, were now usually in private cabs. It saved time, he explained, especially when several meetings had to be attended.

    The Panchayat Bhawan was also upgraded. It had an air-conditioned meeting room and a generator to ensure that official meetings could continue during power cuts. Devendra felt that visiting officers and guests should be received in a proper environment. The village needed to project a certain image if it wanted to attract attention and investment.

    The annual village development day grew larger each year. There were decorated stages, sound systems, invited ministers and officials, elaborate meals and long speeches. Photographs were taken, reports were prepared and the event was described as a celebration of the village’s progress.

    People enjoyed the gathering. Children looked forward to the food and festivities. Some villagers were genuinely proud to see their Panchayat Bhawan and village events receiving attention.

    But outside the building, summer afternoons remained difficult. Electricity shortages continued. Children sat in hot classrooms, the health centre struggled through power cuts, and farmers waited for electricity to run their pumps.

    Nobody raised these differences in the middle of the celebrations. There were always explanations for why certain arrangements were necessary. And the canal was still coming.

    At the tea stall, however, conversations occasionally turned to these things. Someone would mention the generator at the Panchayat Bhawan. Someone else would talk about the annual day expenses. Another would ask when the road to his field would be repaired.

    The conversations rarely went very far. The Panchayat had gradually become a close circle of people around Devendra. Meetings continued, resolutions were passed and discussions took place, but many decisions seemed to have been settled before everyone arrived. Other elected members would sometimes hear that something had already been discussed with Pradhan ji.

    Devendra listened patiently when people offered suggestions. He rarely interrupted. He would nod, ask a question or two and explain why a different approach might work better. The conversation would eventually return to the plan he had already chosen.

    He believed that leadership required taking decisions. Too much discussion, he often said, only delayed development. When something went well, he spoke of how the Panchayat had managed to get it done. When something failed, there was usually a contractor, an officer or a committee that had not performed as expected.

    He remained courteous. He remembered people’s families, asked about their crops and greeted everyone warmly. There was no dramatic change in his manner. Yet, slowly, fewer people found a reason to bring their own ideas to him.

    Among those who had attended the very first meeting was a farmer named Raghu. He had shown the officials his fields and explained how much difference irrigation water would make to his family. For years, he had planned his crops around the promised canal. He had waited through monsoons, arranged pumps when possible and made whatever adjustments he could.

    Raghu eventually passed away, leaving his land to his two sons. Neither son had travelled much beyond the nearby town. The elder had studied up to the tenth grade. They were ordinary farmers, occupied with their land, their families and the familiar uncertainty of each growing season.

    One evening, the elder son was watching videos on YouTube when he came across farmers from another state discussing a farm pond initiative. They were collecting rainwater, storing it on their own land and using it to support cultivation. The idea was simple enough to understand, though putting it into practice would require some work.

    He showed the videos to his younger brother. They discussed it for a few days. Then they decided to try.

    They identified a low-lying patch of their land where rainwater naturally collected and began digging a pond. They shaped small channels to guide the runoff towards it. There was no government grant, no formal announcement and no foundation stone. They used their own resources and whatever help they could arrange.

    Some neighbours laughed. A few asked whether they were planning to become fish sellers. Others wondered how a small pond could possibly make a difference when the village had been waiting for a hundred-crore canal.

    Devendra heard about it too. At one gathering, he made a passing remark that such individual efforts were useful, but could never replace a proper irrigation project. The village needed large infrastructure, he said, not small experiments.

    The brothers did not argue. They knew a canal would be useful. They also knew that their fields could not wait indefinitely. The first monsoon did not fill the pond as they had hoped. Some water escaped, and the channels did not work as expected. They watched where the rain flowed, made adjustments and tried again.

    Over the next seasons, they improved the pond and expanded their efforts. They learned about slopes, soil and water storage from videos, other farmers and their own mistakes. They experimented with fish farming as well. It took time, and not everything worked the first time.

    But gradually, the stored water began to make a difference to their fields. They could plan some irrigation more confidently. The fish provided an additional source of income. Where the local soil and conditions allowed, the additional water storage also helped improve water availability around their land.

    A few neighbouring farmers began visiting them. They asked questions, looked at the channels and discussed how a similar arrangement might work on their own fields. The brothers showed them what they had learned.

    There was no formal village meeting. Nobody invited a minister. There were no speeches or photographs. One farmer started digging a pond, another modified an existing water collection area, and someone else began exploring what could be done with the runoff from his land.

    The idea spread slowly, through conversations and visits to the fields. By then, Devendra was serving his third tenure.

    The canal was still not delivering water to the village. Some stretches had been constructed, but the last-mile connections and distribution arrangements remained unfinished. Every now and then, there would be another announcement, another visit by officials or another assurance that the work was nearing completion.

    Devendra, however, had not lost his enthusiasm. He continued travelling to the city, meeting officials and speaking about the project. Sometimes he returned frustrated with the bureaucracy. Sometimes he spoke about contractors who had failed to deliver, officers who did not understand the urgency, or a system that made even the simplest things unnecessarily difficult.

    He had a new explanation for every delay and a new promise for every gathering. The village, meanwhile, had changed in small ways.

    There were more ponds in the fields now. Farmers had started sharing what they had learned about collecting rainwater, improving irrigation and choosing crops suited to the water available. Some had begun experimenting with better seeds and farming practices. The two brothers from Raghu’s family had become familiar faces among farmers from nearby villages who came to see their ponds.

    One afternoon, Devendra met Raghu’s elder son near the fields.

    “Arre, is saal nehar aa jayegi. Dekha, meri mehnat ka kamaal? Pandrah saal lage, magar le aayenge. Bade kaam samay lekar hi hote hain. Bhagirath ji ko bhi kitne saal tapasya karni padi thi.”

    He said it with the same excitement he had shown at the first gathering fifteen years ago.

    Raghu’s son smiled.

    “Pradhan ji, talaab mein paani hai. Is baar fasal achhi hogi. Agriculture University ke professor sahab keh rahe the, jab unse beej lene gaye the.”

  • Leadership Unfolded: How I Evolved as a Leader

    Leadership Unfolded: How I Evolved as a Leader

    Leadership is a journey of constant evolution. Over the past 5–6 years, I’ve grown into my role, and over time, I’ve come to realize that leadership is much more than just meeting deadlines or driving results. It’s about creating lasting impact, ensuring sustainability, and fostering efficiency that serves both individuals and teams. This understanding didn’t come to me overnight. Instead, it evolved through years of reflection, trial and error, and moments of both success and failure.

    Early in my career, I thought leadership meant pushing harder and faster to achieve more. But as I progressed, I learned that true leadership lies in enabling teams to thrive without sacrificing their well-being or losing sight of our core objectives. Here, I’ll share some of the lessons I’ve learned — the challenges we faced, the strategies we adopted, and the insights I gained through my journey.

    Recognizing the Challenges

    When I first took on leadership responsibilities, my approach was shaped by traditional methods — push harder, set aggressive targets, and demand results. While this approach worked in the short term, it came at a significant cost: burnout, misaligned expectations, and strained team dynamics.

    One of the key challenges was our approach to deadlines. The rigid, push-based model often led to unrealistic commitments. This created unnecessary stress, eroded team morale, stifled creativity, and hindered long-term efficiency.

    Another challenge was how we recognized and engaged our teams. In the rush to deliver, we sometimes overlooked individual contributions, which led to disengagement. Building a transparent and positive recognition culture became a priority, as teams needed to feel valued for their efforts.

    Lastly, balancing expectations while maintaining a healthy work culture was a constant tightrope walk. Teams often faced external pressures. Without proper alignment, these pressures led to inefficiencies and blame cycles. As a leader, my role was to guide the team through these challenges, ensuring clarity, purpose, and alignment in our work.

    The Solutions and Strategies

    1. Adopting a Pull-Based Approach I recall a project where immense deadline pressure had left the team stressed, morale low, and quality slipping. It was a wake-up call for me to rethink my leadership approach. I realized that simply pushing harder wasn’t the solution. We needed to leverage the team’s diverse skills and experiences, recognizing that occasional intense efforts were acceptable but shouldn’t become the norm. By shifting to a more flexible, impact-driven model and aligning objectives with achievable timelines, we fostered a healthier, more sustainable environment. This transformation not only improved outcomes but also reignited the team’s morale and engagement.
    2. Learning and Development Initiatives We emphasized learning and development not just for skill-building but as a path to personal growth. My journey through an MS program in Data Science and AI opened my eyes to areas I hadn’t explored, revealing blind spots and pushing me toward a fulfilling transformation. The satisfaction of gaining technical knowledge and personal growth inspired me to bring the same opportunities to my team. Through our initiatives, we encouraged certifications and workshops, resulting in 76 certifications in a year. This wasn’t just about upskilling — it created a culture of empowerment, pride, and commitment to excellence, where people felt supported in their growth.
    3. Transparent and Inclusive Recognition Recognition became a priority for me after reflecting on my own experiences of feeling overlooked despite putting in tireless effort. I realized how crucial it is for leaders to make their teams feel valued. This insight led to the creation of the ‘Maestro of the Month’ program — a transparent and inclusive initiative where a panel from various teams evaluates self-nominations and peer recommendations. Winners are celebrated publicly with stakeholders, highlighting their impact and fostering a culture of mutual respect. While recognition isn’t the sole motivator, timely acknowledgment can inspire creativity, collaboration, and a deeper sense of belonging. When people feel their work is genuinely valued, they contribute in ways that surpass expectations, unlocking new potential within the team.
    4. Enhancing Communication and Alignment Communication and alignment were key to fostering a cohesive team environment. We introduced initiatives like bi-weekly team morale check-ins, quarterly update meetings with stakeholders, and a tribe newsletter. These efforts ensured everyone stayed connected to our goals and progress, reinforcing the idea that every team member had a role in shaping our collective success.
    5. Leadership Sprint and Retrospection We embraced retrospection techniques like the Six Thinking Hats framework and SWOT/TOWS analyses. These exercises helped us understand team strengths, weaknesses, and opportunities. They also provided a structured way to make informed decisions and continuously improve. We used these insights to better leverage learning and development platforms, ensuring our efforts were aligned with the org’s evolving needs.

    Impact and Outcomes

    The results of these strategies were profound — not just in terms of metrics, but in the healthier, more resilient team culture they fostered. We observed:

    • Improved Developer Experience: Streamlined processes and tools led to a noticeable improvement in developer experience.
    • Enhanced Project Scalability and Security: We saw enhanced scalability, performance, and security across several key projects, including major migrations and framework upgrades.
    • Stronger Team Culture: A thriving, engaged team culture was supported by continuous learning, transparent recognition, and better work-life balance.

    However, the real success lay in the cultural shift that these results represented. By creating an environment where teams could focus on their strengths, collaborate openly, and operate without fear of failure, we saw not only improved well-being but also sharper, more efficient outcomes.

    Next Steps: Continuing the Journey

    As I look back on my leadership journey, it feels like navigating a long road with twists, turns, and occasional roadblocks. There were moments when I thought I knew it all, only to find out that growth was waiting just around the corner. I know there’s still a long road ahead. Leadership isn’t a destination — it’s a continuous process of learning, adapting, and evolving. I look forward to the next lessons that lie ahead, knowing that each experience will continue to shape who I am as a leader.

  • The Cost of Misalignment: A Leadership Tale!

    The Cost of Misalignment: A Leadership Tale!

    In a fast-paced world, whether in healthcare or software development, misaligned priorities and poor communication can derail even the most straightforward plans. This story from a hospital ward — modeled after challenges faced in software organizations — offers valuable insights into leadership, communication, and effective problem-solving.

    A Patient’s Choice

    Mr. Tata, an elderly patient struggling with mobility, sought medical advice at a renowned hospital. After a thorough diagnosis, Dr. Banga and Dr. PK — both experienced surgeons — recommended a minor surgery. The procedure was straightforward, with a quick recovery period, and it promised to restore Mr. Tata’s movement.

    Initially receptive to the idea, Mr. Tata later expressed his hesitation to Jassi, the patient care coordinator. He preferred a medication-based treatment over surgery, citing discomfort and unease. While the doctors did not recommend this approach, Mr. Tata insisted on his choice.

    The Administrative Roadblock

    Jassi, empathetic to the patient’s concerns, approached Chaudhary Jagga, the hospital’s administrator, to arrange for Mr. Tata’s admission and start the alternative treatment. However, Jagga was firm: formalities must be completed before any admission or treatment could proceed.

    Despite the urgency, neither Jassi nor Jagga was willing to compromise. The process stalled, leaving Mr. Tata without treatment and the hospital staff in limbo.

    Leadership Intervention — or Lack Thereof

    Hoping for a resolution, Jassi escalated the issue to Dr. Khoya, the Head of Surgery, and Dr. Patel Managing Director of the Hospital. Instead of addressing the core problem — aligning Jassi and Jagga to admit the patient — Dr. Khoya diverted his focus. He instructed the surgeons, Dr. Banga and Dr. PK, to consult an external expert, Dr. Angad, to validate the proposed treatment plan.

    Meanwhile, the rest of the management team, including Dr. Patel, remained silent. Their lack of engagement compounded the issue, leaving Jassi and Jagga in a stalemate and the surgeons frustrated.

    The Surgeons’ Dilemma

    Reluctantly, Dr. Banga and Dr. PK complied with Dr. Khoya’s directive. Dr. Angad reviewed the case and confirmed that the surgeons’ original plan was appropriate. He was also aligned with alternative treatment that both the Dr. has prepared. However, the consultation did nothing to address the root cause: the misalignment between the patient care coordinator and the hospital administrator.

    The Fallout

    • The Patient: Mr. Tata, left untreated, grew increasingly uncomfortable and lost trust in the hospital’s ability to provide timely care.
    • The Coordinators: Jassi and Jagga remained at odds, unable to break the procedural deadlock.
    • The Surgeons: Dr. Banga and Dr. PK felt demoralized, their focus disrupted by unnecessary directives.
    • The Organization: A simple issue spiraled into a web of inefficiencies due to a lack of coordination, engagement, and decisive leadership.

    Key Takeaways

    Engage Proactively: Leadership must actively engage with escalated issues. A lack of response from key stakeholders, like Dr. Patel, left the team to navigate challenges without support.

    Focus on the Core Problem: Dr. Khoya’s decision to consult Dr. Angad diverted attention from the real blocker — the admission impasse. Leaders must identify and address the actual bottleneck.

    Empower Cross-Functional Collaboration: Misalignment between Jassi and Jagga reflects a broader issue of siloed teams. Clear communication and shared goals are essential for smooth operations.

    Avoid Unnecessary Pressure: Redirecting the surgeons’ attention to a redundant validation task frustrated the team and delayed action. Leaders must prioritize tasks that directly solve problems.

    Stay Customer-Centric: At the center of any organization is its stakeholder — be it a patient, customer, or end-user. Processes should serve their needs, not hinder them.

    Conclusion

    This story highlights the dangers of misaligned priorities, poor communication, and disengaged leadership — whether in healthcare or software development. Teams lose focus, stakeholders suffer, and inefficiencies multiply.

    To prevent such scenarios, leaders must:

    • Engage proactively with escalated issues.
    • Focus on solving root problems.
    • Foster alignment and empower teams to collaborate effectively.

    The question every leader must ask is: Are we addressing the right issues, or are we just adding to the noise?

  • My Leadership Journey

    My Leadership Journey

    Leadership is a journey of constant evolution. Over the past 5–6 years, I’ve grown into my role, and over time, I’ve come to realize that leadership is much more than just meeting deadlines or driving results. It’s about creating lasting impact, ensuring sustainability, and fostering efficiency that serves both individuals and teams. This understanding didn’t come to me overnight. Instead, it evolved through years of reflection, trial and error, and moments of both success and failure.

    Early in my career, I thought leadership meant pushing harder and faster to achieve more. But as I progressed, I learned that true leadership lies in enabling teams to thrive without sacrificing their well-being or losing sight of our core objectives. Here, I’ll share some of the lessons I’ve learned—the challenges we faced, the strategies we adopted, and the insights I gained through my journey.

    Recognizing the Challenges

    When I first took on leadership responsibilities, my approach was shaped by traditional methods—push harder, set aggressive targets, and demand results. While this approach worked in the short term, it came at a significant cost: burnout, misaligned expectations, and strained team dynamics.

    One of the key challenges was our approach to deadlines. The rigid, push-based model often led to unrealistic commitments. This created unnecessary stress, eroded team morale, stifled creativity, and hindered long-term efficiency.

    Another challenge was how we recognized and engaged our teams. In the rush to deliver, we sometimes overlooked individual contributions, which led to disengagement. Building a transparent and positive recognition culture became a priority, as teams needed to feel valued for their efforts.

    Lastly, balancing expectations while maintaining a healthy work culture was a constant tightrope walk. Teams often faced external pressures. Without proper alignment, these pressures led to inefficiencies and blame cycles. As a leader, my role was to guide the team through these challenges, ensuring clarity, purpose, and alignment in our work.

    The Solutions and Strategies

    1. Adopting a Pull-Based Approach I recall a project where immense timeline pressure had left the team stressed, morale low, and quality slipping. It was a wake-up call for me to rethink my leadership approach. I realized that simply pushing harder wasn’t the solution. We needed to leverage the team’s diverse skills and experiences, recognizing that occasional intense efforts were acceptable but shouldn’t become the norm. By shifting to a more flexible, impact-driven model and aligning objectives with achievable timelines, we fostered a healthier, more sustainable environment. This transformation not only improved outcomes but also reignited the team’s morale and engagement.
    2. Learning and Development Initiatives We emphasized learning and development not just for skill-building but as a path to personal growth. My journey through an MS program in Data Science and AI opened my eyes to areas I hadn’t explored, revealing blind spots and pushing me toward a fulfilling transformation. The satisfaction of gaining technical knowledge and personal growth inspired me to bring the same opportunities to my team. Through our initiatives, we encouraged certifications and workshops, resulting in all time max certifications in a year. This wasn’t just about upskilling—it created a culture of empowerment, pride, and commitment to excellence, where people felt supported in their growth.
    3. Transparent and Inclusive Recognition Recognition became a priority for me after reflecting on my own experiences of feeling overlooked despite putting in tireless effort. I realized how crucial it is for leaders to make their teams feel valued. This insight led to the creation of a recognition program—a transparent and inclusive initiative where a panel from various teams evaluates self-nominations and peer recommendations. Winners are celebrated publicly with stakeholders, highlighting their impact and fostering a culture of mutual respect. While recognition isn’t the sole motivator, timely acknowledgment can inspire creativity, collaboration, and a deeper sense of belonging. When people feel their work is genuinely valued, they contribute in ways that surpass expectations, unlocking new potential within the team.
    4. Enhancing Communication and Alignment Communication and alignment were key to fostering a cohesive team environment. We introduced initiatives like bi-weekly team morale check-ins, quarterly update meetings with stakeholders, and a tribe newsletter. These efforts ensured everyone stayed connected to our goals and progress, reinforcing the idea that every team member had a role in shaping our collective success.
    5. Leadership Sprint and Retrospection We embraced retrospection techniques using the Six Thinking Hats framework and SWOT/TOWS analyses. These exercises helped us understand team strengths, weaknesses, and opportunities. They also provided a structured way to make informed decisions and continuously improve. We used these insights to better leverage learning and development platforms, ensuring our efforts were aligned with the team’s evolving needs.

    Impact and Outcomes

    The results of these strategies were profound—not just in terms of metrics, but in the healthier, more resilient team culture they fostered. We observed:

    • Improved Developer Experience: Streamlined processes and tools led to a noticeable improvement in developer experience.
    • Enhanced Project Scalability and Security: We saw enhanced scalability, performance, and security across several key projects, including major migrations and framework upgrades.
    • Stronger Team Culture: A thriving, engaged team culture was supported by continuous learning, transparent recognition, and better work-life balance.

    However, the real success lay in the cultural shift that these results represented. By creating an environment where teams could focus on their strengths, collaborate openly, and operate without fear of failure, we saw not only improved well-being but also sharper, more efficient outcomes.

    Next Steps: Continuing the Journey

    As I look back on my leadership journey, it feels like navigating a long road with twists, turns, and occasional roadblocks. There were moments when I thought I knew it all, only to find out that growth was waiting just around the corner. I know there’s still a long road ahead.

    Leadership isn’t a destination—it’s a continuous process of learning, adapting, and evolving. I look forward to the next lessons that lie ahead, knowing that each experience will continue to shape who I am as a leader.