Agile Kata is "a good fit for knowledge work teams working in the Complicated-to-Complex and Complex quadrants"? It almost explicitly *excludes* the business and includes no documented requirements or definitions of done, just a high-level Team Strategy Map and Product or Outcome Roadmap?

HAHAHAHAHAHAHAHAHAHAHAHAHAHAHA!!!!

Well, bless your heart. Best of luck, but I predict this will much more often than not lead directly to the chaos quadrant.

Where is "the problem" -- the purported focus of the Technical Solution Meeting and UI/UX Meeting -- written down? And from whom is the problem received?

To what standard are teams to be held accountable, and how is progress to be objectively measured without written requirements?

Back in the '90s there was an acronym, WHISKEY, which stood for "Why the Hell Isn't Somebody Koding Everything Yet". This chaotic "that's not the way *I* understood it" hellscape is where Agile Kata is likely to lead.

This is complete nonsense.