Need someone to lead product management at your software company? I build high-craft software and the teams that build it. I'm looking for my next opportunity. Check out my resume and get in touch.

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

Business & Strategy

Other uses for your content

Freshness Warning
This blog post is over 21 years old. It's possible that the information you read below isn't current and the links no longer work.

I went to a company’s Web site today to get their address. I’ve got an appointment with the company next week and I wanted to put their address in my calendar. The company’s Web site uses white text on a dark background, so when I copied the address and pasted it into Outlook, I couldn’t see it. It pasted into Outlook as white text.

Now you could argue that this is an Outlook problem. And it is. Outlook should be smart enough to realize that pasting white text on a white background is silly and correct the color for you. But since Outlook and other applications have this problem, you need to take that into consideration when putting together your Web site.

When you put information on your Web site, you need to remember that the text you write might be used in ways that you didn’t think of. Potential clients, customers, and partners might copy and paste any text you have on the site into another document. You need to test your content in alternate environments.

Another common problem is companies that set their text as a graphic or in Flash. I’ve seen countless companies that place their phone number in a big graphic banner at the top of each page. That makes it impossible to copy and paste the phone number into a contact manager. It also introduces accessibility problems. Customers might be trying to look up your phone number from a text-only web browser on a mobile phone.

It’s impossible to account for all the ways that someone might try and access and use your information. You’ll never test for them all. The thing to remember is that every non-standard thing you do will increase the odds that someone’s going to have a problem.

Recently Written

Building the Next Big Thing: A Framework for Your Second Product
Nov 19: You need a first product sooner than you think. Here's a framework for helping you identify a winner.
A Framework for Scaling product teams
Oct 9: The people, processes, and systems that make up a product organization change radically as you go through the stages of a company. This framework will guide that scaling.
My Networked Webcam Setup
Sep 25: A writeup of my network-powered conference call camera setup.
Roadmap Outcomes, not Features
Sep 4: Drive success by roadmapping the outcomes you'll create instead of the features you'll deliver.
Different roadmaps for different folks
Sep 2: The key to effective roadmapping? Different views for different needs.
Micromanaging and competence
Jul 2: Providing feedback or instruction can be seen as micromanagement unless you provide context.
My productivity operating system
Jun 24: A framework for super-charging productivity on the things that matter.
Great product managers own the outcomes
May 14: Being a product manager means never having to say, "that's not my job."

Older...

What I'm Reading