Documentation and training stay in Ryan org - development work does not belong there

Situation

Ryan Smith raised that the breadth of what his org produces has outgrown the label customer engineering and asked what Peter sees the function as. Peter separated the container from the placement. On placement he gave a clear two-sided answer: documentation and training legitimately sit with Ryan org and he likes them there, and development work does not belong in that org. Gauntlet was the worked example - Peter thanked Ryan for building it, said that in a perfect world it lived under Justin and should have been built by Justin org, and said explicitly that he does not want the fact that Ryan built it to reshape Ryan world so that more of that happens. He also said forward-deployed engineering will likely grow to dwarf customer support in Ryan purview, and that the title would be VP of Engineering with owned scope explained separately - both of which he treated as secondary to the placement rule.

Reasoning

Capability created under duress should not become a permanent charter. An org absorbing orphan work when there is no better home is fine and Peter said so about documentation and training; an org becoming an attractor for a category that belongs elsewhere is not. The distinction is between work that has nowhere else to go and work that has a rightful owner who did not pick it up. Peter was deliberately indifferent to the naming question - is that customer engineering? fine, whatever - because the label is not what determines where work accretes.

Additional Context

Ryan had been told by Brian Dawson that the volume coming out of his org was impressive, and came to the 1:1 unsure what to call the function. Peter had already slotted Ryan for a VP title under the leadership-level collapse decided on 8/24. Ryan separately flagged he is going to try building an agentic team to automate the maintenance burden his org has accumulated.

Observed Evidence

Direct quotes from the 1:1. Peter confirmed and sharpened the scope in review: this is about training staying and docs staying, and dev not being right in Ryan org.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis