I recently had to redesign my business card and decided to take a step back and think about the different functions it serves at different times. What resulted was my new mullet cards: business in the front, party in the back.
A business card can be much more than just a means to contact you at a later time.
It’s a way to connect with people on a personal level
At networking events I notice that people often jump to the address when handed a business card in order to strike up a conversation about people or places they know near there. There’s a good chance we have a lot more in common than that so I threw several work and personal interests in a sort of thin word cloud. Maybe they’re an avid cyclist, maybe they’ve just started coworking, or maybe they want to blow off this networking event and go get a good beer.
Who the hell was this and why do I have their card?
If I don’t process (I use CardMunch) the cards I’ve collected at an event with 24 hrs (which I usually do) I often can’t place a person by their name or company alone if I didn’t have more than a brief conversation with them. My interests might help someone recall who handed them the card, but a face will almost certainly do the trick. Realtors usually have a headshot on their cards, why shouldn’t I?
Use QR codes wisely
QR codes are meant to ease entry and access for mobile devices. Often people put all of their contact info in one QR code in something like a vCard format, which can work, but when you try to put all of your information in a single code it can greatly affect the ability of QR readers recognize it, especially in bad lighting. Even if the vCard does get captured it most often gets neatly tucked away in their address book, never to be viewed again.
I chose instead to go with two simple codes; one that is the URL for my About Me page, and one that is my Google Voice number. If I’m telling someone how cool Untappd is or discussing cycling routes they can quickly snap the About Me QR code I just handed them and get right to my Untappd or RunKeeper profiles from there. If weeks later they find my card and decide they want to chat they can snap the Call Me code which is only the phone number so most readers will just ask for a quick confirmation then dial directly, no hunting through address books.
Don’t buck the trend too much
The front is pretty much your traditional card with basic contact info. Obviously not everyone knows what a QR code is, let alone how to read them, or is going to want to look at my ugly mug. Business in the front.
A shout out to the printers
I used MOO. I was very impressed with the ease of submitting and verifying, speed of printing and shipping, and quality of the final product. They did a fantastic job and I highly recommend them.
This was a good first pass, I’ll probably modify them a bit for the next round. Do you have any suggestions?
This one incited a bit of facepalm.
When trying to changing part of RightsPro‘s header implementation to use the
HTML BASE tag the element seemed to be ignored completely and resource references were still relative to the page URL. The tag was present, correct, and closed, but having no affect.
It turns out the
BASE tag must appear ‘before any element that refers to an external source’ but MyFaces Tomahawk adds any script references needed immediately after the opening
HEAD tag, rendering the
BASE tag useless.
I don’t have time to modify the Tomahawk source at the moment for a proper fix but did submit a bug.
As a workaround you can put the BASE tag above the head element. It’s not valid HTML but most browsers will still obey it and render the page properly.
A short post, but it may save a few precious hairs from being pulled out. I’ll update if and when the bug is resolved.
We’ve chosen to go with jQuery UI as an interface framework and while the progress bars look great out of the box we wanted to add the effect of the progress growing to its value when the user visits the page to draw attention to it.
jQuery’s documentation for the UI components, including the progress bar, is straight forward.
500 is the time the animation should take in milliseconds.
This gives the desired effect of the progress bar growing to its value when the page loads rather than immediately rendering the final result.
Not earth-shattering, but a nice little trick.