post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

mission statement

Deep dive: Crafting your product vision and mission

Podcast

Connecting fans to creators at Spotify (Dariusz Dziuk, Product Lead, Spotify)

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Join us at #mtpcon London in 2025 – mark your calendars

How Google makes AI work at Enterprise scale – Miku Jha (Director, AI/ML and Generative AI, Google Cloud)

5 ways to invent and simplify as an AI/ML product manager

Why teams often struggle with OKRs: A conversation with Jeff Gothelf

Building your own user experience and software stack: This week’s product news

Anna studied English Literature and History at university. She is new to product management and is enjoying learning more about it.

Anna von Hagen

<p>In this ProductTank Prague talk, <a href="https://www.linkedin.com/in/jan-kaltoun/?originalSubdomain=cz" target="_blank" rel="noopener">Jan Kaltoun</a>, Chief Technology Officer at STRV dives into debt in the eyes of the developer and how to navigate tech debt.</p>
<p>Watch the talk in full, or read here for a summary of his main points:</p>
<ul>
<li>What is tech debt to you?</li>
<li>How did it affect you in your career?</li>
<li>How would you solve it?</li>
</ul>
<h3>How the talk works</h3>
<p>For his talk, Jan asked 20 engineers who worked on a project with tech debt the above 3 questions. This puts the answers through the lens of those who have experienced it first-hand and displays what debt means to the developer.</p>
<h3>What is tech debt to you?</h3>
<p>Jan begins by presenting the answers he gathered to his first question, ‘What is tech debt you?’. He received a handful of answers, which include “a state where the team prioritised a quick solution over a clean one”, “occurs after some time when the project is not maintained regularly”, “a simple solution that is quick to do, but not robust or extendable” and “a nature of any software development”.</p>
<p>These are his takeaways from what tech debt is to engineers:</p>
<ul>
<li>It is inevitable</li>
<li>It is prioritising development speed over output quality</li>
<li>It is postponing issues for future us to solve</li>
<li>It is the lack of maintenance</li>
<li>It is a result of bad architectural decisions and not doing the best job possible</li>
<li>It is unreadable or unclear code</li>
<li>It is the fear of changes</li>
<li>It is a lack of robustness and extendability</li>
<li>It is a “temporary” solution</li>
</ul>
<h3>How have you been affected?</h3>
<p>Jan then moves on to his second question, ‘How have you been affected’ by tech debt. Again, he goes through his answers, which include that “tech debt is a never ending story”, that happens “mostly on quickly growing projects” and “it is always hard to define the line when the costs saved by introducing technical debt are higher than the costs of maintaining an unsustainable codebase”.</p>
<p>The takeaways from how people have been affected by tech debt are:</p>
<ul>
<li>It was very stressful</li>
<li>It meant code was duplicated all over the place</li>
<li>The bad practices bulk up when fragile codebases are hard to refactor</li>
<li>Time pressure was often the culprit</li>
<li>Overcomplicated tech is tech debt too</li>
<li>Long running projects are the ones which suffer the most</li>
<li>Tech debt complexity only tends to grow</li>
<li>Sometimes a little tech debt does not hurt</li>
<li>Sometimes a shortcut is simpler and much faster to develop</li>
<li>Documentation is essential</li>
<li>Tech debt needs to have the perfect balance of the right solution, but also not over-engineered.</li>
</ul>
<h3>How to solve tech debt</h3>
<p>Jan then concludes by looking at how to solve tech debt. The engineers he asked gave a variety of answers, which are all based on the idea that “tech debt is inevitable” and the only way forward is “to minimise it as much as possible”. The solution given is to be careful, organised and calculated with tech debt: “Get time. Refactor. Upgrade”. Jan’s answers recommend that “by documenting tech debt”, encouraging “the refactoring mindset” and to “keep thinking forward on how to prepare the code for the future” it can be made manageable.</p>
<p>Jan’s takeaways on how to solve tech debt:</p>
<ul>
<li>Think about how the code can be decoupled later on</li>
<li>Always make sure to document your tech debt</li>
<li>Stay up to date with the tech and the best practices for it</li>
<li>Do proper code reviews, automated testing can help</li>
<li>Find time to refactor, upgrade and encourage the refactoring mindset</li>
<li>Make continuous improvements part of the process, define clear goals</li>
<li>Assign priority to each piece of tech debt</li>
<li>Do not over-engineer</li>
<li>Don’t be afraid of tech debt, control it</li>
<li>Choose your dependencies wisely</li>
<li>Take to and make agreements with your product managers and clients</li>
<li>Always leave the tech base better and clearer than you found it.</li>
</ul>
<p>Learn more about <a href="https://www.mindtheproduct.com/producttank/" target="_blank" rel="noopener">ProductTank </a>and find some exciting new ways to get involved!</p>

core/freeform

Product Management

It’s the Strategy, stupid – Andrew Martinez-Fonts (VP Product, Honeysales)

LLM workflows for product managers: 3 key takeaways (Niloufar Salehi, Assistant Professor at UC Berkeley) – ProductTank SF

How to survive the next phase of tech – Jonty Sharples (Product and Strategy Consultant)

Transformed: Moving to the product model by Marty Cagan

Product teams in flux – Pendomonium+#mtpcon roadshow: Berlin

AI in practice at Berlin’s leading companies – Pendomonium+#mtpcon roadshow: Berlin

Product teams in flux – Pendomonium+#mtpcon roadshow: Amsterdam

Product teams in flux – Pendomonium+#mtpcon roadshow: London

What’s next for product management in 2024? Nichole Mace (SVP Product and User Experience, Pendo)

“You’re not as competent as you think” 5 lessons from Ken Chin on navigating a product career (CPO, Spark Networks)

Tech debt in the eyes of the developer by Jan Kaltoun

Anna von Hagen