Urgent.News

What's breaking now, across hundreds of outlets.

Tech

QCon San Francisco 2026: Scaling Tech by Aligning Humans

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. By Daniel Dominguez

At the QCon San Francisco 2026 conference, Scott Behrens, a Principal Security Engineer at Netflix, discussed how staff-plus engineers can define and align a company-wide technical strategy. Behrens argued that a strategy centered around people can often scale impact more effectively than individual engineers' code.

The discussion began when multiple product strategies, each with distinct directions, started to share similar technical risks. Without a unified technical strategy, teams were optimizing locally for different goals. Behrens posited that technical strategy can complement product strategy without waiting for it, that concise strategies prove more effective than lengthy documents, and that a clear north star exerts a stronger guiding influence than anticipated.

The talk outlined a playbook structured like levels in a video game. The initial step involved identifying the right problem to address. Behrens proposed examining company communications, incident trends, technical debt, conversations with other tech leads, and discrepancies between team charters. The problem's worthiness was assessed by determining if it should be tackled immediately, if it is foundational or compounding, and if the presenter is the appropriate leader.

Next was crafting a compelling pitch. Behrens advocated for a succinct problem statement that outlines the intent, anticipated value, supporting evidence, relevance to the present moment, and upcoming steps. He advised leaving alternative approaches open-ended to allow new team members to contribute. Early testing of the statement with colleagues, including potential critics, was also recommended.

Behrens then delved into forming a small "tiger team" dedicated to developing the strategy, rather than executing it. He stressed the importance of diverse perspectives, selecting individuals comfortable with ambiguity, securing manager support, and establishing a clear scope, timeline, and predefined exit strategy. At his first meeting, Behrens noted having too many participants and still missing crucial functions, emphasizing that the most crucial attribute of an effective team is the ability to safely challenge ideas.

With the team established, the next phase involved crafting a north star—a concise, aspirational statement that provides direction and helps assess whether a particular initiative advances or detracts from the organization's goals. Behrens highlighted the difficulty in writing a compelling north star and advised creating it collaboratively with the team, pairing it with key outcomes that define necessary conditions for success.

According to Behrens, the strategy itself is merely a collection of choices. He likened writing strategy bets to selecting one reasonable option over another, explicitly naming the tradeoff, keeping each bet brief, and regularly revisiting them.

Behrens underscored the importance of effective communication and feedback. He suggested gradually expanding support from the immediate team to managers, directors, and executives, recruiting internal champions, and openly demonstrating how feedback influences the strategy. Success, Behrens concluded, occurs when the strategy can still be comprehended by others, even when the presenter is absent.

He also addressed common pitfalls, such as unclear problem statements, selecting the wrong team, vague north stars, ill-defined bets, and strategies that remain unknown to the team. Behrens concluded by urging engineers to keep strategies simple, communicate them broadly, utilize a brief north star to guide decisions, and adapt the playbook to their specific context.

As organizations increasingly launch concurrent initiatives, particularly in AI, the ability of senior engineers to unite various teams around a shared technical vision may prove as invaluable as the systems they develop.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at infoq.com →

Report a problem with this story

More in Tech

Synology CVE-2026-120382: How to Check Your NAS (DSM 7.2 Has No Patch Yet)

If your Synology NAS runs DSM 7.2 and can be reached from the internet, CVE-2026-120382 is a CVSS 9.8 bug that needs no password and no click.

  • Synology NAS devices with DSM 7.2 vulnerable to CVE-2026-120382.
  • No patch available for DSM 7.2 as of November 2026.
  • Upgrade to DSM 7.3.2-86009-6 or higher to mitigate risk.

Flutter 3.50 is out: Material and Cupertino are deprecated - here's the migration path

Flutter 3.50 shipped on 11 November with Dart 3.14. The headline change is not a widget or a performance graph - it is a structural one: the Material and Cupertino libraries bundled with the framework…

  • Flutter 3.50 released on November 11th deprecates Material and Cupertino libraries
  • MaterialUiCompatibilityBridge aids transition for code straddling both worlds
  • Dart fix tool applies majority of migration changes, official guide available

More from Saturday 21 November →