<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									How do you kept the project moving forward despite roadblocks? - Program Management				            </title>
            <link>https://nikhildesh.com/community/program-management/how-do-you-kept-the-project-moving-forward-despite-roadblocks/</link>
            <description>nikhildesh.com Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 07 Jun 2026 23:19:48 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>How do you kept the project moving forward despite roadblocks?</title>
                        <link>https://nikhildesh.com/community/program-management/how-do-you-kept-the-project-moving-forward-despite-roadblocks/#post-51</link>
                        <pubDate>Thu, 04 Sep 2025 10:27:00 +0000</pubDate>
                        <description><![CDATA[When roadblocks hit, I start by diagnosing the root cause: whether it is

Resource bottlenecks
Misaligned stakeholders
Technical constraints

Sample Answer - In one digital migration p...]]></description>
                        <content:encoded><![CDATA[<p>When roadblocks hit, I start by diagnosing the <strong>root cause:</strong> whether it is</p>
<ol>
<li>Resource bottlenecks</li>
<li>Misaligned stakeholders</li>
<li>Technical constraints</li>
</ol>
<p>Sample Answer - <br />In one digital migration project, a key vendor missed a milestone due to integration issues. Rather than escalate prematurely, I convened a rapid triage session with both internal and external teams.</p>
<p>We re-mapped the dependencies, created a workaround using interim APIs, and adjusted the delivery sequence to keep downstream tasks on track.<br />I also kept leadership informed through impact dashboards and scenario planning, so decisions could be made with clarity.</p>
<p>The project didn’t just survive the roadblock—it gained trust and agility.</p>
<p><br /><strong>My approach is always</strong>:</p>
<ol>
<li>Stabilize,</li>
<li>Re-sequence</li>
<li>Communicate</li>
<li>Deliver.</li>
</ol>
<p>Because progress isn’t linear—it’s adaptive.</p>]]></content:encoded>
						                            <category domain="https://nikhildesh.com/community/program-management/">Program Management</category>                        <dc:creator>Nikhildesh</dc:creator>
                        <guid isPermaLink="true">https://nikhildesh.com/community/program-management/how-do-you-kept-the-project-moving-forward-despite-roadblocks/#post-51</guid>
                    </item>
							        </channel>
        </rss>
		