4 ms·
More than a dozen years in tech have taught me that roles are simply ways of expressing organizational wishes. You want someone who thinks about something as a
by remoquete 3y ago
More than a dozen years in tech have taught me that roles are simply ways of expressing organizational wishes. You want someone who thinks about something as a product? You open a PM position. You want a team lead? Here's an EM position. Job titles are elements of fiction that allow us to play that RPG called work under different angles. What you ultimately bring to work is your unique mix of talents and experience.
Some people will often break the boundaries of those roles, though, and that's ok. They have ideas and might even come up with their own job titles. An organization must be smart enough to let that people grow and thrive. That doesn't mean one cannot thrive as a PM, or do great work; it's just that an organization usually cannot invest time in deeply knowing who they're getting onboard and so offer precooked roles.
- waldothedog 3y ago[emoji reaction: 100%]; [emoji reaction: thanks]
- waldothedog 3y agoWow, I guess this was un-funny enough to warrant downvoting.
- par 3y ago> An organization must be smart enough to let that people grow and thrive. Agree 100%, but this is where I've seen a lot of organizations fail, especially large ones.
- ZephyrBlu 3y agoYes! I've really bought into this idea recently. Roles are about hiring someone to always think about things from that particular perspective. Eng are capable of being PMs, but they will never think about everything from the PM point of view, because they are primarily engineers not PMs. Something else I've realized in line with breaking the boundaries of roles is that usually, the most valuable aspects of a person's role are the responsibilities that are not explicitly defined. Hard to explain, but often people provide value in ways that are hard to describe and quantify.