bookmark_borderCultural Appropriation and Invitation

Culture is a fundamental facet of identity. We all have culture(s) we identify with. But what counts as cultural appropriation is nuanced. Most of the time — but not all — adopting food is not appropriation. Most of the time — but not all — adopting ritual is. Whether or not adopting practices around clothing, hair, body decoration, home and environmental decorations are appropriation is impossible to predict in the abstract.

One nuance is that appropriation depends on who you are and your relationship to the locally dominant culture. In particular, adopting common practices of the dominant culture is often not considered appropriation — in fact, it may be considered a measure of that culture’s dominance. For example, most Christians in the United States don’t object to secular choirs singing Christmas hymns. Translate this same example to a non-dominant culture’s religious holidays, and the situation becomes much more ambiguous.

What makes the difference? A problematic explanation might be that because a locally dominant culture is aligned with the dominant power structures, that culture is less deserving of respect. In this perspective, the culture of, e.g., white Christian Americans in inherently less valuable than that of other cultures. This perspective is problematic and wrong.

In my perspective, a better model is to think of cultural practices as being subject to a social immune system. A dominant culture has the ability to defend itself. If a cultural marker is used inappropriately, there are plenty of members of around to object, and they generally will have ways to be heard. The social immune system is well tuned toward violations of the norms of a dominant culture. This leads to a situation where people can generally assume that what they see is what they get with regards to adopting the cultural practices of a locally dominant culture.

On the other hand, when markers of a non-dominant culture are used, there may not be people with the right background to say whether or not it is appropriate. Or they may object but not have the power or safety to make themselves heard. Thus, when we see a practice being adopted from a locally non-dominant culture, we can’t just assume that it’s okay. It might be problematic. It might be fine. When faced with this uncertainty, we should tread with caution. The social immune system isn’t tuned for these situations.

This isn’t an argument for static, isolated cultures. Cultures evolve over time, and practices can join or leave the locally dominant culture over time. Fashion and food, in particular, are areas of frequent cultural blending. Just as a physical immune system can learn to recognize new things as acceptable or unacceptable, the social immune system can move from “don’t know” to providing reliable feedback that a practice is or not okay to adopt.

One way this evolution happens is through invitation. Cultures are not monoliths and no single person (or group) can authoritatively speak for a culture. Still, as a rule of thumb, if a member of a culture invites you to participate in their practices or gives permission to your usage of a practice, then it’s probably not appropriation. So don’t avoid learning about and participating in practices that may not be a part of your culture. Don’t give into the fear that you might mess up. Instead, keep listening, keep asking, and let the invitations of others help you navigate the way.

(A lot more could be said about this. Invitation is a nuanced topic. For example, an invitation to participate in a particular event can be taken as permission to participate at that time but not necessarily as permission to duplicate the practice on your own. However, a more general invitation, such as selling a cookbook, is a pretty good indicator that you can duplicate the practice on your own.)

bookmark_borderCreating a Career Narrative

If it’s been awhile since you’ve updated your resume, it can be hard to know where to start. Today, I want to share the process that helped me convert 15 years at Google into a narrative which showed the progression of my career.

Even if you’ve been at the same company for years, you and your career evolved over time. Your goal is to figure out how to represent that as a story arc with defined beats. The right slicing for me was to structure my career by team. Your right slicing might be by role/level, location, or something else.

Whatever slice you choose, the goal is to represent your career in a way that is targeted toward your career goal. Tell the story of the sort of contributor you want to be.

Start with memory. Make your career journey live again. Go back — maybe even back to your school days. How did you end up the places you did? Include the bare facts — “started this team on this date and did these projects” — but also remember the things that add texture: who were the people you worked with? What did you like about them? Dislike? What were some inspiring accomplishments or frustrating challenges? Take the time to remember the fun things too — like the time 4 of us from my team distributed 60 inflatable Portal turrets around the office.

The purpose of this exercise is twofold: first, it will help you recall the bare facts that will make up your narrative. Second, it will bring your career back to life so that when you talk about it in interviews it’s clear that you’re talking from real experience, not memorized talking points.

Once you’ve spent some time walking down memory lane, capture key events. Include official transitions such as changing teams, changing roles, or getting promoted. Also include points of personal significance such as being chosen to run a significant project. For each point, write down information that captures why this milestone is important to you and your role in it. What did you do? What did this milestone mean for your career progression? Then capture why it was important to the company you worked for. This second part is where the data that resume advice stresses come in. As best as you can recall, what did you make better? Why? By how much? How many people and teams did you work with?

This is the raw data. Now it’s time to put it into a narrative. What that narrative looks like will depend on the role you are targeting. Do you want to apply for a role as a highly technical individual contributor? Look for points that emphasize your technical contribution and impact. Do you want to tell a story of someone who gets things done? Focus on data that shows an “after” that is significantly better for users or the company than the “before”. Looking to emphasize your leadership skills? Find the points in your narrative that show how you grew and impacted people and teams? Capture the points and supporting detail that support your desired narrative.

Now you are ready to write the actual resume. Follow the standard resume writing advice including things like removing company specific jargon, including keywords, being quantitative, etc. Be sure to run it by someone in your industry but who has no idea about the internals of the teams or companies you’ve worked for so they can make sure it makes sense without that context.

No resume can guarantee an interview, but by being intentional about how you think about your career in the context of the role you want to have, you can make sure that your resume is the best representation of how where you’ve been connects to where you want to go.