Project Jam #2☕ - Djordje Grujovic - Building Bridges: How Technical Knowledge Enhances Project Management
Welcoming a Guest Article: Djordje Grujovic
Hey, fellow Leader 🚀,
Welcome to a very special edition of The Long Missing Sow. Today, we have an article by Djordje Grujovic, an experienced Engineer and Project Manager. I invited Djordje to write an article and am excited to share it with you. Please have a look at Djordje’s LinkedIn and feel free to connect with him. Without further ado, let’s read what Djordje Grujovic has to share with us.
Hello, Djordje here,
When I first transitioned from software engineering to project management, I thought my technical background might be a liability. After all, weren’t project managers supposed to focus on timelines and deliverables rather than APIs and frameworks? But as I’ve come to realize, my technical background have been one of my greatest assets - not just for understanding the work but for bridging the gap between teams and stakeholders.
The Great Estimation Debate
One of the first challenges I faced was explaining development timelines to upper management. Example: a developer gives an estimate of three weeks for a task (or maybe two), and a stakeholder hears, “It’ll be done tomorrow”. Somewhere between the two lies a land of frustration and misaligned expectations.
As a software engineer, I knew how those three weeks would be spent: debugging, testing, reworking code after unexpected edge cases pop up. But explaining this to someone with no technical background required a different approach. My solution? Borrowing a bit of storytelling magic from my dev days.
Speaking Two Languages
I found myself acting as a translator - fluent in both “dev speak” and “business speak.” To developers, I broke down stakeholder priorities into actionable tasks, making sure the team understood not just what to do but why it mattered. To stakeholders, I explained technical complexities in relatable terms - like comparing debugging to untangling a pair of headphones that have been in your pocket all day (if anyone still use such headphones).
When it came to communicating timelines, I started using metaphors. Estimating a software feature became like building a house: “Sure, we can lay the foundation quickly, but you wouldn’t want to move in without walls, plumbing, or a roof.” Suddenly, stakeholders stopped pushing for faster timelines and started appreciating the craftsmanship behind the code.
Trust and Transparency
This approach worked wonders. Developers felt heard because their challenges were accurately represented, and stakeholders appreciated the clarity and transparency. One moment was when a stakeholder told me, “I never understood why features took so long, but now it makes sense. You make it sound so...logical!” That’s when I knew my technical background wasn’t just helpful - it was essential.
Why This Matters
Having technical knowledge can be a valuable plus when communicating with your team, helping to foster better understanding and collaboration, while your ability to simplify complex ideas earns trust with clients and upper management. It’s not about choosing one side; it’s about building a bridge. As a project manager, you’re the architect of that bridge, ensuring smooth communication and aligned expectations.
Bringing It All Together
If you’re a project manager stepping into the world of technical teams, don’t be afraid to ask questions. And if you’re a developer eyeing a move to management, know that your technical knowledge is a superpower. Just remember to sprinkle in some storytelling—it’s amazing how much smoother things go when everyone speaks the same (or at least a relatable) language.
About the author
I’m Djordje Grujovic, a software engineer and project manager, with nearly 10 years of experience in the industry. Co-founded two startups. I’m passionate about turning startup ideas into amazing products. I had the opportunity to participate in several startups, developing a product from scratch and building a team that would later continue to work on product development.
Let’s connect on LinkedIn if you want to chat about startup ideas, building teams, or tackling exciting new challenges together.
That’s it. If you find this post useful please share it with your friends or colleagues who might be interested in this topic.
Cheers,
Djordje & Artur