Graham McNicoll

I once sat in a meeting that ran for an hour debating which shade of green to use for a button. Nobody could agree, and nobody had data to break the deadlock. At some point I realised that in the time we had been arguing, I could have built the test, run it across our user base, and had an actual answer. Instead we were going in circles because everyone in the room had an opinion and nobody had data. That is what ego-driven development looks like up close. It is not malicious. It is just what happens when a team has no mechanism for resolving disagreements other than whoever argues loudest or longest. The Google 41 shades of blue experiment is famous for a reason. The difference between the winning blue and the starting blue was reportedly worth $200M in revenue. No designer in that meeting could have told you which one it was. The users told them. Product intuition is a starting point. It is a reasonable place to generate ideas. It is a terrible place to end the conversation. Most features that get built with total confidence never move a metric. The ones that do are rarely the ones anyone predicted. That gap is not a reason to distrust your team. It is a reason to test before you commit. If your team is stuck in a subjective loop, the fastest way out is to agree on a metric and run the test. The data does not have an ego. What is the most confident your team has ever been about something that the data completely disagreed with?

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