Domain Knowledge: What You Need – Or Don’t Need – To Know: We have a burgeoning Information Architecture practice here at Blend, and there’s a problem I’ve always struggled with: where is the dividing line between (1) what I know about IA, and (2) what I know about [insert client’s business here]?
We did an IA project for a nursing organization last year. I was struck by the fact that while I knew a lot about IA, I didn’t know anything about nursing. And, as a freelance IA, you’re probably never going to know as much about the client’s business as they do.
I told my IA guy, Corey, to figure out what this means. He did so, and wrote a blog post about it.
Imagine: you’ve just pulled in a big project for Major Academic Ornithology Organization (MAOO). The organization has big plans for standardizing its academic papers and providing a richer experience for its members, all while providing a lasting impact on modern ornithological study. It’s a big deal – they want to pay you lots of money, in REAL DOLLARS, for an overall content strategy plan.
You assume you should bone up on your ornithology. But how much do you need to learn?