Description

A focused course, tailored for you

Platform Product IC's Workload-Authorship Playbook

How a product IC at a collaboration-software platform authors a workload narrative when the AI-cycle cut redraws product benches.

When the AI-cycle cut redraws product benches, the product ICs without workload authorship read as fungible. ICs with it stay attached to the workload.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

Collaboration-software platforms that publicly announce AI-cycle cuts redraw product benches in the same operating-model cycle. Product ICs who continue running 'product work' without a documented workload they personally authored are read by the deck as fungible. ICs whose workload reads as authored stay attached to the workload.

The ICs who survive own a documented workload narrative under their byline, a roadmap finance and engineering both quote, and a weekly workload-state artefact the engineering director adopts.

The course covers the three artefacts and the 90-day path to workload-authorship framing. Plus a hand-built implementation playbook against your real product workload.

What you walk away with

A documented workload narrative under your byline.
A roadmap finance and engineering both quote.
A weekly workload-state artefact the engineering director adopts.
A clean translation from generic product IC to workload-authorship.
A defensible answer when the AI-cycle review asks which workload your work is associated with.
A 90-day plan to land the framing.

The 12 modules

Module 1. Reading the AI-cycle cut for product implications

AI-cycle cuts at collaboration-software platforms redistribute product benches in the same operating-model cycle. The diagnostic for the product IC layer specifically. What 'AI-cycle cut' means at product IC level inside the platform.

Module 2. Generic product IC vs workload authorship

Two structurally different framings of the same product IC seat. Generic product IC reads as fungible bench; workload-authorship reads as the seat the platform needs to keep the workload running. The three artefacts that mark the shift.

Module 3. Your workload narrative

Document one workload you currently own. The workload narrative with your byline that the engineering director reads as authoritative. Three worked examples for collaboration-software product workloads.

Module 4. Roadmap finance and engineering quote

Roadmap finance and engineering both quote. Investment, dependency, expected outcome per quarter. The roadmap that travels across functions as the standard. Worked examples calibrated for collaboration-software products.

Module 5. Weekly workload-state artefact for the engineering director

Format, cadence, content of the weekly workload-state artefact the engineering director adopts. Three worked examples for collaboration-software product workloads at different stages of AI-cycle review.

Module 6. Working with engineering, design, and customer success

Product work overlaps engineering, design, and customer success. The collaboration pattern that strengthens workload-authorship positioning rather than producing turf disputes.

Module 7. AI-cycle language translation

AI-cycle language has specific meaning at collaboration-software platforms. The translation that connects product work to AI-cycle priorities. Worked examples of three product-language translations.

Module 8. Cross-workload leverage

Reusable PM practices that strengthen workload-authorship positioning across multiple workloads. Cohort framing, retention review cadence, attribution model. The patterns that compound across the product organisation.

Module 9. Conference and external positioning

External presence at PM conferences and through writing accelerates workload-authorship positioning. The talks the firm endorses. The publication channels that strengthen the seat.

Module 10. Scope statement: product IC vs senior PM / Group PM

Two overlapping seats. The scope statement that puts you in the senior PM or Group PM track defensibly.

Module 11. Promotion mechanics inside collaboration-software platforms

Internal path inside collaboration-software platforms. The promotion artefact. The two reviewers who matter.

Module 12. Your 90-day move to workload-authorship framing

Day-by-day plan. Workload narrative v1 in week one. Roadmap drafted by week two. Weekly workload-state artefact running by week three. Engineering director conversation in month two. Senior PM conversation in month three.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

Modules 1 and 2 cover the diagnostic.

Modules 3 to 5 produce the three artefacts.

Modules 6 to 9 cover cross-function partnership, AI-cycle language, leverage, and external presence.

Modules 10 to 12 cover scope, promotion, and 90-day execution.

What you get with this course

The 12-module course delivered as text plus downloadable templates.
Templates for the workload narrative, the roadmap, and the weekly artefact.
A hand-built implementation playbook generated for your specific work.
Three worked examples of the weekly artefact.
Scripted talking points for the engineering director conversation.

What you will have in hand by Day 1, Week 1, Month 1

Day 1: Workload narrative scaffold drafted.

Week 1: Narrative v1 written; roadmap v1 drafted.

Month 1: Weekly artefact landing with engineering director; workload-authorship conversation scheduled.

Before and after

Before

You run product IC work. Roadmaps land. The AI-cycle cut is being discussed.

After

Your workload narrative is what the engineering director quotes. The roadmap is what finance and engineering both read. The weekly artefact lands above the IC level. The senior PM / Group PM conversation is scheduled.

What happens if you do not address this

AI-cycle cuts redraw product benches within one or two cycles.

Who it is for

For Product Managers, Senior PMs, and Product ICs at collaboration-software platforms facing AI-cycle workforce reviews.

Who this is NOT for. Junior PMs still building scope. Product leaders at director+ level. ICs at firms not in active workforce-mix review.

How it arrives

Text-based course via LMS, plus downloadable templates and the hand-built implementation playbook.

Time investment. Roughly 10 hours of reading and 12 to 16 hours producing your real artefacts.

Why $199 is the right number

Internal product training is general. External PM communities cover technique. A senior Group PM mentor would cover maybe four of these 12 modules informally. $199 buys the focused playbook plus the implementation document for your real workload.

FAQ

Will the engineering director actually quote my workload narrative?

Module 3 is built around the format directors quote.

What if my workload is co-owned?

Module 3 covers that case.

What is in the implementation playbook for me specifically?

A draft workload narrative; a draft roadmap; a 90-day plan with conversations against your engineering director and skip-level.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.