001✓ copiedspec
Data product management, installed
Twelve to sixteen weeks to build the data product management function: the role, the hiring loop, the intake process, proven by shipping real products.
- Duration
- 12 to 16 weeks
- Commitment
- 2 days a week
- Price
- Quoted per engagement
002✓ copieddetail
What does a data product manager actually do?
A data product manager owns a data product the way a product manager owns software: they know who uses it, what decision it changes, and when it should be retired. They are not analysts with a new title and they are not project managers. The job is deciding what gets built and, more importantly, what does not.
Almost nobody sells this as an engagement, and almost every article about the role is written by someone who has never hired one. I hired seven, one at a time, over about eighteen months.
Why a company needs one
The pattern is the same everywhere I have seen it. Requests arrive from marketing, from product, from finance, and the data team works through them in roughly the order they arrived. Good analysts spend their weeks building things that get used twice. Nobody can tell you what the data organisation shipped last quarter, because it shipped forty things and none of them were products.
The reason there is no way to say no is that saying no requires a stated basis for comparison, and there is none. The product layer is that basis.
How the twelve to sixteen weeks are spent
Weeks one to three: the role. Written for your company, your politics, your P&L. The generic spec is why most of these hires fail.
Weeks two to eight: hiring. I run the loop with you and sit in the interviews. The exercise I use is simple: take a real request from your backlog and argue for not building it. It sorts candidates faster than anything else I have tried.
Weeks four to sixteen: shipping. We build two or three real data products while the process is being designed, because a process that has never survived contact with a delivery is a proposal, not a process.
Throughout: the intake. The forum where prioritisation actually happens, with named attendees and a cadence. This is the part I got wrong the first time and it is covered in the case study.
What I would tell you before you buy this
I hired the seventh data product manager before I fixed the intake process. For the first year they spent too much of their time being a more expensive version of the ticket queue, because I had given them ownership without giving them a forum where prioritisation was real. Two of them nearly left over it.
If I did it again the intake process and the forum would exist in week one with two people, rather than in month nine with six. That sequencing is most of what you are paying for here.
003✓ copieddeliverables
What you get
- The data product manager role defined for your company specifically, not a generic job spec
- The interview loop and scorecard, including the exercise that reveals whether a candidate can say no
- Support through your first two hires, from screening to offer
- An intake and prioritisation process, with the forum where prioritisation actually happens
- Two or three data products shipped end to end while the process is being built
Not for
- Teams under about ten people in data. You do not need a product layer yet, you need clearer ownership.
- Companies that want the title without the authority. A data product manager who cannot decline a director is an expensive coordinator.