Main Takeaways:
-How product debt accumulates
-Types of product debt, including technical and design debt and how they differ
-How to incorporate product debt into strategy
-How product debt translates into increased value
6. How debt happens
Get organized
Get smart
Get results
Agenda
Manage debt,
maximize value.
7. Prototype
Prod Release
Legacy Use Case
Global Expansion
Scale Up
Concurrency
Integration with
New Market Tool
DEBT
Technical debt Product debt
Feature bloat Scope creep
Low value features
14. Debt categories:
Where does your debt fall?
UNPROFESSIONAL PROFESSIONAL
ACCIDENTAL
INTENTIONAL
Good
debt
Mistakes and
surprises
happen
Experience
gap
Bad
debt
15. Debt categories:
Where does your debt fall?
UNPROFESSIONAL PROFESSIONAL
ACCIDENTAL
INTENTIONAL
Good
debt
Mistakes and
surprises
happen
Experience
gap
Bad
debt
24. How NOT to demonstrate impact
“We need to use Splunk for logging because everyone uses Splunk”
25. Our objective of {measurable goal} can be
improved by {specific actionable task}. If we
don't address this, we will immediately feel the
pain through {quantifiable impact}. In the
future, we anticipate {long term implications}.
28. Conversion through
impact analysis and
strategic choices
UNPROFESSIONAL PROFESSIONAL
ACCIDENTAL
INTENTIONAL
Good
debt
Mistakes and
surprises
happen
Experience
gap
Bad
debt
33. • Devbridge team began work on an existing
client product with considerable debt
• Sequenced technical module work according
to business priority
• Reduced delays on new feature development
from 12 months to 3 months
• New revenue streams available as each
feature area was “unlocked” on the back-end
Strategic approach for services refactoring
overhaul
De-risking with up-front investment
for complex features
34. • Goal: determine whether an existing tool will
generate enough demand in a new market
• Implemented a representative subset of
functions for an industry event
• Client was able to gather actual user intel to
decide whether to continue with the current
path or pivot to invest in other features
Releasing a portion of features to test a new market
Choosing to incur good debt as an
early-to-market strategy
35. • Mobile apps (iOS and Android) which
duplicated web features and required
significant maintenance
• Team recommended a shift to Progressive
Web App based on industry trends
• Benefits: up to 75% reduction in ongoing
maintenance, increased speed to market
Spinning an industry shift to PWA to a
client’s advantage
Minimizing or capitalizing on impact
of technology shifts
36. • Tendency to postpone long-term decisions leads
to increased total cost of ownership
• Capture intentions and implications of future
vision early
• Include debt work in each release to future proof
your product, reduce refactoring, and prevent
later architectural blockers
• Example: Data model planning for globalization
accounting for language selection, storing
multiple translations, date formats
Expansion and scalability
Spreading costs of scalability and
technical maturity across multiple releases