Posts

Showing posts with the label Technical leader career growth

The Observation Framework: How Leaders Get Called Visionary Without Predicting the Future

Image
Quick Bridge: Visionary leaders aren't predicting the future. They're watching the present more carefully than everyone else. The Observation Framework (watch the work, notice friction, build proof, tell the story, persist) turns normalized problems into career-advancing solutions without needing authority or a crystal ball. Visionary leadership isn't about predicting the future. It's about observing the present more carefully than everyone else. Early in my career, I won an award for being a visionary team member. The recognition came from work I did improving our localization process. Teams were spending months doing manual translation work. They went through game content line by line, identifying text that needed translation, then retrofitting it all in. It took forever. Most teams put it off until the end of projects, which made it worse. I started pitching ideas to fix it. Built a prototype. Ran the numbers on what it was costing us. I talked to my boss. Then his...

When Following the Process Means Missing the Goal: Why Engineering Leaders Need Context Over Checklists

Image
  TL;DR: In 4 minutes, you'll learn how to stop treating company processes as the goal and start giving your team the context they need to deliver business value when plans inevitably fall apart. The Problem with Process-First Leadership Reed Hastings, Netflix's co-founder, built one of the most successful tech companies by doing something counterintuitive: removing controls and leading with context instead of process . His philosophy was simple. If you give employees context about goals and constraints, they make better decisions than if you force them through rigid procedures. Most engineering and systems leaders do the opposite. They build teams around procedures. Documentation requirements. Approval chains. Sign-off processes. These become "the rules of working with my team." And when things go sideways (which they always do), those same leaders try to force the anomaly back into the existing process. I learned this the hard way during a game launch that nea...