---
title: "Comment by Ascendra Ventures on \"AI-Driven Development Is a Diagnostic for Your Organization\" | Hashnode"
description: "Treating the speedup as a diagnostic is a useful frame, because it turns a tooling debate into a question about the organization. The three placements line up n"
url: "https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52/comment/6ad976bb8dc099e1457aaab0"
---

[Discussion](https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52)

Comment [AI-Driven Development Is a Diagnostic for Your Organization](https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52)

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[Oct 22](https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52/comment/6ad976bb8dc099e1457aaab0)

Treating the speedup as a diagnostic is a useful frame, because it turns a tooling debate into a question about the organization. The three placements line up neatly: the objective before the work, context during it, verification after it.

The ASKUL part stood out most. A team told to restore optimizes differently from a team told to go past where it was, and no stage in AI-DLC can produce that sentence for you. Your suggestion to have two people write the objective separately and compare is cheap and would catch most cases where a team only thinks it agrees.

We see the same pattern at a smaller scale on client builds. When the problem and its finish line are written on a page before anything is generated, verification has something to check against, and the Spotify question about change volume becomes measurable. Without that page, review time goes into working out what was intended. Will the next part look at how LY assigns owners to the refresh triggers?

[Shota Yamazaki](https://hashnode.com/@simukappu)

[Oct 22](https://hashnode.com/posts/ai-driven-development-is-a-diagnostic-for-your-organization/6ad8710cc077907c524a2e52/comment/6ad976bb8dc099e1457aaab0#reply-6ad9bd58b3940b516ff6cfdc)

Thank you for reading it so closely. One clarification on your question. The owner and refresh trigger fields are a general recommendation for teams, not something from LY's talk, so I can't speak for how LY assigns owners. The next article I plan for this series goes further into verification. Your point about writing down the problem and its finish line before anything is generated is close to where it starts, because verification needs something written to check against.
