Problem 1 maps almost exactly to what I keep hearing. Ask GTM teams where they're actually stuck and AI almost never comes up first. Data silos, broken CRM, no clean signal underneath. The teams getting durable traction solved the plumbing before adding anything on top.
I'd argue Problem 2 is downstream of something even bigger. Most GTM teams haven't defined success clearly even without AI. The GTME role inherits that ambiguity with a harder mandate attached.
Definitely true on "everyone needs GTME skills or face obsolescence." That said, I'd argue the operators getting the most traction have domain knowledge first, builder skills second. Without the GTM foundation underneath, the builder skills just accelerate movement toward the wrong problems.
Curious whether the data shows any patterns there — which archetypes tend to skew technical-background-first vs. domain-first?
YES! The growth engineer archetype skews very deeply technical. The CODE axes on the spider maps is created by an average of a score that was given to each role on how necessary coding skills are for the role. The data is also here is curious on running your own analyses: https://www.notion.so/0ac758ea76474561b7880564132b0455
Problem 1 maps almost exactly to what I keep hearing. Ask GTM teams where they're actually stuck and AI almost never comes up first. Data silos, broken CRM, no clean signal underneath. The teams getting durable traction solved the plumbing before adding anything on top.
I'd argue Problem 2 is downstream of something even bigger. Most GTM teams haven't defined success clearly even without AI. The GTME role inherits that ambiguity with a harder mandate attached.
Definitely true on "everyone needs GTME skills or face obsolescence." That said, I'd argue the operators getting the most traction have domain knowledge first, builder skills second. Without the GTM foundation underneath, the builder skills just accelerate movement toward the wrong problems.
Curious whether the data shows any patterns there — which archetypes tend to skew technical-background-first vs. domain-first?
YES! The growth engineer archetype skews very deeply technical. The CODE axes on the spider maps is created by an average of a score that was given to each role on how necessary coding skills are for the role. The data is also here is curious on running your own analyses: https://www.notion.so/0ac758ea76474561b7880564132b0455
Amazing and comprehensive! I feel like GTME just clicked for me for the first time.