Skip content
Prepare for Impact:
A Conversation on AI Readiness
Generative AI is already changing how digital products get built, but most teams aren’t set up to take meaningful advantage of this shift. Lack of structure, fragmented workflows, disconnected systems, and unclear ownership are holding back real progress.
What AI readiness really looks like across design, engineering, and product.
How leading orgs are structuring teams and systems to support AI adoption.
Where to start and what to prioritize for meaningful progress.
How to connect AI initiatives to org-wide goals and secure leadership buy-in.
Our moderators and panelists
.webp)
“We’ve been experimenting with the token structure in Knapsack, and it’s been really helpful for maintaining consistency across our design system. The way Knapsack handles tokens makes it easier to implement changes across the board.”
.webp)
“Knapsack give us prototyping in code that designers can play with. And, dropping our technical scope of maintaining the code and Storyboard is way more valuable to us than trying to maintain those things with the hope that eventually it becomes a design asset.”
.webp)
“Knapsack’s approach simply matches how we expect collaboration software to work–log in, make changes, and trust that everyone sees what you did. Members of our team trust that everything in our design system is up to date and official.”
“We’ve been experimenting with the token structure in Knapsack, and it’s been really helpful for maintaining consistency across our design system. The way Knapsack handles tokens makes it easier to implement changes across the board.”
“We’ve been experimenting with the token structure in Knapsack, and it’s been really helpful for maintaining consistency across our design system. The way Knapsack handles tokens makes it easier to implement changes across the board.”
“Knapsack give us prototyping in code that designers can play with. And, dropping our technical scope of maintaining the code and Storyboard is way more valuable to us than trying to maintain those things with the hope that eventually it becomes a design asset.”
“Knapsack’s approach simply matches how we expect collaboration software to work–log in, make changes, and trust that everyone sees what you did. Members of our team trust that everything in our design system is up to date and official.”
“We’ve been experimenting with the token structure in Knapsack, and it’s been really helpful for maintaining consistency across our design system. The way Knapsack handles tokens makes it easier to implement changes across the board.”
