Deep Work For Leaders
Enabling Others Flow State
What does deep work look like when you’re in a managerial rather than an execution position?
Different but equally necessary.
You may think that since you’re not executing you’re getting in the way of Engineers by working alongside them.
Nonsense.
Software Engineering is exceedingly complex, requiring deep thought and concentration to make any meaningful progress. Asking an Engineer to figure out operational things such as coordinating meetings, product requirements or understanding the “why” can be too much to handle. Here’s some concrete actions you can either facilitate or do yourself:
Detailed Product Requirements
Introductions to Key Stakeholders
A thorough discussion of the “why” behind a direction
High Fidelity Designs
Product walkthrough for new hires.
Probably sounds time consuming. It can be. But your Engineers are likely the most expensive component of your team. Having them work efficiently pays dividends. They weren’t hired for this stuff. They can figure it out on their own. But much more slowly than an expert.
Staying in the proactive quadrant of important but non-urgent tasks is the key to success in any enterprise.
Firefighting is not a strategy.
Know someone who needs technical guidance?
100% Typo Guarantee - This message was written without any AI assistance. All yours imperfectly truly. Therefore, I can virtually guarantee there’s a double word or misspelling in there somewhere. Happy Hunting!


