<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by NAGESH P on Medium]]></title>
        <description><![CDATA[Stories by NAGESH P on Medium]]></description>
        <link>https://medium.com/@nageshraopmp?source=rss-fee4016baf70------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*u6PhS4LSkmteYrsG2elObw.png</url>
            <title>Stories by NAGESH P on Medium</title>
            <link>https://medium.com/@nageshraopmp?source=rss-fee4016baf70------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:51:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nageshraopmp/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Hope Is Not a Risk Mitigation Strategy]]></title>
            <link>https://medium.com/@nageshraopmp/hope-is-not-a-risk-mitigation-strategy-e55e12b6efbf?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/e55e12b6efbf</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 14:59:10 GMT</pubDate>
            <atom:updated>2026-10-24T15:00:27.521Z</atom:updated>
            <content:encoded><![CDATA[<p><em>From the Field — 5 | Connecting the Dots — Personal observations &amp; lessons from working with products, people and organizations</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*rYskTxUMRl2slSnKtnun0A.png" /><figcaption>Hope is Not a Risk Mitigation Strategy</figcaption></figure><p>In product management and project execution, we spend a lot of time discussing risks.</p><p>We identify them, assess their impact, assign owners and put mitigation plans in place.</p><p>At least, that is what the process tells us to do.</p><p>But I have often wondered whether having a mitigation in a risk register necessarily means that we are managing the risk.</p><p>Consider a few familiar statements.</p><p>“We will get x% cost out.”</p><p>“We will hold the price.”</p><p>“We will recover the schedule.”</p><p>“We will get the certification in time.”</p><p>“We will find an alternate supplier.”</p><p>All of these outcomes may be achievable. But there is a difference between believing something can happen and having a credible plan to make it happen.</p><p><strong>Hope is not a risk mitigation strategy.</strong></p><h4>When an aspiration becomes a mitigation</h4><p>Consider a product whose cost is higher than the business case allows.</p><p>The team identifies a margin risk and proposes a mitigation: achieve x% cost reduction.</p><p>It sounds reasonable. Cost reduction is often necessary, and the team may have several ideas to explore.</p><p>But what has actually changed?</p><p>Have the opportunities been identified? Have the design changes been evaluated? Have suppliers been engaged? Are the savings quantified? Is there a timeline, and does someone own each action?</p><p>And what happens if the expected savings do not materialize?</p><p>Until we have credible answers, the proposed cost reduction remains an aspiration.</p><p>It may be a good aspiration. It may even be achievable. But recording it as a mitigation does not, by itself, reduce the risk.</p><p>I think this distinction is important because, once an action appears in a risk register, it can create a sense of progress even when the underlying exposure has not changed.</p><h4>The same problem appears in other areas</h4><p>This is not just about cost.</p><p>A project is running behind schedule.</p><p>“We will recover the delay during execution.”</p><p>A new certification requirement emerges.</p><p>“We will get the approval before the first build.”</p><p>A supplier is struggling to meet commitments.</p><p>“We will find an alternate source.”</p><p>The market is becoming more competitive.</p><p>“We will hold the price.”</p><p>These statements are not necessarily wrong. Experienced teams can recover schedules, qualify alternate suppliers, secure approvals and find ways to reduce costs.</p><p>The question is what sits behind the statement.</p><p>For a schedule recovery, have we identified the activities that can be shortened, the dependencies that can be removed or the resources that need to change?</p><p>For an alternate supplier, have we assessed capability, capacity, quality, qualification requirements and lead time?</p><p>For certification, do we understand applicability, documentation, testing and approval timelines?</p><p>For pricing, do we have a clear understanding of customer value, competitor positioning and the commercial options available to us?</p><p>The actions will differ, but the principle remains the same.</p><p><strong>An intended outcome is not the same as a risk mitigation.</strong></p><h4>The risk register can look better than reality</h4><p>This is where I think we need to be careful.</p><p>A risk register might say:</p><p><strong>Risk:</strong> Margin below threshold<br><strong>Mitigation:</strong> Achieve x% cost reduction<br><strong>Owner:</strong> Product team<br><strong>Status:</strong> In progress</p><p>Everything looks fine.</p><p>The risk has been identified. There is an owner. A mitigation has been recorded.</p><p>But does that mean the risk has reduced?</p><p>Not necessarily.</p><p>The cost-reduction target may still depend on design changes that have not been validated, supplier negotiations that have not happened or savings that have not been quantified.</p><p>The register tells us that an action has been identified. It does not automatically tell us whether the action is credible or whether the risk exposure has changed.</p><p>This is why I believe we should distinguish between <strong>having a mitigation and having mitigated a risk</strong>.</p><p>They are not the same thing.</p><h4>One experience reinforced this for me</h4><p>I once worked through a situation where a new regional regulatory requirement came into force with relatively little notice.</p><p>There were many components to consider, and the first challenge was understanding which ones were affected.</p><p>The team focused on the major components and brought in specialist support to assess the more complex requirements.</p><p>A significant amount of effort went into addressing these issues.</p><p>However, some simpler items were assumed to be straightforward and were overlooked.</p><p>They were not the most technically challenging parts of the problem. But they still needed attention.</p><p>The experience reinforced something for me: we can spend a great deal of time solving the complex parts of a problem and still be caught out by something that was sitting in plain sight.</p><p>The lesson was not simply to maintain a more detailed risk register. It was to question our assumptions, including the ones that seem too obvious to challenge.</p><p>Sometimes, the risk is not hidden. We have just assumed it will take care of itself.</p><h4>What does a real mitigation look like?</h4><p>For me, a useful way to examine a mitigation is to ask three questions.</p><p><strong>1. What needs to change?</strong></p><p>Be specific about the action required to reduce the probability or impact of the risk.</p><p><strong>2. How will we get there?</strong></p><p>Identify the steps, owners, timelines, dependencies and evidence that support the proposed action.</p><p><strong>3. What happens if it does not work?</strong></p><p>Understand the residual risk and identify what we will do if the expected outcome is not achieved.</p><p>Not every mitigation will have complete certainty. That is the nature of risk.</p><p>But there should be a credible basis for believing that the proposed action will make a difference.</p><p>And if that basis does not yet exist, we should be honest about it.</p><p>The risk may still be open. That is better than giving ourselves a false sense of security.</p><h4>Ask for the bridge</h4><p>One question I find useful is:</p><p><strong>“Show me the bridge.”</strong></p><p>If we need to reduce cost, show me the path from the current cost to the target.</p><p>If we need to recover the schedule, show me how we will move from the current position to the committed date.</p><p>If we need certification, show me the steps and milestones that give us confidence in the approval timeline.</p><p>The <em>bridge </em>connects where we are today with where we need to be.</p><p>It exposes assumptions, makes gaps visible and clarifies ownership.</p><p>Sometimes, it confirms that the plan is credible. At other times, it reveals that we need a different approach.</p><p>Neither outcome is a problem. In fact, discovering a weakness early is one of the reasons we perform risk assessments in the first place.</p><p>The objective is not to make every risk look green. It is to understand the risk well enough to make a sound decision.</p><h4>Connecting the Dots</h4><p>I don’t believe the answer is to become pessimistic.</p><p>Teams need ambition. Product development and business execution often require us to attempt things that are difficult and uncertain.</p><p>But optimism and risk mitigation serve different purposes.</p><p>Optimism gives us the confidence to pursue an outcome. Risk mitigation gives us a credible path to deal with the uncertainty along the way.</p><p>As leaders, we need both.</p><p>The next time a risk review concludes with “we will reduce cost”, “we will recover the schedule” or “we will get it done”, perhaps the most useful question is not whether we believe the team can do it.</p><p>It is whether we understand how it will happen, what evidence supports the plan and what we will do if the assumptions prove wrong.</p><blockquote><strong><em>Hope can motivate a team. A credible plan can reduce risk. And honest assessment tells us how much risk remains.</em></strong></blockquote><p>That distinction matters, not just in risk registers, but in the way we make product and business decisions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e55e12b6efbf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sycophancy: The Bane of a Winning Team]]></title>
            <link>https://medium.com/@nageshraopmp/sycophancy-the-bane-of-a-winning-team-50593bc03bd3?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/50593bc03bd3</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 15:22:22 GMT</pubDate>
            <atom:updated>2026-10-11T15:22:22.996Z</atom:updated>
            <content:encoded><![CDATA[<p><em>From the Field — 4 | Connecting the Dots — Personal observations &amp; lessons from working with products, people and organizations</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m71WRm1gB1N8_jSaIJ_ocQ.png" /></figure><p>Have you ever sat in a meeting where everyone seems to agree with the leader, only to hear a different opinion once the meeting is over?</p><p>Sometimes, people genuinely agree. Sometimes, they have doubts but choose not to express them. And sometimes, they actively support a position even when they have reservations.</p><p>It makes me wonder: are we building teams that think together, or teams that have simply learned to agree?</p><p>There is a difference. Over time, it can make a real difference to how an organization works.</p><h4>When agreement becomes a career strategy</h4><p>Most of us want to grow in our careers. We want recognition, opportunities and the confidence of our leaders. There is nothing wrong with that.</p><p>The problem starts when people believe that agreeing with authority is a more reliable path to growth than demonstrating independent judgement.</p><p>Instead of asking whether a decision is right, they begin to consider <em>whether supporting it is the safer choice</em>.</p><p>Some keep their doubts to themselves. Others actively defend a position because they believe it will strengthen their standing.</p><p>Over time, agreement can become a career strategy.</p><p>The concern is not that people want to progress. It is when pleasing the right people appears to matter more than the quality of their contribution.</p><p>This is where sycophancy becomes damaging. The focus shifts from doing what is right for the team or organization to doing what is advantageous for oneself.</p><h4>What happens to people who challenge?</h4><p>Imagine two people in a team.</p><p>One consistently supports the prevailing view. The other asks difficult questions, points out gaps and occasionally disagrees with the direction being taken.</p><p>The first may be seen as aligned and easy to work with. The second may be labelled difficult or negative.</p><p>Of course, the person raising concerns may not always be right. The way a challenge is presented also matters.</p><p>But what happens when the concern is legitimate and supported by evidence?</p><p>Does the organization examine the argument, or does it start questioning the attitude of the person raising it?</p><p>When people who challenge assumptions lose influence while those who consistently agree gain it, the team receives a message about what is valued.</p><p>People notice these things, even when nobody says them openly.</p><p>Some will continue to speak up. Others will become more cautious. Eventually, some may decide that keeping their views to themselves is simply not worth the professional risk.</p><p><strong><em>When people are penalized for raising legitimate concerns, silence becomes a rational response.</em></strong></p><h4>What happens to people who challenge?</h4><p>This is where the issue becomes more serious.</p><p>Imagine two people in a team.</p><p>One consistently supports the prevailing view. The other asks difficult questions, points out gaps and occasionally disagrees with the direction being taken.</p><p>The first may be perceived as aligned and easy to work with.</p><p>The second may be seen as difficult, negative or insufficiently supportive.</p><p>Of course, the person raising concerns may not always be right. The way a challenge is presented also matters.</p><p>But what happens when the concern is legitimate and supported by evidence?</p><p>Does the organization examine the argument?</p><p>Or does it begin questioning the attitude of the person raising it?</p><p>When people who challenge assumptions lose influence while those who consistently agree gain it, the team receives a message about what is valued.</p><p>It does not take long for people to understand that message.</p><p>Some will continue to speak up. Others will become more cautious. And some will decide that keeping their views to themselves is simply not worth the professional risk.</p><p><strong>When people are penalized for raising legitimate concerns, silence becomes a rational response.</strong></p><h4>Leaders shape the behaviour they receive</h4><p>It is easy to blame those who agree too readily. But leaders also have a role to play.</p><p>Why do some leaders surround themselves with people who rarely challenge them?</p><p>The reasons can differ.</p><p>Some genuinely believe that those who support them are the most capable or best aligned with the organization’s objectives. Others find disagreement uncomfortable because a challenge to their decision can feel like a challenge to their authority.</p><p>And sometimes, leaders recognize the behaviour but tolerate it because those people are useful to them.</p><p>Whatever the reason, the consequences can be similar.</p><p>A leader may ask for honest feedback in a meeting. But if someone who raises a legitimate concern subsequently loses influence, the team will remember what happened more than what was said.</p><p>The next time, people may choose their words more carefully. Some may decide not to raise the concern at all.</p><p><strong><em>Culture is shaped not only by what leaders say they value, but also by what they reward and tolerate.</em></strong></p><h4>The cost to the organization</h4><p>Why should this matter beyond individual careers and workplace relationships?</p><p>Because organizations depend on the judgement and experience of their people to make good decisions.</p><p>Consider a team evaluating a new opportunity.</p><p>One person has concerns about market fit. Another questions the cost assumptions. Someone else believes the schedule is unrealistic.</p><p>These concerns may turn out to be wrong. But they deserve to be examined.</p><p>What happens if the team has learned that challenging the prevailing view is risky?</p><p>The concerns may remain unspoken. The decision moves forward with apparent agreement, and important assumptions go untested.</p><p>The organization may discover the problem only when the market responds, costs increase or the schedule slips. By then, correcting the course may be much more difficult.</p><p>This is one of the hidden costs of sycophancy: <strong>the organization loses access to knowledge that already exists within its own team.</strong></p><p>The same problem can affect product strategy, innovation, investment decisions, quality and risk management.</p><p>No organization can consistently make good decisions if people are reluctant to question the assumptions behind them.</p><h4>Loyalty does not mean blind agreement</h4><p>There is a connection here with loyalty.</p><p>We sometimes see the person who always says yes as supportive, while the person who challenges a decision is perceived as difficult.</p><p>But genuine commitment to an organization’s success sometimes requires disagreement.</p><p>A Product Manager should be willing to question a product direction that does not address customer needs. An engineer should be able to raise a technical concern even when the preferred direction has already been established. A team member should be able to tell a leader that an assumption needs another look.</p><p><em>None of this guarantees that the person raising the concern is right</em>. But it gives the organization an opportunity to examine the issue before committing to a decision.</p><p>Once a decision has been made after a fair discussion, the team can align around execution. That is different from expecting everyone to agree before the discussion has even taken place.</p><p><strong><em>Loyalty is about caring for the outcome, not protecting every decision from challenge.</em></strong></p><h4>Connecting the Dots</h4><p>It is relatively easy to surround yourself with people who agree with you. It is much harder to build a team that will tell you when you might be wrong.</p><p>For leaders, the real test comes when someone raises a concern they would rather not hear.</p><p>Do they listen? Is the evidence examined? Does the person who raised the concern continue to be respected, even if the final decision goes another way?</p><p>These moments reveal more about an organization’s culture than statements about openness and collaboration ever will.</p><p>Leaders need people who can think independently, challenge assumptions and speak honestly. Team members, in turn, need to raise concerns constructively and remain open to being wrong themselves.</p><p>Both sides have a responsibility.</p><p>A team that never challenges its leader may look united. But unity without honest debate can become a weakness.</p><p><strong>In the end, a winning team is not one where everyone agrees. It is one where people can disagree, examine the evidence and still work together towards a common goal.</strong></p><p>The strength of a team lies not in how readily its members agree, but in <em>how well they work together to question assumptions, consider different perspectives and make better decisions</em>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50593bc03bd3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Storage: From an Energy Asset to a Flexibility Asset]]></title>
            <link>https://medium.com/@nageshraopmp/storage-from-an-energy-asset-to-a-flexibility-asset-a31413ca9033?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/a31413ca9033</guid>
            <category><![CDATA[renewable-energy]]></category>
            <category><![CDATA[clean-energy]]></category>
            <category><![CDATA[energy-transition]]></category>
            <category><![CDATA[indian-renewable-energy]]></category>
            <category><![CDATA[energy-storage]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Sun, 04 Oct 2026 08:51:19 GMT</pubDate>
            <atom:updated>2026-10-04T08:51:19.253Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Energy Transition Insights — Part 6</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KSPXqWpJymQlj0lT7Uz0yg.png" /></figure><h4><strong><em>What India’s emerging storage requirements tell us about the changing value of renewable energy</em></strong></h4><p>Something interesting is happening in India’s renewable energy market.</p><p>For years, we focused on making wind and solar cheaper.</p><p>Then we started asking them to become more predictable.</p><p>Then more dispatchable.</p><p>Then available during specific hours.</p><p>And now, increasingly, the grid is asking renewable projects to bring some flexibility along with them.</p><p>In September 2026, the Central Electricity Authority (CEA) proposed draft regulations requiring new ground-mounted solar and onshore wind projects to have co-located Energy Storage Systems equivalent to at least 10% of installed plant capacity, with a minimum two-hour duration for projects commissioned after July 1, 2027.</p><p>For projects commissioned after July 1, 2029 and up to June 30, 2031, the proposed minimum duration increases to four hours.</p><p>For a 100 MW project, that means: <strong>10 MW × 2 hours = 20 MWh</strong></p><p>and later: <strong>10 MW × 4 hours = 40 MWh.</strong></p><p>At first glance, this looks like another technical requirement.</p><p><em>I see it differently.</em></p><p><strong>It is a signal that the value of renewable energy is moving beyond generation towards flexibility.</strong></p><h4><strong>Why does renewable energy need storage?</strong></h4><p>Wind and solar have done an incredible job of reducing the cost of renewable generation. But they generate when the resource is available.</p><p>The grid needs electricity when consumers need it.</p><p>These two things don’t always happen together.</p><p>Solar generation is strongest during the day, while demand can remain high into the evening.</p><p>Wind generation can vary with weather conditions, while demand follows a completely different pattern.</p><p>As renewable penetration increases, this mismatch becomes more important.</p><p>Storage provides a bridge.</p><p><strong>Generate → Store → Deliver</strong></p><p>But I think even this description is incomplete.</p><p>The real value of storage is not simply that it stores electricity.</p><p>It is that it gives us some control over <strong>when that electricity becomes available.</strong></p><p>That is <strong><em>flexibility</em></strong>.</p><h4><strong>The 10% requirement is an interesting signal</strong></h4><p>Take the proposed CEA requirement.</p><p>A 100 MW renewable project does not need a 100 MW battery.</p><p>It needs at least: <strong>10 MW of storage power </strong>with the specified duration.</p><p>Initially: <strong>10 MW × 2 hours = 20 MWh</strong></p><p>Later: <strong>10 MW × 4 hours = 40 MWh.</strong></p><p>The objective is therefore <strong><em>not </em></strong>to make the entire renewable plant fully dispatchable.</p><p>It is to introduce a minimum level of <strong><em>controllability </em></strong>into the generation portfolio.</p><p>And that is an important distinction.</p><p><strong>The battery is not replacing the renewable plant. </strong>It is changing what the renewable plant can do.</p><h4><strong>Why 2 hours? Why 4 hours?</strong></h4><p>This is the part I find particularly interesting. The move from two hours to four hours is not simply about batteries becoming cheaper. It reflects a changing system requirement.</p><p>CEA’s resource adequacy analysis has found that four-hour storage may be required to meet demand during non-solar hours on the majority of days, while the storage requirement for morning peaks can be less than two hours.</p><p>So duration is becoming part of the requirement.</p><p>A: <strong>10 MW / 20 MWh </strong>battery and a: <strong>10 MW / 40 MWh </strong>battery have the same power rating.</p><p>But they don’t provide the same flexibility.</p><p>That brings us to a simple point that is sometimes missed when we talk about BESS:</p><p><strong>MW tells us how much power.</strong></p><p><strong>MWh tells us for how long.</strong></p><p>But neither tells us <strong><em>when </em></strong>or <strong><em>why </em></strong>we need that power. And that is where the discussion becomes much more interesting.</p><h4><strong>From Energy Storage to Flexibility</strong></h4><p>The obvious application of a battery is energy shifting.</p><p>Charge when renewable energy is available. Discharge when it is needed.</p><p>But storage can potentially do more. It can:</p><ul><li>Firm renewable generation</li><li>Support peak demand</li><li>Manage ramps</li><li>Reduce renewable curtailment</li><li>Shift energy across time</li><li>Participate in eligible market opportunities</li><li>Provide certain grid-support services</li></ul><p><a href="https://cea.nic.in/wp-content/uploads/notification/2025/02/Advisory_on_colocating_Energy_Storage_System_with_Solar_Power_Projects_to_enhance_grid_stability_and_cost_efficiency.pdf?utm_source=chatgpt.com">CEA’s 2025 advisory</a> on co-locating storage with solar projects already recognized this broader role. It described both single-cycle operation — charging from co-located solar and discharging later — and double-cycle operation, including charging from the grid during low-demand periods and discharging during peak periods.</p><p>So the battery is no longer simply an energy container.</p><p>It becomes a <strong>flexibility asset</strong>.</p><h4><strong>The Battery Is Not the Product</strong></h4><p>Wearing my product-management hat, I start with a question of “ what does end user / customer need ?”</p><p>When we talk about BESS, the conversation often starts with:</p><p><strong>MW.</strong></p><p><strong>MWh.</strong></p><p><strong>C-rate.</strong></p><p><strong>Round-trip efficiency.</strong></p><p><strong>Cycle life.</strong></p><p>All of these are important. <em>But they are specifications.</em> They don’t tell us what the customer is actually buying.</p><p>Suppose a customer says:</p><p>“I need 100 MW during the evening peak.” That’s a customer requirement. The battery is one possible solution.</p><p>Another customer may say:</p><p>“I need renewable power around the clock.”. That is a completely different requirement.</p><p>The optimal combination of wind, solar and storage will be different.</p><p>This is something product management has taught me repeatedly:</p><p><strong>Start with the customer problem, not the technology.</strong></p><p>The technology configuration should follow the requirement.</p><p><strong>This connects directly to FDRE</strong></p><p>In the <a href="https://medium.com/@nageshraopmp/fdre-when-renewable-energy-became-a-commitment-ba6f29ba3db2">FDRE article,</a> we looked at how the market moved from simply procuring renewable generation towards procuring a <strong>commitment to deliver renewable energy</strong>.</p><p>Storage is one of the tools that enables that commitment.</p><p>But again, the battery is not the product.</p><p>The <strong><em>delivery profile</em></strong> is the product.</p><p>Suppose a customer requires: <strong>300 MW during specified hours.</strong></p><p>The developer now has to determine the optimal combination of:</p><ul><li>Wind</li><li>Solar</li><li>Storage</li><li>Oversizing</li><li>Operating strategy</li></ul><p>to meet that commitment.</p><p>Now, we have moved from:</p><p><strong>Technology selection </strong>to <strong>System optimization.</strong></p><p>And that is a significant change.</p><h4><strong>The Same Battery Can Have Different Value</strong></h4><p>Consider two projects.</p><p>Both have:</p><p><strong>100 MW / 200 MWh BESS</strong></p><p>Technically, they are identical.</p><p>But:</p><p><strong>Project A</strong> uses the battery every evening to shift solar energy into peak hours.</p><p><strong>Project B</strong> uses it to meet a contractual peak-delivery obligation while retaining flexibility for other eligible uses.</p><p>Same battery.</p><p>Different operating strategy.</p><p>Potentially very different economics.</p><p>This is why I increasingly think that the value of BESS cannot be captured simply by saying:</p><p>“₹X per MW” or “₹X per MWh.”</p><p>The value depends on <strong>what the battery is being asked to do.</strong></p><h4><strong>Product Management Perspective</strong></h4><p>This is where I see a strong parallel with product development.</p><p>A customer rarely buys a component simply because the component is technically superior.</p><p><strong><em>They buy an outcome</em></strong>.</p><p>The same is becoming true in renewable energy.</p><p>The customer may not really want:</p><p><strong>300 MW of wind + 450 MW of solar + 200 MWh of BESS.</strong></p><p>They may want:</p><p><strong>A certain amount of renewable electricity, delivered during a certain time window, with a certain level of reliability and at an acceptable cost.</strong></p><p>The generation and storage mix is the solution to that requirement.</p><p>This changes how I would think about product design.</p><p>Instead of asking:</p><p><strong>“What BESS should we use?”</strong></p><p>we should first ask:</p><p><strong>“What delivery problem are we solving?”</strong></p><p>Then:</p><p>What flexibility is required?</p><p>Then:</p><p>What combination of technologies delivers it at the lowest risk-adjusted cost?</p><p>That is a very different way of looking at storage.</p><h4><strong>Connecting the Dots</strong></h4><p>Looking back at the journey we have followed in this series, there seems to be a clear progression.</p><p><a href="https://medium.com/@nageshraopmp/from-lcoe-to-lcod-how-indias-renewable-energy-market-is-redefining-value-4d04f5c3e0c3"><strong>LCOE → LCOD : </strong>How cheaply can we generate electricity → Redefining value</a></p><p><a href="https://medium.com/@nageshraopmp/the-2026-dsm-draft-why-mnres-intervention-matters-for-india-s-renewable-future-6dd0b6a9c620"><strong>DSM : </strong>How accurately can we predict and schedule it?</a></p><p><a href="https://medium.com/@nageshraopmp/fdre-when-renewable-energy-became-a-commitment-ba6f29ba3db2"><strong>FDRE : </strong>Can we commit to delivering renewable energy?</a></p><p><a href="https://medium.com/@nageshraopmp/rtc-vs-peak-power-when-renewable-energy-doesnt-have-to-look-the-same-every-hour-386daf5acb13"><strong>RTC / Peak Power :</strong>When do we need that delivery?</a></p><p><a href="https://medium.com/@nageshraopmp/cfd-when-the-market-starts-pricing-risk-0839ab1c3fc3"><strong>CfD : </strong>How do we participate in the market while managing price risk?</a></p><p><strong>Storage : </strong>How do we move and optimise electricity through time?</p><p>Each step adds another dimension of value.</p><p>And perhaps this is what market maturity looks like.</p><p>Not replacing the previous model. <strong><em>But adding another layer to it.</em></strong></p><h4><strong>From Mandatory Storage to Optimised Storage</strong></h4><p>The CEA proposal, if ultimately notified in its current or modified form, would establish a baseline storage requirement for new wind and solar projects.</p><p>But the more interesting question comes after that.</p><p>Once everyone has some storage:</p><p><strong>Will 10% be enough?</strong></p><p><strong>Will two hours be enough?</strong></p><p><strong>When do we really need four hours?</strong></p><p><strong>Should the requirement be different for wind and solar?</strong></p><p><strong>Should it depend on location?</strong></p><p><strong>Should it depend on the grid node?</strong></p><p><strong>Should the battery be allowed to serve multiple applications?</strong></p><p>These are not simply engineering questions.</p><p>They are <strong>product and market-design questions.</strong></p><p>And I think this is where the next stage of India’s renewable-energy evolution will become particularly interesting.</p><h4><strong>Reflection</strong></h4><p>One lesson from my years across engineering, manufacturing, quality and product management is that the best solutions often emerge when we stop asking:</p><p><strong>“What can the technology do?”</strong></p><p>and start asking:</p><p><strong>“What problem are we trying to solve?”</strong></p><p>I think the same applies to storage.</p><p>A battery is not valuable simply because it has 20 MWh or 40 MWh.</p><p>Its value comes from what those MWh can do.</p><p>Shift energy.</p><p>Firm generation.</p><p>Meet a peak.</p><p>Respond to the grid.</p><p>Support a contractual commitment.</p><p>Or potentially provide multiple services at different times.</p><p><strong>The technology is the enabler.</strong></p><p><strong>Flexibility is the value.</strong></p><p>And perhaps this is the next evolution in renewable energy:</p><p><strong>We are moving from buying renewable energy to increasingly buying the ability to shape, schedule and optimise renewable energy.</strong></p><p>That is a very different proposition.</p><p>And I think we are only beginning to understand how to value it.</p><h3>Coming Next</h3><p><strong>MW Is Not the Product: Why the Shape of Renewable Energy Matters</strong></p><p><em>Two projects can have the same MW and the same annual MWh — yet deliver very different value. What happens when we start valuing the shape of the energy, rather than just the quantity?</em></p><blockquote><em>Disclaimer: The views and opinions expressed in this article are my own, based on publicly available information and my professional experience. They are shared to encourage thoughtful discussion and do not represent the views of my employer or any organization with which I am associated. No confidential, proprietary or non-public information has been used in the preparation of this article.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a31413ca9033" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Loyalty Is a Two-Way Street]]></title>
            <link>https://medium.com/@nageshraopmp/loyalty-is-a-two-way-street-a5a1fb82a81f?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5a1fb82a81f</guid>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Sat, 12 Sep 2026 11:36:01 GMT</pubDate>
            <atom:updated>2026-09-12T11:36:01.377Z</atom:updated>
            <content:encoded><![CDATA[<p><em>From the Field — 3 | Connecting the Dots</em> <em>— Personal observations &amp; lessons from working with products, people and organizations</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XiMMllWFNZKxThiwMt0pJA.png" /></figure><p>Loyalty is a word organizations use often.We talk about loyal employees, loyal customers,loyal teams &amp; loyal leaders.</p><p>But somewhere along the way, loyalty has often become something organizations <strong>expect from people</strong>, rather than something both sides build together.</p><p>That made me think:</p><p><strong>Can loyalty really exist as a one-way street?</strong></p><p>I don’t think it can.</p><p><strong><em>Loyalty is a relationship</em></strong>. And like any meaningful relationship, it works both ways.</p><h4><strong>What do organizations expect from people?</strong></h4><p>We expect people to be committed.</p><p>· To take ownership.</p><p>· To stay through difficult times.</p><p>· To do more than what is written in their job description.</p><p>· To put the organization’s interests ahead of their own at times.</p><p>· To stand behind the team when things don’t go according to plan.</p><p>· And sometimes, we expect people to take risks for the organization.</p><p>These expectations aren’t unreasonable.</p><p>Great organizations need people who care deeply about the outcome.</p><p>But there is another question that is less frequently asked:</p><p><strong>What does the organization owe its people in return?</strong></p><h4><strong>Loyalty cannot be demanded</strong></h4><p>A company can ask an employee to be committed.</p><p>It can create policies around retention.</p><p>It can offer incentives.</p><p>It can even create a culture where loyalty is celebrated.</p><p>But none of these can manufacture genuine loyalty.</p><p>Because genuine loyalty is not created by a contract.</p><p>It is created through <strong>trust</strong>.</p><p>People become loyal when they believe:</p><ul><li>their contribution matters;</li><li>their leaders will be fair;</li><li>their voice will be heard;</li><li>their efforts will be recognized;</li><li>mistakes will be treated as opportunities to learn rather than opportunities to assign blame;</li><li>they will get opportunities to grow;</li><li>and when things become difficult, the organization will not abandon them.</li></ul><p>This doesn’t mean an organization has to agree with an employee all the time.</p><p>It doesn’t mean every employee gets every opportunity they want.</p><p>It doesn’t mean difficult decisions should be avoided.</p><p>It means people should believe that the organization will make those decisions <strong>fairly and transparently</strong>.</p><h4><strong>The loyalty equation</strong></h4><p>I sometimes think of loyalty as an unwritten equation:</p><p><strong>What I give ↔ What I receive</strong></p><p>But what we receive isn’t necessarily money.</p><p>It can be:</p><p><strong>Trust ↔ Trust</strong></p><p><strong>Commitment ↔ Commitment</strong></p><p><strong>Ownership ↔ Empowerment</strong></p><p><strong>Accountability ↔ Support</strong></p><p><strong>Performance ↔ Recognition</strong></p><p><strong>Courage ↔ Psychological safety</strong></p><p>When these exchanges remain balanced, loyalty grows.</p><p>When they become one-sided, loyalty eventually becomes transactional.</p><p>And once everything becomes transactional, people start asking a very different question:</p><p><em>“What’s in it for me?”</em></p><h4><strong>Loyalty doesn’t mean agreement</strong></h4><p>There is another misconception about loyalty that I find particularly dangerous.</p><p>We sometimes confuse <strong>loyalty with agreement</strong>.</p><p>The person who always says “yes” is seen as supportive.</p><p>The person who challenges a decision can be perceived as difficult.</p><p>But I would argue the opposite.</p><p>Sometimes the most loyal person in the room is the one who says:</p><p><strong>“I don’t think this is the right decision.”</strong></p><p>A person who cares about the organization should be willing to challenge it.</p><p>A Product Manager should challenge an engineering decision when it doesn’t serve the customer.</p><p>An engineer should challenge a product decision when the technical risk is unacceptable.</p><p>A finance leader should challenge an investment that doesn’t make economic sense.</p><p>A team member should be able to tell a leader:</p><p><em>“We may be heading in the wrong direction.”</em></p><p>That isn’t disloyalty.</p><p><strong>That is ownership.</strong></p><h4><strong>The danger of conditional loyalty</strong></h4><p>There is also another kind of loyalty that organizations should be careful about.</p><p><strong>Conditional loyalty.</strong></p><p>It sounds like:</p><p><em>“I’ll support you as long as you support me.”</em></p><p><em>“I’ll speak up as long as there are no consequences.”</em></p><p><em>“I’ll take ownership as long as someone else doesn’t get the credit.”</em></p><p><em>“I’ll go the extra mile as long as the organization recognizes it.”</em></p><p>When people begin thinking this way, something important has already changed.</p><p>They may still be performing.</p><p>They may still be meeting their targets.</p><p>They may still appear committed.</p><p>But the emotional connection is weakening.</p><p>The organization still has an employee.</p><p>But it may no longer have <strong>commitment</strong>.</p><h4><strong>What leaders do matters more than what leaders say</strong></h4><p>Culture is often described through values written on walls.</p><p>Integrity.</p><p>Respect.</p><p>Trust.</p><p>People first.</p><p>Customer first.</p><p>But employees don’t experience culture through posters.</p><p>They experience it through decisions.</p><p>Who gets credit?</p><p>Who gets blamed?</p><p>Who gets heard?</p><p>Who gets protected?</p><p>Who gets promoted?</p><p>What happens when someone challenges the status quo?</p><p>What happens when a leader makes a mistake?</p><p>What happens when someone delivers difficult news?</p><p>These moments tell people far more about an organization’s values than any presentation can.</p><p><strong>Culture is what happens when the values are tested.</strong></p><p>And loyalty is built in those moments.</p><h4><strong>The leader’s side of the street</strong></h4><p>If we expect loyalty from our teams, perhaps leaders need to ask themselves a few uncomfortable questions.</p><p>Have I created an environment where people can disagree with me?</p><p>Do I give credit where it is due?</p><p>Do I stand behind my people when they make a reasonable mistake?</p><p>Do I protect people from unnecessary organizational politics?</p><p>Do I create opportunities for people to grow?</p><p>Do I recognize contribution — or only outcomes?</p><p>Do I listen to people who bring bad news?</p><p>And perhaps the hardest question:</p><p><strong>Would my team still choose to follow me if they didn’t have to?</strong></p><p>That question says more about leadership than an employee engagement score ever could.</p><h4><strong>Loyalty during difficult times</strong></h4><p>It is easy to talk about loyalty when everything is going well.</p><p>The real test comes when things become difficult.</p><p>A business misses its numbers.</p><p>A product launch fails.</p><p>A project is delayed.</p><p>A customer is unhappy.</p><p>A major decision turns out to be wrong.</p><p>Budgets are cut.</p><p>People are under pressure.</p><p>These are the moments when organizations discover what kind of culture they have actually built.</p><p>Do leaders immediately look for someone to blame?</p><p>Or do they ask:</p><p><strong>“What happened, what did we learn, and how do we fix it together?”</strong></p><p>The second approach doesn’t remove accountability.</p><p>It creates <strong>shared accountability</strong>.</p><p>And there is a significant difference.</p><p>Blame asks:</p><p><em>“Whose fault is this?”</em></p><p>Ownership asks:</p><p><strong>“What are we going to do about it?”</strong></p><p>People remember how leaders behave when things go wrong.</p><p>And those memories shape loyalty far more than what happens when everything is going right.</p><h4><strong>Loyalty is not retention</strong></h4><p>This distinction is important.</p><p>An employee can stay with an organization for ten years and still be disengaged.</p><p>Another person can spend only three years in an organization and leave with enormous respect for it.</p><p>Tenure is not loyalty.</p><p>Loyalty is not measured simply by how long someone stays.</p><p>It is reflected in how much they care about the outcome while they are there.</p><p>A loyal employee doesn’t just work for the organization.</p><p>They <strong>care about what happens to it</strong>.</p><p>They challenge it.</p><p>They protect it.</p><p>They improve it.</p><p>And sometimes, they tell it something it doesn’t want to hear.</p><h4><strong>The customer understands this too</strong></h4><p>The same principle applies beyond employees.</p><p>Think about customer loyalty.</p><p>Companies want customers to remain loyal.</p><p>But customers expect something in return:</p><p>Reliability.</p><p>Quality.</p><p>Fair pricing.</p><p>Responsiveness.</p><p>Transparency.</p><p>Innovation.</p><p>Trust.</p><p>A customer doesn’t become loyal because the company asks them to.</p><p>They become loyal because the company <strong>consistently earns their trust</strong>.</p><p>The same principle applies inside the organization.</p><p>Employees are not fundamentally different from customers in this respect.</p><p><strong>Loyalty is earned through repeated experiences of value and trust.</strong></p><h4><strong>The two-way street</strong></h4><p>Perhaps the simplest way to think about it is this:</p><p>An organization says: <em>“I need you to care about this company.”</em></p><p>The employee says: <em>“Show me that the company cares about people like me.”</em></p><p>……………………………………………………………………………………………</p><p>The organization says: <em>“Take ownership.”</em></p><p>The employee asks: <em>“Will you trust me with the ownership?”</em></p><p>……………………………………………………………………………………………</p><p>The organization says: <em>“Speak up.”</em></p><p>The employee asks: <em>“Will it be safe to disagree?”</em></p><p>…………………………………………………………………………………………..</p><p>The organization says: <em>“Go beyond your role.”</em></p><p>The employee asks: <em>“Will my contribution be recognized?”</em></p><p>These aren’t unreasonable questions.</p><p>They are the other side of the same commitment.</p><h4><strong>Connecting the dots</strong></h4><p>This is perhaps why I believe loyalty is less about <strong>retention</strong> and more about <strong>reciprocity</strong>.</p><p>People don’t need organizations to be perfect.</p><p>They need them to be <strong>fair, trustworthy and human</strong>.</p><p>And organizations don’t need employees who blindly follow.</p><p>They need people who care enough to challenge, contribute and take ownership.</p><p>That creates something much more valuable than obedience.</p><p>It creates commitment.</p><p>And commitment is what allows teams to perform when circumstances are difficult, information is incomplete and the path forward isn’t obvious.</p><p>Just as in Product Management, where no single function can create the product alone, no leader can create a winning organization alone.</p><p>The relationship has to work in both directions.</p><p>Perhaps the simplest leadership principle is also the most overlooked:</p><p><strong>If you want loyalty from your people, start by giving them a reason to be loyal.</strong></p><p>Because ultimately,</p><p><strong>Loyalty is a Two-Way Street.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5a1fb82a81f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Product Manager’s Panchasutra: Five Trade-offs That Shape Winning Products]]></title>
            <link>https://medium.com/@nageshraopmp/the-product-managers-panchasutra-five-trade-offs-that-shape-winning-products-cf9d6232990a?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf9d6232990a</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 11:16:00 GMT</pubDate>
            <atom:updated>2026-09-09T11:16:00.842Z</atom:updated>
            <content:encoded><![CDATA[<p><em>From the Field — 2 | Connecting the Dots</em> <em>— Personal observations &amp; lessons from working with products, people and organizations</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DCh4POBj3PZhu4BosyF3sg.png" /></figure><p>In my previous article, <strong>“</strong><a href="https://medium.com/@nageshraopmp/product-management-the-orchestrator-26bc09a470e3"><strong>Product Management: Orchestrating the Product</strong></a><strong>,”</strong> I used the analogy of an orchestra to describe Product Management.</p><p>A complex product is rarely created by one function.</p><p>Engineering, manufacturing, supply chain, quality, sales, services, finance and many others bring their expertise to the table.</p><p>The Product Manager’s role is to bring these different perspectives together around one product outcome.</p><p>But there is a difficult part that comes next.</p><h4><strong>What happens when everyone is right?</strong></h4><p>Engineering wants better performance.</p><p>Manufacturing wants simplicity.</p><p>Supply Chain wants standardization.</p><p>Sales wants flexibility.</p><p>Services wants maintainability.</p><p>Finance wants lower cost.</p><p>The customer, quite reasonably, wants all of the above.</p><p>There is rarely a perfect answer.</p><p>There are trade-offs.</p><p>And I have come to believe that <strong>t<em>he ability to make the right trade-offs is one of the defining capabilities of Product Management</em>.</strong></p><p>This led me to think of five principles — my <strong><em>Product Manager’s Panchasutra.</em></strong></p><p><em>Sutra</em> is often used to describe a concise principle that captures a larger body of wisdom. These five are not rules.</p><p>They are questions I believe Product Managers should continuously ask.</p><h4><strong>Sutra 1: Performance ↔ Cost</strong></h4><p><strong>Better is not always more valuable.</strong></p><p>One of the easiest traps in product development is assuming that more performance automatically means a better product.</p><p>More output.</p><p>Higher efficiency.</p><p>Greater capability.</p><p>More features.</p><p>Higher specifications.</p><p>From an engineering perspective, these can all look attractive.</p><p>But every improvement has a cost.</p><p>And the customer doesn’t necessarily value every incremental improvement equally.</p><p>Consider a wind turbine. Increasing energy capture may improve annual energy production.</p><p>But what happens if achieving that improvement requires:</p><ul><li>a more expensive component;</li><li>additional structural reinforcement;</li><li>greater transportation complexity;</li><li>higher installation cost;</li><li>additional maintenance requirements?</li></ul><p>At some point, the incremental value delivered to the customer may be less than the incremental cost.</p><p>The Product Manager therefore has to ask a harder question than:</p><p><strong>“Can we make it better?”</strong></p><p>The question is:</p><p><strong>“Is the additional performance worth what we have to pay for it?”</strong></p><p>This is where product thinking differs from pure technology thinking.</p><p><strong>The best product isn’t necessarily the product with the highest specification.</strong></p><p>It is the product that delivers the right value at the right economics.</p><h4><strong>Sutra 2: Customization ↔ Standardization</strong></h4><p><strong>Win the customer without breaking the product.</strong></p><p>Customers are different.</p><p>Different sites.</p><p>Different operating conditions.</p><p>Different regulations.</p><p>Different business models.</p><p>Different expectations.</p><p>Naturally, they want products tailored to their needs.</p><p>Sales teams therefore hear requests for customization all the time.</p><p>And sometimes customization is exactly what creates differentiation.</p><p>But every customization has a consequence.</p><p>More variants can mean:</p><ul><li>more engineering effort;</li><li>more components;</li><li>more suppliers;</li><li>more inventory;</li><li>more manufacturing complexity;</li><li>more service complexity;</li><li>more certification effort.</li></ul><p>What looks like a small customer request can become a significant system-level cost.</p><p>This creates a difficult Product Management decision:</p><p><strong>Where should we customize, and where should we standardize?</strong></p><p>The answer isn’t necessarily “standardize everything.”</p><p>Nor is it “give every customer exactly what they ask for.”</p><p>The real objective is to create <strong>configurable products on a scalable platform</strong>.</p><p>A good product manager therefore asks:</p><p><em>Is this customization creating meaningful customer value — or are we simply creating complexity that the customer isn’t willing to pay for?</em></p><h4><strong>Sutra 3: Speed ↔ Perfection</strong></h4><p><strong>The best product delivered too late can still lose.</strong></p><p>Product teams often fall into one of two traps.</p><p>Move too quickly — and quality suffers.</p><p>Move too cautiously — and the market moves ahead.</p><p>There is always another validation to complete.</p><p>Another feature to improve.</p><p>Another risk to eliminate.</p><p>Another review to conduct.</p><p>Of course, some things cannot be compromised.</p><p>Safety.</p><p>Reliability.</p><p>Regulatory compliance.</p><p>Quality.</p><p>But not every decision has the same consequence.</p><p>The Product Manager therefore has to distinguish between:</p><p><strong>What must be perfect?</strong></p><p>and</p><p><strong>What must simply be good enough to move forward?</strong></p><p>This requires judgement.</p><p>A product that reaches the market six months late may technically be superior to the competitor.</p><p>But the customer may already have signed another contract.</p><p>The market window may have disappeared.</p><p>The technology may have moved on.</p><p>Being first isn’t always the objective.</p><p>But <strong>being late without understanding why can be equally dangerous.</strong></p><p>The Product Manager’s job is therefore not simply to accelerate the organization.</p><p>It is to determine <strong>where speed creates value and where patience protects value.</strong></p><h4><strong>Sutra 4: Today’s Revenue ↔ Tomorrow’s Strategy</strong></h4><p><strong>Not every order is a good order.</strong></p><p>This may be one of the hardest trade-offs in Product Management.</p><p>Revenue is tangible.</p><p>Strategy is often not.</p><p>A customer comes with a large opportunity.</p><p>Sales wants to win it.</p><p>The customer asks for a special configuration.</p><p>The business case looks attractive.</p><p>The temptation is obvious:</p><p><strong>Take the order.</strong></p><p>But what happens if winning that order requires the organization to:</p><ul><li>create a one-off product;</li><li>divert engineering resources;</li><li>create a new supplier ecosystem;</li><li>add manufacturing complexity;</li><li>compromise the product roadmap;</li><li>or move away from the target market?</li></ul><p>The order may generate revenue today while quietly damaging the product strategy for tomorrow.</p><p>This doesn’t mean Product Managers should reject customization or difficult opportunities.</p><p>It means every opportunity needs to be viewed through two lenses:</p><p><strong>What does this order do for us today?</strong></p><p>and</p><p><strong>What does this decision do to our product tomorrow?</strong></p><p>A strong product strategy sometimes requires saying <strong>no to revenue</strong>.</p><p>That can be an uncomfortable conversation.</p><p>But Product Management is not the function that maximizes orders.</p><p><strong>It is the function that maximizes sustainable product value.</strong></p><h4><strong>Sutra 5: Technology Possibility ↔ Customer Value</strong></h4><p><strong>Just because we can build it doesn’t mean we should.</strong></p><p>Technology creates possibilities faster than organizations can absorb them.</p><p>AI.</p><p>Digitalization.</p><p>Advanced materials.</p><p>Automation.</p><p>New architectures.</p><p>New algorithms.</p><p>New features.</p><p>Every technology team can see opportunities that didn’t exist yesterday.</p><p>And that’s exciting.</p><p>But technology itself isn’t the product.</p><p>A technology becomes valuable when it solves a meaningful customer problem or creates a meaningful business advantage.</p><p>This is where Product Management has to play a critical role.</p><p>The question isn’t:</p><p><strong>“Can we build it?”</strong></p><p>The question is:</p><p><strong>“Why should we build it?”</strong></p><p>And perhaps even more importantly:</p><p><strong>“What problem does this solve for the customer?”</strong></p><p>If the answer is unclear, the technology may be impressive — but the product may not be.</p><p>Product Managers therefore need enough technical understanding to recognize possibilities, but enough customer and business understanding to challenge them.</p><p>That balance is critical.</p><h4><strong>The fifth element: Everything is connected</strong></h4><p>The five trade-offs don’t exist independently.</p><p>They interact.</p><p>A performance improvement may increase cost.</p><p>A customization may reduce standardization.</p><p>A desire for perfection may delay the launch.</p><p>A large order may pull the roadmap in a different direction.</p><p>A new technology may increase complexity without creating enough customer value.</p><p>This is why product decisions cannot be made function by function.</p><p>Optimizing one dimension can easily damage another.</p><p>And that brings me back to the orchestra.</p><p>A conductor doesn’t ask:</p><p><em>“How can I make the violins sound better?”</em></p><p>in isolation.</p><p>The question is:</p><p><strong>“How can the entire orchestra create a better performance?”</strong></p><p>The same principle applies to products.</p><h4><strong>The Product Manager as the integrator of trade-offs</strong></h4><p>I increasingly see Product Management as the <strong>integrator of competing realities</strong>.</p><p>Not the person who always chooses the cheapest solution.</p><p>Not the person who always chooses the highest performance.</p><p>Not the person who always chooses the fastest route.</p><p>Not the person who always sides with the customer.</p><p>And not the person who always sides with engineering.</p><p>The Product Manager has to understand the system.</p><p>Because ultimately, the product sits at the intersection of:</p><p><strong>Customer Need × Technology × Cost × Quality × Supply Chain × Manufacturing × Service × Market × Time</strong></p><p>Every decision changes that equation.</p><p>The challenge is not to eliminate the tension.</p><p><strong>The tension is where the product decision lives.</strong></p><h4><strong>So what makes a good Product Manager?</strong></h4><p>Perhaps it isn’t the ability to have all the answers.</p><p>It is the ability to ask the <strong>right questions.</strong></p><p>When engineering asks for more performance: <strong><em>What additional customer value does it create?</em></strong></p><p>When sales asks for customization: <strong><em>Is the value worth the complexity?</em></strong></p><p>When the organization wants to wait for perfection: <strong><em>What is the cost of being late?</em></strong></p><p>When a large customer opportunity appears: <strong><em>Does winning this order strengthen or weaken our strategy?</em></strong></p><p>When a new technology becomes available: <strong><em>What customer problem does it solve?</em></strong></p><p>These questions don’t make Product Management the function that says “no.”</p><p>They make it the function that helps the organization understand <strong>why it should say yes — and why sometimes it shouldn’t.</strong></p><h4><strong>The Panchasutra</strong></h4><p>If I had to reduce the five principles to five questions, they would be:</p><p><strong>1. Performance ↔ Cost</strong><br> <em>Is the additional value worth the additional cost?</em></p><p><strong>2. Customization ↔ Standardization</strong><br> <em>Are we creating customer value or organizational complexity?</em></p><p><strong>3. Speed ↔ Perfection</strong><br> <em>What needs to be perfect, and what needs to be good enough?</em></p><p><strong>4. Today’s Revenue ↔ Tomorrow’s Strategy</strong><br> <em>Are we winning the order — or compromising the product?</em></p><p><strong>5. Technology Possibility ↔ Customer Value</strong><br> <em>Just because we can build it, should we?</em></p><p>These are not formulas.</p><p>They are reminders.</p><p>Because in Product Management, the difficult decisions rarely come down to <strong>right versus wrong</strong>.</p><p>More often, they are: <strong>right versus right.</strong></p><p>And perhaps that is where the real craft of Product Management lies.</p><p><strong>Making the trade-offs that allow the whole orchestra to create something greater than any individual instrument could create alone.</strong></p><h4><strong>Questions I’m Thinking About</strong></h4><ul><li>Which product trade-off is hardest to get right in your organization?</li><li>When functions disagree, who makes the final product-level trade-off?</li><li>How often do we optimize functional metrics at the expense of the overall product?</li><li>Have you ever seen a technically superior product lose because it wasn’t the right product?</li><li>And perhaps the most difficult question: <strong>What should we stop doing to make room for what matters most?</strong></li></ul><p>Because ultimately, a winning product isn’t the one that maximizes every dimension.</p><p><strong>It is the one that makes the right trade-offs.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf9d6232990a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management: The Orchestrator]]></title>
            <link>https://medium.com/@nageshraopmp/product-management-the-orchestrator-26bc09a470e3?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/26bc09a470e3</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Sun, 06 Sep 2026 09:03:26 GMT</pubDate>
            <atom:updated>2026-09-06T09:03:26.842Z</atom:updated>
            <content:encoded><![CDATA[<p><em>From the Field — 1 | Connecting the Dots — Personal observations &amp; lessons from working with products, people and organizations</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wK5C46iyz0AjAl9PPtDZeg.png" /></figure><p>There is something fascinating about watching an orchestra perform.</p><p>Dozens of musicians sit on the stage. Each is highly skilled. Each knows exactly how to play their instrument. Some may have spent decades mastering it.</p><p>Yet, when the performance begins, something changes.</p><p>Nobody is playing independently anymore.</p><p>The sitar, sarod, bansuri, and tabla / drums have to come together at the right moment, at the right intensity and, most importantly, in service of the same piece of music.</p><p>That made me think about the similarities with the role of Product Management.</p><p>Especially in complex, high-capex products, building a successful product requires engineering, manufacturing, supply chain, quality, sales, services, finance, sourcing, certification and many other functions to work together.</p><p>The more I think about it, the more I see <strong>Product Management as the conductor of an orchestra.</strong></p><p>Not because the Product Manager is the most technically skilled person in the room.</p><p>But because someone has to make sure everyone is playing the same piece of music.</p><h4><strong>The orchestra is the organization</strong></h4><p>Consider a complex product organization.</p><p>Engineering is deeply focused on technology, performance, reliability and technical risk.</p><p>Manufacturing is thinking about how to build the product repeatedly, efficiently and at the required quality.</p><p>Supply Chain is concerned with availability, lead times, cost and resilience.</p><p>Sales is listening to customers and markets — and naturally wants to win the next order.</p><p>Services sees what happens to the product after it leaves the factory, is installed and commissioned, and enters operations.</p><p>Finance asks whether the economics work.</p><p>Quality asks whether the product will consistently deliver what we promised.</p><p>Regulatory and certification teams make sure the product can actually operate in the markets where we want to sell it.</p><p>Each function has a legitimate perspective.</p><p>And that is precisely the challenge.</p><p>The problem in Product Management is rarely that people don’t know what to do.</p><p>The problem is that <strong>everyone knows what they need to optimize — and those objectives are not always the same.</strong></p><h4><strong>The Product Manager is not the musician</strong></h4><p>This is where I think the role of Product Management is often misunderstood.</p><p>A Product Manager doesn’t need to be the best engineer in the room.</p><p>They don’t need to know more about composites than the blade expert, more about converters than the electrical engineer, or more about manufacturing than the factory leader.</p><p>It’s not an expectation.</p><p>Those are the musicians.</p><p>The PM’s job is different.</p><p>The PM needs to understand enough of each domain to bring the pieces together and make decisions about the <strong>whole product</strong>.</p><p>The question is not:</p><p>“Who is right?”</p><p>It is:</p><p><strong>“What is right for the product, the customer and the business?”</strong></p><p>That sounds simple.</p><p>In practice, it is incredibly difficult.</p><h4><strong>The composer, the conductor and the musicians</strong></h4><p>There is another interesting distinction in the analogy.</p><p>Leadership is often like the <strong>composer</strong>.</p><p>Leadership establishes the broader ambition:</p><p>Where do we want to go?</p><p>What markets matter?</p><p>What kind of business do we want to build?</p><p>What outcomes are important?</p><p>The Product Manager then becomes the <strong>conductor</strong>.</p><p>The conductor interprets the composition and turns it into a coordinated performance.</p><p>And the functional experts are the <strong>musicians</strong>.</p><p>They bring the depth of expertise required to actually create the product.</p><p>But there is one important difference.</p><p>In an orchestra, the conductor usually has formal authority over the musicians.</p><p>A Product Manager often doesn’t.</p><p>That makes the role considerably harder.</p><h4><strong>Leading without Authority</strong></h4><p>This may be one of the most misunderstood aspects of Product Management.</p><p>The PM often has accountability without direct authority.</p><p>Engineering may not report to the PM.</p><p>Manufacturing doesn’t report to the PM.</p><p>Sales doesn’t report to the PM.</p><p>Services doesn’t report to the PM.</p><p>Finance certainly doesn’t report to the PM.</p><p>Yet the PM is expected to <em>bring all of them together</em> around a product outcome.</p><p>That requires something more powerful than authority.</p><p>It requires <strong>credibility, clarity and influence</strong>.</p><p>A good PM doesn’t walk into an engineering review and say:</p><p><em>“This is what you need to build.”</em></p><p>They walk in with a clear understanding of the customer problem, market opportunity, business case, product strategy and constraints — and ask the engineering team to help determine the best technical answer.</p><p><strong><em>The PM owns the question.</em></strong></p><p>The experts help develop the <strong>answer</strong>.</p><p>And the PM ensures that the answer remains connected to the original purpose.</p><h4><strong>Are we building the right product?</strong></h4><p>This is where Product Management differs from pure engineering or project management.</p><p>Engineering may ask: <strong>Can we build it?</strong></p><p>Manufacturing may ask: <strong>Can we manufacture it?</strong></p><p>Supply Chain may ask: <strong>Can we source it reliably and competitively?</strong></p><p>Finance may ask: <strong>Does the business case work?</strong></p><p>Services may ask: <strong>Can we support it throughout its life?</strong></p><p>Sales may ask: <strong>Will customers buy it?</strong></p><p>The Product Manager has to connect all of these questions and ultimately ask:</p><p><strong><em>Are we building the right product?</em></strong></p><p>And in a high-capex product, “right” is rarely just about technical performance.</p><p>A technically excellent product or solution can still be the wrong product if:</p><ul><li>its cost structure doesn’t support the market;</li><li>its configuration doesn’t create enough customer value;</li><li>its logistics are impractical;</li><li>its installation requirements are too complex;</li><li>its supply chain is fragile;</li><li>its reliability creates an unacceptable service burden;</li><li>its certification doesn’t match the target market;</li><li>or its economics don’t work for the customer.</li></ul><p>The product is not the spec / design sitting on a drawing board.</p><p>The product is the <strong>entire value proposition delivered to the customer</strong>.</p><p>That is why Product Management has to connect the dots.</p><h4><strong>Services is where the orchestra gets its reality check</strong></h4><p>There is another player in this orchestra that I think deserves special attention: <strong>Services</strong>.</p><p>If the customer is the <strong>audience</strong>, Services cannot be the audience.</p><p>Services is closer to the <strong>backstage crew</strong> that keeps the performance going.</p><p>And there is an important reason for this.</p><p>Engineering may believe the product is robust.</p><p>Product Management may believe the value proposition is compelling.</p><p>Sales may have successfully sold it.</p><p>Manufacturing may have built thousands of units.</p><p>But Services sees what happens when the product meets reality.</p><p>They see the failures.</p><p>They see recurring problems.</p><p>They hear customer frustrations.</p><p>They know which components are difficult to replace.</p><p>They know what technicians struggle with in the field.</p><p>They see the difference between what looked good in a business case and what actually happens over ten or twenty years.</p><p>In that sense, Services provides one of the most valuable feedback loops in Product Management.</p><p><strong>The field is the ultimate product test.</strong></p><h4><strong>And the customer?</strong></h4><p>The customer is the <strong>audience</strong>.</p><p>The audience doesn’t care how difficult the rehearsal was.</p><p>They don’t care whether the sitar player had a disagreement with the tabla player.</p><p>They don’t care that the conductor had to resolve three conflicts backstage.</p><p>They care about the experience.</p><p>Did the performance deliver what they expected?</p><p>Was it worth the ticket?</p><p>Would they come back?</p><p>Would they recommend it?</p><p>The same is true of products.</p><p>Customers don’t experience our organizational structure.</p><p>They experience the product.</p><p>They experience its performance, reliability, cost, availability, serviceability and the outcomes it creates.</p><p>That is ultimately what the entire orchestra exists to deliver.</p><h4><strong>What happens when the conductor disappears?</strong></h4><p>Imagine an orchestra without a conductor.</p><p>The musicians are still talented.</p><p>The instruments are still there.</p><p>The sheet music exists.</p><p>But coordination becomes difficult.</p><p>One section may accelerate.</p><p>Another may slow down.</p><p>One instrument may become too loud.</p><p>Another may disappear.</p><p>Individually, everyone may be performing well.</p><p>Collectively, the performance can still fail.</p><p>I have seen similar situations in product organizations.</p><p>Engineering optimizes technology.</p><p>Sales optimizes orders.</p><p>Manufacturing optimizes efficiency.</p><p>Procurement optimizes cost.</p><p>Services optimizes uptime.</p><p>Finance optimizes investment.</p><p>Everyone can achieve their functional objectives — and the product can still lose.</p><p>That is the paradox.</p><p><strong><em>Local optimization can create global failure.</em></strong></p><p>Product Management exists, in large part, to prevent that.</p><h4><strong>The conductor doesn’t play every instrument</strong></h4><p>Perhaps the biggest lesson from the analogy is this:</p><p>A good conductor does not try to become the best sitar player, tabla player or flautist.</p><p>They don’t take the instrument away from the musician.</p><p>They don’t tell how to play the tabla.</p><p>They create the conditions for specialists to perform at their best — and ensure that their individual contributions create something greater together.</p><p>That is what good Product Management should do.</p><p>The PM doesn’t replace functional expertise.</p><p>The PM <strong>connects it</strong>.</p><h4><strong>Connecting the dots</strong></h4><p>Over the years, I have increasingly come to see Product Management less as a function that “owns the product” and more as a function that <strong>creates coherence around the product</strong>.</p><p>The product sits at the intersection of many competing realities:</p><figure><img alt="Product sits at center of competing priorities" src="https://cdn-images-1.medium.com/max/1024/1*SZW_Tqb5I6nEAtYwZYjvGQ.png" /></figure><p><strong><em>Customer need × Technology × Cost × Quality × Supply Chain × Manufacturing × Service × Market × Time</em></strong></p><p>None of these can be optimized independently.</p><p>The Product Manager’s job is to continuously navigate the trade-offs.</p><p>Sometimes that means saying yes to an engineering opportunity.</p><p>Sometimes it means saying no to a technically attractive idea because the customer doesn’t value it.</p><p>Sometimes it means delaying a launch because quality isn’t ready.</p><p>Sometimes it means accepting a technical compromise because the economics demand it.</p><p>And sometimes it means stopping everyone and asking a very uncomfortable question:</p><p><strong>“Are we still solving the problem we originally set out to solve?”</strong></p><p>That, to me, is the essence of Product Management.</p><p>Not being the person who knows the most.</p><p>Not being the person who makes every decision.</p><p>And certainly not being the person who tells every function what to do.</p><p>But being the person who can look across the entire orchestra and say:</p><p><strong>“This is the music we are trying to create. Now, how do we make all these brilliant people play it together?”</strong></p><h4><strong>Questions I’m Thinking About</strong></h4><p>As organizations become increasingly cross-functional and products become more complex, I keep coming back to a few questions:</p><ul><li>Does every organization have a clear “conductor” for its products?</li><li>When functional objectives conflict, who makes the trade-off at the product level?</li><li>Are Product Managers <strong><em>empowered </em></strong>to challenge technically attractive ideas that don’t create customer value?</li><li>Are we listening enough to Services — the people who see the product after the launch?</li><li>And perhaps most importantly: <strong>Are we measuring individual functional performance, or the quality of the music we create together?</strong></li></ul><p>Because ultimately, the customer doesn’t hear the individual instruments.</p><p><strong>They hear the orchestra.</strong></p><blockquote>The views expressed in this article are my own and are based on my professional experiences and observations. They do not represent the views of my employer.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26bc09a470e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CfD: When the Market Starts Pricing Risk]]></title>
            <link>https://medium.com/@nageshraopmp/cfd-when-the-market-starts-pricing-risk-0839ab1c3fc3?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/0839ab1c3fc3</guid>
            <category><![CDATA[india-energy]]></category>
            <category><![CDATA[fdre-auction]]></category>
            <category><![CDATA[clean-energy-transition]]></category>
            <category><![CDATA[renewable-energy]]></category>
            <category><![CDATA[cfd-energy]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 09:21:28 GMT</pubDate>
            <atom:updated>2026-08-29T09:21:28.858Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojxGobDlOn7F4sFhpYwgDA.jpeg" /></figure><p><em>Energy Transition Insights — Part 5</em></p><h4><strong>How India’s emerging CfD mechanism changes the way renewable energy projects participate in the power market</strong></h4><p>One thing that has become increasingly clear to me while following India’s renewable energy market is that the challenges don’t disappear when technology becomes cheaper.</p><p>They change.</p><p>For years, a large part of the industry’s effort was focused on reducing the cost of generating renewable electricity.</p><p>Then the conversation evolved.</p><p>· How accurately can renewable generation be forecast?</p><p>· How reliably can it be delivered?</p><p>· Can renewable power be made firm and dispatchable?</p><p>· Can it be supplied around the clock or during the hours when the grid needs it most?</p><p>Now another question is becoming increasingly important:</p><p><strong>How do we manage the commercial uncertainty around that electricity?</strong></p><p>This is where <strong>Contracts for Difference (CfD)</strong> become interesting.</p><h4><strong>From Generation Risk to Market Risk</strong></h4><p>A renewable energy project has always carried several types of risk.</p><p>There is resource risk : Will the wind blow as expected? Will solar irradiation match the assumptions?</p><p>There is technology risk.: Will the plant perform as expected?</p><p>There is construction and financing risk. And there is operational risk.</p><p>But as renewable energy penetration increases and electricity markets become more important in determining how power is bought and sold, another risk becomes increasingly relevant:</p><p><strong>Market price risk.</strong></p><p>The same renewable project can generate electricity at the same cost, but the value it receives in the market can vary significantly depending on when that electricity is generated.</p><p>A solar project may generate most of its electricity during hours when many other solar projects are also generating.</p><p>A wind project may generate strongly during periods when demand or market prices are relatively low.</p><p>As renewable penetration increases, this mismatch between <strong>when energy is generated</strong> and <strong>when energy is most valuable</strong> can become more important.</p><p>So the challenge is no longer only:</p><p><em>How do we generate renewable energy economically?</em></p><p>It also becomes:</p><p><strong>How do we create sufficient revenue certainty for projects operating in an increasingly market-based environment?</strong></p><h4><strong>A Different Way of Structuring the Contract</strong></h4><p>The traditional long-term PPA provides a relatively straightforward answer.</p><p>The buyer and seller agree on a price.</p><p>The generator gets a degree of revenue visibility.</p><p>The buyer gets a degree of price visibility.</p><p>This model has played an important role in India’s renewable energy growth.</p><p>A CfD takes a different approach.</p><p>Instead of simply agreeing that the buyer will pay a fixed tariff for the electricity, the project can participate in the power market, while a separate settlement mechanism manages the difference between the applicable market/reference price and an agreed <strong>Strike Price</strong>.</p><p>This creates an interesting combination:</p><p><strong>Market participation + price-risk management.</strong></p><p>And this is where the current Indian CfD experiment becomes particularly interesting.</p><h4><strong>India’s First CfD Experiment</strong></h4><p>In 2026, SECI introduced <strong>SECI-CfD-I</strong>, a tender for assured peak supply of <strong>1,000 MWh, corresponding to 500 MW × 2 hours</strong>, from ISTS-connected renewable energy projects. The current RfS is the result of amendments to the original tender, which was initially structured as 500 MW × 3 hours, or 1,500 MWh.</p><p>That change itself is interesting. The market mechanism is being designed and refined while the procurement is underway.</p><p>The current RfS requires the developer, referred to as the RPD in the tender, to participate as a seller in the power exchanges. It can choose among eligible exchanges and market segments such as GDAM, DAM, HPDAM and RTM, subject to the requirements of the RfS and applicable regulations.</p><p>This is quite different from the traditional model where the developer primarily produces electricity and delivers it under a long-term PPA.</p><p>The developer is now being asked to <strong>participate actively in the electricity market.</strong></p><h4><strong>Two Bids, Two Very Different Purposes</strong></h4><p>This was one aspect of the CfD mechanism that I initially found confusing.</p><p>There are effectively <strong>two different bidding activities</strong>.</p><p>The first happens during the procurement process.</p><p>· The developer bids its <strong>Strike Price</strong> as part of the CfD tender.</p><p>· Once the project is selected, that Strike Price becomes part of the contractual framework.</p><p>The second happens during operation.</p><p>· The developer participates in the power market and submits its electricity for sale through the Power Exchange.</p><p>These two bids should not be confused.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*dmNIXM4wOiE8oighvJq3dA.png" /><figcaption>Table 1 — Strke Price Vs Market Clearing Price</figcaption></figure><p>This distinction is important.</p><p>The <strong>Strike Price is not the daily exchange bid</strong>.</p><h4><strong>So How Does the Money Flow?</strong></h4><p>Let’s take a simple illustrative example.</p><p>Suppose a developer wins a CfD tender with:</p><p><strong>Strike Price = ₹5.50/kWh</strong></p><p>And suppose the project has: <strong>100 MW contracted capacity</strong></p><p>The daily assured peak supply requirement would be: <strong>100 MW × 2 hours = 200 MWh/day</strong></p><p>The developer then participates in the Power Exchange.</p><p>For a particular day, it may select two hours within the permitted Peak Hours and offer the required energy into the market.</p><p>Suppose the market clears the electricity at: <strong>₹7.00/kWh</strong></p><p>The developer receives the market revenue through the exchange.</p><p>The CfD settlement is then calculated separately based on the applicable <strong>Reference Rate</strong> and the contracted <strong>Strike Price</strong>, as defined in the CfD Agreement.</p><p>In a simplified illustration:</p><p><strong>Reference Rate = ₹7.00/kWh</strong></p><p><strong>Strike Price = ₹5.50/kWh</strong></p><p>Difference: <strong>₹1.50/kWh</strong></p><p>Because the Reference Rate is above the Strike Price, the settlement moves in the opposite direction to the case where the market/reference price is below the Strike Price.</p><p>Now consider the reverse.</p><p>If the Reference Rate were: <strong>₹4.00/kWh</strong></p><p>while the Strike Price was: <strong>₹5.50/kWh</strong></p><p>the difference would be:<strong>₹1.50/kWh</strong></p><p>and the CfD settlement would move in favour of the developer, subject to the actual settlement provisions.</p><p>The important point is not the ₹1.50. <strong>It is the mechanism.</strong></p><p><strong>The developer participates in the market, while the CfD settlement manages the difference around the agreed Strike Price.</strong></p><p>The above numbers are illustrative and do not represent an actual SECI bid or discovered price.</p><h4><strong>But There Is Still a Physical Commitment</strong></h4><p>It would be easy to look at the market-linked nature of the CfD and conclude that the developer can simply generate electricity and sell whenever it wants.</p><p>That is not the case.</p><p>The current SECI CfD-I RfS has a defined physical obligation.</p><p>For every MW of contracted capacity, the project must supply: <strong>2 MWh per day during the applicable Peak Hours.</strong></p><p>The developer can choose the qualifying time blocks, subject to the RfS. The selected time blocks must add up to two hours and may be consecutive or non-consecutive.</p><p>So for our 100 MW example:</p><p><strong>100 MW × 2 hours = 200 MWh/day </strong>has to be supplied through the specified market mechanism.</p><p>This is an important distinction.</p><p><strong>CfD changes the commercial mechanism.</strong></p><p>It does not remove the physical delivery requirement.</p><h4><strong>The Developer Now Has an Optimization Problem</strong></h4><p>This is perhaps the most interesting part of the mechanism.</p><p>The developer has to solve several problems simultaneously.</p><p><strong>When should I sell?</strong></p><p>The RPD has discretion to select the eligible two hours within the permitted Peak Hours, subject to the provisions of the RfS.</p><p><strong>Where should I sell?</strong></p><p>The RPD can select the appropriate Power Exchange and eligible market segment.</p><p><strong>How should I bid?</strong></p><p>The offered volume needs to clear in the selected market to be eligible for CfD settlement.</p><p><strong>How should I operate the project?</strong></p><p>Wind, solar, storage and other available resources need to be coordinated to meet the delivery requirement.</p><p>The RfS explicitly states that the bidding activity is to be carried out in the best interest of the CfD mechanism, with the objective of maximizing revenue from the sale of energy.</p><p>This is a significant change in the role of the renewable developer.</p><p>The developer is no longer simply a generator operating behind a fixed-price PPA.</p><p>It becomes an <strong>active participant in the power market.</strong></p><h4><strong>From Risk Transfer to Risk Allocation</strong></h4><p>A CfD does not eliminate risk.</p><p>It changes the nature and allocation of risk.</p><p>The developer still has to:</p><ul><li>Forecast generation</li><li>Manage its renewable resources</li><li>Optimize storage</li><li>Select appropriate market windows</li><li>Submit bids</li><li>Ensure that the required energy clears</li><li>Meet the contractual delivery obligation</li></ul><p>The CfD mechanism then provides a settlement framework around the market/reference price and the competitively discovered Strike Price.</p><p>This creates an interesting question:</p><p><strong>Who should carry each type of risk?</strong></p><p>A developer may be well positioned to manage:</p><ul><li>Plant design</li><li>Resource assessment</li><li>Technology selection</li><li>Operational performance</li><li>Energy optimization</li></ul><p>The power market is better positioned to discover:</p><ul><li>Short-term electricity prices</li><li>Demand and supply conditions</li><li>The marginal value of electricity</li></ul><p>A CfD can then help manage a portion of the:</p><ul><li>Long-term price uncertainty</li></ul><p>To me, this is a sign of market maturity.</p><p>A mature market does not necessarily eliminate risk.</p><p>It tries to <strong>allocate each risk to the participant best positioned to manage it.</strong></p><h4><strong>CfD Is Not Just About Price</strong></h4><p>There is another aspect of the current SECI mechanism that I find particularly interesting.</p><p>The RPD can use an Energy Storage System to meet its peak-supply obligation.</p><p>But after fulfilling the daily requirement, the RfS allows <strong>the ESS to be used for other applications, including market operations</strong>, subject to the conditions specified in the tender.</p><p>This means the battery does not necessarily have to remain locked into one application throughout the day.</p><p>The developer can potentially optimize the asset around multiple value streams.</p><p>That is an important development.</p><p>The battery is no longer simply: <strong>“The storage required to meet the contract.”</strong></p><p>It starts becoming: <strong>“An asset that can be optimized around multiple market opportunities, while first meeting its contractual commitment.”</strong></p><p>This observation will become even more interesting when we look at storage economics separately.</p><h4><strong>How This Fits Into the Renewable Energy Journey</strong></h4><p>If we look at the developments discussed in the earlier articles in this series, an interesting pattern emerges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*X6VT4oagnqteeu1OU-cv5A.png" /><figcaption>Table 2 — Market evolution of value of RE</figcaption></figure><p>This is not a replacement of one mechanism by another.</p><p>They address different dimensions of an increasingly complex electricity market.</p><p>The industry is becoming more sophisticated about <strong>what it values, what it requires and what risks it is willing to carry.</strong></p><h4><strong>From LCOE to LCOD — and Beyond</strong></h4><p>This also brings me back to the idea I explored in the first article of this series.</p><p>The traditional LCOE question is:</p><p><strong>What does it cost to generate one unit of electricity?</strong></p><p>The LCOD perspective adds another dimension:</p><p><strong>What does it cost to deliver dependable renewable electricity when it is required?</strong></p><p>CfD introduces yet another dimension:</p><p><strong>How do we manage the market-price risk associated with that delivered electricity?</strong></p><p>These are different questions.</p><p>A project can have an attractive generation cost but poor revenue realization.</p><p>Another project may have a higher generation cost but a better delivery profile.</p><p>Another may have a good delivery profile but significant exposure to market-price volatility.</p><p>The economics of renewable energy are therefore becoming increasingly multidimensional.</p><h4><strong>The Market Is Learning to Price Different Forms of Value</strong></h4><p>There is something I find particularly interesting about the sequence we have been following.</p><p>The market didn’t suddenly jump from LCOE to CfD.</p><p>It has been learning incrementally.</p><p>First, the focus was heavily on lowering the cost of renewable generation.</p><p>Then higher penetration brought greater attention to forecasting and deviation management.</p><p>Then the market started procuring firm and dispatchable renewable power.</p><p>Then different delivery profiles — such as RTC and Peak Power — began to emerge.</p><p>And now we are beginning to experiment with mechanisms that allow renewable projects to participate more directly in electricity markets while managing price risk.</p><p>Each step addresses a different limitation or uncertainty exposed by the previous stage.</p><p>That is how markets evolve.</p><p>Not through one grand design.</p><p>But through successive experiments.</p><h4><strong>What Could This Mean for Developers and OEMs?</strong></h4><p>For developers, the question may no longer be simply:</p><p><em>What is the lowest-cost renewable project I can build?</em></p><p>It could increasingly become:</p><p><strong>What combination of generation, storage, delivery profile and commercial structure creates the best risk-adjusted return?</strong></p><p>For OEMs, the implication is equally interesting.</p><p>The value proposition may move beyond individual components.</p><p>· Wind turbine.</p><p>· Solar module.</p><p>· Battery.</p><p>· Inverter.</p><p>· EMS.</p><p>The real differentiation may increasingly come from how effectively these components are integrated and optimized around a commercial requirement.</p><p>Technology remains important.</p><p>But optimization becomes equally important.</p><h4><strong>Looking Ahead</strong></h4><p>I don’t think CfD will replace PPAs.</p><p>Nor do I think it will immediately become the dominant procurement mechanism for renewable energy in India.</p><p>It is still an emerging mechanism.</p><p>The current SECI CfD-I tender is for <strong>500 MW × 2 hours</strong>, or 1,000 MWh of assured peak supply, and the procurement is still underway. SECI’s tender page currently lists the bid submission deadline as August 28, 2026.</p><p>That makes this an interesting moment to observe.</p><p>We are watching a new market mechanism being tested in real time.</p><p>The eventual outcomes will tell us much more.</p><p>Will developers find the mechanism bankable?</p><p>Will the discovered Strike Prices be competitive?</p><p>How will the CfD settlement behave during periods of high or low market prices?</p><p>Will developers be able to create additional value through better market participation and storage optimization?</p><p>Will the mechanism scale beyond the initial pilot?</p><p>We don’t know the answers yet.</p><p>And perhaps that is precisely why it is worth watching.</p><h4><strong>Reflection</strong></h4><p>Looking at the evolution of India’s renewable energy market, I find it interesting that each new mechanism seems to address a different layer of the problem.</p><p><strong>LCOE</strong> addressed the cost of generation.</p><p><strong>DSM</strong> addressed predictability.</p><p><strong>FDRE</strong> addressed commitment and firmness.</p><p><strong>RTC and Peak Power</strong> addressed the timing and shape of delivery.</p><p><strong>CfD</strong> brings market participation and price-risk allocation into the equation.</p><p>Perhaps this is what market maturity looks like.</p><p>Not the elimination of risk.</p><p>But the increasingly deliberate <strong>allocation of risk to the participant best placed to manage it.</strong></p><p>And perhaps the next stage of the renewable energy journey will not be about finding one perfect procurement mechanism.</p><p>It will be about combining the right generation technology, delivery profile, storage strategy and commercial structure for the problem we are trying to solve.</p><p>The question may no longer be:</p><p><strong>“What is the cheapest renewable energy?”</strong></p><p>It may increasingly become:</p><p><strong>“What is the most economically efficient way to deliver the renewable energy we need, when we need it, while allocating the right risks to the right participants?”</strong></p><p>That is a much more interesting question.</p><p>And one that I believe the Indian electricity market is only beginning to explore.</p><h4><strong>Continue Reading</strong></h4><p><strong>Energy Transition Insights</strong></p><ul><li><a href="https://medium.com/@nageshraopmp/from-lcoe-to-lcod-how-indias-renewable-energy-market-is-redefining-value-4d04f5c3e0c3"><strong>Part 1:</strong> <em>From LCOE to LCOD: How India’s Renewable Energy Market Is Redefining Value</em></a></li><li><a href="https://medium.com/@nageshraopmp/the-2026-dsm-draft-why-mnres-intervention-matters-for-india-s-renewable-future-6dd0b6a9c620"><strong>Part 2:</strong> <em>The 2026 DSM Draft: Why MNRE’s Intervention Matters for India’s Renewable Future</em></a></li><li><a href="https://medium.com/@nageshraopmp/fdre-when-renewable-energy-became-a-commitment-ba6f29ba3db2"><strong>Part 3:</strong> <em>FDRE: When Renewable Energy Became a Commitment</em></a></li><li><a href="https://medium.com/@nageshraopmp/rtc-vs-peak-power-when-renewable-energy-doesnt-have-to-look-the-same-every-hour-386daf5acb13"><strong>Part 4:</strong> <em>RTC vs Peak Power: When Renewable Energy Doesn’t Have to Look the Same Every Hour</em></a></li><li><strong>Part 5:</strong> <em>CfD: When the Market Starts Pricing Risk</em></li></ul><p><em>Disclaimer: The views and opinions expressed in this article are my own, based on publicly available information and my professional experience. They are shared to encourage thoughtful discussion and do not represent the views of my employer or any organization with which I am associated. No confidential, proprietary or non-public information has been used in the preparation of this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0839ab1c3fc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RTC vs Peak Power: When Renewable Energy Doesn’t Have to Look the Same Every Hour]]></title>
            <link>https://medium.com/@nageshraopmp/rtc-vs-peak-power-when-renewable-energy-doesnt-have-to-look-the-same-every-hour-386daf5acb13?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/386daf5acb13</guid>
            <category><![CDATA[renewable-energy]]></category>
            <category><![CDATA[mnre]]></category>
            <category><![CDATA[wind-energy]]></category>
            <category><![CDATA[india]]></category>
            <category><![CDATA[net-zero-energy]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Sun, 23 Aug 2026 07:24:44 GMT</pubDate>
            <atom:updated>2026-09-06T09:34:03.679Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Energy Transition Insights — Part 4</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DVfTNJN8P7-AQ7nGuUx-Rw.png" /></figure><h4><strong><em>Why the shape and timing of renewable power may matter as much as the cost of the power itself</em></strong></h4><p>One thing that has become increasingly interesting to me while following India’s renewable energy procurement is that we are no longer talking about just “renewable power.”</p><p>We are increasingly talking about <strong>when</strong> that power is required.</p><p>· Round-the-Clock (RTC).</p><p>· Firm and Dispatchable Renewable Energy (FDRE).</p><p>· Peak Power.</p><p>These terms can sometimes appear interchangeable.</p><p>I don’t think they are. They represent different answers to different questions from the electricity system. And perhaps that is an important next step in how we think about renewable energy.</p><p><strong>Power Has a Time Dimension</strong></p><p>For a long time, the renewable energy conversation was largely about one number : <strong>₹/kWh. </strong>How cheaply can we generate electricity? That question remains important.</p><p>But as renewable penetration increases, another dimension is becoming increasingly important:</p><h4><strong>When is that kWh available?</strong></h4><p>A unit of solar energy generated at noon is not necessarily equivalent, from the grid’s perspective, to a unit of renewable energy delivered during an evening demand peak.</p><p>Both are renewable.</p><p>Both are measured in kWh.</p><p>But their value to the system may be very different.</p><p>This is perhaps one of the more interesting developments in India’s renewable energy market.</p><p>We are gradually moving from thinking about the <strong>cost of energy</strong> to thinking about the <strong>cost of energy with a particular delivery profile</strong>.</p><h4><strong>RTC: The Commitment Across the Day</strong></h4><p>Round-the-Clock renewable power is an obvious response to this challenge.</p><p>The requirement is no longer simply: <em>“Generate renewable electricity.”</em></p><p>It becomes: <em>“Provide renewable electricity across the required hours, with an agreed level of firmness.”</em></p><p>That changes the design of the project.</p><p>· Wind alone may not be sufficient.</p><p>· Solar alone may not be sufficient.</p><p>· Adding storage can bridge some of the gaps, but the amount and duration of storage become important economic decisions.</p><p>The developer therefore has to think beyond the generation asset.</p><p>The project becomes an integrated system involving:</p><ul><li>Wind</li><li>Solar</li><li>Energy storage</li><li>Forecasting</li><li>Energy management</li><li>Scheduling</li><li>Grid connectivity</li><li>Commercial optimization</li></ul><p>The question is no longer simply how much energy the project can generate.</p><p>It is whether the combination of resources can <strong>reliably meet the required delivery profile at an acceptable cost.</strong></p><p>SECI’s current procurement activity illustrates how this requirement has evolved. In March 2026, SECI issued an RfS for <strong>1,000 MW of Firm and Dispatchable Renewable Energy Round-the-Clock power</strong> from ISTS-connected renewable projects.</p><p>That is quite different from procuring a standalone wind or solar project. The buyer is specifying an outcome.</p><h4><strong>Peak Power: A Different Question</strong></h4><p>Now consider a different requirement.</p><p>What if the system does not need the same level of renewable power throughout the day?</p><p>What if the real challenge is concentrated in a few critical hours?</p><p>This is where <strong>Peak Power</strong> becomes interesting.</p><p>Instead of asking : <em>Can you supply renewable power around the clock?</em></p><p>the question becomes: <strong>Can you reliably supply renewable power when the system needs it most?</strong></p><p>That is a fundamentally different requirement.</p><p>And it may lead to a fundamentally different project design.</p><p>For example, SECI’s 2026 FDRE-IX procurement seeks assured peak supply of <strong>1,500 MW for four hours</strong>, equivalent to 6,000 MWh.</p><p>· That is not the same product as 24-hour RTC supply.</p><p>· The procurement is focused on a specific delivery window.</p><p>· The project can therefore be optimized around that requirement.</p><p>· Storage duration may be different.</p><p>· The wind-solar mix may be different.</p><p>· Oversizing may be different.</p><p>· The economics may be different.</p><p>· And ultimately, the cost of the delivered kWh may be different.</p><h4><strong>RTC and Peak Power Are Not Competing Products</strong></h4><p>I think this distinction is important.</p><p>It is tempting to ask: <strong>Which is better — RTC or Peak Power?</strong></p><p>I don’t think that is the right question.</p><p>The better question is: <strong>What problem is the customer trying to solve?</strong></p><p>Consider a simple analogy.</p><p>If I need a vehicle to travel 500 kilometres every day, I need one type of solution.</p><p>If I need a vehicle primarily for carrying a heavy load for two hours every day, I may need something quite different.</p><p>Both are vehicles.</p><p>But optimizing one against the other only makes sense if the underlying requirement is the same.</p><p>Renewable energy is beginning to face a similar situation.</p><h4><strong>The Renewable Offering Is Becoming More Granular</strong></h4><p>This is where I think the market is becoming particularly interesting.</p><p>We started with relatively simple products.</p><p><strong>Wind — </strong>Generate when the wind is available.</p><p><strong>Solar -</strong>Generate when sunlight is available.</p><p>Then came:</p><p><strong>Hybrid — </strong>Combine complementary renewable resources.</p><p>Then:</p><p><strong>FDRE — </strong>Combine resources and storage to meet a committed delivery profile.</p><p>And now:</p><p><strong>RTC and Peak Power — </strong>Specify the delivery requirement more precisely.</p><p>The evolution is not simply about adding more technology.</p><p>It is about becoming more precise about <strong><em>what the customer actually needs.</em></strong></p><p><strong>A Simple Way to Look at It</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ed1sIF__lbntoK2pqvRArg.png" /><figcaption>Table 1 — RTC Vs Peak Power</figcaption></figure><p>Neither is inherently better.</p><p>They are different products because they solve different problems.</p><h4><strong>This Is Where Solution Design Gets Interesting</strong></h4><p>One principle I have learned through my years in product development is that a good product does not maximize every specification.</p><p>It optimizes for the <strong>customer’s actual requirement</strong>.</p><p>If a customer needs four hours of dependable power, designing a system for 24-hour delivery may technically provide a better product. But it may not provide a better economic solution.</p><p>The same principle applies to renewable energy.</p><p>If the grid’s critical requirement is concentrated in a few hours, it may not make economic sense to build every project as an RTC project. On the other hand, if the customer needs dependable power throughout the day, a peak-only solution may not address the requirement.</p><p>The optimum solution therefore depends on the <strong>shape of the demand.</strong></p><p>That, in my view, is an important shift in thinking.</p><h4><strong>The Economics of the Delivery Profile</strong></h4><p>This also changes how we should look at tariffs.</p><p>Two projects may both quote a ₹/kWh number.</p><p>But the kWh may not have the same value.</p><p>A low-cost kWh available when the grid has surplus renewable generation may have a very different system value from a higher-cost kWh delivered during a critical demand period.</p><p>This does not mean that every peak kWh is automatically worth more.</p><p>It means that <strong>timing has economic value.</strong></p><p>And once timing has value, project optimization becomes much more interesting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NptDBfGyBvSHQ763-_vdUQ.png" /><figcaption>Table 2 — RTC requirements evolving overtime</figcaption></figure><p>The question becomes:</p><p>What is the least-cost way of delivering the required energy profile?</p><p>That could involve:</p><ul><li>More wind</li><li>More solar</li><li>More storage</li><li>Longer-duration storage</li><li>Renewable overbuilding</li><li>Curtailment</li><li>Better forecasting</li><li>Better dispatch optimization</li><li>Or some combination of all of these</li></ul><p>There is no single answer.</p><p>The optimum depends on the requirement.</p><h4><strong>The Market Is Already Differentiating the Solution</strong></h4><p>What I find particularly interesting is that this is no longer only a theoretical discussion.</p><p>SECI’s 2026 procurement pipeline includes both <strong>1,000 MW of FDRE-RTC power</strong> and separate procurement for <strong>assured peak supply</strong>.</p><p>There is also a separate CfD procurement for assured peak supply, illustrating that the market is increasingly experimenting with different combinations of delivery requirements and commercial structures.</p><p>To me, this is an important signal.</p><p>The market is beginning to differentiate between:</p><p><strong>renewable energy generation</strong></p><p>and</p><p><strong>renewable energy delivered in the shape that the system needs.</strong></p><p>That is a significant evolution.</p><h4><strong>What Happens to LCOE?</strong></h4><p>This brings me back to the idea I explored in the first article of this series.</p><p>LCOE remains an important metric.</p><p>But if the customer is buying a specific delivery profile, perhaps we also need to ask:</p><p><strong>What does it cost to create that delivery profile?</strong></p><p>The question is no longer simply:</p><p>What does one renewable kWh cost?</p><p>It becomes:</p><p><strong>What does one dependable kWh cost when delivered at the time and duration required?</strong></p><p>This is where the concept of <strong>LCOD — Levelized Cost of Dispatchable Energy</strong> — becomes useful as a way of thinking about the problem.</p><p>Not as a replacement for LCOE.</p><p>But as a complementary perspective.</p><p><strong>One Interesting Question</strong></p><p>If RTC and Peak Power are different customer requirements, should we really compare them simply on ₹/kWh?</p><p>Perhaps not.</p><p>A more useful comparison may be to look at the <strong>cost of meeting the required power profile</strong>.</p><p>Imagine having the same wind and solar resources available.</p><p>Now change only the requirement:</p><p><strong>Scenario A:</strong> Deliver power around the clock.</p><p><strong>Scenario B:</strong> Deliver power for four critical hours.</p><p>Would the optimum wind-solar-storage configuration remain the same?</p><p>Probably not.</p><p>How much storage would each require?</p><p>How much renewable overbuilding?</p><p>How much curtailment?</p><p>What happens to project returns?</p><p>And ultimately:</p><p><strong>What happens to the cost of the delivered kWh?</strong></p><p>These are not questions that can be answered by looking at the tariff alone.</p><p>They require us to look at the complete system.</p><h4><strong>Looking Ahead</strong></h4><p>I believe this is where renewable energy product development is heading.</p><p>Not towards one universal configuration.</p><p>But towards <strong>solutions designed around specific requirements.</strong></p><p>Wind will continue to have a role.</p><p>Solar will continue to have a role.</p><p>Storage will continue to evolve.</p><p>But the winning combination may increasingly depend on what the customer is actually asking the project to deliver.</p><p>RTC.</p><p>Peak Power.</p><p>FDRE.</p><p>Perhaps eventually more granular products based on specific demand shapes.</p><p>The technology is only one part of the equation.</p><p>The more interesting question is:</p><p><strong>What problem are we actually trying to solve?</strong></p><h4><strong>Reflection</strong></h4><p>For many years, the renewable energy industry focused on producing electricity more efficiently and at lower cost.</p><p>I believe the next phase will be about producing <strong>the right electricity at the right time and at the right cost.</strong></p><p>That does not make the earlier journey less important.</p><p>It simply means the definition of value is becoming more granular.</p><p>A renewable kWh is not becoming more valuable simply because it is renewable.</p><p>Its value increasingly depends on <strong>when, where and how reliably it can be delivered.</strong></p><p>Perhaps that is the next step in the journey from LCOE to LCOD.</p><p>Not just asking:</p><p><strong>“How much does renewable energy cost?”</strong></p><p>But asking:</p><p><strong>“How much does it cost to deliver the renewable energy the grid actually needs?”</strong></p><p>That is a question I intend to explore further as I build and use some of the optimization and financial models behind these projects.</p><h4><strong>Continue Reading</strong></h4><p><strong>Energy Transition Insights</strong></p><ul><li><a href="https://medium.com/@nageshraopmp/from-lcoe-to-lcod-how-indias-renewable-energy-market-is-redefining-value-4d04f5c3e0c3"><strong>Part 1:</strong> <em>From LCOE to LCOD: How India’s Renewable Energy Market Is Redefining Value</em></a></li><li><a href="https://medium.com/@nageshraopmp/the-2026-dsm-draft-why-mnres-intervention-matters-for-india-s-renewable-future-6dd0b6a9c620"><strong>Part 2:</strong> <em>The 2026 DSM Draft: Why MNRE’s Intervention Matters for India’s Renewable Future</em></a></li><li><a href="https://medium.com/@nageshraopmp/fdre-when-renewable-energy-became-a-commitment-ba6f29ba3db2"><strong>Part 3:</strong> <em>FDRE: When Renewable Energy Became a Commitment</em></a></li><li><strong>Part 4:</strong> <em>RTC vs Peak Power: When Renewable Energy Doesn’t Have to Look the Same Every Hour</em></li></ul><p><strong>Coming Next:</strong> <em>Contracts for Difference: When the Market Starts Pricing Risk</em></p><p><em>Disclaimer: The views and opinions expressed in this article are my own, based on publicly available information and my professional experience. They are shared to encourage thoughtful discussion and do not represent the views of my employer or any organization with which I am associated. No confidential, proprietary or non-public information has been used in the preparation of this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=386daf5acb13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FDRE: When Renewable Energy Became a Commitment]]></title>
            <link>https://medium.com/@nageshraopmp/fdre-when-renewable-energy-became-a-commitment-ba6f29ba3db2?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba6f29ba3db2</guid>
            <category><![CDATA[renewable-energy]]></category>
            <category><![CDATA[hybrid]]></category>
            <category><![CDATA[clean-energy]]></category>
            <category><![CDATA[solar]]></category>
            <category><![CDATA[wind]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Sat, 08 Aug 2026 15:29:27 GMT</pubDate>
            <atom:updated>2026-09-06T09:37:47.350Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Energy Transition Insights — Part 3</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5WuM4_CbA3yg-dhbTCu_uw.png" /></figure><h4><strong><em>What the evolution of FDRE auctions tells us about how India’s renewable energy market is learning</em></strong></h4><p>When the first Firm and Dispatchable Renewable Energy (FDRE) tenders were introduced, much of the discussion naturally revolved around technology.</p><p>·<em> What should be the optimum wind-solar mix?</em></p><p><em>· How much battery storage is required?</em></p><p><em>· Which battery chemistry is most suitable?</em></p><p><em>· How should the Energy Management System (EMS) be configured?</em></p><p>These are all important questions.</p><p>Yet, as I followed successive FDRE auctions over the last few years, I found myself thinking about something different.</p><p>Rather than asking <strong>“What is FDRE?”</strong>, I started asking <strong>“What are these auctions teaching us?”</strong></p><p>Looking back today, I believe the evolution of FDRE tells a much bigger story than the evolution of another procurement model.</p><p><strong><em>It tells the story of a market that is learning.</em></strong></p><h4><strong>Every Auction is an Experiment</strong></h4><p>One aspect I have always appreciated about engineering is that very few successful products emerge perfectly in their first iteration.</p><p><strong><em>We build &gt; We test &gt; We learn &gt; We improve.</em></strong></p><p>Markets evolve in much the same way. Looking at successive FDRE tenders, I don’t see a collection of procurement documents. I see a series of experiments.</p><p>Every auction appears to have tested a slightly different hypothesis.</p><p><em>· Can renewable energy reliably meet firm delivery obligations?</em></p><p><em>· How much flexibility should developers have?</em></p><p><em>· What level of storage is commercially optimal?</em></p><p><em>· How should scheduling and performance be evaluated?</em></p><p><em>· Where should risks be allocated between the procurer and the developer?</em></p><p>Every completed project generated operational experience.</p><p>Every stakeholder consultation improved understanding.</p><p>Every revised tender appears to have incorporated lessons from the previous one.</p><p>Perhaps this is exactly how new markets mature — not by getting everything right the first time, but by learning through successive iterations.</p><p><strong>Figure 1 — The Evolution of FDRE Procurement</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*dNPlyPeFa7jNSUhj-vVcIw.png" /><figcaption><em>Illustrative evolution based on observations from successive public procurements.</em></figcaption></figure><h4><strong>The Premium That Changed the Conversation</strong></h4><p>One aspect of FDRE that I find particularly interesting is that it challenged one of the industry’s long-held assumptions.</p><p>For years, renewable energy success was largely associated with achieving the lowest possible tariff.</p><p>That objective served the industry exceptionally well.</p><p>Standalone wind and solar projects became increasingly competitive, helping renewable energy become one of the most affordable sources of new electricity generation.</p><p>Then something interesting happened.</p><p>Buyers started procuring FDRE projects at tariffs that were generally higher than standalone wind or solar projects.</p><p>At first glance, this appears counterintuitive.</p><p>Why would buyers willingly pay more?</p><p>I believe the answer lies in understanding <strong>what is actually being purchased.</strong></p><p>· A standalone wind project primarily sells wind generation.</p><p>· A standalone solar project sells solar generation.</p><p>· A battery provides operational flexibility.</p><p>· An FDRE project sells something different.</p><p><strong><em>It sells confidence.</em></strong></p><p>Confidence that renewable electricity will be available when committed.</p><p>Viewed from that perspective, the higher tariff is not merely paying for additional equipment.</p><p>It reflects the<strong><em> market assigning economic value to reducing uncertainty.</em></strong></p><p>To me, this is one of the strongest commercial signals that India’s renewable energy market is evolving.</p><p>The discussion is no longer only about generating renewable electricity at the lowest possible cost.</p><p>It is increasingly about delivering renewable electricity with greater confidence.</p><p><strong>Figure 2 — How the Definition of Value is Changing</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*ecOE_KWWkQVx9jkOURM-yg.png" /><figcaption>Emergence of dependable renewable energy</figcaption></figure><h4><strong>Technology Was the Enabler, Not the Destination</strong></h4><p>Battery Energy Storage Systems undoubtedly played an important role in enabling FDRE.</p><p>So did advances in forecasting, digital control systems, hybrid plant optimization and Energy Management Systems.</p><p>However, I believe it is important not to confuse the enabler with the outcome.</p><p>Technology enabled FDRE while market created the need for it. <em>That distinction matters.</em></p><p>Technology answers <strong>how; </strong>Markets determine <strong>why</strong>.</p><p>The renewable energy industry already possessed many of the technical building blocks.</p><p>What changed was the expectation of the buyer.</p><p>The conversation gradually shifted from</p><p><em>“Can you generate renewable electricity?”</em></p><p>to</p><p><em>“Can you reliably deliver renewable electricity when you promised?”</em></p><p>That seemingly small change influences almost every engineering, commercial and financial decision that follows.</p><p>· Storage sizing changes.</p><p>· Forecasting becomes more important.</p><p>· Plant optimization changes.</p><p>· Commercial structures evolve.</p><p>Success is no longer measured solely by the amount of energy generated.</p><p>Increasingly, it is also measured by the<strong><em> ability to honour a commitment.</em></strong></p><h4><strong>What the Evolution of FDRE RFQs Tells Us</strong></h4><p>While every procurement has its own objectives and commercial structure, I find it interesting to observe how the philosophy behind FDRE tenders has matured over successive auctions.</p><p>The focus has gradually moved beyond proving technical feasibility towards improving commercial practicality.</p><p>Delivery obligations have become better understood.</p><p>Scheduling philosophies have evolved.</p><p>Performance evaluation has been refined.</p><p>Developers, procurers, OEMs and system operators have all contributed to this learning process.</p><p>Looking back, I don’t think these changes happened because the original tenders were flawed. They happened because every auction generated experience that made the next auction better.</p><p>That is exactly how engineering improves. That is how products evolve. And perhaps, that is how markets evolve too.</p><h4><strong>Looking Ahead</strong></h4><p>Looking back today, I no longer see FDRE as simply another procurement category.</p><p>I see it as an important milestone in India’s renewable energy journey.</p><p>DSM strengthened forecasting discipline &gt; FDRE introduced delivery commitment &gt; Round-the-Clock (RTC) procurement extended the emphasis on availability. Emerging commercial mechanisms such as Contracts for Difference (CfD) seek to provide greater commercial certainty.</p><p>Viewed individually, each solves a different problem.</p><p>Viewed together, they suggest that the renewable energy market is gradually redefining what it values.</p><h4><strong>Reflection</strong></h4><p>One of the themes I explored in my previous article was the transition from <a href="https://medium.com/@nageshraopmp/from-lcoe-to-lcod-how-indias-renewable-energy-market-is-redefining-value-4d04f5c3e0c3?sharedUserId=nageshraopmp"><strong>LCOE (Levelized Cost of Energy)</strong> to what I described as <strong>LCOD (Levelized Cost of Dispatchable Energy)</strong></a> — the idea that the market is beginning to value not only the cost of generating renewable electricity, but also the ability to deliver it when required.</p><p>Looking at the evolution of FDRE, I feel that this transition is no longer just conceptual.</p><p>The willingness of buyers to procure dependable renewable power at a premium over standalone generation suggests that<strong><em> dispatchability itself is beginning to acquire economic value.</em></strong></p><p>Perhaps that is the real significance of FDRE.</p><p>It is not simply another tender category.</p><p>It is evidence that the renewable energy market is learning.</p><p>Learning what can realistically be delivered.</p><p>Learning how technology should be deployed.</p><p>Learning how commercial structures influence behaviour.</p><p>Most importantly, learning that the value of renewable energy is no longer defined only by the cost of generating a kilowatt-hour.</p><p>Increasingly, it is also defined by the confidence with which that kilowatt-hour can be delivered.</p><p>I would be interested to hear your thoughts.</p><p>Do you see FDRE as another procurement mechanism, or as a sign that the market is gradually redefining the value of renewable energy?</p><blockquote><strong><em>Continue Reading | Energy Transition Insights</em></strong></blockquote><blockquote><a href="https://medium.com/@nageshraopmp/from-lcoe-to-lcod-how-indias-renewable-energy-market-is-redefining-value-4d04f5c3e0c3?sharedUserId=nageshraopmp"><strong>Part 1:</strong> <em>From LCOE to LCOD: How India’s Renewable Energy Market Is Redefining Value</em></a></blockquote><blockquote><a href="https://medium.com/@nageshraopmp/the-2026-dsm-draft-why-mnres-intervention-matters-for-india-s-renewable-future-6dd0b6a9c620"><strong>Part 2:</strong> <em>The 2026 DSM Draft: Why MNRE’s Intervention Matters for India’s Renewable Future</em></a></blockquote><blockquote><strong>Part 3:</strong> <em>FDRE: When Renewable Energy Became a Commitment</em></blockquote><blockquote>Disclaimer: The views and opinions expressed in this article are my own, based on publicly available information and my professional experience. They are shared to encourage thoughtful discussion and do not represent the views of my employer or any organization with which I am associated. No confidential, proprietary or non-public information has been used in the preparation of this article.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba6f29ba3db2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From LCOE to LCOD: How India’s Renewable Energy Market Is Redefining Value]]></title>
            <link>https://medium.com/@nageshraopmp/from-lcoe-to-lcod-how-indias-renewable-energy-market-is-redefining-value-4d04f5c3e0c3?source=rss-fee4016baf70------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d04f5c3e0c3</guid>
            <category><![CDATA[energy-transition]]></category>
            <category><![CDATA[renewable-energy]]></category>
            <category><![CDATA[fdre]]></category>
            <category><![CDATA[india]]></category>
            <category><![CDATA[wind]]></category>
            <dc:creator><![CDATA[NAGESH P]]></dc:creator>
            <pubDate>Sun, 26 Jul 2026 07:30:09 GMT</pubDate>
            <atom:updated>2026-10-11T13:50:56.894Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Energy Transition Insights — Part 1</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zW6-W4iwcN_T7e-l-GFKTg.png" /></figure><p>Over the past decade, India’s renewable energy sector has achieved something remarkable.</p><p>Wind and solar have moved from being alternative sources of power to becoming an integral part of India’s energy mix. Technology has improved, tariffs have fallen dramatically, and renewable energy is now one of the most competitive sources of new electricity generation.</p><p>For much of this journey, one metric quietly influenced almost every decision — <strong>Levelized Cost of Energy (LCOE).</strong></p><p>Whether it was selecting turbine ratings, optimizing solar layouts, improving plant performance or bidding in competitive auctions, the objective was straightforward: generate renewable electricity at the lowest possible cost.</p><p>Looking back, I believe that was exactly the right objective.</p><p>Without the relentless focus on reducing LCOE, renewable energy would not have reached the scale or affordability that we see today.</p><p>So this article is not about questioning LCOE.</p><p>It is about asking whether the market is now <strong>beginning to value something more ?</strong></p><h3>When Success Creates the Next Challenge</h3><p>One thing I have noticed over my one and half decades in the renewable energy industry is that markets rarely change because someone decides they should.</p><p>They change because <em>yesterday’s success creates tomorrow’s challenge</em>. The success of renewable energy is a good example.</p><p>As renewable penetration increases, the grid begins to ask different questions. Generating electricity at the lowest cost is still important. <em>But increasingly, so is </em><strong><em>when </em></strong><em>that electricity is available.</em></p><p>Electricity is unlike most products. It has to be generated and consumed almost at the same time. While storage technologies are changing this reality, the grid still values predictability, flexibility and reliability alongside low-cost generation.</p><p>Perhaps this is simply the natural evolution of a maturing renewable energy market.</p><h3>Connecting the Dots</h3><p>Over the last few years, I have found myself following a series of developments that are often discussed independently.</p><p>· The evolution of DSM regulations.</p><p>· Hybrid renewable projects.</p><p>· Firm and Dispatchable Renewable Energy (FDRE) tenders.</p><p>· Round-the-Clock (RTC) procurement.</p><p>· Peak Power tenders.</p><p>· Battery Energy Storage Systems.</p><p>· More recently, Contracts for Difference (CfD).</p><p>Initially, I looked at each of these as separate developments.</p><p>Over time, however, I started wondering if they were all responding to the same underlying change.</p><p>· Not a technology change.</p><p>· Not a policy change.</p><p>· <strong>A market change.</strong></p><p>Viewed individually, each initiative solves a specific problem.</p><p>· DSM encourages better forecasting and schedule discipline.</p><p>· Hybrid projects improve generation profiles by combining complementary resources.</p><p>· FDRE rewards the ability to deliver committed power instead of simply installing renewable capacity.</p><p>· RTC and Peak Power tenders recognize that electricity has different value at different times of the day.</p><p>· Battery storage introduces flexibility that renewable generation alone cannot always provide.</p><p>· CfD seeks to reduce commercial uncertainty in an evolving electricity market.</p><p>The more I looked at these developments together, <em>the more they appeared to be chapters of the same story.</em></p><p>The market is gradually moving beyond asking,</p><p><em>“How much renewable energy can you generate at low costs?”</em></p><p>It is beginning to ask,</p><p><em>“How reliably can you deliver renewable energy when it is needed?”</em></p><p>One of the things I have learned over the years is that markets rarely announce when they are changing. The signals are usually subtle — a new regulation here, a different procurement model there, changing customer expectations, or a technology that suddenly becomes commercially viable.</p><p>Individually, these developments may appear unrelated. Collectively, they often signal that the market is entering a new phase.</p><p>Looking at India’s renewable energy sector today, I can’t help but feel we are witnessing one of those moments.</p><h3>If Value Is Changing, Should Our Metrics Change Too?</h3><p>This made me think about the role of LCOE itself.</p><p>LCOE has served the industry remarkably well. It has helped developers, investors and policymakers compare technologies, improve efficiencies and drive down the cost of renewable electricity.</p><p>But LCOE answers one specific question.</p><p><strong>What does it cost to generate one unit of electricity over the life of a project?</strong></p><p>As renewable penetration increases, perhaps another question is becoming equally relevant.</p><p><strong>What does it cost to reliably deliver that unit of electricity when the grid actually needs it?</strong></p><p>The two questions are related.</p><p>But they are not identical.</p><p>A project optimized purely for the lowest LCOE may not necessarily deliver the lowest overall system cost once factors such as forecasting uncertainty, storage, curtailment, scheduling obligations and dispatch requirements are taken into account.</p><p>This is where I find it useful to think beyond LCOE. Not because LCOE has become less important. Far from it. Rather, because <strong>dispatchability</strong> itself appears to be acquiring economic value.</p><p>To help myself think about this transition, I have started referring to this broader perspective as the <strong>Levelized Cost of Dispatchable Energy (LCOD).</strong></p><p>I don’t present LCOD as an established industry metric or as a replacement for LCOE. I simply find it a useful way of thinking about how renewable project economics may evolve as renewable energy becomes a much larger part of the electricity system.</p><h3>Looking Ahead</h3><p>Perhaps the transition from LCOE to LCOD is not really about replacing one metric with another.</p><p>Perhaps it reflects something more fundamental.</p><p>As renewable energy becomes the backbone of the electricity system, the definition of value itself is evolving.</p><p>Generating affordable renewable electricity will always remain essential.</p><p>Increasingly, the ability to deliver that electricity predictably, reliably and when it is needed may become just as important.</p><p>Whether LCOD ultimately becomes an accepted industry metric is, in some ways, secondary.</p><p>The more interesting question is this:</p><p><strong>How should we evaluate renewable energy projects in a world where dispatchability itself has value?</strong></p><p>That is a question I intend to explore over the next few articles as I look at FDRE, RTC procurement, Peak Power tenders, CfD and the role of energy storage in shaping the next phase of India’s renewable energy journey.</p><p>I’d love to hear your thoughts.</p><p>Do you think the market is gradually moving beyond LCOE, or do you believe LCOE alone will continue to remain the primary measure of value?</p><blockquote><em>This article is the first in my </em><strong><em>Energy Transition Insights</em></strong><em> series, where I explore how technology, regulation, product strategy and market design are shaping the future of renewable energy.</em></blockquote><blockquote><em>Links to other articles under this series :</em></blockquote><blockquote><a href="https://medium.com/@nageshraopmp/the-2026-dsm-draft-why-mnres-intervention-matters-for-india-s-renewable-future-6dd0b6a9c620">DSM : How accurately can we predict and schedule it?</a></blockquote><blockquote><a href="https://medium.com/@nageshraopmp/fdre-when-renewable-energy-became-a-commitment-ba6f29ba3db2">FDRE : Can we commit to delivering renewable energy?</a></blockquote><blockquote><a href="https://medium.com/@nageshraopmp/rtc-vs-peak-power-when-renewable-energy-doesnt-have-to-look-the-same-every-hour-386daf5acb13">RTC / Peak Power :When do we need that delivery?</a></blockquote><blockquote><a href="https://medium.com/@nageshraopmp/cfd-when-the-market-starts-pricing-risk-0839ab1c3fc3">CfD : How do we participate in the market while managing price risk?</a></blockquote><blockquote><a href="https://medium.com/@nageshraopmp/storage-from-an-energy-asset-to-a-flexibility-asset-a31413ca9033">Storage : How do we move and optimise electricity through time?</a></blockquote><blockquote><strong><em>Disclaimer:</em></strong><em> The views and opinions expressed in this article are my own, based on publicly available information and my professional experience. They are shared for discussion and do not represent the views of my employer or any organization with which I am associated. No confidential, proprietary or non-public information has been used in the preparation of this article.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d04f5c3e0c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>