This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

User Experience

CDNow privacy

CDNow’s new privacy policy is simple and to the point. instead of using legalese, they have made it easy to read and understand what they plan to do with your information. One thing I especially like about their privacy policy is that if they change it, they won’t use any of the information affected by the change without asking you first.

Updates to our Privacy Policy that would affect how we treat your personal information will not apply to information collected before we made the update, unless we first obtain your consent.

That’s a big deal. It is not easy to design a system that segments information in that way.

The other interesting point behind the privacy policy is this:

Please note that because a customer information database is customarily considered a business asset, CDNOW shall have the right to transfer it in a merger or sale of some or all of its company or in an action for bankruptcy. Your information will continue to be treated in accordance with this Privacy Policy by the acquiring or merged company unless you are notified and provided an opportunity to opt of any changes.

Now besides the typo here (it should say "opt out of") this is good. If the company is bought, the will make it a condition of the sale that the new company has to adhere to this privacy policy. If the new company doesn’t want to, they have to give you the chance to remove your information from their customer database.

Amazon got in trouble over this last September. They changed their privacy policy to say that your personal information, shopping history, friend’s names and addresses, and all other information they have from you is their business asset and they can sell it if they want, no strings attached.

Recently Written

Your OKR Cascade is Breaking Your Strategy
Aug 1: Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here's what works better than the waterfall approach.
Your Prioritization Problem Is a Strategy Problem
Jul 23: Most teams struggle with prioritization because they're trying to optimize for everything at once. The real problem isn't having too many options—it's not having a clear strategy to choose between them. Without strategy, every decision feels equally important. With strategy, most decisions become obvious.
Behind schedule
Jul 21: Your team is 6 weeks late and still missing features. The solution isn't working harder—it's accepting that your deadlines were fake all along. Ship what you have. Cut ruthlessly. Stop letting "one more day" turn into one more month.
VC’s Future Lies In Building Winners
Jun 21: AI and megafunds are about to kill the traditional venture model, forcing smaller VCs to stop hunting for hidden gems and start rolling up their sleeves to fix broken companies instead.
Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.

Older...

What I'm Reading