Frank - How are you so productive?

The post treats productivity as the value created by work relative to the time, effort, and tool costs involved. It argues for choosing high-impact, low-effort tasks, maintaining momentum, and using a set of habits and techniques to keep work moving while adapting to change.

Fichamento

#

• Productivitity is defined in terms of value created versus inputs such as work time and tool costs, and the author prefers measuring output by value rather than merged pull requests or closed tickets.
• The text splits productivity into effectiveness and efficiency, where effectiveness means doing the right things and efficiency means doing things right.
• Prioritization should consider both impact and effort, with an impact-effort matrix used to pick quick wins first and avoid waste.
• Long-term productivity depends on building momentum, which the author compares to a snowball that grows through accumulated knowledge and skill and through continued task completion.
• To maintain momentum, the text recommends increasing your “mass” through learning and relationships, planning ahead to avoid blockers, and continuing to push work forward without losing balance.
• The Agile principles highlighted are continuous delivery of value, welcoming change, simplicity, technical excellence, and regular reflection and adaptation.
• Kaizen is presented as continuous improvement through small incremental changes, with attention to process, waste reduction, and measurement.
• The author applies Kaizen by reflecting briefly at the end of each day and reserving weekly time to improve workflows and tools.
• Zero-inbox is described as keeping unread messages near zero by processing messages instead of merely checking them, using the four D’s, and blocking dedicated time for email and Slack.
• The author says digital to-do lists did not work well, so they use a notebook with a daily prioritized list that is checked during the day and revised as needed.
• Time blocking and time boxing are used to plan the week and to prevent getting stuck on details, including for PR reviews, coding, messages, meetings, learning, and workouts.
• For larger tasks, the author starts with a time-boxed proof of concept and reprioritizes if the estimated effort changes.
• Deep work is said to be more productive than mixed work, but it requires the right environment and is mentally and physically exhausting, which is why the author uses Pomodoro breaks.
• The Pareto Principle is used to focus on the 20% of work that brings most value, with examples including using GenAI, avoiding over-engineering, refactoring often, and reducing toil progressively from notes to runbooks, scripts, and automation.
• Gemba walking is described as going to the place where work is actually done so a tech lead can observe bottlenecks, understand context, and stay connected to colleagues.
• Escalation is presented as important when a problem cannot be resolved at the current level, especially when it helps avoid blocking and reaches the right expertise or authority.
• The conclusion restates that productivity comes from balancing effectiveness and efficiency through prioritization, momentum, Agile principles, Kaizen, message management, time management, focus, Pareto thinking, Gemba walking, and quick escalation.