BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage News QCon San Francisco 2026: Scaling Tech by Aligning Humans

QCon San Francisco 2026: Scaling Tech by Aligning Humans

Listen to this article -  0:00

At QCon San Francisco 2026, Scott Behrens, Principal Security Engineer at Netflix, presented how staff-plus engineers can define and align a company-wide technical strategy. Drawing on Netflix's experience scaling internal AI agents, the talk argued that a strategy that brings people together can often scale impact further than any code an engineer could write alone.

Behrens explained that the work started when several product strategies, each with its own direction, began to share similar technical risks. Without a common technical strategy underneath them, teams were optimizing locally for different goals. His view was that technical strategy can complement product strategy without waiting for it, that lightweight strategies deliver faster than long technical documents, and that a clear north star does more steering than people expect.

The talk presented a playbook organized as levels in a video game. The first step is finding the right problem. Behrens suggested looking at company communications, incident trends, technical debt, conversations with other tech leads, and gaps between team charters, then deciding whether the problem is worth solving now, whether it is foundational or compounding, and whether one is the right person to lead it.

Next comes the pitch. Behrens recommended a short problem statement that explains the intent, the expected value, the problems with supporting evidence, why the work matters now, and dated next steps. He suggested leaving possible approaches open so the people who join can shape them, and testing the statement early with a few colleagues, including the likeliest dissenter.

The presentation then covered building a small tiger team focused on creating the strategy rather than executing it. Behrens highlighted the importance of mixing perspectives, choosing people comfortable with ambiguity, getting manager support, and agreeing on scope, timeline, and a clear stop condition from the start. He shared that his first meeting had far too many people and still missed key functions, and emphasized that the most important trait of a good team is making it safe to push back.

With a team in place, the next step is a north star, a short aspirational statement that gives direction and helps answer whether a piece of work moves the organization closer or farther from its goal. Behrens noted that writing a good north star is harder than it looks, and recommended drafting it with the team and pairing it with key outcomes that define what must be true.

The strategy itself, according to Behrens, is simply a set of choices. He described writing strategy bets as a choice versus another reasonable choice, naming the tradeoff explicitly, keeping each bet short, and revisiting them over time. If a bet does not feel a little uncomfortable, he said, it is probably not a real bet. Keeping only a small set of active bets helps the strategy stay focused.

The talk also emphasized communication and feedback. Behrens suggested expanding support gradually from the immediate team to managers, directors, and executives, recruiting champions across the organization, and openly showing how feedback changed the strategy. Success, he said, is when you are not in the room and people can still explain the work. He also reviewed common failure modes, such as unclear problem statements, the wrong team, vague north stars, bets that are not really bets, and strategies that nobody knows exist.

The presentation concluded by encouraging engineers to keep strategy simple, communicate it widely, use a short north star to steer decisions, and adapt the playbook to their own context. As organizations launch more initiatives in parallel, especially around AI, the ability of senior engineers to align many teams around a shared technical direction may become as valuable as the systems they build.

About the Author

Rate this Article

Adoption
Style

BT