Why AI Makes Work Faster but Teams Slower

AI can make individual tasks faster while leaving the organization with the same old coordination problems, or even making them worse.

Sergei Sorokin, CEO and co founder of Highlight, joins The Tech Trek to discuss why faster output does not automatically mean better work. Teams can generate documents, code, notes, and analysis faster, then spend the time they saved reshaping that output, moving information between tools, and figuring out what matters.

The bigger problem, Sergei argues, is often not access to information or model intelligence. It is context. AI needs to understand what matters to a specific person, team, and moment rather than simply searching across everything available.

The conversation also covers proactive AI assistants, privacy and security, team specific customization, and why trust will shape how quickly people allow AI to act on their behalf.

Key Takeaways

• Faster task completion does not eliminate the coordination tax between people and tools.

• The challenge is increasingly signal versus noise. AI needs to understand which information matters now.

• AI that adapts to individual teams could help companies preserve what makes their work distinct rather than producing increasingly similar output.

• Adoption will depend on trust. Drafts, approvals, undo options, and clear boundaries can help people become comfortable giving AI more control.

Key Moments

02:09 Why faster AI output can still create more work across teams

05:02 The coordination tax that existed before AI and why AI can amplify it

08:19 Why chat alone may not be the right starting point for workplace AI

13:58 How AI could adapt to teams rather than forcing teams to adapt to software

18:16 Why human behavior and trust will determine AI adoption

22:05 Why greater agent autonomy may create a demand for more user control

One Line That Stuck

“It’s not an intelligence gap. It’s a context gap.”

Follow The Tech Trek for more conversations about AI, engineering, product, data, and how technical teams are changing.