Arkadium runs a casual gaming platform with nearly a million daily users. The revenue model runs on display advertising. A few years ago, the team introduced a new ad unit - the Sticky Player - that increased ad revenue meaningfully. It stayed on screen as users scrolled. It was technically elegant and commercially successful.
It also quietly destroyed the user experience. Engagement metrics started to move in the wrong direction. Session length dropped. Return visits declined. The ad unit that looked like a win on the revenue line was compressing the thing that made the product valuable in the first place: the feeling of being absorbed in a game.
The product team knew this. The tension was real. More revenue from each session, fewer sessions over time. The Sticky Player was a complexity problem disguised as a monetization decision.
Simplicity is a product problem
John Maeda's book The Laws of Simplicity has been on my shelf for a long time. His core argument is that simplicity is not the absence of complexity - it is the result of decisions about what to keep and what to remove. The iPod did not succeed because it had fewer features. It succeeded because the features it had were exactly the right ones and everything else was cut.
That is harder than it sounds. Every feature that gets added has a stakeholder behind it. Every element that stays in the UI has a reason it was put there. Removing things requires conviction that the product is better without them, and that conviction is hard to maintain under pressure.
The fold problem
At HouseAccount, a home services marketplace, clarity data showed that 70 percent of users never scrolled below the fold. The onboarding flow was thorough, well-designed, and invisible to most of the people it was supposed to serve. The information that mattered was buried under information that seemed important but was not.
The fix was not a redesign. It was a prioritization decision about what the first screen needed to do. One question. One input. One action. Everything else could wait. When you are working with a user who found you through a specific job request - I need a plumber, I need a lawn service - the onboarding job is to confirm that you can help and get out of the way.
The positioning trap
At EditMe, we built a SaaS wiki platform that got PC Magazine's Editor's Choice award. The technology was real. The problem was that we were trying to position it for everyone simultaneously - individuals, small businesses, enterprises, web developers, digital marketers. The pitch tried to cover all of them.
What we actually had was a product that worked particularly well for nonprofits and small businesses that needed to document processes and share knowledge internally. When we focused there - when we simplified the story to match what the product actually did best for the people it served best - the funnel started working.
Maeda's first law is Reduce. It applies to products, to positioning, and to product strategy equally. The question is always the same: what can you remove that makes what remains more valuable?
