Week 36 Day 1: Stop Operating and Start Designing

Operating feels productive. You are making decisions, solving problems, unblocking people, reviewing work. Your calendar is full and your inbox is active. You are needed. Designing feels unproductive. You are thinking about how the team is structured, how information flows, how decisions get made, how quality is maintained. Nobody is waiting for your answer. Nothing is on fire. But the designing work determines whether the operating work scales or collapses.

Here is the diagnostic for whether you are operating or designing. Look at your calendar for the past two weeks. Categorize every meeting and work block into one of two categories. Operating: meetings where you are making decisions about specific work items, reviewing deliverables, triaging issues, attending standup, approving requests, or personally unblocking someone. Designing: meetings or work blocks where you are thinking about team structure, process improvement, capability gaps, cross-team coordination models, hiring strategy, or organizational design. Most first-time and second-time leaders discover that 85-95% of their time is operating and 5-15% is designing. This ratio explains why the team's problems persist -- the leader is too busy operating within the current system to redesign the system. The operating trap is seductive because operating provides immediate feedback. You made a decision and someone was unblocked. You reviewed a deliverable and it shipped. You triaged an issue and it was resolved. Each action produces a visible result. Designing provides delayed feedback. You restructured the team's intake process and three months later the team is less chaotic. You invested in a capacity planning framework and six months later the team stops overcommitting. The results are real but invisible in the moment. The target ratio depends on your level. An individual contributor operates 100% of the time. A team lead should operate 70% and design 30%. A director should operate 40% and design 60%. A VP should operate 20% and design 80%. If your ratio does not match your level, you are working at the wrong altitude. The fix is not to stop operating immediately -- the team depends on your operational involvement in the short term. The fix is to invest design time into reducing the team's dependence on your operational involvement. Each system you build reclaims operating time that you can reinvest into design time. It is a flywheel.

The operating-to-designing transition maps to what Katz (1974) identified as the shift from 'technical skill' (doing the work) to 'conceptual skill' (understanding the organization as a system) as leaders advance. His research found that effective executives spent 70-80% of their cognitive effort on conceptual and systemic thinking, while ineffective executives remained anchored in technical and operational thinking regardless of their organizational level. The 85-95% operating ratio for new leaders is documented by Hill (2003) in 'Becoming a Manager,' which found that new managers spent an average of 90% of their time in operational activities during their first two years, primarily because their identity, confidence, and feedback systems were still anchored in individual contribution rather than systemic design. The altitude metaphor -- different ratios at different levels -- is formalized by Jaques (1989) in 'Requisite Organization,' which identifies seven 'strata' of organizational work, each requiring a longer time horizon and more abstract thinking. Jaques found that leaders who operated at a stratum below their organizational level (a director doing team-lead work) created a 'compression' effect that reduced the organization's effective capacity by forcing their subordinates to operate below their own level. The flywheel dynamic -- design time reducing operating dependence, freeing more design time -- is an instance of what Senge (1990) calls a 'reinforcing loop,' which produces exponential improvement when the initial investment threshold is crossed.