<?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 Sumudu Siriwardana on Medium]]></title>
        <description><![CDATA[Stories by Sumudu Siriwardana on Medium]]></description>
        <link>https://medium.com/@sumudusiriwardana?source=rss-5acfe1a3c3d3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aLzuCapoxHKQUAjiVvDU4Q.jpeg</url>
            <title>Stories by Sumudu Siriwardana on Medium</title>
            <link>https://medium.com/@sumudusiriwardana?source=rss-5acfe1a3c3d3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:54:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sumudusiriwardana/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[Visualize Your Workflow]]></title>
            <link>https://medium.com/@sumudusiriwardana/visualize-your-workflow-719d886549f8?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/719d886549f8</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Fri, 27 Feb 2026 15:51:58 GMT</pubDate>
            <atom:updated>2026-02-27T15:51:58.451Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7WnunV8WyQImQtjn.png" /></figure><p>I recently hosted a planning workshop for one of my projects, expecting to work through a carefully structured agenda and walk away with a draft project management plan. Instead, we ended up with a wall full of sticky notes and a timeline that needed to be rebuilt.</p><p>As with most waterfall projects, we put significant effort and consideration into our planning phase. My goal in this workshop was to confirm the scope, identify risks early, and define tasks and timelines clearly enough to translate the discussion into a formal plan. I prepared a detailed agenda with defined objectives, slides, pre-reads, and expected outcomes.</p><p>On the first morning, we started with a light icebreaker. Some of us were meeting in real life for the first time, so we spent time getting to know each other. Then we moved into scope discussion, and by mid-morning, it became clear that I had made an assumption about the workflow and about everyone’s shared understanding of it. I was new to this project, this team, and even this assessment world. I assumed that since the team had released a smaller version of this product before, everyone was fully aware of how their work depended on one another, why certain tasks could not run in parallel, and why some steps took longer than expected. That assumption turned out to be wrong.</p><p>Thankfully, I had already scheduled a workflow and dependency mapping session, but it was designed as a refinement exercise, not a full remapping of the workflow. As I was considering changing our workshop agenda to focus entirely on mapping the full workflow from start to finish, my colleague suggested we adjust the design of that session as well. So, we ditched the agenda and the original session design.</p><p>Instead, we built a release journey map together, outlining the workflow and dependencies required to move the product from point A to release. We covered the meeting room wall with high-level tasks we needed and their connections, one sticky note at a time. It was not a straightforward conversation. It was a back-and-forth exploration of how work actually gets done, how long certain tasks really take and why, and what constraints shape those timelines. For many of us, this was the first time we saw the full picture laid out visually in one place.</p><p>We quickly realized that some of the assumptions made while drafting the project charter were unrealistic. The timeline looked reasonable on paper, but it was built on partial visibility of the dependencies. Even though we discussed these pieces before, their real implications were diluted across documentation and virtual meetings. Being in the same room, with the materials in hand and the workflow physically mapped out, changed the quality of that conversation.</p><p>By the end of the second day, we didn’t have a polished timeline draft or finalized decisions ready to drop into a project plan. But we had a deeper understanding of milestones, clearer visibility into how scope or decision changes would affect them, and a shared awareness of gaps that needed attention. More importantly, we had a team that understood the complexity of the work and the path required for a successful release.</p><p>This experience reminded me of my earlier days working with Kanban boards, user stories, and story mapping, and how powerful it is to visualize the workflow rather than assume it.</p><p>In many traditional projects, we move quickly from scope discussion to schedule creation. We estimate durations, sequence tasks, and build timelines before fully validating how work actually flows between people. On paper, the schedule can look balanced. In practice, hidden dependencies and overloaded handoffs surface later.</p><p>One of the core ideas in <a href="https://personalkanban.com/">Personal Kanban</a>, as described by Jim Benson and Tonianne DeMaria, is simple: visualize your work. When work is visible, constraints are visible. When constraints are visible, teams can manage flow instead of reacting to delays. This principle applies equally to ongoing work, planning, and brainstorming.</p><p>In our workshop, mapping the workflow before building the timeline exposed assumptions that would have otherwise shown up during execution. The act of visualizing the system shifted the conversation from “How long will this take?” to “What actually has to happen before this can move?” Letting go of the agenda created space for that visibility.</p><p>The plan still matters, and it becomes stronger when it reflects the real flow of work rather than an assumed sequence.</p><p><em>Originally published at </em><a href="https://theprojectlens.substack.com/p/visualize-your-workflow"><em>https://theprojectlens.substack.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=719d886549f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mental Models for Projects — Bottlenecks]]></title>
            <link>https://medium.com/@sumudusiriwardana/mental-models-for-projects-bottlenecks-dab79baf6de1?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/dab79baf6de1</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[mental-models]]></category>
            <category><![CDATA[theory-of-constraints]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Sat, 11 Oct 2025 17:14:23 GMT</pubDate>
            <atom:updated>2025-10-11T17:14:23.247Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mental Models for Projects — Bottlenecks</h3><p>Every project manager knows the frustration of watching a plan stall because of one small hold-up. That one review or approval can make or break your entire schedule, leaving your team stuck for hours, days, or even weeks. That’s the heart of the Theory of Constraints: a system is only as strong as its weakest point. I first noticed this long before I knew the name for it, back when I was playing netball in school.</p><figure><img alt="A bottle floating on the river" src="https://cdn-images-1.medium.com/max/1024/1*_RRrQY1z_vOd1lzXfmnAKg.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/photo/selective-focus-photo-of-bottle-floating-on-body-of-water-1603933/">Maria Tyutina</a></figcaption></figure><h4>What Netball Taught Me About Bottlenecks</h4><p>Back in school, I was on the netball team. I played Center, a position that kept me running nonstop across the court and constantly tested my stamina. Once, as we got closer to interschool matches, our Wing Attack (WA) got injured and was replaced by one of the reserve players who had recently joined the team.</p><p>With a new player on the team, our usual rhythm fell apart, and everything kept breaking down before the ball even reached the shooting circle.</p><p>We realized that the breaking point was the WA position, and she was struggling to keep up with the pace we had been used to, as she was still finding her footing. She needed more practice to warm up to the team’s flow.</p><p>Our coach told us to adapt instead of pushing WA. We stayed closer to her and opened up space, giving her easier passes and covering some of the moves she couldn’t make in time. It kept the ball moving forward and protected our scoring chances. The change worked. We were back in sync.</p><p>That was my first real understanding of bottlenecks and the Theory of Constraints. I realized the team’s success rested on its weakest spot, and once we supported it instead of pushing, the rhythm returned.</p><h4>Where Projects Get Stuck</h4><p>I see the same pattern in project management. A project plan might look neat and balanced, but in reality, one handoff, review, or approval point can quietly hold everything back.</p><p>I’ve seen plenty of teams where all the development work ends up stuck in PR reviews or QA queues. I’ve seen content projects where drafts pile up waiting for a single round of feedback. In all these cases, the whole project gets delayed because one step is overloaded, and everything else gets stuck behind it.</p><p>In some project management methodologies and frameworks, these points are easy to identify, while in others, you have to hunt for bottlenecks to find them.</p><p>When Toyota came up with Kanban, one of the headaches they wanted to fix was unfinished work piling up and getting stuck in the system. So, they set up a pull system, visual boards, and limits on how much could be in progress at one time. That way, bottlenecks couldn’t hide anymore. They were right there on the board for everyone to see. Today, lots of Agile teams, including Scrum teams, use Kanban-style boards for the same reason. You can see right away where the work is jammed.</p><p>But in traditional projects, it’s much harder to spot bottlenecks. On a Gantt chart, everything can look fine until a dependency shifts, an approval drags on, or a delivery runs late. Then half the plan is blocked, and you only notice it once deadlines start slipping.</p><h4>How I Hunt for Bottlenecks as a PM</h4><p>Now, I use the Theory of Constraints as a mental model to understand systems and processes and identify bottlenecks as early as possible before they become a crisis.</p><ul><li>Map the flow — I trace how each deliverable moves, identifying where handoffs, reviews, and decision points sit. That’s usually where the weak spots hide.</li><li>Look for queues — pay attention to where work piles up. If one tester or reviewer has everything landing on their desk at once, that’s a bottleneck waiting to happen. Spotting it early means I can plan around it.</li><li>Check for dependencies — Tasks that unlock ten others are a risk worth watching. Even a small delay here can ripple through the whole plan.</li><li>Listen for friction — if the team keeps saying “we’re waiting on X,” that’s usually the real bottleneck talking. Plans don’t always show it, but the people living the workflow do.</li></ul><p>Identifying a bottleneck is only half the work. Once you see it, you can reduce the load, add capacity, or re-route the flow. The key is to focus on the single spot that unlocks the biggest shift instead of trying to fix everything at once. That’s what makes the Theory of Constraints so powerful. It turns big, messy projects into something you can actually move forward.</p><p>And once you start spotting bottlenecks this way, you stop chasing every little issue. Instead, you give your attention to the one constraint that really matters. That’s when you begin to see the project as a whole system, with its own natural limits like time, resources, and approvals. And that’s the shift that takes projects from stressful to manageable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dab79baf6de1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mental Models for Projects: Part 2]]></title>
            <link>https://medium.com/@sumudusiriwardana/mental-models-for-projects-part-2-a7a4c6196cf3?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7a4c6196cf3</guid>
            <category><![CDATA[project-costs]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[cost]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Tue, 22 Jul 2025 11:45:11 GMT</pubDate>
            <atom:updated>2025-09-26T12:20:16.805Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mental Models for Projects — Tradeoffs</h3><p>In my <a href="https://medium.com/@sumudusiriwardana/mental-models-for-project-work-part-1-6b6ae151fa72">last post</a>, I explained three mental models that help me think clearly when projects get messy: First Principles, Second-Order Thinking, and Inversion. Those are my go-to tools when I need to plan better or understand what’s really happening when things start to drift.</p><p>But planning is only half the job. The other half is making decisions when you can’t have everything you want. When the budget is tight, the timeline is short, and the team is stretched. When you have to choose between features, resources, or quality. When someone asks you to do more with less.</p><p>That’s where these next three models come in. They help me make smarter tradeoffs without getting stuck or making choices I’ll regret later.</p><figure><img alt="A person in a red jacket stands at a colorful crossroads, with paths in black, red, and yellow, symbolizing choices and directions." src="https://cdn-images-1.medium.com/max/1024/1*FWs9HGHObxgDRIvrbPxiPg.png" /><figcaption>Illustration by <a href="https://www.lummi.ai/creator/ricardomatos">Ricardo Matos</a></figcaption></figure><h3>Cost of Delay</h3><p><em>Time has a price. Know what you’re paying for waiting.</em></p><p>Most of us think about cost in terms of money. We ask how much the features will cost to build, and what our budget looks like. But we don’t always think about the cost of waiting. What’s the real price of delaying something by three months?</p><p>Every day of not shipping something is a day we’re not getting value from it. Every week of debating which approach to take is a week we’re not learning from real users. Every month of delay in production is a month our competitors might be moving ahead.</p><p>Think of it like maintenance on your car. You know the oil needs changing. The brakes are starting to squeak. The check engine light has been on for weeks. You could deal with it now, but you’re busy. It’s not urgent. The car still runs.</p><p>But every mile you drive without changing the oil is wear on the engine. Every day you ignore the brakes is a risk you’re taking. Every week you postpone maintenance is a week closer to a much bigger, more expensive problem.</p><p>Technical debt works the same way. That messy code that slows down new features. The database that takes forever to run reports. The testing process that requires three people and half a day to deploy a simple fix. You know it needs to be addressed, but there’s always something more urgent.</p><p>Meanwhile, the cost keeps accumulating. Every sprint where developers spend extra time working around the messy code is lost time in new development. Every week where reports run slow is another week of frustrated users. Every deployment that takes hours instead of minutes is productivity lost to inefficiency.</p><p>I’ve seen teams avoid refactoring work for months because it felt less important than shipping new features, including teams I’ve been on. But by the time they finally addressed it, they had lost weeks of productivity to workarounds and inefficiencies. The cost of delay had become higher than the cost of the work itself.</p><p>Now, when I’m stuck between perfecting something and shipping it, I try to put a number on delay. What does it cost us to wait another week? Another month? Sometimes it’s actual revenue we’re missing. Sometimes it’s learning we’re not getting. Sometimes it’s momentum we’re losing.</p><p>Once you see the price tag, the decision becomes clearer. You’re not just choosing between good and perfect. You’re choosing between the value you get today and the value you might get later. And some work isn’t urgent until you realize the cost of waiting.</p><h3>Opportunity Cost</h3><p><em>Every ‘yes’ is a ‘no’ to something else.</em></p><p>This one may sound obvious, but it’s easy to forget when you’re in the middle of making decisions. You get excited about a new feature, approach, or project. You focus on what you’ll gain. But you don’t always think about what you’ll give up.</p><p>Opportunity cost is what you give up by choosing one option over another. It’s the value of the next-best use of your time, budget, or attention. It’s almost always invisible, making it easy to overlook.</p><p>But in project work, it adds up fast. I’ve seen teams say yes to so many small, one-off requests that their actual roadmap slipped by months. No one could pinpoint where the time went. It just leaked away through favors, workarounds, and ‘quick wins’ that weren’t really wins.</p><p>So I try to make the tradeoff visible by saying:</p><ul><li>“We can do this, but it pushes that other thing out. Is that okay?”</li><li>“If we say yes to this now, we’re saying no to X, Y, and Z.”</li><li>“What are we giving up if we say yes to this?”</li></ul><p>I’m not trying to slow things down. I just want everyone to see the full picture.</p><p>We often think of prioritization as choosing what is most important. But it’s just as much about what we are willing to let go. Opportunity cost forces that part of the conversation.</p><h3>Sunk Cost Fallacy</h3><p><em>Don’t keep going just because you’ve already started.</em></p><p>This one is painful, especially when you are months into a project that isn’t working out. You’ve invested time, money, and energy. The team has put in effort. But deep down, you know it’s not going where you hoped. Yet you keep pushing because you don’t want to waste what you’ve already put in.</p><p>The sunk cost fallacy is when we keep investing in something just because we’ve already invested so much. Even if it no longer makes sense.</p><p>I’ve seen this play out across different areas. A tool that slowed everything down, but we kept using it because we’d already trained the team. A new onboarding process that frustrated employees, but we stuck with it because we had spent months designing it. A feature that users clearly didn’t want, but we shipped it anyway just because the code was already written. A pilot program that clearly wasn’t working, but we rolled it out company-wide anyway because we had already committed to leadership.</p><p>The model helps me step back and ask:</p><ul><li>If we were deciding today, would we still choose this?</li><li>Are we continuing because it’s the right thing to do or because we don’t want to waste what we’ve already spent?</li><li>What would it cost to stop? And is that actually less than finishing?</li></ul><p>This one takes a bit of courage. You have to be okay with walking away, even after the effort. But letting go isn’t failure. It’s just redirecting that energy somewhere more useful.</p><p>Sometimes the smartest decision is to stop digging.</p><p>Projects are a constant negotiation between what we want to do and what we realistically can do. These three models work together to help me make better tradeoffs. Cost of Delay reminds me that waiting has a price. Opportunity Cost shows me what I’m giving up. And Sunk Cost Fallacy keeps me from throwing good time after bad.</p><p>They don’t remove the tension. But they give you language to talk about it. They help you explain why a “quick change” has a hidden cost. Why sticking with a broken process isn’t loyalty, it’s waste. Why doing less can sometimes deliver more.</p><p>I don’t use all these models every day. But when I find myself stuck between two priorities or defending a hard call, I pull one of them out. Usually, it makes the next step a little clearer.</p><p>Next time, I’ll share a few other models that help me manage the work. If you’ve found yourself stuck on any of these tradeoffs in your own projects, I’d love to hear how you worked through them.</p><h3><strong>View all posts in this series:</strong></h3><ol><li><a href="https://medium.com/@sumudusiriwardana/mental-models-for-project-work-part-1-6b6ae151fa72">Mental Models for Projects: Planning</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7a4c6196cf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mental Models for Project Work: Part 1]]></title>
            <link>https://medium.com/@sumudusiriwardana/mental-models-for-project-work-part-1-6b6ae151fa72?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b6ae151fa72</guid>
            <category><![CDATA[mental-models]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[risk-management]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Thu, 26 Jun 2025 12:47:22 GMT</pubDate>
            <atom:updated>2025-09-26T12:17:44.763Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mental Models for Projects — Planning</h3><p>Recently, my manager asked if I was familiar with the term <em>premortem</em>. It rang a bell, but I couldn’t place it right away. She explained what it meant and then asked if I had ever used it in projects. As she talked, it clicked. I had heard the term before, but more importantly, I had been using that exact thinking approach for a long time, just not under that name.</p><p>I had always known it as part of inversion thinking, one of the mental models I reach for when I need to identify risks early. That moment made me realize that, over time, I’ve come to rely on a few mental models that help me think clearly and solve problems. I fall back on them in moments of uncertainty, under pressure, or when I’m trying to make a clear decision without perfect information.</p><p>They are not formal steps, more like habits that help me slow down and focus when projects become noisy and complicated. So, I decided to write them down as a short series. This first post focuses on three models I lean on for better planning or when a project starts to drift or become chaotic: First Principles Thinking, Second-Order Thinking, and Inversion Thinking.</p><figure><img alt="A person holding a wooden puzzle ball, surrounded by brain teasers and logic games on a white table." src="https://cdn-images-1.medium.com/max/1024/1*DvUMuHSgQRmOtXo_Lk4SYg.jpeg" /><figcaption>Photo by Kaboompics.com</figcaption></figure><h3>First Principles Thinking</h3><p><em>Break it down. Start from what’s true. Build up from there.</em></p><p>This one sounds simple, but it’s harder to use in real life than it seems. The goal is to get to the truth behind something. Break it apart, see what it’s really made of, and understand why it exists the way it does. When we were kids, a lot of us did this without even realizing it. I remember taking toys apart just to see how they were built. I’d test which parts still worked on their own or try combining pieces from different toys to make something new.</p><p>That curiosity fades a bit as we grow up. We get used to systems, habits, and tools. We stop asking questions and start assuming things are the way they are because that’s how they should be.</p><p>Ask someone why a process exists, and you’ll probably hear, “That’s how we’ve always done it.” If you push a little more, you’ll get, “It works for how we operate.” But very few people can say what problem that process was actually created to solve. Or whether that problem still exists.</p><p>We confuse comfort with correctness. Just because something works doesn’t mean it’s the best or only option.</p><p>So when a team says something like, “Our process takes four weeks,” I try to pause and ask a few questions. What exactly happens in those four weeks? Why was it set up that way? Which parts are still useful? Which ones are just legacy steps we stopped questioning?</p><p>Once you start pulling it apart, you can see what actually matters. From there, you can streamline what’s needed, cut what isn’t, and rebuild something that still works without holding on to old habits that don’t.</p><p>That’s what First Principles Thinking helps with. It’s about getting to the root of things and building from there, and about starting from what’s actually true, not what’s always been assumed.</p><h3>Second-Order Thinking</h3><p><em>Don’t just think about what happens now. Think about what happens next.</em></p><p>When you’re under pressure to decide, it’s easy to just do what works right now. Perhaps you’re in a meeting, time is ticking, and the team is exhausted. You want to keep moving. So you make a call that solves the problem today.</p><p>But what happens next?</p><p>Second-order thinking is about pausing to ask, “And then what?”, about looking at the ripple effect. You’re not only looking at what the decision solves today, but what it might create or complicate later on.</p><p>When I first learned to play chess, I was hooked on how good players thought ahead. You couldn’t just make a move because it looked good. You had to think through what your opponent might do next and how that would shape the board. You might give up a piece in the short term to open up a stronger position a few moves later. That’s how I first learned to think past the obvious.</p><p>In project work, we talk a lot about fast delivery and quick wins. It might seem like a win at the moment, but it can come back later as a bigger issue for the team, the product, or the people using it.</p><ul><li>A first-order decision is what you see right away.</li><li>A second-order effect is what comes next.</li><li>And if you keep tracing it, you’ll find third-order effects, the things that sneak up later.</li></ul><p>I’ve seen this happen during sprints. We would rush out a few features just to hit the sprint goal, close the burndown chart, and have something to show in a demo. But the next few sprints would then be filled with fixes for those same features. We wouldn’t build anything new. We would just clean up what we rushed.</p><p>So now, I ask a few questions before I make a fast decision:</p><ul><li>What happens next week if we do this?</li><li>What happens next month, next quarter, or next year?</li><li>Who will bear the consequences if this goes sideways?</li><li>Are we actually solving something or just buying time?</li></ul><p>I also like to bring in examples from past projects to help the team see the pattern. If we’ve rushed something before and paid the price later, we can use that to justify a better approach this time.</p><p>Not every decision needs a five-year plan, but every decision creates consequences. If you can get in the habit of spotting them early, it saves a lot of stress later.</p><h3>Inversion Thinking</h3><p><em>Instead of thinking, “How do we succeed?” ask, “What would make us fail?”</em></p><p>This is one of my favorite ways to spot risks early. Most of the time, we focus on what success looks like. We plan for our goals. We outline steps to get there. But we don’t always spend enough time asking what could go wrong. And even when we do, it’s often too shallow, a quick list of risks on a kickoff slide that never gets looked at again.</p><p>Inversion thinking is about turning that question around. Instead of only asking, <em>“What do we want to happen?”</em> it forces you to ask, <em>“What are the ways this could fall apart?”</em> It’s uncomfortable, but it’s one of the most useful ways I’ve found to plan smarter.</p><p>I still remember watching <em>Titanic</em> when I was little. I didn’t understand why such a huge ship didn’t have enough lifeboats. It wasn’t until much later that I learned the real reason. No one planned for failure. They didn’t ask the hard question. <em>What happens if this thing sinks in the middle of the ocean?</em></p><p>If someone had stopped to ask, “What do we need if everything goes wrong out at sea?” things might have turned out very differently. The focus had been on making the ship impressive, not on preparing for failure. So they haven’t thought deeply about risk. They believed the ship wouldn’t sink, so they never planned for what to do if it did.</p><p>In projects, I try to ask those questions early. At the start of a project, I like to sit with the team and ask:</p><ul><li>What could delay us?</li><li>What might force us to cut corners?</li><li>What risks are we ignoring because we think they’ll never happen?</li><li>What happens if we miss the milestones and deadlines?</li><li>What would cause users to stop trusting the product?</li></ul><p>These questions open up the conversation. People bring up things that don’t always make it into the plan. Like that dependency we’re assuming will work, or the team member who’s stretched too thin. Once you name those things, you can build around them. You add a buffer. You clarify decisions early. You flag the risk so it doesn’t catch you off guard.</p><p>And when something does go wrong, which it usually does, you’re not panicking. You’re already prepared.</p><p>Most plans only work if everything goes right. Inversion thinking helps you build a plan that still works when things go wrong.</p><p>These three mental models have helped me think more clearly when everything else feels rushed or messy. I don’t use them in a fixed order. Sometimes, I start with Inversion to flag risks. Sometimes, I pause for Second-Order Thinking when I’m under pressure to make a fast call. And when something doesn’t make sense, I reach for First Principles to reset and understand what’s really going on.</p><p>The more I practice using them together, the more they start to work in the background. I don’t need to overthink every decision. I just need to ask better questions. That’s how I keep things moving without losing sight of what actually matters.</p><p>More to come in the next post. If you’ve used any of these mental models in your own work or have your own go-to ways of thinking through messy projects, I would love to hear about it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b6ae151fa72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Things Done Without Power]]></title>
            <link>https://medium.com/@sumudusiriwardana/getting-things-done-without-power-587ae308da0c?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/587ae308da0c</guid>
            <category><![CDATA[project-leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[lead-without-authority]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Fri, 13 Jun 2025 16:26:34 GMT</pubDate>
            <atom:updated>2025-06-14T00:04:03.707Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A flamingo balancing on a skateboard in front of palm trees on a sunny day." src="https://cdn-images-1.medium.com/max/1024/1*qSyK4JN9s8Ty3ys57DFwEw.jpeg" /><figcaption>Image from gratisography.com</figcaption></figure><h3>Getting Things Done Without Authority</h3><p>As project managers, we often lead projects that don’t really belong to us. We are expected to plan the work, manage the progress, and deliver results, but we don’t always have the authority to make decisions.</p><p>Over the years, I have worked in various companies and seen different flavors of this setup. Sometimes you are part of a projectized organization where the PM has a lot of say, and the team reports to you for the duration of the project. But in most places I have worked, especially in matrix environments, that’s not the case. You are responsible for the project, but the team doesn’t report to you. They have their own managers, their own priorities, and sometimes, their own version of the plan.</p><p>To be honest, this used to frustrate me quite a bit. In my earlier PM days, I didn’t fully understand how I was supposed to lead a project without actually being in charge of the people doing the work. It felt like I was set up to be accountable for something I couldn’t fully control, like being handed the steering wheel while someone else controlled the brakes and the engine.</p><p>I still remember one of my first projects, where this became very obvious. I had to bring together a team, build out some features, and hit a tight deadline while everyone I worked with had different reporting lines and department goals. I wasn&#39;t trying to step on anyone’s toes, but I still ended up in a few awkward conversations with department heads who weren’t too happy with me making requests of their teams. It was messy. But I managed to get it done somehow.</p><p>Eventually, I realized that what makes the difference isn’t authority, it is influence.</p><p>And that’s not just a personal opinion. As Larson and Larson point out in a PMI published article, <em>influencing without authority</em> is one of the most essential skills for project managers working in environments where team members aren’t directly accountable to them. The ability to build trust, communicate clearly, and establish credibility is just as important as knowing how to create a timeline or manage a risk register (<a href="https://www.pmi.org/learning/library/influencing-without-authority-project-requirements-8100">Larson &amp; Larson, 2006</a>).</p><p>Once I figured that out, things started to fall into place. I stopped trying to act like I had control and started focusing on building relationships. I spent more time listening to what team members were juggling, rather than just assigning tasks. I followed up consistently, but not in a robotic or transactional way. If someone was swamped, I offered to shift timelines or help remove blockers. I also made the work visible by setting up simple tracking systems and sharing weekly updates so everyone could see what was happening and why it mattered. And I got better at surfacing decisions early. Rather than waiting for someone to speak up, I started asking direct but respectful questions to move things forward.</p><p>Leading a project when you are not the boss means playing the roles of connector, translator, and facilitator all at once. You need to know how to communicate effectively with different teams, how to keep things moving without being pushy, and how to adapt when people aren’t prioritizing your project.</p><p>You also need to be okay with repeat conversations. Many people assume that once you say something in a meeting, it’s done. But when you are not the boss, you have to keep reinforcing priorities and gently nudging people back to the shared goals. Not because they are ignoring you, they just have a lot going on.</p><p>There are multiple influence strategies that you can add to your toolbox throughout this journey, including persuasion, building coalitions, and understanding your sources of power. For me, most of that came down to consistency. Not trying to win people over in one meeting, but showing up over time with clarity, calm, and follow-through.</p><p>Somewhere along the way, I realized that leadership doesn’t come from a title. It comes from trust. From being reliable. From connecting the dots when no one else does.</p><p>A few things that worked for me:</p><ul><li><strong>Ask the questions no one is asking.</strong> The biggest gaps usually come from assumptions. The “dumb” questions are often the most useful ones.</li><li><strong>Follow up, but make it human.</strong> People respond better when they feel respected, not managed.</li><li><strong>Share progress often.</strong> Even if things are moving slowly, showing momentum builds trust.</li><li><strong>Understand what motivates your team.</strong> Some people need structure. Others need context. A few want a heads-up before a deadline lands in their lap.</li><li><strong>Don’t fake expertise.</strong> If you are not the subject matter expert, that’s okay. Your role is to keep the work moving, not to have all the answers.</li></ul><p>If you have ever been in that weird “I’m responsible, but not really in charge” spot, you are not the only one. It’s more common than people admit. The real challenge isn’t trying to act like you have authority. It’s figuring out how to lead with influence, clarity, and a bit of patience. It takes longer, but it works.</p><p>You don’t need to be the boss to get things done. You just need to be the person people trust to keep the work moving forward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=587ae308da0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First 100 Days in Assessment: Still Learning, but Less Lost]]></title>
            <link>https://medium.com/@sumudusiriwardana/my-first-100-days-in-assessment-still-learning-but-less-lost-1a783b2616ba?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a783b2616ba</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[first-100-days]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Fri, 09 May 2025 17:09:22 GMT</pubDate>
            <atom:updated>2025-05-09T17:09:22.220Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A personal card from my supervisor, alongside appreciation notes, placed next to a potted plant and a stack of colorful books." src="https://cdn-images-1.medium.com/max/1024/1*QxrrmniS0bS4lZ8yZjszfw.jpeg" /></figure><p>I stepped into a new role 100 days ago, one that came with a steep learning curve, a whole new domain, and a flood of acronyms I had never seen before. Coming from a different industry, I had no idea what to expect. But this was a change I had been hoping for. Since we have just wrapped up annual planning for one of my projects, it felt like a good moment to look back on my first stretch in this role.</p><p>That first day in a new role always brings a mix of nerves and excitement, no matter how long you’ve been in the game. I still remember joining the tech setup meeting first thing in the morning, coffee in hand, thinking I’d get my logins and be tossed into the deep end by the afternoon. That had been the pattern in most of my past jobs. A couple of intros, a few shared docs, and then a quick “good luck out there.”</p><p>I was honestly surprised (in the best way) to see a full two weeks of onboarding sessions blocked on my calendar. It was thoughtfully paced, with enough breathing room to explore, take in the details, and not feel rushed. There were then another two weeks focused solely on project-specific onboarding. No rush to get up to speed within a few days when you start, or pressure to prove yourself. I had access to clear documentation, training sessions, and time set aside to really understand the domain, systems, and project cycles.</p><p>Everyone was incredibly generous with their time, happy to answer questions (even when I asked more than once), and always willing to walk me through anything I was confused about. That kind of support made a huge difference. It gave me the confidence to dig in, ask better questions, and ramp up way faster than I expected. Honestly, it was one of the most thoughtful onboarding experiences I’ve had, and it set me up with a solid foundation from the very beginning.</p><p>One piece of advice I kept hearing in almost every conversation was this: “Don’t beat yourself up. It takes a long time to understand everything here and get used to the workload.” I hadn’t worked in education or building large-scale assessments before, so I kept wondering what exactly makes it so complex that it takes years to become familiar with. Still, it was comforting to hear. It meant no one was expecting me to have it all figured out from day one or feel like I had to prove myself right away.</p><p>It didn’t take me long to understand what they meant. My early days were all about trying to understand the big pieces. The various assessments, standards, test building process, operational aspects, and how all the vendor partnerships actually work. It started to feel a bit like an orchestra, with a lot of moving parts across different teams and organizations coming together to pull off each test cycle. And like any orchestra, if one part goes off beat, the whole thing starts to feel out of sync.</p><p>When I think about these first 100 days, it’s not the big milestones that come to mind. It’s the small wins and the things I didn’t expect to learn. Some days, the biggest victory was getting a Smartsheet formula to work on the first try. Smartsheet was completely new to me, and just figuring out where things lived felt like an achievement at first. On other days, it was finally understanding the different Braille versions and which grade clusters use each one. That one felt impossible at first, like trying to learn a new language without a phrasebook.</p><p>And when I started digging deeper into how test development and cycles actually work, the high-level view seemed simple enough. But once I started connecting that to our actual project plans, with all the layers of tasks, dependencies, and timelines, I saw just how much work goes into keeping everything moving. I’m still spending a good chunk of my time trying to understand how it all fits together, not just within my own projects but also how it connects to other projects. Now I fully understand why people say it takes time to learn this. There’s a lot to dig into just to understand my own project plans and feel familiar with them. It’s a lot, but every piece helps me see the bigger picture a little more clearly.</p><p>And then there were the moments that weren’t about tools or processes, but about showing up. Like leading a meeting, even when I wasn’t totally sure what I was doing or figuring out when to ask for clarity and when to roll with it. I learned the value of good documentation, not just to keep the team aligned, but to help me stay sane when things got busy. I also started to notice how much leadership happens quietly. It’s in the follow-ups, the questions no one else is asking, the small connections that help others see the bigger picture, and making sure the little details don’t slip through the cracks.</p><p>I’ve felt incredibly grateful for my supervisor and close colleagues, who always made time to help me understand things, discuss ideas, and support me through the challenging parts of the process. One small win that I’m proud of is being able to make a few process improvements to one of the projects I’m managing, even within this short time. There’s still so much more to learn and a lot more to improve, but that’s part of what makes this role exciting. It keeps me thinking, keeps me learning, and pushes me to use every skill I’ve picked up along the way.</p><p>Today, after wrapping up our big annual meeting for this test cycle, I took a long breath. The kind you don’t realize you’ve been holding. I thought to myself, I actually made it through that. I showed up, navigated the discussions, answered the questions, and didn’t completely panic. I walked into that planning process not knowing what to expect. Now, I can see the full picture and what it takes to lead these projects with more confidence. I’m not done learning, not even close, but I finally feel like I’ve found my footing.</p><p>I’m starting to see how things connect now, but there’s still a lot I’m piecing together. I don’t expect to have it all figured out anytime soon, and that actually feels fine. My focus is on learning as I go, asking better questions, and getting more comfortable with the parts that still feel a bit unclear. These first 100 days gave me a solid start. The rest, I’ll figure out one conversation, one task, and probably one Smartsheet at a time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a783b2616ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Not Always Online, On Purpose]]></title>
            <link>https://medium.com/@sumudusiriwardana/not-always-online-on-purpose-7df3042b908f?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7df3042b908f</guid>
            <category><![CDATA[digital-minimalism]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[career-change]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Sat, 12 Apr 2025 21:38:12 GMT</pubDate>
            <atom:updated>2025-05-03T00:31:27.825Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A collection of fantasy and fiction books arranged on grass outdoors. Visible titles include “The Will of the Many,” “The Bone Season,” “City of Brass,” “The God of the Woods,” “The Way of Kings,” “Clytemnestra,” “Children of Ruin,” “The Covenant of Water,” and others." src="https://cdn-images-1.medium.com/max/1024/1*3sBpJwpz2VmQmv2_t8EDoQ.jpeg" /><figcaption>Some <em>of books from my shelves this past year</em></figcaption></figure><p>Like many millennials, I grew up immersed in the internet, first as a user and then as someone who has built a whole career in tech. I worked as an IT Project Manager, stayed active on X (Twitter) to grow my professional brand, used Facebook and Instagram to keep up with friends and life updates, and am still active on LinkedIn to maintain my professional network.</p><p>All of it felt normal: the constant connection, the notifications, the daily updates, and the endless scrolling. It was just part of the rhythm. But sometime last year, that rhythm started to feel off. I had moved thousands of miles away from friends and family, so I often caught up with them by sharing updates when we chatted. Then I started to wonder…why was I sharing so much online, too? Why was I spending hours scrolling through other people’s lives without really thinking about it? Around the same time, I met a few online creators, which shifted something in me. Slowly, I started pulling back. I became less active, less interested, and more aware of how much time I was spending there.</p><p>Without the constant pull of social feeds, alert pings, and endless context switching, I started to notice something. I was saving hours of focused time every day. It made me pause and realize that I’ve actually been in this multi-tasking haze for over a decade.</p><p>But the hardest part of stepping back wasn’t the habit itself. It was the fear of missing out. I kept thinking I would fall behind on trends, tech news, or the latest AI updates. That’s what kept dragging me back into the scroll. So, I found a workaround. I started subscribing to a few solid newsletters that delivered exactly what I needed, right to my inbox. No more endless scrolling, no rabbit holes, and no wasted hours.</p><p>As part of that shift, I uninstalled X (Twitter), Instagram, and a few other apps from my phone. I still check them now and then, usually on my laptop when needed, but they’re no longer following me around in my pocket. And that quiet felt really good!</p><p>That one small change opened up a surprising amount of mental space.</p><p>With all that time back, I noticed something simple but powerful: I felt more present. I’ve also returned to one of my favorite old habits — reading. For years, I was barely finishing a book a month. Now, I’m reading closer to five. But this shift hasn’t just been about productivity or better habits. It’s about peace. There’s something calming about not knowing everything that’s happening, everywhere, all the time.</p><p>Another shift I noticed was in how I connected with people. When I stepped back from social media, some connections naturally faded, those that were mostly kept alive by likes, stories, and casual replies. And that was okay. What remained were the people who genuinely checked in, who made the effort to stay in touch beyond the feed. It made space for deeper, more intentional friendships, the kind built on real conversations, not just digital presence.</p><p>Then something unexpected happened, something I had quietly been hoping for. I moved into a new role in the education space. Still a PM, but in a completely different environment. I’ve always been drawn to the education and EdTech space. That shift made me feel like I had fully stepped away from the fast-paced tech world. Project management is still at the core, but the tone, culture, and pace are different. Less buzz. Fewer buzzwords. More purpose. More patience. The shift from tech to education and from always online to mostly offline brought a kind of balance I didn’t expect.</p><p>I’m not writing this as some grand declaration that social media is bad. It’s not. It really comes down to how we use it. It still has value, and who knows, I might return to it more actively someday, especially for professional use.</p><p>For over a year now, I’ve been enjoying this slower pace, more quiet, more reading, and more time to be present.</p><p>And that feels like a shift worth holding onto.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7df3042b908f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Accessibility Story Behind Deprecated HTML Elements]]></title>
            <link>https://medium.com/@sumudusiriwardana/the-accessibility-story-behind-deprecated-html-elements-98396a877893?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/98396a877893</guid>
            <category><![CDATA[html5]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[html]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Fri, 20 Sep 2024 13:34:14 GMT</pubDate>
            <atom:updated>2024-09-27T00:55:00.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6AmbYDlM5Wlwp2ePluYIng.png" /><figcaption>A blog cover image titled “The Accessibility Story Behind Deprecated HTML Elements.</figcaption></figure><p>I attended the <a href="https://conference.webaim.org/">Web Accessibility in Mind Conference</a> a few weeks ago, and the sessions gave me valuable new perspectives on accessibility. I kept thinking about some of the design choices we make when developing products and services as developers, product managers, designers, or anyone contributing to them and how we can advocate designing for an inclusive and equitable user experience with these choices.</p><p>Interestingly, right after the conference, I came across a cool design created with a marquee tag. It explained how easy it was to use this HTML element and whether we should bring it back since it was deprecated in HTML5. As “accessibility” kept running through my mind, that design made me think about why some HTML elements, once so popular, are now deprecated.</p><h3>Why are HTML elements deprecated?</h3><p>Over time, with evolving web technologies and a better understanding of how to structure and style content and pages, they were eventually deprecated as better ways for structuring and styling content emerged. Although these elements were deprecated, they are sometimes still available due to backward compatibility and their future removal (which we call “sunsetting” a feature). So, we can still use some of these elements, but they are discouraged to use for valid reasons.</p><p>There are several reasons for deprecating these elements. One main reason is the separation of concerns. Once the HTML standard introduced the versioning system, CSS and JavaScript became the norm for handling styling and behavior. The role of HTML shifted to focusing solely on structuring the content. This separation made some older HTML elements that blended structure and styling, such as font, big, and small, redundant and eventually led to their deprecation.</p><p>Accessibility has also been a key factor in deprecating some HTML elements. Some older HTML elements, like marquee and blink, were not designed with accessibility in mind, making these tags visually distracting and also making it difficult for screen readers and other assistive technologies to interpret or interact with the content properly. Some of these elements could even cause a health hazard. For example, flashing or blinking content can trigger seizures in someone with photosensitive epilepsy. So, there are <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-does-not-violate.html">technical requirements issued by WCAG 2.0 from W3C</a> for flashing and flickering contents. This emphasis on accessibility led to the deprecation of several HTML elements, which prioritized visual effects over user inclusivity.</p><p>Let’s dive into a few specific examples to understand why they were deprecated and how we can learn from these decisions to build better, more accessible websites.</p><h4>The Accessibility Story Behind Deprecated HTML Elements</h4><ol><li><strong>marquee</strong></li></ol><p>Microsft introduced the marquee tag in the 1990s. Remember those old, retro websites with moving text or images? Those classic screen savers with floating shapes and text? While it was fun and impressive to develop web pages with this effect, it was not supported across all browsers and was not a part of any official HTML standard. Soon, developers realized the main issues and the accessibility problems it was causing.</p><p>One of the main accessibility problems with this effect was that the constantly moving text was distracting, and there was no option for users to stop scrolling except to close the web page. Even worse, screen readers struggled to interpret the content within a marquee element. Those who relied on assistive technologies could easily miss important information. Because of these issues, the marquee element was deprecated.</p><p>However, the concept of moving text or images is not obsolete. Although you can still use this tag, it’s better to avoid using it. Instead, we can use CSS and JavaScript to design the same effect with accessibility in mind, providing controls for users to pause or stop animations if they find it distracting. While creating impressive visual designs, it’s important to ensure they are accessible to everyone and follow accessibility guidelines.</p><p><strong>2. </strong><strong>blink</strong></p><p>Netscape introduced the blink element a few months before Microsoft introduced the marquee. This tag did exactly what it sounds like, giving the text a blink effect. Like the marquee tag, web creators used this tag to grab users’ attention. They created visually stand-out content to highlight special offers, warnings, or anything that should be highlighted on web pages.</p><p>Some users found this blinking effect really annoying, and it also caused serious accessibility issues. Users with cognitive disabilities might find it really hard to focus on other parts of the page due to this effect. Also, flashing or blinking content can trigger seizures in someone with photosensitive epilepsy, which makes this effect dangerous to some and a potential health hazard.</p><p>The blink tag was eventually decreased due to these concerns and was never a part of HTML standards. Although we can use CSS and JavaScript to create the same effect, ensuring the design follows the accessibility standard is important since it can cause serious harm to some users. If you want to refresh your mind on the technical requirements for flashing and flickering contents, check the <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-does-not-violate.html">guideline issued by WCAG 2.0 from W3C here</a>.</p><p><strong>3. </strong><strong>frameset and </strong><strong>frame</strong></p><p>Netscape introduced the frame and frameset in 1996. The primary use of these tags is to split a website into different sections or frames to display multiple documents in a single view. Designers and developers could improve the page loading time by separating elements of the web page, like headers and navigation bars, from the main content. This was useful back then when most users had slow internet connections.</p><p>Although they improved the loading time, frames introduced a whole set of usability and accessibility issues. For example, frames made it difficult for users to bookmark specific pages or use the back button effectively. Also, frames were not compatible with responsive web design. One of the major accessibility issues was that the content inside frames was difficult to access and index, making websites less accessible and harder to find.</p><p>Instead of frames, we can create better layouts and complex, responsive designs that work seamlessly across all devices with CSS Flexbox and Grid. Modern layout tools provide far greater control and accessibility than frames ever could.</p><p><strong>4. </strong><strong>applet</strong></p><p>The applet was introduced with HTML 3.2, released in 1997, and it was highly popular during the mid-to-late 1990s due to the rich possibilities of adding interactive content to websites. Java applets brought an exciting and new level of interactivity to the web by enabling features like games, dynamic charts, and media playback.</p><p>However, besides the security and compatibility issues, the &lt;applet&gt; created major problems for accessibility. The content inside a Java applet was often a black box to screen readers and other assistive technologies. For users with disabilities, this issue made it nearly impossible to interact with or even understand the content within the applet.</p><p>The applet element was deprecated when the HTML 4.01 specification was released in December 1999. We can now create more secure, accessible, and widely supported interactions on websites using JavaScript and other web technologies.</p><p><strong>5. </strong><strong>dir</strong></p><p>The dir was introduced to create multi-column directory lists, specifically to present a list of items, such as file directories or links, in a compact format. However, it wasn’t as flexible or semantically clear as the ul (unordered list) and ol (ordered list) that we commonly use today.</p><p>The ul and ol tags allow us to create accessible lists by providing clear, structured ways to present information with better semantic meaning, making it easier for screen readers and other assistive technologies to interpret the content. So, the ul tag became the standard when the dir was deprecated in HTML 4.01.</p><h4>Why understanding deprecated elements matters</h4><p>As web designers and developers, it’s important to understand the reasoning behind these deprecations to know why certain elements were phased out. This could be related to several factors:</p><ul><li><strong>Separation of concerns</strong>: Keeping content structure (HTML), style (CSS), and behavior (JavaScript) separate allows for cleaner, more maintainable code.</li><li><strong>Security</strong>: Elements like applet introduced security vulnerabilities.</li><li><strong>Accessibility</strong>: Older HTML elements like marquee and blink were not designed with accessibility in mind and created barriers and issues for users with disabilities.</li></ul><p>By understanding these factors, we can make more informed choices in our design and development practices, ensuring that we avoid past mistakes and create more accessible, user-friendly websites.</p><h4>Conclusion:</h4><p>While it’s fun to look back at the quirky, nostalgic elements of early web design, we must prioritize inclusivity and accessibility in modern web development. The decisions we make today will shape users’ experiences tomorrow. So, when tempted to use impressive visual effects, remember the lessons from deprecated HTML elements and make sure your designs are accessible to everyone.</p><p>Feel free to connect with me on <a href="https://twitter.com/sumusiriwardana">X (Twitter)</a> and <a href="https://www.linkedin.com/in/sumudusiriwardana/">LinkedIn</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98396a877893" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dealing with Difficult Stakeholders]]></title>
            <link>https://medium.com/@sumudusiriwardana/dealing-with-difficult-stakeholders-1609eaf82466?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1609eaf82466</guid>
            <category><![CDATA[stakeholder]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-manager]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Mon, 05 Aug 2024 14:07:53 GMT</pubDate>
            <atom:updated>2024-08-05T15:58:30.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gPcWqShAAqJwS7shSRrYqw.png" /></figure><p>Anything that involves humans is bound to come with its fair share of complexities. Whether it’s working on a team project, managing a household, or even just navigating daily interactions, human behavior’s unpredictability can throw unexpected challenges your way. In any project, product, or business, managing stakeholders isn’t just a box to check off. It’s the foundation of success. Your stakeholders’ support can make or break your project. That doesn’t mean that you have to say yes to everyone and make everyone happy all the time, which is impossible. However, whether you’re a project manager, a team leader, or anyone leading a project, product, or business, knowing how to navigate difficult conversations, tackle challenging situations, and remove roadblocks is essential to keep things moving forward.</p><p>While I only had a brief module on stakeholder management during my PM studies, the real lessons came from years of hands-on experience, learning through trial and error. Over time, I discovered that building long-term, trustworthy relationships with stakeholders is not only key to success but also essential for effectively managing difficult situations. It’s about knowing when to stand your ground, when to compromise, and always keeping the project’s best interests at heart. Here are a few tips I’ve learned along the way.</p><h3>1. Prioritize Stakeholders</h3><p>When dealing with challenging stakeholders and potential issues, the first step is to map out all the stakeholders involved and understand their level of influence and interest in the project or product. This will help you identify at least one stakeholder who might pose challenges or have high demands throughout the project cycle. By being proactive and planning your communication, engagement, and information sharing strategies with these stakeholders, you can lower the chances of conflicts in the future and gain their early collaboration.</p><p>Remember that the intention here is not to categorize stakeholders as “good” or “bad.” Instead, it is to identify potential risks of future conflicts that could cause project delays or obstacles. This method has always helped me identify all the relevant stakeholders, establish relationships positively and early on, and monitor them closely. It’s all about building good relationships and ensuring everything runs smoothly.</p><h3>2. Set Clear Expectations</h3><p>You’ve probably heard the saying, “Prevention is better than cure.” One of the best ways to prevent conflicts with stakeholders is by setting clear expectations from the start. By laying out what’s expected and possible, you create a foundation for smoother collaboration, reducing misunderstandings and aligning everyone towards common goals.</p><p>At the beginning of every project, during the kickoff meeting, I take the time to clearly explain the goals, timelines, limitations, everyone’s role, and communication methods, including how often we’ll check in. I make sure everyone understands and addresses any concerns right away. Also, whenever I set up meetings with stakeholders, I ensure that the agenda is clear, and the expected outcomes are communicated in advance. This approach has consistently helped get everyone on the same page from the start, avoiding surprises and minimizing misunderstandings down the road.</p><h3>3. Constant Communication</h3><p>James Clear wisely said, “It’s generally better to over-communicate. Silence frustrates and confuses people. Better to communicate early and often.” This is especially true when it comes to stakeholder management. Good communication is essential in any relationship, but great communication is what builds trust. It’s not just about showing stakeholders that you’re on top of things, reliable, and working in their best interest. It’s also about keeping the lines of communication open for feedback, sharing information proactively, and trusting them to make informed decisions based on regular updates.</p><p>For example, imagine your client is expecting a feature release in the next quarter, something the management has promised. However, your team is concerned that they may not be able to deliver on time and might need to push the release to the following quarter. While it might be uncomfortable to share this news with the client, it’s crucial that they’re informed about the situation as early as possible. This way, they can make an educated decision and discuss alternative solutions, rather than waiting until the next quarter and facing disappointment and potential conflict when the feature isn’t delivered as expected.</p><h3>4. Be Kind, Empathetic, and Diplomatic</h3><p>Dealing with difficult situations requires a lot of diplomacy and emotional intelligence. Most of the time, to a stakeholder’s eyes, you’re seen as the bouncer or the gatekeeper. But instead of closing doors, keep them open. Show them you’re always ready to listen, collaborate, address their concerns, and fix issues. Melt them with kindness, and you’ll find that even the most difficult stakeholders can become more cooperative and open to collaboration.</p><p>I once took over an internal project halfway through, relying on shared resources from another unit. These team members were crucial for meeting our deadline, but they couldn’t allocate the necessary time because of their workload under their unit head. I’ve been trying to schedule a meeting with the unit head for weeks to discuss the issue, but he hasn’t given me an opportunity. I also couldn’t catch him for a casual chat because he’s been avoiding me. After a few more deliberate attempts and with some help from another colleague, I was finally able to set up a meeting with him to discuss the issue.</p><p>At first, he was reluctant to be open and mentioned the workload and high priorities of his team, which I had already checked and knew were lower than he suggested. But after some back and forth conversation and actively listening to his concerns and reasoning, I realized the real issue. The team members had been assigned to my project without consulting him first, and he felt threatened by the loss of control over his team. I apologized for the oversight and promised to keep him informed about task timelines and priorities, ensuring he’d be involved in future resource-sharing discussions. This approach helped us solve the problem and strengthened our working relationship for the future.</p><h3>5. Understand Their Needs and Listen Carefully</h3><p>When dealing with difficult stakeholders, it’s important to recognize that they’re often pushing for something they deeply care about, whether it’s their team’s success, meeting specific targets, or ensuring the needs of end-users are met. Instead of looking at their demands as obstacles, listen carefully and try to understand the underlying reasons behind them. What pressures are they under? What are they trying to achieve?</p><p>The “5 Whys” technique can help answer these questions and uncover the root cause. Often, the initial conversation only scratches the surface, and stakeholders may not immediately reveal what they want and why they’re resistant or unhappy. Sometimes, they might need help understanding the root cause themselves. It’s your job to ask, “Why do you think that is?” or “Why do you feel that way?” after each response, digging deeper to uncover the real demand or issue. By seeing the situation from their perspective and getting to the heart of the matter, you can find common ground and work towards a solution that benefits everyone.</p><h3>6. Address the Root Cause</h3><p>Suppose you don’t address the root causes of the issues as early as possible. In that case, you’ll find yourself constantly dealing with and negotiating with stakeholders, which may become increasingly difficult over time. Stakeholders won’t trust you just because you’re diplomatic, kind, and easy to work with. They’ll trust you when you resolve their issues and get the work done. So, it’s crucial to identify root causes, find solutions, plan fixes, and communicate clearly with your stakeholders about when those issues will be resolved.</p><p>I once had a team member who was disengaged during our retrospective meetings. I tried adding some fun activities to encourage participation, but it didn’t work. During a one-on-one meeting, he explained that he didn’t see the point of retrospectives if we weren’t actually having serious conversations and implementing the solutions we discussed. In his previous teams, retrospectives had become just a routine of noting down things without real action.</p><p>This feedback gave me a new perspective. It made me realize the importance of addressing concerns and root causes immediately. After this conversation, we made retrospectives a time to celebrate wins, truly solve the team’s issues, and find ways to improve rather than just going through the motions. By focusing on real solutions and meaningful conversations, we were able to create a more productive, trustworthy, and engaged environment.</p><h3>7. Negotiate and Find Common Ground</h3><p>Managing difficult stakeholders is not so different from negotiating with a lawyer. They’re meticulous, relentless, and always looking for the slightest advantage. You need to be well-prepared, stay calm under pressure, and be ready to find common ground without giving up too much. But remember, it isn’t about winning. It’s about finding a solution that works for everyone involved. When working with difficult stakeholders, start by looking for areas where your goals align with theirs. Focus on these commonalities to build a foundation for collaboration, ensuring that both sides feel heard and valued.</p><p>However, there will be times when you can’t get everything you want. In these situations, being ready to compromise is key. Flexibility shows that you’re committed to finding a solution that benefits everyone, even if it means adjusting your own expectations. By finding a middle ground, you can resolve conflicts and keep the project on track, all while maintaining strong, cooperative relationships with your stakeholders.</p><h3>8. Don’t Take Things Personally</h3><p>If you take criticism and closed-off reactions personally, you’re setting yourself up for a rough ride throughout your projects. The work is never about you. Stakeholders often have reasons for disagreements and conflicts, and while it’s easy to internalize that as something personal, it’s important to recognize that it’s usually not the case.</p><p>This doesn’t mean you have to put up with rude behavior or discrimination (handling that deserves a post of its own). In my previous experience, that unit head kept rejecting my meeting requests and avoiding me altogether, and it would have been easy to assume he had something against me personally. But the reality was, he didn’t even know me, and his frustration was rooted entirely in something else. The real issue was that his team members were being reassigned without his approval.</p><p>In situations like these, it’s important to step back and consider why someone is acting the way they are. By not jumping to conclusions and taking things personally, you can begin to understand the real issue at hand.</p><h3>9. Saying ‘No’ the Right Way</h3><p>Steve Jobs once said, “Focusing is about saying no.” But let’s be honest, saying “no” is easier said than done. It’s even harder to do it without burning bridges or coming across as rude. Yet, pushing back in certain situations is necessary, and being assertive without being rude is not always easy.</p><p>When working on projects, you’re often faced with requests, ideas, or demands that may not align with the project’s goals, and saying “no” becomes essential to maintaining focus and ensuring the project’s success. The goal is to be assertive without coming across as harsh. Start by understanding the request thoroughly and gathering any necessary data or research to support your decision. When you push back, explain your reasoning clearly, showing that it’s not a personal rejection but a decision based on the project’s best interests.</p><p>Always choose the right communication channels, and back up your reasoning with solid research, data, and information. I highly recommend setting up a meeting or video call instead of explaining things over email. Text is a one-way communication, and your message can easily be misinterpreted. But when you’re face-to-face, whether in person or via video, you have the chance to explain your decision, counter with data, and ultimately gain stakeholder buy-in without burning bridges in the process.</p><h3>The Bottom Line</h3><p>When it comes to managing stakeholders, teams, or clients, there’s no one-size-fits-all approach. Every person, relationship, and situation is different, and that’s what makes human interactions both challenging and rewarding. Instead of rigid instructions, we rely on guidelines, best practices, and shared experiences to navigate these complexities. Success in these situations lies in your ability to understand the unique dynamics at play and adapt your approach to match them, build trust, and foster an environment where collaboration can thrive, even when things get tough.</p><p>Every experience brings new lessons, and we all have our own ways of navigating tough stakeholder relationships. What’s worked for you? Share your advice and experiences in the comments!</p><p>Feel free to connect with me on <a href="https://twitter.com/sumusiriwardana">X (Twitter)</a> and <a href="https://www.linkedin.com/in/sumudusiriwardana/">LinkedIn</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1609eaf82466" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering the PMP Exam: Essential Tips for Success]]></title>
            <link>https://medium.com/@sumudusiriwardana/mastering-the-pmp-exam-essential-tips-for-success-33247614e70c?source=rss-5acfe1a3c3d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/33247614e70c</guid>
            <category><![CDATA[pmp]]></category>
            <category><![CDATA[pmp-certification]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[pmp-exam]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Sumudu Siriwardana]]></dc:creator>
            <pubDate>Tue, 25 Jun 2024 13:10:09 GMT</pubDate>
            <atom:updated>2024-08-04T23:54:55.836Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*81r-lLzCpEcLEtOqStemOA.png" /></figure><p>Last month, I attended my first PMI chapter meeting, where I was seated with two other members next to me, one who had earned her PMP a year ago and another who was still preparing for the exam. As we introduced ourselves, our conversation naturally flowed into our experiences with the PMP exam, study processes, and resources. I took the PMP exam online that morning and was nervously waiting for the results. The next day, I was over the moon to see that I had passed with “Above Target” scores in all three domain areas.</p><figure><img alt="My PMP certification and the results breakdown" src="https://cdn-images-1.medium.com/max/1024/1*ckQkzjFoycyWFMXfMYIApQ.png" /></figure><h3>Preparation and Resources</h3><p>It took me nearly three weeks to study and prepare for the PMP exam. I was already familiar with the PMP processes and agile concepts through my CAPM and CSM certificates and had almost a decade of work experience. Even so, preparing for and sitting through this four-hour exam can be time-consuming, confusing, challenging, and stressful. Therefore, I thought of sharing my experience, a few resources, and tips that might help you strategize your study plan and exam prep.</p><h3>Resources</h3><p>There are many resources available to prepare for the PMP exam. To maximize the efficiency of my study, I applied the Pareto principle. After thoroughly researching the options and considering what would best suit my study methods, I selected a few key resources besides the PMBOK and Agile Practice Guide by PMI to maximize my learning and results.</p><h4>1. <a href="https://www.udemy.com/course/pmp-certification-exam-prep-course-pmbok-6th-edition/">PMP Certification Exam Prep Course by Andrew Ramdayal</a></h4><p>Once I decided to take the PMP exam, I enrolled in this course to earn the Professional Development Units (PDUs) necessary for the PMP application process. Andrew has structured the course in a very simple and easy-to-understand manner, dividing it into sections based on traditional, agile, and hybrid methods, ethics, mindsets, and tips. Even if you have a certified PMI trainer to earn your PDUs, I recommend checking out <a href="https://www.youtube.com/@AndrewRamdayal">Andrew’s YouTube channel</a>, where he posts all his tutorials and tips.</p><h4>2. <a href="https://store.rmcls.com/pmp-exam-prep-eleventh-edition">Rita Mulcahy’s PMP Exam Prep</a></h4><p>This book is very helpful in understanding the PMBOK and the various process groups, including agile methodologies. It provides the necessary guidelines and tips on what PMI expects and what to anticipate on the exam. Additionally, each chapter includes practice questions to test your knowledge and identify weak areas.</p><h4>3. <a href="https://www.youtube.com/@davidmclachlanproject">David McLachlan’s YouTube Channel</a></h4><p>This channel offers tutorials, questions, and explanations that are extremely helpful for students at any level in understanding concepts and answering questions. During his question videos, he also teaches how to break down the question into parts, use keywords to identify answers, eliminate options, and strategically align responses with concepts.</p><h4>4. <a href="https://tiaexams.com/course/tiapmpsimulator">TIA Exam Simulator by Andrew Ramdayal</a></h4><p>This simulator includes six mock exams and video explanations for each question. It helps you understand how to break down questions and select the correct answers.</p><h3>Study Tips</h3><h4>1. Understand your learning style:</h4><p>Unless you have a photographic memory or enjoy reading big books and memorizing them, reading the PMBOK and other materials from start to finish can be frustrating and unproductive. Understanding your learning style and how you comprehend fundamentals is crucial in preparing for this exam. I prefer to break down topics and simultaneously use videos and reading materials to grasp the concepts. I then explain these concepts verbally or in writing to reinforce my understanding and identify gaps. I applied this learning style to understand new concepts and remember old ones, using Andrew’s videos, PMI materials, and Rita’s book as references.</p><h4>2. Do not just memorize the topics:</h4><p>The PMP exam consists of situational questions where you need to understand a scenario and apply your knowledge to achieve the best possible outcome. You need a deep understanding of the knowledge areas, process groups, and processes. Once you grasp these concepts, you can logically identify the inputs, tools &amp; techniques, and outputs (ITTOs) associated with each process without memorizing them. It’s essential to understand them well enough to recognize the current process when faced with a situation or technique, determine what actions to take, and identify the next steps. Additionally, understand the concepts behind each formula as much as the calculations themselves. The questions focus more on interpreting a situation based on the formula results than the calculations alone.</p><h4>3. Learning the Mindset:</h4><p>One of the most valuable tips I got from Andrew’s course is understanding how to develop the necessary mindset. Shifting from a plan-driven to a change-driven mindset and adopting the PMI mindset despite years of experience is crucial for tackling each question. Situational questions are designed to identify whether the scenario is plan-driven, change-driven, or hybrid, and you must choose the best answer accordingly. It’s important always to prioritize servant leadership, face-to-face communication, minimizing escalations, inclusivity, proactive management, and adherence to standards and regulations.</p><h4>4. Set a realistic goal and deadline:</h4><p>It’s important to understand your schedule and how much effort and energy you can invest, and based on that, set a realistic deadline for yourself. Many people apply for the exam and wait until they feel fully prepared before scheduling it. However, time tends to expand without a clear deadline, leading to procrastination and delaying the exam, often until the next curriculum change. Once you schedule the exam, you’ll be motivated to ensure you are prepared by the exam date.</p><p>When I was applying, I had some free time to prepare, so once my application was approved, I scheduled my exam for one week later, knowing I had a whole week to dedicate to longer study sessions. Familiarity with the concepts and the right mindset helped me fast-track my revision and focus more on practice. If I had set the date further in the future, I might have lost momentum and motivation to meet the deadline.</p><h4>5. Practice, Practice, and Practice</h4><p>The best way to prepare for the exam is through practice. Utilize questions from simulators, YouTube, and other sites to test your knowledge and apply what you’ve learned, even though they might not be as challenging as actual PMP questions. Practicing these questions allows you to reinforce what you’ve learned, which is extremely helpful for remembering concepts. I used questions from Rita’s book, Andrew’s TIA simulator, and David’s YouTube channel. These resources helped me understand the types of scenarios to expect and learn how to break down these questions to find the correct answer.</p><h3>Exam Tips</h3><h4>1. Exam Day Preparation</h4><p>I took the exam online because I preferred the comfort of my own environment rather than driving to an unfamiliar location. When taking the exam online, having a completely distraction-free and isolated space is crucial. Proctors monitor and inspect you through a webcam during the exam. Once you log into the system, they will ask you to show your surroundings and inspect all your items. Ensure you don’t keep anything on your desk except the laptop. The proctors will stay with you until you finish the exam, so make sure no one enters your sitting area, maintain quietness, and remain seated unless you are allowed to take a break. Breaking any of these rules will immediately result in being thrown out of the system and having your exam canceled.</p><h4>2. Maintaining Focus</h4><p>This is a long, stressful exam, and you must be 100% focused for 4 hours to understand the subtle differences between questions and each answer.</p><ul><li>Make sure you have a good meal before the exam.</li><li>Keep a glass of water to stay hydrated, but don’t drink too much.</li><li>Ensure you have a reliable internet connection and power.</li><li>Take the two 10-minute breaks during the exam. They’ll help you refresh your mind, move around, and use the restroom.</li><li>If you don’t like white mode and can’t stare at the screen for a long time, reduce the brightness of your screen before your eyes get blurry.</li></ul><h4>3. Answering the Questions</h4><ul><li>One strategy I used to identify whether a question belongs to traditional, agile, or hybrid methods is to look for keywords. If the question mentions keywords related to a particular method, I filter the answers corresponding to that method.</li><li>If the question is too long, I first read the answers to get an idea, then the last sentence of the question, and finally, the whole question. This helped me quickly understand the scenario and highlight the keywords.</li><li>I used the elimination method to filter answers. Often, at least two answers can be eliminated due to irrelevance, leaving two very similar answers that are hard to choose between if you don’t have the right mindset.</li><li>Leverage the right mindset, not just experience, to understand the first, next, and best options and select the correct answer.</li><li>If you need more time to think or are unsure, flag the question and move on to the next one. You can review all flagged questions before submitting.</li></ul><h3>Conclusion</h3><p>Earning the PMP certification requires knowledge, experience, and practice. It’s one of the most recognizable qualifications for a project manager or anyone who leads projects. I hope this helps you understand how to plan your study time and prepare for your exam. I would love to hear from you if you have any additional tips or resources to share or if you have any questions.</p><p>Wishing everyone good luck on your journey to PMP success!</p><p>Feel free to connect with me on <a href="https://twitter.com/sumusiriwardana">Twitter</a> and <a href="https://www.linkedin.com/in/sumudusiriwardana/">LinkedIn</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33247614e70c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>