An Introduction to Technical Product Management

Jensen Loke
3 min readOct 21, 2018

As we bury our heads to establish new norms, break the barriers and shift towards the digitization, there is often ambiguity about what technical product managers do, and what are they actually here for. As the saying goes, there can never be enough time spent on aligning the team, and here, I would cover about what I think technical product management means, as the basis of the discussion for debate.

Depending on the type of organization you come from or are going towards, the term product management in a rapidly digital organization could mean a lot of different things to different people. The most common titles that Technical Product Managers get confused with are; Business Analyst, IT or Internal Consultants, Project Managers and Product Owners. I won’t cover why these titles are different in this article nor discrediting their relevancy to your organization, but let me attempt to help establish three things about technical product managers. The first, what product managers do, how do they actually do it, and what it means in an organization.

My previous manager once told me, the hardest part of the product manager’s job, is to make complex ideas really easy to understand. In that note, I will make a closing attempt to explain technical product management in the simplest way possible to the layman. Feel free to challenge this! :)

What Product Managers do

Product Managers are in charge of these four elements for their product; Vision

--

--

Jensen Loke

Technical Product Management @temasek digital tech| Building AI & big data products #rootaccess. www.jensenloke.com