01. Conflict & Ego Latency
What happens the morning after two senior people clash over an API contract or product scope? Radio silence, routing messages through a 3rd person, and one of them quietly stepping back from ownership. Polite but cold distance for a few days until a manager intervenes. Zero grudge: fierce debate on the pitch, coffee in the locker room, and 2x execution on the agreed path.
02. End-to-End Ownership vs. The Handoff Trap
When a critical dependency is blocked by another team or stakeholder, what do your engineers/PMs say? “I did my part—I tagged them in Jira / sent an email last week and I’m waiting for them to reply.” They ping again on the same channel after a few days, or wait until the next sprint retro to mention it. They escalate channels within 24–48h (Async ➔ Direct Chat ➔ 5-min Call ➔ Huddle) until the loop is closed.
03. Radical Transparency vs. Toxic Politeness
How do alignment and architecture review meetings feel inside your organization? Everyone nods politely in the room, says nothing, and complains in private DMs five minutes after the meeting. Risks are raised cautiously with heavy corporate sugarcoating to avoid bruising egos. Brutal intellectual honesty in the room: broken designs and unrealistic timelines are called out directly.
04. Flow-Based Engineering vs. Meeting Tax
How does your team plan, align, and ship features week to week? Heavy Scrum ceremonies, story-point poker, daily verbal status standups, and matrix Chapter Leads. 2-week sprints with moderate meetings, but written design docs (RFCs) are rare or inconsistent. Async-first: 1-page written RFCs, automated signals instead of status meetings, and continuous flow delivery.
05. Architectural Symmetry (Frontend & Backend Parity)
How are Frontend engineers and client-side architecture treated when designing new features? Backend builds APIs in isolation and throws JSON over the wall; TLs/EMs are only picked from Backend. Frontend is consulted mid-sprint, occasionally causing late API refactoring. Equal sovereignty: no API contract or schema ships without explicit sign-off from both FE & BE leads.
06. Strategic Thinking vs. Permanent Firefighting
Look at the calendars of your Tech Leads, EMs, and PMs this week. What do they look like? 100% packed with back-to-back operational syncs and heroic last-minute firefighting. Mostly reactive execution; strategic pruning only happens once a quarter during OKR planning. Protected empty blocks every week to view the system from 20 feet up and ruthlessly kill low-impact scope.
07. Operational Depth vs. Title Inflation
How are senior titles (Staff, Principal, Director, Head) and promotions awarded in your org? Handed out casually to retain people or match resume buzzwords, without deep production battle-testing. Tied to tenure and being an 'indispensable single point of failure' in one silo. Earned strictly through systemic impact, eliminating major debt, and actively multiplying/training successors.
08. Culture of Writing vs. Hallway Agreements
Where do real product and architectural decisions happen and live? In hallway chats, private DMs, or late-night calls that evaporate by the next week. Scattered across slides and tickets, with occasional gaps between Business, Product, and Tech. Single source of written truth: open backlogs, symmetric cross-reviews, and zero shadow agreements.