You probably have a job like I did. Maybe you’re even an intern. Whatever. Anyway, you have some job and you’re doing whatever they’re asking of you. Some days, that’s writing some stuff. Other days, maybe it’s design and code. Regardless, you’re always doing something.
Here’s the problem. When you work at the intersection of tech and you’re doing work that nobody else around you understands, it becomes necessary to develop a shorthand for communicating with laymen.
At the risk of burying the lede, you need to start showing your work. Document what you’re doing, because nobody will ever tell you to do it at work. It’s easy to get really good at your job by simply knowing what you know, melding your processes with whatever your organization requires. It’s tempting when you’re a lone ranger to eschew with formal processes, because “people aren’t going to it anyway.”
The reason is easy. It’s the reason people laugh watching The IT Crowd or the stereotype of the cranky, know-it-all tech person exists. Having started my career as an IT guy, I knew the trope well. When I switched to the web, I was adamant about making the work accessible to people. Frankly, this applies whether your job is making artisanal french fries or doing UX. Most jobs have a language, but unlike working on your car or the plumbing getting stuck, there’s not a real need to engage in the language of the web everyday. It’s not until something breaks or needs to be fixed, that you need to start understanding what your “web person” is talking about.
Most of the people reading this on Medium somewhere probably don’t identify with this. If you’ve got some great job at some bleeding-edge startup in some semi-hip city off the continental shelf, you’re not dealing with the things ordinary people do everyday. The ones who are too busy to tweet; with bosses skeptical of social media and wondering why everything on the web takes so long to actually make.
Everyone has some kind of process. Documenting what you’re doing, even if it’s just for you, is a good way to signpost throughout your process. If you’re about to embark on an effort you’ve never performed before — a web redesign, user research, content audit — take the time to do some research about what other people have done before you get started. Do a search for other people’s frameworks, adapt them and move on. It’s tempting when you’re a lone wolf in an organization to feel like you need to know everything. There’s no one around to tell you otherwise. In fact, it probably feels like people actually do expect you to know everything because in their minds “that’s what we hired you for.”
Part of being a subject matter expert is understanding how to learn. Having a documented process, more than anything, gives you a chance to look back years later at what you did and helps you improve your methods. It took me years to realize how critical it was to document mental models and other tools that I used consistently on projects both large and small throughout my career thus far. I have some tools I used a lot, but the process of actually keeping track of my own progress came fairly late for me.
You can start today.