Graham McNicoll

The most important transition for a product team is learning how to be ruthless with ideas without making it personal. I’ve seen too many build features that we had evidence were not going to work because the team was more focused on protecting an executive's ego than improving the business. When you use experimentation and analytics to lead the way, "being wrong" stops being a failure and starts being a learning. Do you have a system for using data to test ideas before they reach your developers?

Only one snapshot so far — the engagement-over-time curve appears once the daily scrape has captured this post at least twice.