The anatomy of an AI-native org
ajeygore.in
The anatomy of an AI-native org
1–10 of 43 posts
Re: The anatomy of an AI-native org
#2The why and what of any business capability is also a translation. From market needs and signals to requirements and features.
Re: The anatomy of an AI-native org
#3> the cost of executing on a bad why just dropped to nearly zero
Ah ok, wait until Anthropic sends you the bill.
Re: The anatomy of an AI-native org
#4This completely chimes with my own thoughts on this. In my mind a lot of AI adoption has been about AI Efficiency” - ICs using AI to do what they’ve always done with less effort but no actual change to the org chart. Whereas I think we need to think about “AI Effectiveness” - using AI more smartly to better communicate and coordinate what we are doing, and transforming the org structure and ways of working towards “AI Native” - the North Star that a fresh competitor startup would execute when starting out with AI as a given.
Re: The anatomy of an AI-native org
#5The why and what of any business capability is also a translation. From market needs and signals to requirements and features.
The „how“ too. I’m not sure I really understand the point they are getting at. The act of translation isn’t passive, there is a lot of decision making that comes with it. If we could delegate it cleanly to LLMs, and they would reliably „just translate“ I’m pretty sure I wouldn’t have any problem with that technology. But that’s not how things happen, instead you give a goal, and the system will make you believe everything is done the way you want. Until you actually verify and notice it took quite a lot of decisions that don’t align with your actual goal.
Re: The anatomy of an AI-native org
#6Im starting to think that these days the easiest way to detect frontier model influencer content designed to push a stock boosting narrative and real content is the simple presence of one word: "slop".
It matches my other experiences with the PR industry - they'd often have blanket bans on the usage of certain phrases, terms or references to "uncomfortable" events.
I'm pretty sure this goes for bots on social media too. Indirect references to slop (particularly where it is due to a skill issue) - fine. Just Don't Mention The Word.
Re: The anatomy of an AI-native org
#7> the how people who survive are the ones who can still operate at the deepest layer when something genuinely hard breaks.
How do you think the How people learn how to How at the deepest layer when something genuinely hard breaks?
Re: The anatomy of an AI-native org
#8I don't get the second graphic, can someone explain it to me in simpler terms?
Re: The anatomy of an AI-native org
#9> The work that’s left is more interesting and more valuable than the work that’s leaving.
I'm not sure I agree with that. Many (or most) of the software engineers I know find the heavy reliance on AI coding agents/assistants pretty soul-sucking and uninteresting. I feel the same, and I'm looking for some kind of middle ground. For example, I will only use agents when doing so would not deprive me of learning and discovery.
Re: The anatomy of an AI-native org
#10> the how people who survive are the ones who can still operate at the deepest layer when something genuinely hard breaks. How do you think the How people learn how to How at the deepest layer when something genuinely hard breaks?
This comment highlights the cultish naivete so much