The gap between AI that works for one person and AI that works for a team
Every engineer in the room has a private AI workflow that makes them faster. The team has not caught up. The org has not caught up. Individual productivity gains are real, but they are making shared context more fragmented, not less. One person's prompt library is invisible to the next. One person's agent setup assumes context that nobody else has. The question is not whether to adopt AI. It is how to make the gains portable across a team without the workflow changes killing the gains. Two practitioners at this month's event are tackling exactly this: Nirmal Jingar on embedding AI into engineering workflows at Wayfair, and Ananya Shah on the patterns for collaborative AI that work for whole teams, not just individuals.
The question from the room
Everyone on my team is using AI differently. How do I standardize without killing the thing that makes each person productive?
Collected anonymously from practitioners in the room.
A practitioner answers
Get the next Signal in your inbox
One problem. One question. One answer. Monthly, from the Boston practitioner community.
Read by AI practitioners at IBM, Amazon, Meta, Google, Nvidia, OpenAI, MIT, Harvard, and more for production learnings.
Free. No spam. Unsubscribe in one click. See past issues →