Graham McNicoll

I've watched design teams spend months on an interface that looked great, and was based on research, and yet moved zero metrics when it shipped. Their response was to deny the data, and want to not A/B test things anymore. Wrong direction. Ego can run into conflict with data, and this can be hard for teams to deal with. They may want to protect their ego, at the expense of the product or business goals. The reframe that actually helps: what you're shipping isn't a finished product. It's a materialized hypothesis. It's one possible design against a hypothesis that could be valid, even if the experiment failed. A losing experiment is data you didn't have before. It's a great opportunity to learn more about what your users want. Your job is to learn fast. The teams that compound learnings fastest are the ones who will win in the long term. Want to talk about building that kind of culture? DM me.

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