1 min lesson
Every pillar produces an artifact
Use "Every pillar produces an artifact" to explain each part and the role it plays.
Step 1 of 2
Every pillar produces an artifactwhat "done" looks like
Pillars are abstractions. What a customer remembers is the document you left behind. Tie each pillar to a deliverable you could describe in detail under questioning.
- Adoption
- A rollout plan and an enablement curriculum tailored to this org's stack and SDLC.
- Expansion
- An account map showing the next teams to activate and the trigger for each.
- Partnership
- An architecture / governance review doc the platform and security teams can sign off on.
- Outcomes
- A QBR or impact deck quantifying the change, aimed at the economic buyer.
- Feedback loop
- A structured feedback brief - prioritized, with evidence - that Product can act on.
When asked "what would your first quarter look like?", answer in artifacts, not adjectives: "a rollout plan for account A, an enablement curriculum the platform team co-owns and an impact readout I can put in front of their VP of Eng." Concrete deliverables prove you understand the job's output, not just its vibe.
The product-feedback pillar is easy to forget and Cursor cares about it a lot. You are the bridge between strategic customers and Product/Engineering. "I'd just file tickets" is weak; "I'd bring prioritized, evidence-backed briefs so the roadmap reflects what elite eng orgs actually hit" is the bar.