Building an Agile Project Roadmap

Most change initiatives don't fail because of the change that's happening, they fail because of how the change is communicated. I've watched brilliant restructurings collapse and transformative acquisitions unravel… Not because the plan was flawed, but because leaders were more focused on explaining the "what" and "why" than on how they were addressing the fears and concerns of the people on their team. People don't resist change because they don't understand it. They resist because they haven't been given a compelling story about their role in it. This is where the Venture Scape framework becomes invaluable. The framework maps your team's journey through five distinct stages of change: The Dream - When you envision something better and need to spark belief The Leap - When you commit to action and need to build confidence The Fight - When you face resistance and need to inspire bravery The Climb - When progress feels slow and you need to fuel endurance The Arrival - When you achieve success and need to honor the journey The key is knowing exactly where your team is in this journey and tailoring your communication accordingly. If you're announcing a merger during the Leap stage, don't deliver a message about endurance. Your team needs a moment of commitment–stories and symbols that anchor them in the decision and clarify the values that remain unchanged. You can’t know where your team is on this spectrum without talking to them. Don’t just guess. Have real conversations. Listen to their specific concerns. Then craft messages that speak directly to those fears while calling on their courage. Your job isn't just to announce change, but to walk beside your team and help your team understand what role they play in the story at each stage. #LeadershipCommunication #Illuminate

Bad news is like fish. The longer it sits, the worse the whole situation smells. The Dilemma: A high-stakes launch is on the roadmap. Your team has brilliantly de-risked the plan, securing the most critical milestone ahead of schedule. Rock-solid work. But... they also know the full scope won't make the original date. And leadership? They haven't been told yet. The temptation to stay silent is powerful. The logic is seductive: "Let's not raise a flag until we have the perfect solution," or "Let's wait for a 'better time' to deliver this news." Here’s the counterintuitive truth: Waiting is the riskiest move you can make. Transparency without all the answers isn't weakness; it's a strategic advantage. A Better Way: Proactive Transparency Escalation isn't failure; it's a tool for alignment and trust-building. You don't need a perfect solution. You just need to own the narrative. My playbook for this conversation: 💪 Lead with the Win: Start with the good news. "We've secured the most impactful part of the launch and will deliver it early." 💪 State the Reality, Simply: Be direct. "This smart pivot means the subsequent phases will be delayed." 💪 Show Proactivity: Demonstrate control. "We are actively re-planning the remaining milestones." 💪 Own the Next Step: Provide certainty on communication. "We will share a full, revised plan with you by next week." When you do this, you're no longer delivering "bad news." You're delivering a reality-checked, responsibly managed plan. You're treating your leaders like partners. Surprising your leadership is a risk you can't afford. Building their trust is an asset you can't put a price on. Don't wait until the house is on fire. Be the leader who points to the smoke and says, "I've got this, and here's the plan." – 👉 Follow me, Rony Rozen, for more real-world insights on tech leadership. 

70% of change management efforts fail. Because most leaders go straight to execution. You treat change as a logistics problem. You build the roadmap, communicate the timeline, and track the milestones. And then you're blindsided when people push back. I've seen this happen in every room I've worked in,  From Capitol Hill to Fortune 150 boardrooms. The process is rarely the problem.  The people side is where change actually happens or falls apart. Here's the reframe that changes everything: Change is emotional before it is ever operational. When your team pushes back, they're not resisting the initiative. They're feeling something: 😨 Fear of losing ground they've worked hard for.  🤔 Uncertainty about where they fit in what comes next.  ❌ A lack of trust in whether leadership will follow through this time. When you understand that the emotional layer comes first, resistance stops being a problem to overcome. Instead, it becomes information to work with. That means before you roll out the roadmap, ask yourself what people are actually worried about. Before you send the announcement, ask: Do they trust this? And before you expect buy-in, check if you have given them a reason to believe in it. Here's the difference it makes in practice: ❌ Change management focuses on the process. ✅ Change leadership takes people on the journey. ❌ Change management treats resistance as a problem. ✅ Change leadership treats resistance as information. ❌ Change management makes one announcement. ✅ Change leadership communicates consistently. And when you are ready to have the conversation, your team needs four things from you, in this order: 1️⃣ What is changing and why. People cannot commit to something they do not understand. 2️⃣ What it means for them. Specific clarity creates confidence. Tell them exactly how this affects their role. This turns fear into focus. 3️⃣ What success looks like. If people cannot picture the destination, they will not start the journey. 4️⃣ What you need from them. Ask for their input before the plan is final. People commit to what they helped build. The leaders who get change right understand that people don't resist a revised plan. They resist feeling unseen in the middle of it. Address the emotion first, then lead the process. What's the hardest part of leading change right now? Let me know in the comments. Every day inside The Leadership Boardroom, I share daily leadership coaching on leading through moments like this: The tools senior leaders need to bring people with them, not just move them. Join us now: https://lnkd.in/g2WGzder ♻️ Repost for a leader in your network navigating change right now.  And follow me, Cicely Simpson, for daily leadership insights like this.

The best PMs don’t just build features. They build alignment. When I led my first cross-functional team, I thought I could rely on meetings and Slack messages to keep everyone on the same page. Spoiler: I couldn’t. Deadlines slipped. Teams got confused. Even the designers weren’t sure why we were building a feature. That’s when I built 10 internal docs that changed everything. No fluff. Just clear, actionable systems to keep everyone focused. Here’s what worked: 1/ Vision Doc – So everyone knows what we’re building—and why. 2/ Roadmap – To track progress and plan ahead. 3/ PRDs – With real user stories and clear edge cases. 4/ User Feedback Log – Straight from the source. No assumptions. 5/ Prioritization Sheet – Because not everything can be urgent. 6/ Daily Standup Notes – Async updates that actually work. 7/ Experiment Tracker – What we tried. What failed. What won. 8/ Postmortem Doc – No blame. Just lessons. 9/ Stakeholder Updates – Monthly, sharp, and honest. 10/ Internal Release Notes – So support and sales don’t get blindsided. Alignment isn’t magic. It’s process. P.S. Save this if your team constantly asks: “What’s the plan again?” Repost ♻️ if you think more PMs need this clarity. #helping #pm #apm #career #tuesdaypost #careergrowth

After my last post on automating 60% of T/PM work… My inbox exploded. So here it is— The exact AI prompt stack I use weekly as a Technical Project & Program Manager> 1// Weekly status report “Act as a TPM. Summarize these updates into a crisp weekly report. Include: key progress, risks, blockers, next steps. Keep it leadership ready.” 2// Meeting Notes → Action Items “Convert these meeting notes into structured outputs: Decisions made, action items, owners, ETA, and open questions.” 3// Executive summary (30-sec read) “Summarize this project update for executives. Max 5 bullet points. Focus on outcomes, risks, & business impact.” 4// Stakeholder specific updates “Rewrite this update for: 1. Leadership (concise) 2. Engineering (detailed) 3. Business (outcome-focused)” 5// Risk identification “Analyze this project update and identify potential risks. Include likelihood, impact, and suggested mitigation steps.” 6// Dependency mapping “From this data, extract all dependencies. Highlight critical ones and potential delays they may introduce.” 7// Follow up messages (that get replies) “Draft a polite but firm follow-up message for a delayed task. Make it actionable and hard to ignore.” 8// Roadmap narrative “Turn these bullet points into a clear roadmap narrative. Explain why this matters, what’s changing, and expected outcomes.” 9// Conflict framing “Two stakeholders disagree on priorities. Frame both perspectives and suggest a neutral resolution approach.” 10// Pre meeting brief “Summarize everything I need before this meeting: Context, key discussion points, risks, and decisions required.” Real shift? T/PMs who use AI → focus on thinking T/PMs who don’t → stuck formatting updates I repeate ...AI will NOT replace T/PMs But T/PMs who use AI will replace those who do NOT. If you found this useful> Repost so other T/PMs can save hours every week —The Ordinary TPM

Two project management truths: → Your team needs updates → Your leaders need outcomes A one-size-fits-all communication is a fast track to confusion. PMs are the translator between ground-level work and top-floor priorities. If you're saying the same thing to everyone, someone is not hearing what they need. Here's how you tailor your communication AND drive clarity at every level: 👉 Lead with "what this means for you" Customize your opening line based on who's listening/receiving. 👉 Use dashboards for execs and details for doers High-level visuals win at the top, while tasks/dependencies/blockers matter most to teammates. 👉 Talk outcomes over activity Tell leaders what got done and what it unlocks next. 👉 Summarize first, explain second Start updates with a clear summary (think TL;DR). Include details further down for those who want more. 👉 Repeat your message but adapt the framing Repetition builds trust. Repeat the right level of detail to each audience. Effective PMs are more than organized. They're multilingual. 🤙

"I was promised a Ferrari, but I got four wheels."   When a stakeholder said this a few months ago, it stuck with me.   It wasn’t just about the product. It reflected everything around the product that wasn’t working: -No clarity on when the Ferrari would be ready -No feedback loop to align on progress or expectations -No visibility into the fact that we were building the engine first   Without that context, all they saw were four wheels. And understandably, it didn’t feel like progress. They weren’t sure if it was going to be a Ferrari or a bullock cart.   Today, while watching my son build his LEGO Ferrari, that moment came back to me. He followed the steps — patiently, layer by layer, no shortcuts. He knew the final shape would emerge after the foundation was strong.   It reminded me: even real Ferraris start with structure. -The engine is built and tested before the body is assembled -The frame is tuned long before the shine is added -And once the base is ready, the rest comes together fast   We follow the same path in product development. We invest deeply in the invisible work — architecture, data layers, resilience, and security. But when that’s all you can see, it just looks like “four wheels.”   That’s not a failure in delivery. It’s a failure in communication.   So, how do we avoid the “just four wheels” reaction? 1. Make the invisible visible: Use metaphors, visuals, roadmaps—whatever it takes to show that “no UI” doesn’t mean “no progress.” Show the engine, not just the exterior. 2. Communicate like a co-pilot, not a broadcaster: Don’t just share updates—build shared ownership. Ask, listen, align. It’s not a stakeholder review, it’s a stakeholder journey. 3. Set expectations that teach, not just promise: Go beyond timelines. Explain trade-offs, dependencies, and value. Educate stakeholders on why things take time, not just when they’ll be done.   Because in software, the foundation phase is the hardest to see — and the easiest to misjudge. When people understand the why, how, and when, even the earliest stages feel like momentum — not disappointment.   Everyone wants the Ferrari. But only a few are patient enough to get the final one—through the right process. Here’s the progress of that LEGO Ferrari. It still doesn’t look like one. But it will. #ProductDevelopment #EngineeringExcellence #StakeholderAlignment #TechLeadership #Communication

“This roadmap is useless.” The words hit like a gut punch. After weeks of alignment, dependencies mapped, and every detail airtight… it fell flat in front of leadership. ❌ Too many details. ❌ No clear business impact. ❌ Buried in feature updates. That’s when I learned the hard way—one roadmap doesn’t work for everyone. One roadmap for all? Like sending the same email to your CEO, engineers, and customers—it won’t land. Each group needs different information, framed for their decisions. Here’s how to tailor your roadmap for success: 1️⃣ The Strategic Roadmap (For Executives) Audience: CEOs, leadership, investors Focus: Business outcomes, long-term vision, and key initiatives ✅ How to get it right: -> Keep it high-level—focus on themes, not feature lists. -> Tie initiatives directly to business goals and revenue impact. -> Use concise visuals (timelines, OKRs, measurable impact). 💡 Pro Tip: Your execs don’t need sprint details—just the “why” and how it moves the business forward. 2️⃣ The Tactical Roadmap (For Engineering) Audience: Product & engineering teams Focus: Priorities, dependencies, technical feasibility ✅ How to get it right: -> Provide clarity on scope, timelines, and trade-offs. -> Show how engineering efforts ladder up to business goals. -> Address dependencies upfront to avoid last-minute surprises. 💡 Pro Tip: Engineers don’t just want deadlines—they need the "why" behind decisions to make smarter trade-offs. 3️⃣ The Narrative Roadmap (For Customers) Audience: Users, customers, prospects Focus: Features, value, what’s coming next ✅ How to get it right: -> Focus on pain points solved, not just new features. -> Use visuals like wireframes, mockups, or sneak peeks. -> Be transparent—set clear expectations on timelines. 💡 Pro Tip: Customers don’t care about your internal priorities—they just want to know how you’re making their lives better. — 👋 I’m Ron Yang, a product leader and advisor. Follow me for insights on product strategy + leadership.

To become a great tech leader, you have to communicate meaning. Are you saying something meaningful or only providing data? While leaders love "data driven," it is critical to communicate why the metrics matter. All leaders give status updates; strong leaders connect them to the big picture. Here is how successful executives deliver status updates: As a busy leader, it’s easy to fall into the habit of sharing updates that focus on tasks and metrics, like: ▪️ “We’re 70% done” ▪️ “X feature is live.” But great executive communication isn’t just about what is being done, it’s about why it matters. Without that connection to purpose, your team will lose focus, motivation, and alignment. When we delivered streaming for the Paris 2024 Olympics at Warner Bros. Discovery, our deadlines were fixed and the stakes were global. We couldn’t just share milestones to keep everyone engaged and in sync; we had to make sure everyone understood WHY the milestones were important in the grand scheme of the project. This involves providing answers to questions like: ▪️ Why is X feature critical to the audience experience? ▪️ Why does it matter to the business? ▪️ Why are certain trade-offs necessary to meet deadlines? For the Olympics, communicating the “why” ensured that the engineers, product teams, and operations staff shared a common purpose: delivering an excellent experience for millions of viewers across 47 markets. When done right, creating a shared purpose makes the work your team does about more than just “getting it done.” To create that shared purpose for your team, here are three lessons tech leaders can use: 1) Frame communication around purpose and impact. Help your teams see how their work drives customer value and/or advances business goals. It’s not enough to tell them what to do, tell them why it matters. 2)Ensure alignment across cross-functional teams. Different teams bring different perspectives, so bridge those gaps and make sure everyone is moving in the same direction. 3) Use regular updates to reinforce the bigger vision. Status updates should provide objective benchmarks, but they should also anchor progress back to the larger goals. Many leaders mistake communication for a “soft skill.” In reality, it is a strategic advantage. Master telling the story of the broader initiative and your team will outperform anyone who simply follows orders. Leaders - How do you communicate broader purpose to your teams?

Here’s a lesson I had to learn the hard way…and something I find myself repeating regularly to my team: If you’re not actively communicating progress, people assume there isn’t any. Even if you’re deep in the work. Even if things are actually moving forward. Even if you’re heads-down solving real problems. Silence creates a vacuum—and in that vacuum, people rarely assume the best. They assume you’re stuck. Or stalled. Or overwhelmed. Or….worst of all, not doing anything. They start asking: “What’s going on with that?” And you’re suddenly on the back foot, defending instead of leading. I’ve had moments where I thought, “Why are they micromanaging me and checking in so much? Don’t they trust me?” But looking back, I wasn’t giving them anything to reassure them or provide confidence that “I’ve got this”. So now, I default to visibility: • A quick update in a Teams chat • A weekly email with what’s changed, what’s blocked, what’s next • One slide that tells the story clearly and simply It’s not performative and it doesn’t take long. It’s strategic. Because communicating progress—especially when you’re doing the leg work behind the scenes, a tricky phase, or a quiet stretch—builds confidence, keeps those relying on you aligned, and clears the path for you to move faster. I learnt that, if you want to be seen as a strategic operator, don’t just do the work. Create a drum beat.