Transformed
Moving to the Product Operating Model
Transformed
Menuju Product Operating Model
How legacy organizations — not just Silicon Valley startups — can move from an IT-style feature factory to a true product company. Based on the book by Marty Cagan (with Lea Hickman).
Bagaimana organisasi legacy — bukan cuma startup Silicon Valley — bisa berubah dari mesin pengiriman fitur ala proyek IT, menjadi perusahaan produk sejati. Berdasarkan buku Marty Cagan (bersama Lea Hickman).
Renaming job titles isn't transformation
Ganti nama jabatan bukan transformasi
Many companies claim to have "gone agile" — daily stand-ups, sprints, Kanban boards. The job title "Project Manager" gets swapped for "Product Manager."
Banyak perusahaan mengaku sudah "adopsi agile" — daily stand-up, sprint, papan Kanban. Job title "Project Manager" diganti jadi "Product Manager".
But underneath, how decisions get made hasn't changed at all: executives still decide which features get built, teams are still evaluated on how much got "shipped," and the roadmap is still a dated list of features.
Tapi di baliknya, cara keputusan dibuat sama sekali tidak berubah: eksekutif tetap menentukan fitur apa yang harus dibangun, tim tetap dievaluasi dari seberapa banyak yang "selesai dikirim", dan roadmap tetap berisi daftar fitur bertanggal.
Agile Theater
New rituals, old decisions. The top-down power structure stays fully intact behind the Scrum ceremonies.
Ritual baru, keputusan lama. Struktur kekuasaan top-down tetap utuh di balik seremoni Scrum.
What is the Product Operating Model?
Apa itu Product Operating Model?
Not just a work framework or a new tool — it's a coherent way an organization operates, built on four interlocking pillars:
Bukan sekadar framework kerja atau tool baru — melainkan cara koheren sebuah organisasi beroperasi, dibangun di atas empat pilar yang saling mengunci:
Empowered Cross-Functional Teams
Tim Lintas-Fungsi Berdaya
Product manager, designer, and engineer work as one team — not a handoff chain.
Product manager, designer, engineer bekerja sebagai satu tim — bukan rantai handoff.
Continuous Discovery
Discovery Berkelanjutan
Teams constantly test ideas with real customers, not one round of research followed by execution.
Tim terus-menerus menguji ide dengan pelanggan nyata, bukan sekali riset lalu eksekusi.
Outcome-Based Objectives
Objective Berbasis Outcome
Given a business problem to solve, not a list of features to ship.
Diberi masalah bisnis untuk dipecahkan, bukan daftar fitur untuk dikirim.
Genuine Leadership Commitment
Komitmen Kepemimpinan Nyata
Executives genuinely change how they fund and direct teams.
Eksekutif benar-benar mengubah cara mereka mendanai dan mengarahkan tim.
Legacy Operating Model vs Product Operating Model
| Dimension | Legacy / IT-Project Model | Product Operating Model |
|---|---|---|
| Funding | Per project — budget & schedule fixed upfront | Per product team — durable, follows the ownership area |
| Work direction | Roadmap is a dated list of features | Objectives based on business/customer outcomes |
| How teams work | PM writes specs, thrown over to engineering ("handoff") | Collaborative cross-discipline discovery from the start |
| Measure of success | Output — number of features shipped | Outcome — real impact on customers & business |
| Dimensi | Legacy / IT-Project Model | Product Operating Model |
|---|---|---|
| Pendanaan | Per proyek — anggaran & jadwal ditetapkan di depan | Per tim produk — durable, mengikuti area kepemilikan |
| Arahan kerja | Roadmap berisi daftar fitur bertanggal | Objective berbasis outcome bisnis/pelanggan |
| Cara kerja tim | PM menulis spek, dilempar ke engineering ("handoff") | Discovery kolaboratif lintas disiplin sejak awal |
| Ukuran sukses | Output — jumlah fitur yang berhasil dikirim | Outcome — dampak nyata ke pelanggan & bisnis |
Not just for tech startups
Bukan cuma untuk startup teknologi
Transformed's core claim: legacy companies — banks, insurers, retailers, manufacturers, decades-old institutions — can and must adopt this model to stay competitive.
Klaim inti "Transformed": perusahaan legacy — bank, asuransi, ritel, manufaktur, institusi berusia puluhan tahun — bisa dan harus mengadopsi model ini untuk tetap kompetitif.
This isn't a model exclusive to Silicon Valley unicorns. The principle is universal: a team given a real problem and the trust to find a solution will produce a better product than a team that only executes a spec.
Ini bukan model eksklusif milik unicorn Silicon Valley. Prinsipnya universal: tim yang diberi masalah nyata dan kepercayaan untuk mencari solusi, akan menghasilkan produk yang lebih baik daripada tim yang hanya mengeksekusi spek.
Banking
Perbankan
Insurance
Asuransi
Manufacturing
Industri
Retail
Ritel
Three Pillars of Transformation
Tiga Pilar Transformasi
🏛️ Leadership Commitment
Executives genuinely change how they fund & direct teams — not just say the word "empowerment."
Eksekutif benar-benar mengubah cara mendanai & mengarahkan tim — bukan sekadar mengucapkan kata "empowerment".
🧩 Team Topology
Durable, cross-functional teams organized around customer journeys or business capabilities — not temporary projects.
Tim durable, lintas-fungsi, disusun berdasarkan customer journey atau kapabilitas bisnis — bukan proyek sementara.
🛠️ Skills
PMs, designers, and engineers genuinely level up their capabilities — not just get a new title.
PM, designer, engineer benar-benar naik level kapabilitasnya — bukan sekadar dapat title baru.
Empowered teams need real coaching
Tim berdaya butuh coaching nyata
Empowering a team doesn't mean "hands off." It's actually the opposite — leaders need to be more involved, just in a different way.
Pemberdayaan tim tidak berarti "lepas tangan". Justru sebaliknya — leader harus lebih terlibat, dengan cara yang berbeda.
The role shifts: from directing tasks (what to build, and when) to coaching people — helping the team think more sharply, giving them a clear objective, then trusting them to find the best solution.
Pergeseran perannya: dari mengarahkan tugas (apa yang harus dibangun, kapan) menjadi melatih orang — membantu tim berpikir lebih tajam, memberi objective yang jelas, lalu mempercayakan tim menemukan solusi terbaik.
"Build feature X before the quarter ends."
"Kerjakan fitur X sebelum kuartal berakhir."
"Here's our customer's problem. What's your approach?"
"Ini masalah pelanggan kita. Bagaimana pendekatanmu?"
Changing titles without changing power
Ganti title tanpa ganti kekuasaan
The most common trap: a project manager gets rebranded as a "product manager" — but isn't given real authority over discovery and prioritization.
Jebakan paling umum: project manager di-rebranding jadi "product manager" — tapi tidak diberi otoritas nyata atas discovery dan prioritisasi.
They still receive a feature list from above, are still evaluated on execution speed, and still lack direct access to customer data or the authority to change product direction.
Mereka masih menerima daftar fitur dari atas, masih dievaluasi dari kecepatan eksekusi, masih tidak punya akses langsung ke data pelanggan atau kewenangan mengubah arah produk.
⚠️ The telltale sign⚠️ Ciri khasnya
The business card changes, the job doesn't. The team still executes specs decided by someone else — just now it's called a "product team."
Kartu nama berubah, deskripsi kerja tidak. Tim tetap menjalankan spek yang sudah diputuskan orang lain — hanya sekarang disebut "product team".
Without genuine executive sponsorship
Tanpa sponsorship eksekutif yang sungguhan
Transformation stalls when senior leadership isn't willing to change how funding and roadmap decisions get made.
Transformasi macet ketika kepemimpinan senior tidak bersedia mengubah cara keputusan pendanaan dan roadmap dibuat.
Teams can be trained, workshops can be run — but if executives still hold full control over what gets worked on, the old model keeps running behind new jargon.
Tim boleh dilatih, workshop boleh diadakan — tapi jika eksekutif tetap memegang kendali penuh atas apa yang dikerjakan, model lama tetap berjalan di balik jargon baru.
⚠️ The telltale sign⚠️ Ciri khasnya
"Roadmap review" meetings are still executives approving a feature list — not a discussion about what outcomes were achieved.
Rapat "roadmap review" tetap berupa persetujuan daftar fitur oleh direksi — bukan diskusi tentang outcome apa yang tercapai.
Trying to change everything at once
Mencoba ubah semuanya sekaligus
A big-bang reorg across the whole organization often fails — too many variables change at once, making it hard to prove what actually worked.
Big-bang reorg ke seluruh organisasi sekaligus sering gagal — terlalu banyak variabel berubah bersamaan, sulit membuktikan apa yang berhasil.
A more realistic approach: prove the model on one pilot team or area first, gather real evidence, then expand gradually based on results — not promises.
Pendekatan yang lebih realistis: buktikan model ini pada satu tim atau area pilot lebih dulu, kumpulkan bukti nyata, baru perluas secara bertahap berdasarkan hasil — bukan janji.
✔️ A better approach✔️ Pendekatan lebih baik
Small pilot → proof of results → gradual expansion. Not a mass reorganization announced in a single day.
Pilot kecil → bukti hasil → ekspansi bertahap. Bukan pengumuman reorganisasi massal dalam satu hari.
The CPO's role during transformation
Peran CPO selama transformasi
During transformation, the role of product leadership (the CPO and their organization) shifts from simply "running one product team well" to building coaching capability across the whole organization.
Selama transformasi, peran product leadership (CPO dan jajarannya) bergeser dari sekadar "menjalankan satu tim produk dengan baik" menjadi membangun kapabilitas coaching di seluruh organisasi.
Their job is to train leaders of other teams to do the same thing — give clear objectives, trust teams with discovery, and evaluate based on outcomes.
Tugasnya melatih para leader tim lain untuk bisa melakukan hal yang sama — memberi objective yang jelas, mempercayakan discovery, dan mengevaluasi berdasarkan outcome.
From: "I run my own product team well."
Dari: "Saya menjalankan tim produk saya sendiri dengan baik."
To: "I build coaching capability in every leader, so the whole organization can operate this way."
Ke: "Saya membangun kemampuan coaching di semua leader, agar seluruh organisasi bisa berjalan seperti ini."
What does "success" look like?
Seperti apa "berhasil" itu?
Durable Ownership
Kepemilikan Durable
Teams own a problem area long-term, not a temporary project.
Tim memegang area masalah dalam jangka panjang, bukan proyek sementara.
Independent Discovery
Discovery Mandiri
Teams run discovery themselves, without waiting for instructions from above.
Tim menjalankan discovery sendiri, tanpa menunggu instruksi dari atas.
Measured by Outcome
Diukur dari Outcome
Evaluated by business and customer impact, not feature count.
Evaluasi berdasarkan dampak bisnis dan pelanggan, bukan jumlah fitur.
Genuine Trust
Kepercayaan Nyata
Leadership genuinely trusts the team to determine the solution.
Leadership benar-benar mempercayai tim untuk menentukan solusi.
Transformation takes years, not one announcement
Transformasi butuh bertahun-tahun, bukan satu pengumuman
This isn't a project with a finish line — it's an ongoing shift in how decisions get made, continually refined as the organization learns.
Ini bukan proyek dengan garis akhir — melainkan perubahan berkelanjutan pada cara keputusan dibuat, yang terus disempurnakan seiring organisasi belajar.
Five Key Elements
Lima Elemen Kunci
Signs your organization is still on the legacy model
Tanda organisasi masih pakai legacy model
📋 Roadmap full of dated features
📋 Roadmap penuh fitur bertanggal
Not filled with objectives or problems to solve.
Bukan berisi objective atau masalah yang ingin dipecahkan.
⏱️ Teams measured by velocity/output
⏱️ Tim diukur dari velocity/output
Success = a lot "shipped," not its impact.
Sukses = banyak yang "selesai dikirim", bukan dampaknya.
📝 PM writes specs, not exploration
📝 PM menulis spek, bukan eksplorasi
Discovery gets skipped; the PM becomes a requirements translator.
Discovery dilewati; PM jadi penerjemah requirement.
🔺 Every decision escalates to executives
🔺 Semua keputusan naik ke eksekutif
Even small prioritization calls must escalate upward.
Prioritisasi kecil pun harus eskalasi ke level atas.
Run this with your leadership team
Jalankan bersama tim leadership Anda
The sequel to Inspired
Sekuel dari Inspired
If Inspired answers "how do great product teams work?", Transformed answers the next question: how does an entire organization change into a place where that way of working can happen?
Jika Inspired menjawab "bagaimana caranya tim produk hebat bekerja?", maka Transformed menjawab pertanyaan berikutnya: bagaimana caranya seluruh organisasi berubah menjadi tempat di mana cara kerja seperti itu bisa terjadi?
This isn't a book about product management technique — it's about organizational transformation: the structure, funding, leadership, and culture that make those techniques actually usable.
Ini bukan buku tentang teknik product management — tapi tentang transformasi organisasi: struktur, pendanaan, kepemimpinan, dan budaya yang memungkinkan teknik-teknik itu benar-benar dipakai.
Inspired: how great product teams work.
Transformed: how organizations change so those teams can exist.
Inspired: cara kerja tim produk hebat.
Transformed: cara organisasi berubah agar tim seperti itu bisa ada.
Transformation isn't about a new title — it's about who genuinely holds control over product decisions.
Transformasi bukan tentang judul baru — tapi tentang siapa yang benar-benar memegang kendali atas keputusan produk.
As long as funding, roadmaps, and evaluation still run on old IT-project logic, renaming a team to "product team" will only produce new disappointment — not better business results.
Selama pendanaan, roadmap, dan evaluasi masih berjalan dengan logika proyek IT lama, mengganti nama tim menjadi "product team" hanya akan menghasilkan kekecewaan baru — bukan hasil bisnis yang lebih baik.