Is AI compounding in your product and engineering organization, or stuck as activity?

Eight questions on whether the team is moving real AI work that the business will feel, or running tools and pilots that look like progress but do not compound. The lightweight front-end to the AI Trajectory Read. About five minutes.

// SCOPE

This diagnostic is about AI inside your product and engineering organization. The tools, workflows, and operating system your team uses to build software. It is not about AI features in the product you sell to customers. That is a separate question with a separate answer. This diagnostic is also not about AI in GTM, finance, or back-office automation. Those are different conversations.

Best answered by the CEO, ideally with input from your product and engineering leaders. If you do not know the answer to a question, that is itself the answer. Choose "I don't know" and we will surface what that means in your result. You will see one of five results and the conditions worth attention.

0 of 8 answered

// LEFT EDGE
NOT POSITIONED
Conditions not set up. AI compounds the wrong way.
//
NOT YET SET UP
Significant readiness gaps. Local wins, no system gain.
//
PARTIALLY SET UP
Parts of the system in place. The gaps are the agenda.
// RIGHT EDGE
SET UP
Conditions for AI to compound are in place.
// AND WHERE YOUR LINE IS HEADING

Two trajectories chart: rewired companies see substantial productivity gain by Q4 (McKinsey 2025), not-rewired companies stay flat at the company level (Faros AI / DORA 2025)

Illustrative shape. Sources: McKinsey 2025 (rewired) and Faros AI / DORA 2025 (not rewired).

Conditions worth attention