I’ve paid for Reforge five times now: Mastering Product Management, Leading a Product Strategy, Multi-Domain Strategy, Retention & Engagement, and Pricing & Monetisation. People ask me, often, whether it’s worth it. The honest answer is more interesting than yes or no.
Reforge doesn’t teach you what to do. The frameworks aren’t the value. The value is in six mental shifts that the programs gradually impose on you, mostly through case work and peer pressure in the cohort. Once those shifts have landed, the frameworks become almost redundant — but you can’t skip the work that gets them to land.
Here are the six shifts, in the order they typically happen.
1. From features to systems
Before Reforge, my unit of thinking was the feature. A roadmap was a stack of features ordered by priority. After Mastering, the unit of thinking is the system: a set of inputs, mechanisms, and outputs that produce some compounding outcome.
Concretely: instead of “ship the referral feature,” the question becomes “what referral system creates the feedback loop we want, and what is the smallest version of it I can ship to test the loop?”
This shift sounds semantic. It isn’t. Once you start designing for systems, you stop shipping isolated features and start shipping loops. The roadmap looks completely different. So does the team.
2. From PMF to retention
I used to think product-market fit was binary. You either had it or you didn’t. Retention & Engagement reframed it for me as a spectrum measured in cohort curves.
A flat retention curve at 25% means you have product-market fit for a real but limited audience. A flat curve at 60% means you have it for a much larger one. The product is the same — the market changed.
The mental shift: stop asking “do we have PMF?” Start asking “for whom, and at what curve height?” That’s the question that has actionable answers.
3. From shipping to outcomes
This one sounds like an LinkedIn-PM cliché until it actually happens. Pre-Reforge, I measured velocity in shipped tickets. Post-Reforge, I measure it in cohort movement.
The practical consequence: I will hold a feature for three weeks if we don’t have a clean way to measure whether it moved the outcome. That sounds slow. It’s actually faster, because the alternative is shipping ten things that don’t move the outcome and then doing the analytics work anyway, in a panic, three months later.
4. From owning to enabling
Leading a Product Strategy was the program that broke the I-must-have-the-best-idea reflex. The Senior PM’s job is not to be the smartest person in the room about every decision. It is to design the conditions under which the team makes good decisions without you.
Concretely: instead of writing the spec, write the strategy doc that makes the spec writeable by anyone on the team. Instead of choosing the option, frame the trade-off cleanly enough that whoever owns the call can make it on their own.
This is the shift that moves you from “a good PM” to “a leader of PMs”, and it’s the one Reforge forces in a way no other resource I’ve found does.
5. From product to growth-integrated
Multi-Domain Strategy hit me last year, and it was the most uncomfortable program of the five. It dissolves the wall between “the product” and “the growth motion.” They’re the same surface area. Your pricing page is part of the product. Your onboarding email is part of the product. Your sales motion shapes what you build.
After this program, I stopped accepting org-chart boundaries as product boundaries. The activation flow at Kkiapay involves product, marketing, ops, and risk. Any one of those teams shipping in isolation produces a slightly worse product. Designing the integrated motion is the work.
6. From frameworks to first principles
This is the meta-shift. After enough Reforge work, you stop reaching for a specific framework and start asking the underlying question every framework was a different attempt to answer: what is actually happening with my user, and what is the smallest intervention that would change it?
That’s the punchline. The frameworks are scaffolding. The scaffolding lets you build the muscle. Once the muscle is built, you don’t need most of the scaffolding anymore.
What Reforge doesn’t teach you
For honesty, three things you don’t get:
- Politics. Reforge assumes a relatively healthy org. Real organisations have power, fear, and history. Reforge won’t prepare you for those.
- Emerging-market context. The case work is overwhelmingly North American B2B SaaS. If you’re building for West Africa, mobile-first, low-trust environments, you have to do significant translation yourself.
- Execution. Reforge is strategic. It will not help you ship faster. The hands move, but the muscles in the fingers come from elsewhere.
Worth the money?
For me, five times: yes — but with a caveat.
The cost of Reforge is real. It is more time than money. The programs are eight to ten weeks of weekly cohort work, and you only get the value if you do the case work seriously. If you treat it as a video library, you’re wasting both your money and your time. If you treat it as a peer cohort with assignments, the return is among the best educational investments I’ve made.
Recommendation: pick one program. Do the work seriously. See if the first mental shift lands. If it does, do another. If it doesn’t, the framework wasn’t the issue — your job context wasn’t ripe for the shift, and another program won’t fix that.