» Rather than focusing on engineering team productivity, examine the causes of their low / negative value work
» When asked for development estimates, ask why they need the information and what they’ll do with the answer
» Different development tasks need varying amounts of user story detail
» Treat your developers with the same thoughtfulness as your users
» The best moment to teach a user to use a new feature is when it is valuable for them
» Uncompleted tasks stick in a person’s memory, completed tasks are more easily forgotten
» Provide a safe, controlled environment to help users experiment and learn a new skill
» Developers and managers often have conflicting views of what constitutes value in software
» Software engineers should ideally understand both what they are building and why
» Unforeseen edge cases can cause headaches at roll-out, but provide valuable lessons
“Hi Jock, I’m currently applying for loads of product manager jobs. I’ve received an offer from a sales-led company where the Product team reports in to Sales. Should I take the job?”
» Create space for your engineering team, understand the ebbs and flows of work, and help them to avoid burn-out
» Work to understand the technical complexities facing the engineering team
» Engineers typically focus on a small number of large tasks
» Product and engineering overlap: clarify who does what
