Your Title Is Doing Half Your Job
She was one of the best product managers I'd worked with. Every sprint had a clean backlog. Every stakeholder got a weekly status update. Her Jira board was immaculate. When something slipped, she caught it within hours, re-sequenced the work, and sent an updated status before anyone had to ask.
Her product was dying. Customer churn had climbed for three consecutive quarters. The two largest accounts had started evaluating competitors. The roadmap was a list of feature requests from the loudest internal stakeholders, sequenced by sprint capacity, pointed at nothing in particular. When I asked her where the product was headed in twelve months, she paused, then pulled up the roadmap. "It's all in here," she said. It wasn't. What was in there was a backlog: sequenced work with no destination. No picture of the future, no articulation of why these features and not others.
Her response to the churn was to work harder at what she was already doing: tighter sprint planning, more stakeholder check-ins, a new status dashboard. She doubled down on the management function because that's what she knew how to do, and because every signal around her confirmed that's what her job was. Her title said "Product Manager." So she managed.
The anchor
Job titles create identity. They anchor your behavior to one function. The other function atrophies. Once you carry a title with "Manager" in it, your brain builds a model of what that person does: plans, organizes, tracks, reports, allocates, controls. The management function becomes the job. The leadership function starts to feel like someone else's responsibility. Maybe the VP's. Maybe the CEO's.
This isn't laziness. It's structural. The title is the first thing you learn about your job, and it shapes everything you assume the job requires. People titled "Manager" default to planning and controlling. People titled "Lead" default to vision and inspiration. Neither is doing their full job.
The anchor pulls both ways. I've watched engineering leads spend their weeks evangelizing technical vision to anyone who would listen while their teams had no reliable delivery cadence, no resource plan, and no way to track whether anything was on schedule. Their title said "Lead." So they led. The planning and controlling sat undone.
What the title hides
A job title is a label for a bundle of functions. It names one function at most. The job requires all of them.
Take that Product Manager title and unbundle it. Product strategy is a leadership function: setting direction, spotting patterns in customer data, articulating where the product needs to go. Roadmap planning is management: sequencing work, setting milestones, allocating resources. Then there's stakeholder alignment, which falls on the leadership side: building shared understanding so engineering, sales, and support pull together. And backlog maintenance is management again: tracking commitments, monitoring progress, adjusting when reality shifts.
Four activities. Two belong to the management function, two to the leadership function. The title names one. The PM who performs only the titled function is doing half the job by design. And the half she neglects isn't optional: without product strategy and stakeholder alignment, the managed backlog marches efficiently toward irrelevance.
This function-bundling pattern repeats everywhere. A "Scrum Master" bundles Scrum mechanics with teaching the organization to redesign how it works. An "Engineering Director" bundles resource allocation with technical vision. Look at any title in your organization and try to unbundle it. You will find both functions inside, usually unmarked.
The two functions have names. Kotter called them complementary systems of action: management copes with complexity (planning, organizing, controlling), leadership copes with change (setting direction, aligning people, motivating). Both needed at every level, not just the top. Mintzberg went further: he observed what managers actually do with their time and found ten distinct roles. Leadership was one of ten. The title "manager" bundles all ten into a single word and pretends that word describes the work.
Why nobody notices
The title doesn't just anchor your self-perception. It gets reinforced by every system around you.
Performance reviews evaluate what the title names. A "Project Manager" gets reviewed on delivery: was it on time, on budget, within scope? The leadership functions bundled into that same job go unmeasured. Nobody asks whether you aligned stakeholders, motivated a demoralized team through a migration, or set direction when requirements were ambiguous. That's not what the title advertises. Promotions reward mastery of the titled function. Peers expect the titled behavior: when a manager starts talking about vision and strategic direction, someone in the room is thinking "that's above your pay grade."
The untitled function atrophies because nothing in the system asks for it, measures it, or rewards it. The person holding the title may never realize they've stopped performing half their role, because every signal they receive confirms that the half they are performing is the whole job.
Consider what happens over time. A new engineering manager starts the role doing some of both: organizing the team's work and setting direction for the technical architecture. But the quarterly review only asks about delivery velocity, incident response time, and headcount planning. After two review cycles, the manager learns what counts. The direction-setting doesn't get criticized; it simply gets no response. It becomes invisible labor. By year two, the manager has unconsciously dropped it. The team has execution without direction, and everyone wonders why they feel busy but purposeless.
Nobody made a decision to drop the leadership function. The title, the review template, and the promotion criteria made that decision collectively, without anyone noticing. Deming had a name for this: 94% of outcomes are produced by the system, not the individual. The title, the review template, and the promotion criteria are the system. The person's behavior is the output.
The immaculate Jira board
Back to the product manager with the clean backlog and the dying product. Four activities bundled into her title. The title named one function. The review template measured that function. The promotion criteria rewarded it. She performed it brilliantly.
The other function, the one that would have told her the roadmap was a list of features pointed at nothing, sat undone. Not because she lacked the skill. Because nothing in the system ever asked for it.
The same pattern operates in every titled role. Scrum Master. Engineering Director. VP of Engineering. Team Lead. The question isn't whether you're "a manager" or "a leader." That turns a job design question into an identity question. Which functions does your role actually need right now, and which ones are you leaving unfulfilled because your title didn't name them?