Description

A focused course, tailored for you

Principal MTS to Architect-of-Record Playbook

How a Principal MTS publishes the reference design and lands as the credited architect on a specific workload.

The 18 percent number names the Principal MTS layer in the slide. Principals who are credited architects survive the slide. Principals who are waiting to be promoted are exactly the layer the slide is about.

$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

When the cut number circulating is roughly 18 percent of the workforce and the operating-model slide explicitly names the Principal Member of Technical Staff layer, the diagnostic is no longer abstract.

That layer is where 'individual contributor' meets 'fungible specialist' in the deck the SVP reviews. Principals who survive the slide are already operating as credited architects with a published reference design and a specific workload. Principals who are waiting to be promoted to architect are exactly the layer the slide is talking about.

The move from Principal MTS to credited architect is not a job change. It is the publication of one reference design, the maintenance of an architecture-decision-record catalogue, and the framing of one workload as your specific scope. Plus the visibility work that puts your name on the architect slide before the slide is finalised.

This playbook is that publication, that catalogue, that framing, and the 90-day execution.

What you walk away with

A published reference design for one workload that the field can cite by name.
A clean translation from 'Principal MTS' to 'Principal Architect' language the field actually uses.
A weekly architecture-decision-record artefact that other Principals adopt.
A reusable design-review template the senior director will quote.
A migration plan from 'Principal MTS' to 'credited architect on a specific workload'.
A defensible answer when the architecture-review board asks who owns the design for your workload that puts your name on it.

The 12 modules

Module 1. Reading the 18 percent slide before it lands

Workforce-mix slides with double-digit reduction numbers are built within two quarters of being announced. The diagnostic for the Principal MTS layer specifically. What the slide measures. What it ignores.

Module 2. Principal MTS vs Principal Architect: the actual difference

Both titles exist at most enterprise software vendors. The actual operating-model difference. The work each is assumed to do. The artefact each is assumed to produce. The slide reads the artefacts, not the titles.

Module 3. The reference design the field can cite

Structure of a published reference design for one workload that the field can cite by name. Components, decisions, trade-offs, the credited owner. The artefact that defines architect-level work.

Module 4. Architecture decision records and the catalogue

An architecture-decision-record catalogue is the published record of architect-level work. How to start one for a workload that does not yet have one. The format. The cadence.

Module 5. Design-review template the senior director will quote

Design reviews at enterprise vendors follow predictable formats. The template that lands cleanly in the existing design-review meetings. The format that gets adopted by other Principals.

Module 6. Naming the workload as your scope

The scope statement that puts one specific workload formally on your scope as the credited architect. The language. The framing. The conversation with your senior director.

Module 7. Weekly artefact for the architecture leadership

A weekly architecture-state artefact that lands with the architecture leadership. Format, cadence, content. Three worked examples calibrated for different enterprise workload types.

Module 8. Working with product, SRE, and other Principals

specific architecture work involves product, SRE, and other Principals. The work split. The credit-sharing pattern. The escalation rhythm.

Module 9. Architecture board presence

Architecture review boards exist at most enterprise vendors. How to be present without being demanded. The artefacts you bring. The artefacts that get you invited back.

Module 10. Migration path: Principal MTS to Principal Architect

Internal migration path between the two titles at the firm. The promotion artefact. The two reviewers who matter. The fallback if the answer is 'not this cycle'.

Module 11. External market context for Principal MTS

External market for Principal MTS and Principal Architect roles at peer firms. The CV moves, the LinkedIn moves, the interview prep specific to the Principal-architect transition. Useful regardless of whether you move externally.

Module 12. Your 90-day move to credited architect

Day-by-day plan. Reference design v1 in week one. ADR catalogue started in week two. Weekly architecture-state artefact running in week three. Scope-statement conversation with senior director in month two. credited architect 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 for a Principal MTS whose firm's operating-model slide names the Principal layer.

Modules 3 to 6 produce the artefacts (reference design, ADR catalogue, design-review template, scope statement) that credited architects all have.

Modules 7 to 9 cover the visibility cadence (weekly artefact, partnerships, architecture board).

Modules 10 to 12 cover the promotion mechanics, external context, and 90-day execution.

What you get with this course

The 12-module course delivered as text plus downloadable templates.
Templates for the reference design, the ADR catalogue, the design-review template, and the weekly architecture-state artefact.
A hand-built implementation playbook generated for your specific work (Principal MTS at an enterprise software vendor in a stated workforce-mix cycle).
Three worked examples of the reference design (calibrated for different workload types).
Scripted talking points for the scope-statement conversation with your senior director.

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

Day 1: Reference design target workload chosen; ADR catalogue scaffold drafted.

Week 1: Reference design v1 written; ADR catalogue running.

Month 1: Weekly architecture-state artefact landing with architecture leadership; scope-statement conversation with senior director scheduled; design-review template adopted in one review.

Before and after

Before

You ship Principal-MTS level technical work. The product and SRE teams know you. The reference design for your area lives in your head and in scattered design docs. There is no single document with your name on it that the field can cite. The 18 percent slide is being prepared somewhere.

After

Your reference design is the document the field cites. Your ADR catalogue is what other Principals adopt. Your weekly architecture-state artefact lands with the architecture leadership. Your scope formally includes 'credited architect on this workload'. The promotion to Principal Architect is queued.

What happens if you do not address this

Operating-model slides that name the Principal IC layer specifically are not redrawn for individuals. The slide either lists you as an architect with specific scope or it lists you as a fungible Principal in the cut number. Principals who waited for the slide to be announced before publishing their reference design get the cut-side outcome. The window is the months before the slide is finalised.

Who it is for

For Principal Members of Technical Staff, Principal Engineers, and Senior IC engineers at enterprise software vendors where the operating-model slide names the Principal IC layer specifically.

Who this is NOT for. Junior or staff-level engineers (the Principal-to-architect move does not yet apply). Engineers already on a specific architecture role. Engineers at firms not in active operating-model review.

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 the reference design and ADR catalogue. Most Principals ship the reference design v1 in week two.

Why $199 is the right number

Internal architecture training inside an enterprise vendor is generic. External architecture content (Fowler, Newman, etc.) teaches pattern not the Principal-MTS-to-credited architect move. A Principal Architect mentor would cover maybe four of these 12 modules informally over months. $199 buys the focused playbook plus the implementation document for your specific work.

FAQ

Will the architecture board actually adopt my reference design?

Module 3 is built for the format the architecture board reads. Implementation-ready, with decisions and trade-offs explicit. Worked example included.

What if my firm's architecture function is centralised in a separate team?

Module 9 covers that case. The credited architecture-on-a-workload move is compatible with a central architecture team. The work split is different but the move is possible. Worked example included.

How is this different from free architecture content from Martin Fowler or thoughtworks?

Free architecture content teaches pattern. This teaches the Principal-MTS-to-credited architect move inside an enterprise software vendor running an operating-model review. Different problem, different artefacts, populated for your specific workload.

Is the credited architect seat actually open or has someone already taken it?

Module 10 covers that diagnostic. The reading of internal signal that tells you whether the seat is open and how to read which Principal will be named if the firm decides.

What is in the implementation playbook for me specifically?

A draft reference design for one workload you currently own technically; an ADR catalogue scaffold against your real architecture decisions; a 90-day visibility plan with scripted conversations against your senior director and the architecture leadership.

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.