Skip to main content
Image coming soon

Enterprise Architect's Productised-Pattern Playbook

$199.00
Adding to cart… The item has been added

A focused course, tailored for you

Enterprise Architect's Productised-Pattern Playbook

How an enterprise architect at a services firm authors a pattern the firm sells repeatedly when delivery shifts to productisation.

When the firm shifts toward productised delivery, enterprise architects without an authored pattern read as advisory cost. Architects with a pattern read as sellable IP.

$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

IT services firms shifting toward productised delivery reorganise the architecture function in the same operating-model cycle. Enterprise architecture has historically been priced as advisory hours; the new model prices it as productised IP.

The EAs who survive own an authored architectural pattern the firm sells. A productised reference architecture. A methodology document the partner channel quotes. EAs who continue producing bespoke advisory work without authored IP are read as advisory cost the operating-model review can compress.

The course covers the pattern, the reference architecture, the methodology, and the 90-day path to productised-pattern framing. Plus a hand-built implementation playbook against your real architecture work.

What you walk away with

  • An authored architectural pattern in the firm's catalogue.
  • A productised reference architecture customers implement directly.
  • A methodology document the partner channel quotes.
  • A clean translation from advisory EA to author of productised pattern.
  • A defensible answer when the productisation review asks which IP your seat owns.
  • A 90-day plan from advisory architect to productised-pattern owner.

The 12 modules

Module 1. Reading the productisation shift for EA-level implications
Productisation reorganises the EA function. The diagnostic for the EA layer.
Module 2. Advisory EA vs productised-pattern owner
Two structurally different framings. The artefacts ownership requires.
Module 3. Your authored architectural pattern
Identify one pattern you've shipped and frame it as an authored pattern the firm catalogues.
Module 4. Productised reference architecture
Implementation-ready reference customers can deploy directly. The artefact that turns pattern into productised IP.
Module 5. Methodology document for the partner channel
Methodology the partner channel quotes verbatim. Worked examples.
Module 6. Working with capture, BD, and the partner channel
Productised patterns sell through capture, BD, and partners. The collaboration pattern.
Module 7. Cross-pattern leverage
Architectural patterns compound across engagements. The structure that strengthens productised-pattern positioning.
Module 8. Customer references attached to the pattern
First customer implementation becomes the reference. The reference-shaping conversation.
Module 9. Open-source contributions and the pattern connection
OSS contributions strengthen pattern positioning when they connect to productised IP.
Module 10. Scope statement: EA vs Architecture Practice Lead
Two overlapping seats. The scope statement that puts you in the practice-lead track.
Module 11. Promotion mechanics inside IT services architecture
Internal path.
Module 12. Your 90-day move to productised-pattern framing
Day-by-day plan.

How this addresses your situation

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

Modules 1 and 2 cover the diagnostic for an EA at an IT services firm in productisation.
Modules 3 to 5 produce the three artefacts (pattern, reference architecture, methodology) every productised-pattern owner has.
Modules 6 to 9 cover the capture cadence, cross-pattern leverage, customer references, and OSS connection.
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 architectural pattern, the productised reference architecture, and the methodology document.
  • A hand-built implementation playbook generated for your specific seat (EA at an IT services firm in productisation).
  • Three worked examples of productised patterns (calibrated for different EA practice profiles).
  • Scripted talking points for the capture conversation about productised-pattern framing.

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

Day 1: Pattern target chosen; reference-architecture scaffold drafted.

Week 1: Pattern v1 written; reference architecture v1 drafted.

Month 1: Methodology document in front of partner channel; pattern-owner conversation scheduled.

Before and after

Before

You ship EA advisory work. Engagements land. The productisation shift is being discussed. There is no productised pattern with your byline in the firm's catalogue. The Architecture Practice Lead conversation has not started.

After

Your architectural pattern is in the firm's catalogue. The productised reference architecture is what customers implement. The methodology document is what the partner channel quotes. The Architecture Practice Lead conversation is scheduled.

What happens if you do not address this

Productisation reshapes the EA function within one or two operating-model cycles. EAs without an authored productised pattern get the advisory-EA compression. The window is the weeks before the next operating-model review.

Who it is for

For Enterprise Architects, Senior Solution Architects, and Architecture Practice Leads at IT services firms moving toward productised delivery.

Who this is NOT for. EAs at product companies (productisation is already done). Junior architects still building reference designs. EAs at firms with no productisation shift.

How it arrives

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

Time investment. Roughly 12 hours of reading and 15 to 20 hours producing your real artefacts.

Why $199 is the right number

Internal EA training is general. External architecture content covers technique not the productisation move at services firms. A senior practice lead mentor would cover maybe four of these 12 modules informally. $199 buys the focused playbook plus the implementation document for your real EA scope.

FAQ

Will the partner channel actually quote my methodology?
Module 5 is built around the format partner channels adopt. Specific, defensible, designed for resale.
What if my firm has not formally announced productisation?
Module 1 covers that case. The move applies pre-announcement.
Why pay for this instead of reading free architecture content?
Free content covers technique. This covers the productisation move at EA level at IT services firms.
Is the Architecture Practice Lead seat actually open?
Module 10 covers that diagnostic.
What is in the implementation playbook for me specifically?
A draft productised pattern against your real EA work; a draft reference architecture; a 90-day visibility plan with conversations against the partner channel and senior architects.

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.