People Over Process

Processes are supposed to support people, not people support processes. A process should be documented in one document or checklist or directory or wiki or website that everyone has access to. Everyone should have a copy readily available. It should not be outlined in emails or sporadically over several documents across different locations. Always review the process and remove friction. Try to minimize steps when possible, centralize the information, anoint clear responsibilities, build in safety nets, empower developer to make decisions, let it grow as the team grows. Automate the process as much as you can, make reports people can use, make everyone’s progress visible. For some certain teams, there is diminishing returns for adding more processes.

Related posts:

  1. Remote Debug Your Thinking Process
  2. Knowledge Transfer
  3. Retweet January 2010
  4. When Saying Yes Means Seppuku
  5. Scan Your Ports
  6. Hire Smart, Not Seniority


Leave a Reply