top of page
Search

๐Ÿ“ฌ ๐—ช๐—ต๐—ผ ๐—ผ๐˜„๐—ป๐˜€ ๐˜๐—ต๐—ฒ ๐˜๐—ฒ๐—ฐ๐—ต๐—ป๐—ถ๐—ฐ๐—ฎ๐—น ๐—ฟ๐—ผ๐—ฎ๐—ฑ๐—บ๐—ฎ๐—ฝ?

  • Writer: Kjell Moens
    Kjell Moens
  • Jul 31
  • 2 min read

๐˜—๐˜ณ๐˜ฐ๐˜ฅ๐˜ถ๐˜ค๐˜ต-๐˜›๐˜ฆ๐˜ค๐˜ฉ๐˜ฏ๐˜ฐ๐˜ญ๐˜ฐ๐˜จ๐˜บ ๐˜ˆ๐˜ญ๐˜ช๐˜จ๐˜ฏ๐˜ฎ๐˜ฆ๐˜ฏ๐˜ต ๐˜ด๐˜ฆ๐˜ณ๐˜ช๐˜ฆ๐˜ด.

ree

A founder asked me this last month.


Engineering was building internal tools.ย 

Product wanted customer features.ย 

The technical roadmap felt disconnected from the product roadmap.


Sound familiar?


Here's the gap I see at most scale-ups:

๐—ฃ๐—ฟ๐—ผ๐—ฑ๐˜‚๐—ฐ๐˜ ๐—บ๐—ฎ๐—ป๐—ฎ๐—ด๐—ฒ๐—ฟ๐˜€ ๐—บ๐—ฎ๐—ป๐—ฎ๐—ด๐—ฒ ๐—ณ๐—ฒ๐—ฎ๐˜๐˜‚๐—ฟ๐—ฒ๐˜€.ย 

๐—•๐˜‚๐˜ ๐˜„๐—ต๐—ผ ๐—บ๐—ฎ๐—ป๐—ฎ๐—ด๐—ฒ๐˜€ ๐˜๐—ฒ๐—ฐ๐—ต๐—ป๐—ถ๐—ฐ๐—ฎ๐—น ๐—ฐ๐—ฎ๐—ฝ๐—ฎ๐—ฏ๐—ถ๐—น๐—ถ๐˜๐—ถ๐—ฒ๐˜€?


Traditional product management focuses on:ย 

โ†’ User stories and customer needsย 

โ†’ Feature prioritization and deliveryย 

โ†’ Go-to-market alignmentย 

โ†’ Revenue and engagement metrics


But technical platforms need different thinking:ย 

โ†’ Developer experience and productivityย 

โ†’ System reliability and performanceย 

โ†’ Technical debt and infrastructureย 

โ†’ Capability enablement for future features


๐—ง๐—ต๐—ฒ ๐—ฝ๐—ฎ๐—ถ๐—ป๐—ณ๐˜‚๐—น ๐—ฟ๐—ฒ๐—ฎ๐—น๐—ถ๐˜๐˜†: Technical decisions made without product context create the wrong solutions.


Most companies try to solve this by:

โ€ข Making engineering "more product-minded"

โ€ข Having product managers "learn technical skills"

โ€ข Creating endless alignment meetings


But here's what actually works:


๐—ง๐—ฒ๐—ฐ๐—ต๐—ป๐—ถ๐—ฐ๐—ฎ๐—น ๐—ฃ๐—ฟ๐—ผ๐—ฑ๐˜‚๐—ฐ๐˜ ๐— ๐—ฎ๐—ป๐—ฎ๐—ด๐—ฒ๐—บ๐—ฒ๐—ป๐˜ - a hybrid discipline that bridges both worlds.


Technical PMs think about:ย 

โ†’ Platform as product (with internal customers)ย 

โ†’ Technical capabilities as competitive advantagesย 

โ†’ Infrastructure investments as product investmentsย 

โ†’ Developer velocity as a product metric


They translate between:

โ€ข Business strategy โ†” Technical strategy

โ€ข Customer needs โ†” Platform capabilities

โ€ข Product vision โ†” Technical vision

โ€ข Market timing โ†” Technical readiness


๐—ง๐—ต๐—ฒ ๐—ถ๐—ป๐˜€๐—ถ๐—ด๐—ต๐˜ ๐˜๐—ต๐—ฎ๐˜ ๐—ฐ๐—ต๐—ฎ๐—ป๐—ด๐—ฒ๐—ฑ ๐—บ๐˜† ๐—ฝ๐—ฒ๐—ฟ๐˜€๐—ฝ๐—ฒ๐—ฐ๐˜๐—ถ๐˜ƒ๐—ฒ:


๐Ÿง  Technical product management isn't product management for engineers. It's product management for platforms that enable other products. When you treat technical capabilities like products, you start making better technical investments.


๐Ÿ—ฃ๏ธ Do you have technical product managers at your company? How do you bridge the gap between product and engineering roadmaps? Let me know your thoughts in the commentsย 


๐Ÿ™ I help startups / scale-ups design the systems, teams, and technical strategy they need to grow โ€” without burning out, breaking down, or bottlenecking the business.ย 


๐Ÿ” Like this kind of thinking? Follow along for more โ€” or book a quick, no-pressure call.



ย 
ย 
ย 

Comments


© 2021 The Baseline BV

bottom of page