Jordan & Craig - I have no questions but wanted to thank you both so much for this awesome thread. From an Ops POV its wildly helpful to read how you both are orienting in this world.
Yaaa know what, perhaps I do have a question, @craig_2 & @jordan_dalladay , in your own work, where are you struggling with AI, if at all? I think this is a piece that often gets overlooked a bit. We hear a lot about people leveraging it, learning with it, etc. but I’d love to hear if either of you struggle with any piece of it in your work?
For me, the struggles are less about using AI and more about how it integrates into real work and world. I’ll try and expand:
Context - AI can generate thoughtful outputs quickly, but it does not understand nuance. It does not grasp the history behind decisions, the dynamics in a room, or the subtle signals that shape how something will land. Translating something that is technically strong into something that feels right for a specific moment still requires judgement, care and often the allocation of more time than the cognitive processing.
Pace - The rate of change is intense. New models, new capabilities, new possibilities almost weekly. Staying current without becoming reactive takes intention. A key learning has been that the elastic in many areas is already stretched, rapid iteration if not handled carefully stretches it further.
And closely connected to that is helping others keep pace. When you spend time close to the pace of Cognitive Infrastructure, your mental model shifts quickly. Not everyone is living inside that shift every day. Bridging that gap thoughtfully, without overwhelming people, is real work.
If I was framing this, I would say capability scales fast. Understanding does not.
Coming back to this thread @craig_2 and @jordan_dalladay, great stuff. Looking at this idea of Cognitive Infrastructure to wrap my head around the ideas.
